WpfGeometryModel3DNode vs MeshObjectNode
#3
As written in the previous post, I have tried to add support for exporting a single MeshGeometry3D that is used by many GeometryModel3D objects that would be created from InstanceData. Unfortunatelly the assimp object model allows to store only a single material with a mesh - the material is not assigned to the node but to the mesh. This means that when using assimp exported the same mesh will be saved for each GeometryModel3D.

If you want to save to some simple text base file format, then you may want to wrote your own exporter - this does only need to support your objects and therefore it may be more simple.


You can also check the source for Ab3d.PowerToys.Assimp. You may provide a way to export the ObjectNodes directly - you would need to convert them to Assimp objects.

Here is the new repo for the Ab3d.PowerToys.Assimp: https://github.com/ab4d/Ab3d.PowerToys.Assimp
Andrej Benedik
  


Messages In This Thread
RE: WpfGeometryModel3DNode vs MeshObjectNode - by abenedik - 05-08-2021, 06:40 PM

Forum Jump:


Users browsing this thread:
1 Guest(s)