| Age | Commit message (Collapse) | Author |
|---|
|
Changes in UI are significant enough to justify it.
|
|
Reviewers: Severin
Maniphest Tasks: T69482
Differential Revision: https://developer.blender.org/D5671
|
|
Updates importers/exporters for the new file-browser design. They are
now reorganized into sub-panels.
Updated the Blender version requirement (won't be compatible with older
Blender versions). Left the Add-on versions untouched, will leave that
up to Authors to change.
|
|
Based on investigation and patch by Yannick (@kschoice), many thanks!
|
|
Add option 'Export Subdivision Surface' to the FBX exporter (disabled by default).
When enabled the exporter will write the **last active Catmull-Clark subdivision surface modifier**
as FBX properties instead of applying it.
Edge crease data is also written to the FBX file if 'Use Creases' is enabled in the subsurf modifier.
Reviewers: mont29
Tags: #add-ons
Differential Revision: https://developer.blender.org/D4982
|
|
Handle more gracefully the case where we cannot compute tangent space
for a mesh.
|
|
Differential Revision: https://developer.blender.org/D5240
|
|
|
|
Relative filepath having a 'absolute look' (starting with a path
separator) can lead to recursively checking for the whole root!
This is nasty, so try to avoid it by making relative paths actually
relative.
Based on D5143 (report and patch) by andreas atteneder (@atti), thanks!
|
|
Not sure when that mistake was introduced, Armature modifier is not
considered a 'real' modifier to be baked, from FBX exporter point of
view...
Reported/followup from T64994.
|
|
Classical stupid issues when trying to shorten an utf8 string to match a
given bytes length... ;)
|
|
of orig custom data layers.
Now we can get full-featured mesh with new system too.
|
|
3DSMax can produce pure white `TransparentColor` with (default, from
template) `TransparencyFactor` of 0.0... Looks like we are supposed to
use `Opacity` then... sigh...
|
|
We cannot reliably use `mesh.materials`, since those might be empty when
materials are only assigned/linked to the object...
|
|
|
|
|
|
Reviewers: sergey
Differential Revision: https://developer.blender.org/D4883
|
|
Addresses new behavior of object.to_mesh().
This is corresponding part for D4875.
Reviewers: brecht
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D4876
|
|
Mainly search-and-replace approach.
Tested the enabled-by-default export/import addons. Seems to work with
an exception of X3D which is still referencing Blender Internal material
properties.
Reviewers: brecht
Reviewed By: brecht
Differential Revision: https://developer.blender.org/D4866
|
|
Much better option than using Principled's Transmission setting.
Related to T64609.
|
|
|
|
This reverts commit 55d0ff708c617f190fd898c37f90b70a2fd6a293.
|
|
This reverts commit 9524a08a60cf570e9b0540a6ae195a269b403817.
|
|
Sequell to rB55d0ff708c617f, grrrrr....
|
|
Looks like FBX also likes to make a mess with materials' behaviors...
Many thanks to Thomas Chollet (@thomasch) for his help understanding how
Unity handles materials' alpha when importing from FBX.
Hopefully this won't break any other importer... ;)
|
|
Please update scripts when you do such changes...
|
|
Although we had no way to reproduce the issue, that fix indeed seems
needed from code logic point of view.
Investigation and patch by Pete Chown (@PeteX), thanks!
|
|
Currently all empty shape keys are not exported when exporting as FBX. The reason for this is that empty shape keys cause issues like crashing Unity. This can cause confusion because it is done without explanation.
This patch fixes this by making the shape keys technically empty while still keeping them intact and working as shape keys.
Reviewers: campbellbarton, mont29
Reviewed By: mont29
Tags: #bf_blender_2.8, #addons
Differential Revision: https://developer.blender.org/D4496
|
|
We need a way for add-ons to generate a temp render depsgraph and
evaluate it, for this to work again, with new Blender 2.8 design.
|
|
more maps.
Do not do 'smart' init of our UV/VCol data layers, this is lost
computation and can generate issues when not all items are explicitely
defined in FBX file.
|
|
This reverts commit 96a51679699c75e1a08f2d91b2b055bf6430e9d1.
My tests fail to test this properly. They key elements here are not
Blender's keyframes. I need to tackle this differently.
|
|
If all the keyframes were set to constant interpolation.
Reviewers: mont29
Differential Revision: https://developer.blender.org/D4429
|
|
Please do basic grep on whole source repo (including add-ons & co) when
removing RNA property (or any other change affecting the API)...
|
|
Blender only supports 8 UVMaps per mesh, avoid crashing addon when
trying to import more.
|
|
Usual crap with PoS of FBX... feeling bad though, that report skipped
out of my radar for too long. :|
|
|
Quiet hard to believe, but looks like that critical recursive call has
never been there... This basically broke any real-life case of 'objects
parented to bones' relationships.
Scaling issues remain though, this will be for some other time.
|
|
Looks like we need to not merge UVs from different islands into same set
of coordinates in the 'compressed' mapped storage of FBX data, seems to
be the way for that piece of crap of a wanabe format to convey islands
concept...
Gets the code even more cryptic, yay!
|
|
|
|
Identity checks should never be used with strings, it may fail based on
Python's interning logic.
|
|
'_RNA_UI' (and rna runtime properties) should not be included, these
would have been included as string properties causing errors on reimport
backport rBAe4f4053de64e (fix for T59202) from 2.8 branch
Differential Revision: https://developer.blender.org/D4068
|
|
'_RNA_UI' (and rna runtime properties) should not be included, these
would have been included as string properties causing errors on reimport
Fixes T59202
Differential Revision: https://developer.blender.org/D4068
|
|
Indirectly reported in T59162. We do not have access to render depsgraph
currently, so we need to work on `show_viewport` option of modifiers we
want to hide when generating temp export mesh, instead of `show_render`
one...
|
|
|
|
This follows naming convention agreed on in T56648.
|
|
Also extended a bit the options for batch exporting (collections give
more ways to organize your scene).
And added non-batch option to only export objects from active Collection.
'partial' support because until we can force generate depsgraph for
inactive view layers, we cannot support exporting instances (dupli
objects etc.) for batches.
TODO: move the batch logic to IO helpers, that could be another
decorator, to easily add the same feature to all exporters able to
export several objects...
|
|
|
|
|
|
|
|
Differential Revision: https://developer.blender.org/D3746
|
|
|
