Using 2014.2 fbxsdk code if you include the call to LoadPluginsDirectory it will load all the DLL files in the diectory of the exe file, not just available or needed plugins - everything!. Repeated load of FBX files will eventually lead to memory fragmentation as the DLL's loaded are never closed! There is no workaround, apart from not using the call to LoadPluginsDirectory . To test simply compile any real world executable example that loads 1 or more required DLL's for operation from its own EXE directory. Then iterate through enough loads to get the FBXSDK code to fail. This also failed in earlier SDK versions! Documentation on the behaviour of this command is not extensive. IF you get random out of memory after continous loading of files, and or fbxblob errors, , look no further. Fix this please, and also fix examples so that they call with fixed parameters to limit the danger of this command.
I waste a whole weekend in this function
such a bull**** function .
I thought some code i wrote was wrong ,untill traced this LoadPluginsDirectory.
Can't find what you're looking for? Ask the community or share your knowledge.