The X3D exporter currently adds prefixes to each node name such as CA_ for cameras and ME_ to meshes. This is inconvenient if a downstream app needs to look for nodes with specific names, as the prefixes means the names no longer match exactly what appears in Blender. The following patch makes this behavior optional.
In addition, this patch adds options allowing the user to specify both the desired Blender and X3D coordinate systems for coordinate conversion.
Description
Description
Event Timeline
Comment Actions
Just to expand on this a bit, the original reason for the CA_ and ME_ prefixes was to avoid name collisions; while Blender does not allow objects of the same type to have the same name, objects of different types *can* have same name. The X3D exporter has since been fixed (not by me) to use bpy_extras.io_utils.unique_name() to generate the X3D DEFs, which tests for identifier collisions and generates a new name in that case.