Sign in to follow this  
Ed Welch

OpenGL which is better rgba as uniform or varying?

Recommended Posts

I "color" my quads using 2 different ways, first is to supply the rgba color as a uniform:

		// fragment shader
                uniform sampler2D sampler2d;
		uniform lowp vec4 color1;
		varying mediump vec2 texCoordVar;
		void main (void)
		{
			gl_FragColor = texture2D(sampler2d, texCoordVar) * color1;
		}

Then, the quads are sorted according to color and then batched together, but if the color varies a lot then you end up with a lot of draw calls.

The other way is to use a vertex color attribute:

uniform highp mat4 matrixPVM;
attribute highp vec3 inVertex;
attribute lowp vec4 inColor;
attribute mediump vec2 texCoordAttr;
varying mediump vec2 texCoordVar;
varying lowp vec4 outColor;
void main(void)
{
	gl_Position = matrixPVM * vec4(inVertex, 1.0);
	texCoordVar = texCoordAttr.st;
	outColor = inColor;
}
// fragement shader
uniform sampler2D sampler2d;
varying lowp vec4 outColor;
varying mediump vec2 texCoordVar;
void main (void)
{
	gl_FragColor = texture2D(sampler2d, texCoordVar) * outColor;
}

This has much less draw call, but it's wastefull, because I only need a color attribute for each quad, not each vertex.

Maybe, there's a third way of doing this that I haven't thought of (but this is on OpenGL ES 2.0, so I can't use any fancy stuff).

Anyone have any suggestions?

Share this post


Link to post
Share on other sites

Depends.

 

What you call "waste" isn't necessarily so.  If you're just drawing 2D quads (which it looks like you're drawing) then an extra 4 bytes (or worst case, 4 floats) per vertex is peanuts, and the extra performance from being able to batch draw calls is more than a fair tradeoff: memory isn't everything.

Share this post


Link to post
Share on other sites

Earning batched drawcall is a win situation, while worrying about 4 extra bytes is not an issue since vertex alignment is a much larger issue (16/32/64 bytes, any other byte alignment makes a rather large performance impact). The last fact, that you have an extra varying input to fragment function, would be the only con of this solution, but of course trivial one.

Share this post


Link to post
Share on other sites

BTW, the reason vertex color is the better solution is that your goal is the best constant-framerate and best worst-case framerate *not* the best best-case framerate.

If your game can have 1-1000 colors, then your uniform solution will use 1-1000 draw calls, which means performance is dependent on number of colors. Even if the uniform solution was faster than varyings for 1 color batch (which it probably is not), the fact that it is much slower at 1000 colors is a big problem. When you have the choice, choose constant framerate even if it is slightly slower.

----

At the risk of overcomplicating the discussion, depending on the details you might consider instancing your quads. When you instance, you can set how often a varying attribute increments, so you can supply only one color per quad (or for multiples of quads). If you are only varying color per instance, you will not see a difference vs per vertex colors. However, if you vary alot more, instancing can be a win.

Whether to instancing or not has to do with what you are doing with the quads, and how they are being moved or updated.

What are the quads? How do they change?

Edited by DaveSF

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628354
    • Total Posts
      2982243
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now