Process .object files in the Blender addon #7
Description
For whatever reason, Diesel doesn't store all the information in the .model file that it could. In particular, .object files contain annotations as to the role of an object, which can hint as to how things should be configured in Blender land and which attributes to retain when writing out a .model. Therefore, io_scene_diesel should process them.
Known information:
<animation_group>: Objects that share a logical animation. Unsure what Diesel does if an object belongs to two.<body>: Physics objects. Set wireframe display, disregard attributes other than position.<decal_mesh>: Invisible, disregard UV and vertex colour?<graphic_group>and friends: Collections, possibly.
Not sure yet how to do LOD grouping, or graphics. Quite likely some sort of "role" property should be added to objects:
- Graphic (options: enabled, shadowcaster, lod)
- Physics
- Decal
With appropriate options enabled when each is selected, although collision type could mirror Blender's own selection.
Collections may need roles, on account of things coming in groups.
LOD stuff looks like
<graphics>
<lod_object name="lod_group_name">
<object name="g_lod0" max_distance="5000" lod="0" enabled="true" />
<object name="g_lod1" max_distance="10000" lod="1" enabled="true" />
<object name="g_lod2" lod="2" enabled="true" />
</lod_object>
</graphics> So that'll be a collection for the lod_object and more object properties. Maybe mirror the object props in the collections UI... if we had one.