Jump to content
  • Advertisement
Sign in to follow this  
Ectara

OpenGL [C] Need help with 3d Rendering Wrapper

This topic is 2677 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I have a design for a renderer wrapper that is coming along decently, but I became stuck on initialization and destruction of different renderer contexts. The wrapper functions as such:
1. Dynamically load the driver library for a particular renderer.
2. Call the init function found in the library, which fills a renderer structure with function pointers and constants.
3. Use the function pointers and constants.
4. Call the destruction function from the library.

Right now, I support OpenGL and my own software renderer, but the main problem is, OpenGL contexts usually need to be started when the window is created, while my renderer can be initialized at any point. Additionally, my renderer requires a width, height, and pixel format for the display, where my application is currently configured to use SDL for window management; this means that SDL with OpenGL decides its own pixel format, and can't be specified. Also, since OpenGL needs to be enabled in the SDL display creation function, this would make the separation of display and rendering a challenge.

Can anyone advise on this? I've been stuck for a while.

Share this post


Link to post
Share on other sites
Advertisement
Personally I'm not understanding the exact question. But what I did was make a base "Renderer" class with virtual functions that can be over written for each seperate renderer. Then just derive your seperate renderers from that. In the code call something like:

if(renderer == "ogl")
lprenderer = new OpenGLRenderer();
else if(renderer == "d3d")
lprenderer = new D3DRenderer();
else
lprenderer = new SoftwareRenderer()

Where each renderer is derived from the main Renderer class with renderer specific functions. I hope that helps or be a little more specific.

Share this post


Link to post
Share on other sites
The way I handle it is after creating the window using SDL or whatever, I ask my RendererFactory to create a renderer. All my renderers derive from an abstract interface which at minimum has a Create/Init function which you pass the window height/width and the window handle which in win32 would be the HWND (you can get this from SDL). The window handle argument is just a void* so I can pass whatever into it and the renderer can cast it to whatever it is expecting it to be. You could easily have some kind of Device or WindowParams struct which contains this info and any other generic stuff that a renderer might need to set itself up but I found the minimum to be the 3 I listed above. Having a struct like I mentioned would allow you to easily extend it though.

Share this post


Link to post
Share on other sites
@bjz
I suppose it's relevant that I'm using C89, so classes and inheritance aren't quite available. Also, that solution sort of encompasses what I'm already doing. The problems I've presented, are that each renderer requires different data, like the software renderer requiring a width, height, and pixel format, while OpenGL contexts generally have their pixel formats chosen by the window manager, and have the width and height set to the display's dimensions.

Also, the biggest problem, is that OpenGL with SDL needs to be initialized with the display creation. The software renderer needs to be initialized separately, and I was hoping to separate the rendering module and the display module.

@Shael
I suppose I could pass parameters that are ignored, but the problem is, I need to have the OpenGL context created with the SDL window. For D3D, I'm not sure.

Thank you both for the replies.

Share this post


Link to post
Share on other sites
I suppose it would be possible to initialize the renderers when the display is initialized, but that's something I was hoping to avoid, as they are separate modules. Any suggestions would be appreciated.

Share this post


Link to post
Share on other sites
[color="#1C2837"]Ectara: for Direct3D, you may can just can simply use TitaniumGL. See the downlad link in my signature.

Share this post


Link to post
Share on other sites

[color="#1c2837"]Ectara: for Direct3D, you may can just can simply use TitaniumGL. See the downlad link in my signature.


Thank you, but this doesn't help my problem. The current wrapper in place would handle Direct3D, OpenGL, my own software renderer, any others added in additional libraries. To remove that entirely, use the OpenGL API, and install an entire extra software renderer would be of no use to me. Also, TitaniumGL supports less platforms than I do.

Share this post


Link to post
Share on other sites
What other platforms do you need?

Btw you can create an opengl context any time. But you cant call opengl functions, before you fully init the context (you can manage it with tricks, but i would not do it!)

Share this post


Link to post
Share on other sites

What other platforms do you need?

Btw you can create an opengl context any time. But you cant call opengl functions, before you fully init the context (you can manage it with tricks, but i would not do it!)


Whichever platforms I decide to support. More accurately, all of the platforms that aren't eliminated for a good reason(This would run poorly on a C64).

SDL requires it to be created at the same time as the display is initialized. See the documentation:
http://sdl.beuc.net/sdl.wiki/SDL_SetVideoMode

Share this post


Link to post
Share on other sites
SDL is a crap. I suggest to use native platform initialiastions instead of it. You can get a copy for winapi/Xlib context creation at nehe tutorials. I used glut for a while, but now i throw it out becouse the unlimit numbers of never-fixed-10-year-old bugs. This also stands for SDL.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!