05-07-2021, 11:41 AM
We have integrated Assimp to provide import/export of 3D models into our app.
- Importing via Assimp creates a Model3D. This then generates WpfGeometryModel3DNodes to display the meshes via SceneNodeFactory.CreateFromModel3D().There are also MeshObjectNodes that we can manually create to display meshes as well. These two aren’t compatible and the MeshObjectNodes cannot be exported unless they are first converted to a Model3D object (we haven’t done this yet, but it looks possible).The major difference we see is MeshObjectNode uses Vector3/StandardMaterial, whereby WpfGeometryModel3dNodes use Point3D/Media3D.Material. 1. Is performance of one better than the other, or are the any benefits to using either one?2. Is there a built in way to convert nodes?