Sign in to follow this  
Pilpel

OpenGL How to build a "renderer"

Recommended Posts

I render with OpenGL and I wonder how common engines build their Renderer class.

 

1. Does this class hold data members like: vec4 m_clearColor; bool m_isWireframe, or they they just contain functions that abstract the actual opengl routines? Something like

void MyRenderer::setWireframe(bool flag)
{
    glPolygonMode( GL_FRONT_AND_BACK, flag ? GL_FILL : GL_FILL );
}

2. How does the whole framework use this class? Does it even have to be a class?

 

I know I asked really broad questions so if you can link me to other sources it would be nice too.

Share this post


Link to post
Share on other sites

Just a question for you rendering architects: Do you have some central place that does all the drawing, regardless of what is actually drawn, or do you have something like custom render modules where each implements their own rendering, including setting up buffers, fixed function state, shaders, submitting draw commands etc.?

 

I have been thinking... it should be enough when those custom renderCmds gather the data that is required to render somewhere and submit it to a central renderer (which buffers do I need? which shaders do I need? etc.). Would get rid of a lot of boiler plate (only a couple hundred lines of rendering code for each API backend? one can dream), and that central renderer would have all the info available to batch stuff efficiently.  But I'm not sure how feasible this is in practice until you end up with lots of ifs() that handle special cases anyways, or if there's something else that prevents it from being as clean as it sounds.

 

edit: Having read it now, the presentation by Hodgman above seems to implement exactly this. Does it work for everything? No custom drawing code needed anymore?

Edited by agleed

Share this post


Link to post
Share on other sites

Most renderers are all the same.

Typically you have an abstraction interface for all the API's that it supports. Then because Directx's Effect files are no longer useable, they will typically build their own passes. Which to be fair, is more efficient this way anyways.

Share this post


Link to post
Share on other sites

I prefer generic design where graphic engine only consist of a RenderQue, RenderParamTracker and TokenProcessor (meshes, materials and vertex definitions have those). INI file has definition of render modes, render targets, render params, token rules, etc...

 

It's tiny and efficient and you don't have to touch engine code ever (if implemented properly)

Share this post


Link to post
Share on other sites

I prefer generic design where graphic engine only consist of a RenderQue, RenderParamTracker and TokenProcessor (meshes, materials and vertex definitions have those). INI file has definition of render modes, render targets, render params, token rules, etc...

 

It's tiny and efficient and you don't have to touch engine code ever (if implemented properly)

 

 

Essentially something like this.

My current design seperates the engine's data from it's own.When The engine calls the renderer, the rendering logic does not need to know about the particulars of the actual engine's data. Instead, it's api recieves copies and transforms the data to a state that is needed.

 

When it comes time to render, the culling system will work independently of the current game state, it'll display a latent frame instead, and cull data based on what it has. This also means that the Renderer uses it's own octree for it's own processes. Primarily culling, But also as a way of determining some broader spectrum of LOD.

 

The engine's logic has it's own octree for logical processes. RayCasting, Scripts that effect certain regions of land, Navmesh Collisions, etc.

Share this post


Link to post
Share on other sites

 

I prefer generic design where graphic engine only consist of a RenderQue, RenderParamTracker and TokenProcessor (meshes, materials and vertex definitions have those). INI file has definition of render modes, render targets, render params, token rules, etc...

 

It's tiny and efficient and you don't have to touch engine code ever (if implemented properly)

 

 

Essentially something like this.

My current design seperates the engine's data from it's own.When The engine calls the renderer, the rendering logic does not need to know about the particulars of the actual engine's data. Instead, it's api recieves copies and transforms the data to a state that is needed.

 

When it comes time to render, the culling system will work independently of the current game state, it'll display a latent frame instead, and cull data based on what it has. This also means that the Renderer uses it's own octree for it's own processes. Primarily culling, But also as a way of determining some broader spectrum of LOD.

 

The engine's logic has it's own octree for logical processes. RayCasting, Scripts that effect certain regions of land, Navmesh Collisions, etc.

 

For occlusion culling I'm using view frustum culling + Hi-Z algorithm (actually it's Lo-Z because of inverted z-buffer).

 

Main engine script does this:

  SetRenderMode("PrepForHiZ"); // This will invoke setting of render targets, rendering quads, and after rendering is done, setting shader textures of those render targets, etc...

  RenderOcclussionSpheres(); // this is main engine command - it keeps track of current objects (each has his own id and pos/radius)

  void * flags = LockGraphicBuffer("occlusion_test_render_target", (X + 10)%10); // I'm having 10 frames delay (and 10 occlusion buffers)

  SetOcclussionFlagsForObjects(flags);

 

Graphic engine doesn't even know that it did occlusion calculation. It doesn't understand what data sent to it means - only how to send it to graphic card.

That way it can be forward renderer, deffered rendered, forward+ rendered, ray tracer, <some new renderer that hasn't been invented yet>. It doesn't care what the data is - only how to render it efficiently.

 

As for token processor:

 

Rendering_technique_name = <Render Mode Name> + <Remaining Mesh Tokens> + <Remaining Material Tokens> + <Remaining Vertex Tokens>

 

