X-Change 3D is a plugin for Unity which allows you to export GameObjects in your scene to Obj, FBX, DAE, and DXF format.
You simply select the GameObject, even if it’s created from several imported models, and click export; that’s it, you now have an FBX created from your GameObject(s).
Features:
Support for Unity Terrain (export as OBJ or FBX)
Support for Skinned Mesh Renderers
Support for Material Color and Transparency
Support for texture locating(Applied automatically during import to 3D software)
Support for Animation Export
Support for Skinned mesh or Mesh Filter Detection(exported as MF).
Better support for SMR’S(slower but calculates bind poses and bone weights for proper location of exported SMR(s) to MF(s).
All GameObjects are now supported
1.5.5 supports Windows and Mac (tested only on Mavericks 10.9), and Batch processing to OBJ and FBX (only Batch to OBJ on Mac).
All classes (C# and C++) have been optimized in preparation of source release later down the road (needs several hours of code commenting).
Yes, X-Change does export vertex color and alpha transparency as it is set on the source GameObject(s) in inspector view.
Any more questions, don’t hesitate to ask.
Yes, this will export any GameObject. If it is a SkinnedMesh, then it will be exported as MeshFilter instead.
We have taken a hiatus on SkinnedMesh support until after Unity 5 is released, but do not yet have a date for X-Change3D v.2.0 until we can spend some time with the new SDK.
Vern,
0xc00007b is usually an issue with the .NET framework. Please try the solutions below. If this does not work, get back to me and I’ll look into it further.
Also. does this only happen with terrains to FBX? Does exporting GameObjects to FBX produce the same error? Can you export the terrain to OBJ successfully? In the X-Change3D info window at the bottom (red or green), does it produce an error or warning after you close the Windows error window?
Thank you.
Solution 1
In most cases it’s .NET framework causing issues. This can easily be fixed by re-installing the latest .NET framework
Solution 2
Download and re-import X-Change3D. It sounds simple but the data files (Compiled C++ Autodesk FBX SDK) could be corrupt. This could be caused by an import that did not complete successfully or by anti virus software.
Solution 3
Running the application as an administrator could fix this error. Right click on the Unity3D shortcut, then click on Run as Admin. Also try temporarily disabling your real time antivirus scan, if this fixes the issue, then add Bloodsucker to the Av ignore/allow list.
Solution 4
Run Windows update as it can provide application fixes and updates. Furthermore it installs missing drivers and updates the outdated ones like graphic card drivers. Windows 7 / 8 / 8.1 users need to search for “windows update”. select all important and optional updates and click on the “install updates” button.
Thank you for the rapid response. I will try these solutions and experiment. At the moment I am only exporting a Terrains. I will try other GameObjects.
Hello, an interesting feature would be able to import mesh and convert it to editable terrain in Unity, is there any way to do this? If not, here is a nice feature to be implemented.
The plugin did not work, said miss mscrt110.dll or something similar name, fixed it by installing the MS Visual Redist 2013.
I could not export to .dae, is impossible, while exports .obj instantly, I let the computer try to export to .dae for about 20 minutes, I had to go in task manager and end the program.
I can not build the .exe of my game, in the Unity console says it can not import some X-Change DLLs, which is the cause of the blockage.
Unfortunately, the update will remove Mac support as I don’t have a way to debug it and the added Mac support causes issues with the Windows portion. It will probably end up as a Windows version and a zipped Mac version inside the project folder. ETA: 6-10 days for Windows and 2-3 weeks for Mac.
It has only been tested on early Mavericks 10.1 I believe, but that was way back when Unity was 4.1-ish.