I think you should seperate the functionality from the data objects, similar to the way you would seperate database records from the actual database provider logic / queries. Instead, implement a renderer base class that takes the above primitives, then derive that for OpenGL / D3D. That way you could do: Renderer r = new D3DRenderer(); r.Render(myModels); Hope that helps Tris ------------------------------- Carrier Bags - 21st Century Tumbleweed.

Try it...it doesn't hurt Do your best to be the best

Have you come up with any good ideas? "I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon

Have you come up with any good ideas? "I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon

Let's say you have a List (or something else that is disposable). You will want to give your Base class a Dispose() method so that you can loop through the List and Dispose of everything manually. Basically, if your class contains unmanaged resources OR contains members that implement IDisposable, you'll want your class to implement it as well. --sorry, meant this as a reply to OP.

Thanks! I will look into it. Still, if I keep thinking about using OpenGl, anyone has more sugestions? Rui

I'm a bit late, but check out the book Practical C# Charts and Graphics by Dr. Jack Xu. Great book with some excellent 3d examples. http://authors.unicadpublish.com/~jack_xu/

As far as OpenGL is concerned, this article http://www.codeproject.com/opengl/GLBase.asp[^] might be of interest... "Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus