Hi,
I am doing some early beta testing and one of our native plugins is crashing when invoking FBX SDK ( specifically FbxManager::Create() )
Has there been a change of FBX version from 5.6? Anything else we should be away of on our end?
Thanks for the help!
Hi ShadowM8,
Could you please file a bug report with a minimal reproduction case for this issue and reply in here with the case #?
Thanks, bug submitted Case 913680.
After running into this in the beta I did some more extensive testing and was able to reproduce the crash in 5.6 too.
The question I have is when I allocate memory in a native plugin does the Unity MemoryManager get involved in any way? Because it appears as that’s where the crashes originate, either when FBX tries to allocate some data or when memory manager tries to reallocate some some memory a little later.
Tips on any rules/best practices that I should be aware of would be appreciated.
Hi again,
It appears that this has to do with some incompatibility with the standard FBX SDK library and the one used by unity.
Instead of linking to libfbxsdk.dylib I changed it to link against Unity’s ImportFBX.dylib (unity 5.6.1) which I saw in the stack trace. This fixes the crash!
I checked the version of FBX thats returned from ImportFBX and it is 2016.0 (libstdcpp variant).
I figured, great I will just use the 2016 libstdcpp SDK but unfortunately that also crashes, there must be some other issues.
To make matters worse, in the 2017.1 beta ImportFBX.dylib is gone, so I can’t work around the issue or check the actual FBX SDK version.
Would really appreciate some input,
Thanks!
Hi,
Could you try with FBX SDK 2016.1.2? That’s the version 2017.1 is using: Importer Improvements (2017.1) - Google Docs