Now, find the scene most 'used' by exported group elements, and use its unit settings!

Now also check modifiers stack.

When we are exporting actions or strips from NLA, and an evaluated anim leads to no anim
at all (like single-keyed actions or pure static ones), key all start and end frames.

Note this might be overkill (due to baked anim, we will key *all* transform channels),
but probably better than skipping completely those actions!

Not sure at all it will work actually, spent another couple of hours trying to make my UE4
work on VBox, with no luck so far. :/

So, blind guess.

Revision: D735

Patch by jrestemeier (Jens Restemeier).

For now, mere copy of 'main' addon...

Own mistake in previous smoothdata vs normals fix.

unsuported mat type (like nodal ones).

See T41396 for rationals (having dummy placeholder still helps e.g. with
face-assigned materials...). Thanks to piiichan (Arnaud Couturier) for raising that issue.

For some reason, Unity (and FBX SDK in general?) does not support well mixing
normals and smooth data, at least when using shapekeys.

Odd, odd, you said odd? That's odd...

Anyway, we do not really need both of those data at the same time, so for now
either write smooth or normals data, not both!

Also add support for 3DVectors as custom properties in exporter.

With some minor edits by ideasman42 (Campbell Barton) and mont29 (Bastien Montagne).

FBX IO Cleanup: add a global settings namedtuple to importer too, and rename those used by exporter.

With some minor edits by mont29 (Bastien Montagne).

We have to store and restore pbones' matrices as well when baking animations...

We have to convert them to global space on export, and back into local space on import...

Issue raised by jrestemeier (Jens Restemeier) in D607, thanks!

* Rework unit conversion system to avoid dict lookup each time, also use it in import;
* Optimize a bit by removing some double-dict-lookups;
* Add basic timing info to importer as well.

Based on patch D629 by jrestemeier (Jens Restemeier), but removed 6.1 settings, no use of that here.

Each time I think I have reach the limits of the crappyness of this "format", it manages to amaze
me again! This time, looks like SDK expects always the same values in the 'templates' (Definitions),
else it declares properties as invalid! One would have to explain me the interest/need to write
those default values in the file, up to this point...

Anyway, went over all defaults I could gather from 'official' FBX files, and replaced the few
ones I had change (because it was better suited to Blender's data). Hopefully it'll be OK now.

Thanks to FslNopper (Norbert Nopper), which helped me troubleshooting this stuff!

There is a good thing here though - it made me find how textures are linked to UVMaps
(by mere names, 'UVSet' property of texture nodes).

Based on patch/idea by jrestemeier (Jens Restemeier), many thanks!

Differential Revision: https://developer.blender.org/D601

Based on patch/idea by jrestemeier (Jens Restemeier), many thanks!

Differential Revision: https://developer.blender.org/D600

Idea from karanikk (Kostas Karanikolas).

not in sync with actual loc/rot/scale values (and hence export wrong 'rest' transform
of some objects).