SAMPLE: When rendering depth, there is no need to have tokens that have something to do with color. Then if all texture tokens are removed from material, Vertex token that represents texture coordinates will be removed (if there is no alpha mask texture). At the end you end up with only few tokens. Vertex token that represent NORMAL will probably also be removed (since it isn't even registered for RenderDepth render mode).

 

Once you know rendering technique name, you know which render parameters need to be sent to graphic card - and RenderParamTracker does that efficiently (without repetition).

 

The point is: there is no harcoding of anything graphic wise (shaders + graphic data come with the game files - not engine).

You write graphic engine once and then you don't touch it for years.

If some new way of rendering/post process effect gets published you don't change the engine - you just stuff the shader into first game package and add a few lines in the INI file. Maybe add few SetRenderModes("blablabla") into rendering script for some new post-processes.

Edited by JohnnyQ

Share this post


Link to post
Share on other sites

 

 

I prefer generic design where graphic engine only consist of a RenderQue, RenderParamTracker and TokenProcessor (meshes, materials and vertex definitions have those). INI file has definition of render modes, render targets, render params, token rules, etc...

 

It's tiny and efficient and you don't have to touch engine code ever (if implemented properly)

 

 

Essentially something like this.

My current design seperates the engine's data from it's own.When The engine calls the renderer, the rendering logic does not need to know about the particulars of the actual engine's data. Instead, it's api recieves copies and transforms the data to a state that is needed.

 

When it comes time to render, the culling system will work independently of the current game state, it'll display a latent frame instead, and cull data based on what it has. This also means that the Renderer uses it's own octree for it's own processes. Primarily culling, But also as a way of determining some broader spectrum of LOD.

 

The engine's logic has it's own octree for logical processes. RayCasting, Scripts that effect certain regions of land, Navmesh Collisions, etc.

 

For oclussion culling I'm using view fustrum culling + Hi-Z algorithm (actually it's Lo-Z because of inverted z-buffer).

 

Main engine script does this:

  SetRenderMode("PrepForHiZ"); // This will invoke setting of render targets, rendering quads, and after rendering is done, setting shader textures of those render targets, etc...

  RenderOcclussionSpheres(); // this is main engine command - it keeps track of current objects (each has his own id and pos/radius)

  void * flags = LockGraphicBuffer("oclussion_test_render_target", (X + 10)%10); // I'm having 10 frames delay (and 10 oclussion buffers)

  SetOcclussionFlagsForObjects(flags);

 

Graphic engine doesn't even know that it did oclussion claculation. It doesn't understand what data sent to it means - only how to send it to graphic card.

That way it can be forward renderer, deffered rendered, forward+ rendered, ray tracer, <some new renderer that hasn't been invented yet>. It doesn't care what the data is - only how to render it efficiently.

 

As for token processor:

 

Rendering_technihnique_name = <Render Mode Name> + <Remaining Mesh Tokens> + <Remaining Material Tokens> + <Remaining Vertex Tokens>

 

SAMPLE: When rendering depth, there is no need to have tokens that have something to do with color. Then if all texture tokens are removed from material, Vertex token that represents texture coordinates will be removed (if there is no alpha mask texture). At the end you end up with only few tokens. Vertex token that represent NORMAL will probably also be removed (since it isn't even registered for RenderDepth render mode).

 

Once you know rendering tehnique name, you know which render parameters need to be sent to graphic card - and RenderParamTracker does that efficiently (without repetition).

 

The point is: there is no harcoding of anything graphic wise (shaders + graphic data come with the game files - not engine).

You write graphic engine once and then you don't tuch it for years.

If some new way of rendering/postprocess effect gets published you don't change the engine - you just stuff the shader into first game package and add a few lines in the INI file. Maybe add few SetRenderModes("blablabla") into rendering script for some new post-processes.

 

 

Never said the data was hard coded :P Only that the renrderer recieves copies of relevant data, but does not care for how the game engine manages it.

Currently, Rendering data is defined through json like Lua scripts. and is instantiated as called upon.

Edited by Tangletail

Share this post


Link to post
Share on other sites

So yeah,

Renderer are pretty much always done through abstract interface (as demonstrated by Hodgman and Tangletail).

 

This is the abstract graphic interface in my case (used by main engine either through scripts or hardcoded):

 

  SetRenderMode("bla bla"); // This will set render targets and prepare everything (and remove prev render targets and bind them to shader texture variables for the future use)

  // Main engine will loop through visible objects and call these two commands (similar is done for light-shadow pass):

  SetRenderParam(renderParamID, value); // camData or objPos or obj bones or some custom constant or whatever (done by object script).

  RenderMesh(meshID, availableDesiredLODDistance); // This will add mesh to render que and calculate render stuff based on material/mesh tokens

 

 

That is it - It is very very abstract. I don't think it is possible to have it more abstract than that. There are also some callbacks that graphic engine will do to calc some required rendering parameter that was not set, but that's another story...

 

NOTE: Sometimes I assign some material to some geometry that are not compatible (defined by meshID). In that case graphic engine will issue a warning that it doesn't know how to render this particular combination of render_mode/mesh/material/geometry tokes. Then I have to add exception rule to the INI file or add a shader for that particular combination.

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
      628364
    • Total Posts
      2982269
  • 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