dwmkerr.com

For those who are interested, I’m now starting development of SharpGL 2.1. SharpGL 2.1 will primarily be a release to implement features and fix bugs that users have added to the Codeplex site. The actual features and bugs that’ll be sorted are on the CodePlex site - just search for release ‘SharpGL 2.1’. This will also be the first release of SharpGL that will be published on Nuget.

SharpGL 2.0 has been released - hit the GitHub site to get it: https://github.com/dwmkerr/sharpgl Some new features: Full support for all OpenGL functions up to OpenGL 4.2 Full support for all commonly used OpenGL extensions Support for WinForms applications Support for WPF applications (without resorting to WinForms hosts) A powerful scene graph including polygons, shaders, NURBs and more Many sample applications as starting points for your own projects. Visual Studio Extension with SharpGL project templates for WPF and WinForms.

It's been a long time coming, but the first Beta of SharpGL 2.0 is finally here! The Beta is on CodePlex at: http://sharpgl.codeplex.com/releases/view/74704 This includes the binaries, example applications and full source code. Some of the more exciting features are: Full hardware acceleration OpenGL Extensions Full core functionality up to OpenGL 4.2 Native WPF Control Below is a screenshot of SharpGL in a WPF application:       And here's a link to a new CodeProject article describing how to use SharpGL in a WPF application:   http://www.

There are only a small set of the core OpenGL functions that can be imported via p/invoke - the majority of OpenGL functions are actually extension functions which are supported only on specific video cards. OpenGL offers a function called wglGetProcAddress which can return the address of a named function - but how do we deal with this in the managed world? Here's a brief description of how it's handled in SharpGL.

It took a bit of working out, but finally SharpGL can support hardware acceleration. Previously, all rendering in SharpGL was done to a DIB Section, the result of this would be blitted to the screen. Much playing around has shown that in fact this is problematic - rendering to DIB sections can never be hardware accelerated. To hardware accelerate rendering, the rendering must be to a window or a pixel buffer.

SharpGL has not been updated for a while, the original CoreProject article is at: http://www.codeproject.com/KB/openGL/sharpgl.aspx Recently I have begun work on SharpGL 2.0, with plans to address some of the issues people have had with SharpGL 1.83. In preparation there is a public accessible repository on CodePlex: http://sharpgl.codeplex.com/ check it soon, it will shortly be online. Trying to squeeze acceptible performance from SharpGL has so far been an interesting task, I have found out many interesting things on the way, I'll be posting small snippets as I work on SharpGL 2.