Sign in to follow this  
dc443

OpenGL FBO's and Multisampling

Recommended Posts

dc443    144
http://www.opengl.org/wiki/Multisampling This page goes over the standard method of creating a program that detects and enables FSAA under windows, but I can't seem to find any instructions for doing the same on Linux. Can anybody provide me with information on this topic? Also kind of related: what is the difference from FSAA (the type that you force from the driver control panel in windows) vs the ARB Multisample Extension (which i'm hoping one can use to selectively antialias parts of a scene by using glEnable(GL_MULTISAMPLE) or some such)? I've been googling this stuff for hours now and all i've got is a headache. Heres an interesting tidbit: I have a Ubuntu 9.04 VM in Virtualbox on Windows 7 host, and when I put this line
	SDL_GL_SetAttribute(SDL_GL_MULTISAMPLEBUFFERS, 1); 
before creating my SDL window, Virtualbox crashes when I run the program. [Edited by - dc443 on November 6, 2009 11:59:45 PM]

Share this post


Link to post
Share on other sites
Yann L    1802
OK, well first of all, the ARB_multisample extension is a mess. Try to avoid it if possible. A much better alternative is to use a non-FSAA screen format, together with a multisampled FBO. This is much more flexible, powerful and clean. It's also much easier to setup and use.

That said, I'm not sure if you can get any of this on Linux if it is running under a VM.

Share this post


Link to post
Share on other sites
dc443    144

So I take it that you are suggesting I use GL_EXT_framebuffer_multisample and GL_EXT_framebuffer_blit in addition to the GL_EXT_framebuffer_object extension... as described in this page: http://blog.dexta.ch/2008/08/27/gl_ext_framebuffer_object-with-multisampling/

(btw how do you do hyperlinks on this forum?)

How does this method compare to "the other ways" of doing multisampling? Is this separate from the settings that you force in the display drivers?

Share this post


Link to post
Share on other sites
SimonForsman    7642
Quote:
Original post by Yann L
OK, well first of all, the ARB_multisample extension is a mess. Try to avoid it if possible. A much better alternative is to use a non-FSAA screen format, together with a multisampled FBO. This is much more flexible, powerful and clean. It's also much easier to setup and use.

That said, I'm not sure if you can get any of this on Linux if it is running under a VM.


VirtualBox has Pretty decent OpenGL support (OpenGL 2.0 was fully supported in VB 3.0 including GLSL support (On Linux, Windows and Solaris guests atleast)

Share this post


Link to post
Share on other sites
Yann L    1802
Quote:
Original post by dc443
So I take it that you are suggesting I use GL_EXT_framebuffer_multisample and GL_EXT_framebuffer_blit in addition to the GL_EXT_framebuffer_object extension...

Yep. Or use ARB_framebuffer_object, which includes all three extensions in one.

Quote:
Original post by dc443
How does this method compare to "the other ways" of doing multisampling? Is this separate from the settings that you force in the display drivers?

It's separate, since FBOs are independent render targets. You choose the multisampling level and config separately for each FBO (although you can share attachments). You can even have several FBOs with different MS settings in use simultaneously, within the same application.

The settings on the driver page will only change the AA config of your main framebuffer, ie. the one that is eventually displayed on the screen. This one is independent of any FBO you create.

In practice, your screen framebuffer would be non-multisampled. You do all your rendering into a MS FBO, resolve it (possibly using a customized resolve shader, if needed) and copy it onto the non-AA'ed screen framebuffer.

Quote:
Original post by dc443
(btw how do you do hyperlinks on this forum?)

Standard HTML link tags.

Share this post


Link to post
Share on other sites
dc443    144
Thanks for the quick replies! :)

How does the performance of this multisampled FBO method compare with traditional methods?

As I understand it, I need to render to a multisampled FBO, then blit it into another FBO attached to a texture, and then render that texture as a full screen quad. This seems like doing so much extra work. Drawing a full screen texture quad always felt like a big hack to me.

How is support for this from ATI? I saw some Nvidia charts indicating that the FBO extensions are supported for the hardware that is capable of it with recent drivers, but I don't know about ATI.

Share this post


Link to post
Share on other sites
V-man    813
Quote:
Original post by Yann L
OK, well first of all, the ARB_multisample extension is a mess. Try to avoid it if possible. A much better alternative is to use a non-FSAA screen format, together with a multisampled FBO. This is much more flexible, powerful and clean. It's also much easier to setup and use.

That said, I'm not sure if you can get any of this on Linux if it is running under a VM.


Hehehe. That's an interesting idea.

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 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.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now