12-21-2016, 01:45 PM
Great! I am glad that you have solved the problem.
After your initial post I have spent some time with analyzing performance in a scenario similar that yours.
I did not find any performance problems in the code. The performance should be already very good.
But I have a few ideas on how to further improve the performance is such scenarios. I will implement that in the next version of DXEngine.
Therefore I would recommend you to use the exiting code with disconnecting Positions before changing them.
It would be possible to achieve even better performance using lower level DXEngine objects (instead of WPF's GeometryModel3D and MeshGeometry3D).
In the following hours I will try to prepare a sample on how
SimpleMesh<PositionNormalTexture> for that - I will post the sample code under this thread.
To get a good performance overview of how DXEngine is rendering the scene, I highly recommend that you try the DXEngineSnoop tool. It is installed in the Ab3d.DXEngine\Tools folder.
It is easy to use:
- First start your application so that the 3D scene that is rendered with DXEngine is shown.
- Then start DXEngineSnoop. It should show your application in the drop down list. Click Snoop button (you can also start DXEngineSnoop with -auto startup parameter to automatically snoop to your application)
- The DXEngineSnoop should attach to your application (change the title of the main window) and show diagnostics window. The diagnostics window shows rendering statistics that helps you analize the rendering times.
- Under the menu you can also start advanced performance analyzer and some other tools.
After your initial post I have spent some time with analyzing performance in a scenario similar that yours.
I did not find any performance problems in the code. The performance should be already very good.
But I have a few ideas on how to further improve the performance is such scenarios. I will implement that in the next version of DXEngine.
Therefore I would recommend you to use the exiting code with disconnecting Positions before changing them.
It would be possible to achieve even better performance using lower level DXEngine objects (instead of WPF's GeometryModel3D and MeshGeometry3D).
In the following hours I will try to prepare a sample on how
SimpleMesh<PositionNormalTexture> for that - I will post the sample code under this thread.
To get a good performance overview of how DXEngine is rendering the scene, I highly recommend that you try the DXEngineSnoop tool. It is installed in the Ab3d.DXEngine\Tools folder.
It is easy to use:
- First start your application so that the 3D scene that is rendered with DXEngine is shown.
- Then start DXEngineSnoop. It should show your application in the drop down list. Click Snoop button (you can also start DXEngineSnoop with -auto startup parameter to automatically snoop to your application)
- The DXEngineSnoop should attach to your application (change the title of the main window) and show diagnostics window. The diagnostics window shows rendering statistics that helps you analize the rendering times.
- Under the menu you can also start advanced performance analyzer and some other tools.
Andrej Benedik