X3D Export: export objects as their correct type #35

Open
opened 2024-11-07 23:40:08 +01:00 by Cedric Steiert · 2 comments
Collaborator

Currently the exporter only exports blender objects as IndexedFaceSet. This is okay for most use cases, however makes the files not really reusable by other software.

For example:

  • Text gets exported as IndexedFaceSet instead of Text, which means changes in font style or content is not possible.
  • Curves are exported as IndexedFaceSet instead of IndexedLineSet or their Specialized Geometry, which means they are not visible at default, as curves in blender have no depth and so no faces to be exported
  • Simple geo like box are exported as IndexedFaceSet, which doesn't really seem like a problem per se. I think this case would be quite hard to implement on the blender side as it would require comparison of vertex data to the original primitive...
Currently the exporter only exports blender objects as IndexedFaceSet. This is okay for most use cases, however makes the files not really reusable by other software. For example: - Text gets exported as IndexedFaceSet instead of Text, which means changes in font style or content is not possible. - Curves are exported as IndexedFaceSet instead of IndexedLineSet or their Specialized Geometry, which means they are not visible at default, as curves in blender have no depth and so no faces to be exported - Simple geo like box are exported as IndexedFaceSet, which doesn't really seem like a problem per se. I think this case would be quite hard to implement on the blender side as it would require comparison of vertex data to the original primitive...
Cedric Steiert added the
question
label 2024-11-07 23:40:08 +01:00
Author
Collaborator

@vmarchetti @yottzumm what do you guys think about this? Should we aim to try to distinguish between object types in the exporter? At least for a few selected cases like text and curves for afore mentioned reasons? Would this be unnecessary development overhead or an actual useful change?

@vmarchetti @yottzumm what do you guys think about this? Should we aim to try to distinguish between object types in the exporter? At least for a few selected cases like text and curves for afore mentioned reasons? Would this be unnecessary development overhead or an actual useful change?
Collaborator

I think this would not be a priority task, even for exporting text. It may be an interesting problem to solve for the sake of completeness, but if someone claims they need this capability for the production generation of X3D files, I'm pretty sure there's a better solution than Blender export.

I think this would not be a priority task, even for exporting text. It may be an interesting problem to solve for the sake of completeness, but if someone claims they need this capability for the production generation of X3D files, I'm pretty sure there's a better solution than Blender export.
Cedric Steiert added
enhancement
Low
and removed
question
labels 2024-11-08 16:01:01 +01:00
Sign in to join this conversation.
No description provided.