11-04-2021, 01:42 PM
(11-03-2021, 03:16 PM)abenedik Wrote: GetClosestHitObject uses the DXEngine's hit testing. The DXEngine automatically generates OctTree structures for meshes there have more than **** (this is defined by a static ****). This hit testing works very fast even on meshes with many triangles.
But when you use EventManager3D that is defined in Ab3d.PowerToys library this uses the WPF's objects and its hit testing. This hit testing is much slower.
If you want to use the mouse events that are provided by EventManager3D please use the DXEventManager3D - see the "Ab3d.DXEngine hit testing / DXEventManager3D" sample for more info.
You are obviously absolutely correct about this, thanks. I will note I was concerned that even though the performance of the hit testing is clearly much faster with this than the PowerToys class, it seems odd that the diagnostics window was still showing my CPU usage of 25%-50% (on my 8C/16T CPU). However, testing in Process Explorer (from Microsoft SysInternals) showed this not to the be the case - CPU usage of the entire system never exceeded 8%.