> why use OpenGL if you are relying on WPF? Why not use DirectX directly?
I've not yet decided to do this. I'm just in an exploration phase, trying out some libraries and technologies for a scientific visualisation project.
The next lib I will try is SlimDX, which seems to be a proper substitute for managed DX, which is not going to be further developed.
Posted Thursday, 21 May, 2009 - 10:56 by the Fiddler
Sounds interesting.
OpenGL has the advantage of inherent support for quad buffer stereo and cross-platform compatibility, both of which can be important for scientific visualizations (and that's why I went with OpenTK for my last project, a VR platform driven by a BCI).
On the other hand, DX has a cleaner API and its drivers tend to be more stable. Depending on the kind of visualization, this can be a good tradeoff.
Comments
Re: OpentTK/WPF integration
You have to use a WindowsFormsHost to host a
GLControl.There are no plans to provide native WPF support, because:
Edit: why use OpenGL if you are relying on WPF? Why not use DirectX directly?
Re: OpentTK/WPF integration
> why use OpenGL if you are relying on WPF? Why not use DirectX directly?
I've not yet decided to do this. I'm just in an exploration phase, trying out some libraries and technologies for a scientific visualisation project.
The next lib I will try is SlimDX, which seems to be a proper substitute for managed DX, which is not going to be further developed.
Re: OpentTK/WPF integration
Sounds interesting.
OpenGL has the advantage of inherent support for quad buffer stereo and cross-platform compatibility, both of which can be important for scientific visualizations (and that's why I went with OpenTK for my last project, a VR platform driven by a BCI).
On the other hand, DX has a cleaner API and its drivers tend to be more stable. Depending on the kind of visualization, this can be a good tradeoff.