Migrate to HelixToolKit WPF to HelixToolKit SharpDX

Anonymous 4 years ago • updated by anonymous 1 year ago 5
This discussion was imported from CodePlex

cedrelo wrote at 2014-02-07 08:50:


First really thanks for your work!!!!

I use HelixToolKit WPF to develop an WPF application of robot trajectory, i use import of .stl, camera, viewport3D, LineVisual3Ds.

It's works really great, but when we load large data and a lots of stl, the perfomance fall on
some computer.

Do you think it's possible to migrate the projet to the fork HelixToolKit SharpDX to improve perfomance ?
Does the fork has all the functionnality of the orginal project ?
It is possible to use HelixToolKit SharpDX inside a WPF application ?


I'm considering the same, so any information or advice would be really appreciated.

To start with your last question; yes, it is possible to use the SharpDX-versjon of the HelixToolkit inside a WPF-application. I am currently using it, and it works really good. The performance is of course than the main fork, but by using instancing, grouping of objects with the same color etc. I think the performance in the main fork is adequate (unless you have a really large model).

Per now the SharpDX-fork does not have the same functionality as the main fork, but most of the main functionality is implemented, tested and working OK. I do not have a list that compares the two forks, but look at the methods and you will find out what you are missing. Please let us know so we can prioritize the functionality that we want.

I think it is good too have the two projects as seperate forks, since the functionality is different. The main fork is also more stable. What that will happen over time is tho another question :)

Przem and Øystein knows far more about this than I do, but I hope that my answare has given you some clues about the SharpDX-fork.

Best regards
(Developer at the SharpDX-fork)
Thanks for the answer Isdas,

I haven't tested the SharpDX version in depth and its capabilities. I think the main problem of the standard edition of Helix Toolkit (at least for me) is that it renders extremely slow large number of ScreenSpaceVisual (i.e LinesVisual3D). I was amazed how fast SharpDX handled that.

I may missed it, but as far as I know there is not BackMaterial in SharpDX, and I can't afford changing my application in so many places, duplicating the geometry, inverting the normals, just for the correct visualization. If a BackMaterial is not set, the model seems transparent. I don't know if there is a special reason behind this, but for me, that would be one of the key points.

Other key functionality, for me, would be the ability of project from/to 2D/3D and being able to handle the standard mouse events (there is an example of this, so I assume it's already implemented).

Again, thank you very much.
Dear cedrelo,

I would also like to apply a trajectory using HelixToolkit.Wpf to navigate into a 3D model. But since I am a new in programming, could you please share with me how I could apply that? Could you please share the lines of code that have to do with trajectory?

Thank you in advance!