• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
weeska

OpenGL
Multiple Render Target Rules

8 posts in this topic

Hi there,

in some presentations there are statements, that one can only use Render Targets of the same depth and number of channels. Is this still true for newer versions of OpenGL?

I tried looking it up in the specs, but i didn't find anything useful except framebuffer completeness rules. I wrote a sample program where i use different number of channels, different depths and so on, and it works.

I just need to know if this is officially supported or some implementation-specific "advantage".

Background is, when writing about deferred shading, some people said they're limited in what formats they can use due to resctrictions with multiple render targets. Now i need to know if that's true anymore.

thanks in advance,
weeska
0

Share this post


Link to post
Share on other sites
You are talking about FBO:s, aren't you? A FBO never has more than one depth buffer, but can have many render targets.

I am not sure what you mean by "channel", but I suppose you mean a render target. If you are talking about FBO:s with different sets of render targets, I can't see why and how there could be a restriction that all FBO:s have to use the same setup.

In my game, I use different FBO:s. One for the deferred lighting, one for shadow maps, one for terrain maps, etc. And they are all different.

Maybe you are thinking about the vertex attrib pointers. In that case, you should use the same numbers for these for every shader program that will be using the FBO. Do that either by using the layout directive in the shader logic (easiest), or by calling glBindAttribLocation() before the linking phase. That is, you define the index instead of query for them. If you do this, the same vertex attribute index will be used for all programs using your FBO, which means you can have a common logic for glVertexAttribPointer() and glEnableVertexAttribArray(). I do this by having a common program shader base class (in C++) that defines an enum with all render targets. The programs doesn't have to use all render targets available in the FBO. But you are still allowed to call glEnableVertexAttribArray() for all of them (making it easier to have common code).
0

Share this post


Link to post
Share on other sites
Sorry, i shoud have made that more clear: i'm talking about Multiple Render Targets.

In my case i'm using 3 color attachments as textures:[list]
[*]RGBA8
[*]RG16F
[*]RGB32F
[/list]
So it's possible - at least with my gpu (GL 3.3) - to have a different number of channels, as it all works as expected. I think i assume that it's not possible in general, i think.

Thanks for your help ;) Edited by weeska
0

Share this post


Link to post
Share on other sites
[quote name='Ignifex' timestamp='1345063580' post='4969941']
Yes, there are obvious restrictions to the types of the separate render buffers attached. All must have the same number of color channels. However, data types may differ. I have used 4 channel half-float and float buffers in MRT without problem.[/quote]

Are you absolutely certain that is still a requirements in newer versions? I remember reading (although the source currently eludes me) that it was at some time a requirement but was removed in one of the OpenGL revisions in between.
Also, I have a hobby project running on an AMD card (which generally make more of an effort to be standard compliant) which has a four channel byte render target and a one channel integer render buffer bound to the same FBO and I can render to both at the same time with the expected results.
2

Share this post


Link to post
Share on other sites
Hmm, well, as I said, I am not sure about official support. The last time I experimented with the possibilities on a GL 3.3 system (pre-Fermi card), I wasn't able to create such an FBO, although that has been a while.

Currently reading through the opengl Wiki pages. The [url="http://www.opengl.org/wiki/Framebuffer_Object#Completeness_Rules"]framebuffer completeness rules[/url] only provide one limitation:
- All images must have the same number of multisample samples
Also, on the Image Format page, a list of [url="http://www.opengl.org/wiki/Image_Formats#Required_formats"]required formats[/url] for render buffers is provided.
This says that 1, 2 and 4 channels with some typical formats must be supported. 3 channel textures and some other formats are optional for implementations. This does not appear to mention anything on multiple render targets.

Number of channels used to be a limitation, but clearly isn't anymore. If anyone can find a good source, it would help to clear this up. Edited by Ignifex
1

Share this post


Link to post
Share on other sites
[quote name='weeska' timestamp='1345070697' post='4969980'][list]
[*]RGBA8
[*]RG16F
[*]RGB32F
[/list]
[/quote]Technically, the number of channels is a semantic quantity--the underlying hardware will use whichever internal format it wants to. E.g., RGB is almost always some for of RGBA under the covers, because hardware operates on ones and fours. For example, I would guess that RG16F would be stored in four 8-bit channels. You probably knew that though.

I regret that I don't know for sure whether it is a portability limitation to include color attachments/rendertargets of differing internal formats. It never occurred to me, but everything I've seen seems to suggest it is possible, including its working on my card. It's an interesting concern though.

A helpful analogy might be to compare FBOs to a standard OpenGL context, wherein you can request a number of different buffers--stencil, depth, color, accumulation, etc. These are necessarily different formats, but they've all cooperated with each other for as long as they've been around. A FBO is just like a standard context, except you can choose whether you want to be able to read the buffers directly (attach a texture instead of a renderbuffer to an attachment point). I see no reason why FBOs should be different.

-G Edited by Geometrian
1

Share this post


Link to post
Share on other sites
The rules should be more relaxed on OpenGL 3.0 and onwards. However if you look at http://www.opengl.org/wiki/Framebuffer_Object it still says: "There's one more rule that can trip you up: The implementation likes your combination of attached image formats. (GL_FRAMEBUFFER_UNSUPPORTED when false)."

I've only used OpenGL 2.0 with EXT_framebuffer_object extension and with that, different color formats would work on recent GPUs on Windows/Linux, but OS X liked to play it strict and gave an error when the color formats differed. So if possible, I'd suggest testing on OS X to see if you're compatible.
1

Share this post


Link to post
Share on other sites
[quote name='AgentC' timestamp='1345200283' post='4970502']
The rules should be more relaxed on OpenGL 3.0 and onwards. However if you look at [url="http://www.opengl.org/wiki/Framebuffer_Object"]http://www.opengl.or...mebuffer_Object[/url] it still says: "There's one more rule that can trip you up: The implementation likes your combination of attached image formats. (GL_FRAMEBUFFER_UNSUPPORTED when false)."
[/quote]

It also says:
"Basically, don't concern yourself with GL_FRAMEBUFFER_UNSUPPORTED too much. Check for it, but you'll be fine as long as you stick to the required formats."

The way i understand it is, use the formats that have to be supported, and there shouldn't be a problem.


Checking for support on OS X is no option nor needed at the moment, but it's always good to know who's strict with these optional parts.

Thanks for the answers so far ;)
0

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  
Followers 0

  • Similar Content

    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
    • By Tchom
      Hey devs!
       
      I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.
       
      Vertex Shader
      uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
      precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
    • By yahiko00
      Hi,
      Not sure to post at the right place, if not, please forgive me...
      For a game project I am working on, I would like to implement a 2D starfield as a background.
      I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
      I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

      Is there someone who could have an idea of a distribution which could result in such a starfield?
      Any insight would be appreciated
  • Popular Now