Blender > UDK Batch Export Helper
polycounter lvl 5
I've been working on a script that should help with batch exporting to UDK
I think you will like it for:
http://www.youtube.com/watch?v=f8EJ5SGAsWI&feature=youtu.be
You can find the script HERE (Github)
I searched the internet trying to find a script like this, closest I found was Marko Jakić's MAYA>UDK solution . Most of the time the search returned threads on forums.epicgames.com/forums discussing why people must export static meshes individually, and arrange everything in UDK. Which is obviously flawed thinking.
I think you will like it for:
- exporting set pieces with one click
- placement of static mesh instances
http://www.youtube.com/watch?v=f8EJ5SGAsWI&feature=youtu.be
You can find the script HERE (Github)
I searched the internet trying to find a script like this, closest I found was Marko Jakić's MAYA>UDK solution . Most of the time the search returned threads on forums.epicgames.com/forums discussing why people must export static meshes individually, and arrange everything in UDK. Which is obviously flawed thinking.
Replies
This kind of thinking is pretty common but if you think about it you can make this really easy on yourself even if you exporting individual pieces. UDK places the object's control handle at the origin based in whatever 3d program you used. So if you built a complex object in Maya for example, and then exported each piece out, as long as you didn't move it, you can rebuild the same complex mesh because all the control points will match up.
The t3d export is a must.
I suggest you tu post it over blender artist forum and UDN to gain visibility. This script is gold.
I noticed in the code that TD_SCALE = 50 does that mean the Blender to UDK unit conversion is by a factor of 50? Could you let the factor be set by the user?
At the moment I'm working on modifying the script to interface with Unity.
I will look into adding a scale input box. I chose a scale of 50 because Blender and utgame has a 1:50 scale ratio, and I wanted each blender unit to be 1m.
Until I get around to adding the UI element, you can set the TD_SCALE to whatever you wish, and hit the "Run Script" button again. That should work as a temporary solution.
Also modified the script to replace "." characters in group names to "_" so there will be no .fbx import errors.
I will look into changing how users interact with groups, since the instances are based on the distance to the world origin. The offsets help when exporting to UDK, but are not helpful when building things out of instances in blender.
The new changes are on the github page.
Thanks