03-27-2026, 10:33 AM
I have sent you the source code for the ReaderObj so you can tweak it to your needs - getting one Model3D at a time.
Also note that it would save a lot of memory if you would not create the WPF 3D objects (that are then converted into DXEngine objects behind the scene) but create the DXEngine objects directly. This would save the conversion time, and also because DXEngine objects use float Vector3 structs instead of double-based Point3D, this would take much less memory.
See the DXEngineAdvanced/ManuallyCreatedSceneNodes.xaml.cs sample on how to manually create Ab3d.DirectX.GeometryMesh and Ab3d.DirectX.MeshObjectNode objects.
To improve the performance, I would also recommend using .Net 10 because each version improved the performance just by upgrading to a newer version.
Another option is to use Ab4d.SharpEngine instead of Ab3d.PowerToys / Ab3d.DXEngine. This may also improve the performance.
Also note that it would save a lot of memory if you would not create the WPF 3D objects (that are then converted into DXEngine objects behind the scene) but create the DXEngine objects directly. This would save the conversion time, and also because DXEngine objects use float Vector3 structs instead of double-based Point3D, this would take much less memory.
See the DXEngineAdvanced/ManuallyCreatedSceneNodes.xaml.cs sample on how to manually create Ab3d.DirectX.GeometryMesh and Ab3d.DirectX.MeshObjectNode objects.
To improve the performance, I would also recommend using .Net 10 because each version improved the performance just by upgrading to a newer version.
Another option is to use Ab4d.SharpEngine instead of Ab3d.PowerToys / Ab3d.DXEngine. This may also improve the performance.
Andrej Benedik