Sign in to follow this  
Oranda

OpenGL Texture errors in multiple wxGLCanvas windows

Recommended Posts

Oranda    122
Hi all. I'm currently building a quick utility to help me layout some scenes, and I have two window classes, both of which extend wxGLCanvas. Each class has its own event handler for painting. If I run the utility with only one or the other windows enabled, they work fine, but if I try to enable both of them at the same time, each texture in the scene will only work for one or the other window. i.e, if I can render a quad in one window with a certain texture, I will only get a null texture in the window. I don't think there are any race conditions present, since I am not multithreading and there is no randomness to which render target gets which textures. Both render windows get the texture ids from the same class, so I don't think that should be a problem either. FYI, in my test case, after adding a texture to the scene, exactly one quad with that texture applied to it is added to CRenderWindow, so I should see the exact same textures in both CRenderWindow and CTextureWindow (only in different locations, obviously :)). Here is the offending code, stripped down to just the OpenGL setup specific parts: This class just renders a bunch of quads and guidlines into a window
void CRenderWindow::OnPaint(wxPaintEvent& event)
{
  wxPaintDC dc(this);
  this->SetCurrent();
  
  //resize the viewport
  int width;
  int height;
  
  //--snip-- build the viewport
  
  glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
  glDisable(GL_CULL_FACE);
  glEnable(GL_DEPTH_TEST);
  
  //--snip-- build the matrices
 
  //--snip-- render a bunch of quads with textures. textures have ids
  //         which are contained in scene->GetTexture(i)->getTextureID()
  //         as done in CTextureWindow::OnPaint below
  
  //--snip -- render some other non-texture related stuff
	
  glFinish();
  this->SwapBuffers();
  event.Skip();
}


And this function renders the contains of a texture list window:
void CTextureWindow::OnPaint(wxPaintEvent& event)
{
  
  wxPaintDC dc(this);
  this->SetCurrent();
  
  //--snip-- build the viewport
  
  glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
  glDisable(GL_CULL_FACE);
  glDisable(GL_DEPTH_TEST);
  
  //--snip-- build the matrices
  
  //render all of the textures to the window 
  int numTextures = scene->getNumTextures();
  for(int i = 0; i < numTextures; i++)
  {
    //to clamp x to every n units: x - x % n
    width = (width - width % 100);
    
    int x = (i * 100) % (width);
    int y = (i * 100) / (width) * 100;
    
    CTexture* texture = scene->getTexture(i);
    
    if(texture != null) 
      glBindTexture(GL_TEXTURE_2D, texture->getTextureID());
    else
      glBindTexture(GL_TEXTURE_2D, 0);
  
    //--snip-- render the actual quad
  }
  
  glFinish();
  this->SwapBuffers();

  event.Skip();


Any help/suggestions would be very much appreciated!

Share this post


Link to post
Share on other sites
vx7johmi    139
For every wxGLCanvas you create you get a separate OpenGL context. When you create/upload a texture in OpenGL it is only accessible/usable in the context where you created it, UNLESS you call [wglShareLists]. So, let your main context (your main wxGLCanvas) generate the textures and then pass the rendering context to any other wxGLCanvas you use and call [wglShareLists].

I'm using this for my GL-based texture-palette:

void TextureGLCanvas::OnPaint(wxPaintEvent& event)
{
//Must always be here.
wxPaintDC dc(this);

//Do we need this every time..?
if(!GetContext())
return;

//Only need to do this once...
if(!_hasCalledShareLists)
{
//wglShareLists(HGLRC,HGLRC)
wglShareLists(Core::getInstance()->getMainOGLContext(),
m_glContext->m_glContext);

_hasCalledShareLists = true;
}

//Set current OpenGL context
SetCurrent();

//Does clear, render and swap...
Render();
}



/Mike

Share this post


Link to post
Share on other sites
Oranda    122
Thanks, that makes a lot more sense now. I'm running Linux on my development box, though, so wglShareLists won't work for me (since it's part of the microsoft-specific OGL API).

There appears to a special constructor that allows me to share a context from within the wxWindows containers. I added it to my texture window, but it doesn't appear to be working. Here is the modified constructor:


CTextureWindow::CTextureWindow(wxWindow *parent, wxGLContext *sharedContext, wxPoint pos, wxSize size, CScene *scene):
wxGLCanvas(parent, sharedContext, -1, pos, size, 0,
wxString(wxT("GLCanvas")), NULL, wxNullPalette)
{
this->scene = scene;
}



And here is where I actually construct the two windows:


renderWindow = new CRenderWindow(this, renderPoint, renderSize, scene);


wxDialog* dialog = new wxDialog(this, -1, wxT("Textures"), wxDefaultPosition,
wxDefaultSize, wxRESIZE_BORDER|wxCAPTION, wxT("dialogBox"));
textureWindow = new CTextureWindow(dialog, renderWindow->GetContext(), wxDefaultPosition, wxDefaultSize, scene);




Any ideas on why this doesn't seem to work either?

Share this post


Link to post
Share on other sites
vx7johmi    139
Forgot to mention that it is Windows only... Sorry!

However, I don't think it is practical to have two separate wxGLCanvas sharing the same context (drawing into one window will very much affect the other one, as you are using the same context). Could be problem with clearing and swapping (how do you restrict it to a certain window?).

The easiest workaround (unless there is som Linux-specific way to share textures between context's) would probably be to generate duplicates of the textures, one for each context. It is of course a question of memory, and depends on the amount of textures you plan to use...

The other workaround would be to use one (1) wxGlCanvas and "split" the window by use of pure OpenGL commands (restrict by [glViewport], or by using two FBO's, one for each "window" and display the results on two textured quads that will represent the two "window", using the FBO's as textures)...

/Mike

Share this post


Link to post
Share on other sites
Oranda    122
I think you might be getting contexts and render targets mixed up. Contexts hold OGL data and state, wheras the seperate wxGLCanvas objects are seperate render targets. You can render to the one window without affecting the contents of the other window if they have the same context, the only thing you need to be careful of is restoring any changes you make to the context state (such as changing clear colors, etc) before rendering to the other target again.

Which is why I'm confused. I'm still getting separate render contexts in both windows, even though I'm passing the context for the CRenderWindow to the CTextureWindow. Which means there is either a bug in wxWindows (unlikely), or else I'm missing some other step.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now