Sign in to follow this  
Followers 0
TheChubu

OpenGL
Structure of an OpenGL renderer

0 posts in this topic

Hi! So, I was following arcsynthesis.com online book (OpenGL 3.3) which uses C++ (though very plain C oriented). Thing is, I've been using Java lately for an OOP course and I thought that porting Arcsynthesis tutorials to Java would be a good learning experience using LWJGL. I would like to transform all of that, someday, into an usable render.

For that I need to know the general structure of a render if I want to avoid massive refactoring every now and then when I discover new functionality. So that's the issue, what's the general structure of a render? What kind of methods it would involve? What about the parameters of those methods? It's possible to make some generalized "OpenGLClass" or it's better to tailor it for what you currently need and leave it at that?

I'm currently trying with a "GLClass" . Its constructor sets up the display size and the context. It has a few methods:

loadShader(String shaderfile, int shaderType) which takes the location of a file in the form of a string, reads it, compiles it, and returns its integer Id.

createShaderProgram(int[] shaderIdArray) which takes an array of compiled shader Ids and creates a program out of them, storing its Id into an attribute of GLClass.

draw() which is currently a mess and the incoming parameters change everytime I learn a new way of drawing things (ie, first with vbos, then with vaos, then with interleaved vbos with color and vertex information, etc) and I'm not sure what should do.

disposeOfGL() which deletes all OpenGL's buffers that changes as often as the draw() method.

I haven't come across good ideas for making a "createVAO" method since it always changes depending on how many vbos it has, or how they're organized.

I'm not sure either what GLClass object should store. For now it stores the Id of everything I'm using (vbos, vaos, shaders, etc) though I'm actually passing a lot of those from the main class to the methods as parameters instead of reading them directly from the GLClass object.

I also need to know what kind of other methods should have in the future, load model? load texture? pass textures/models to the gpu?

I understand that I know very little about OpenGL, so maybe its better just to code what I need right now to keep learning and then start over once I can distinguish what can be done and what not, but I'd need someone with more understanding of OpenGL to clarify that for me.
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 recp
      Hi,
      I'm working on new asset importer (https://github.com/recp/assetkit) based on COLLADA specs, the question is not about COLLADA directly
      also I'm working on a new renderer to render (https://github.com/recp/libgk) imported document.
      In the future I'll spend more time on this renderer of course, currently rendering imported (implemented parts) is enough for me
      assetkit imports COLLADA document (it will support glTF too),
      importing scene, geometries, effects/materials, 2d textures and rendering them seems working
      My actual confusion is about shaders. COLLADA has COMMON profile and GLSL... profiles,
      GLSL profile provides shaders for effects so I don't need to wory about them just compile, link, group them before render

      The problem occours in COMMON profile because I need to write shaders,
      Actually I wrote them for basic matrials and another version for 2d texture
      I would like to create multiple program but I am not sure how to split this this shader into smaller ones,

      Basic material version (only colors):
      https://github.com/recp/libgk/blob/master/src/default/shader/gk_default.frag
      Texture version:
      https://gist.github.com/recp/b0368c74c35d9d6912f524624bfbf5a3
      I used subroutines to bind materials, actually I liked it,
      In scene graph every node can have different program, and it switches between them if parentNode->program != node->program
      (I'll do scene graph optimizations e.g.  view frustum culling, grouping shaders... later)

      I'm going to implement transparency but I'm considering to create separate shaders,
      because default shader is going to be branching hell
      I can't generate shader for every node because I don't know how many node can be exist, there is no limit.
      I don't know how to write a good uber-shader for different cases:

      Here material struct:
      struct Material { ColorOrTexture emission; ColorOrTexture ambient; ColorOrTexture specular; ColorOrTexture reflective; ColorOrTexture transparent; ColorOrTexture diffuse; float shininess; float reflectivEyety; float transparency; float indexOfRefraction; }; ColorOrTexture could be color or 2d texture, if there would be single colorOrTex then I could split into two programs,
      Also I'm going to implement transparency, I am not sure how many program that I needed

      I'm considering to maintain a few default shaders for COMMON profile,
      1-no-texture, 2-one of colorOrTexture contains texture, 3-........

      Any advices in general or about how to optimize/split (if I need) these shaders which I provied as link?
      What do you think the shaders I wrote, I would like to write them without branching if posible,
      I hope I don't need to write 50+ or 100+ shaders, and 100+ default programs

      PS: These default shaders should render any document, they are not specific, they are general purpose...
             I'm compiling and linking default shaders when app launched

      Thanks
    • By CircleOfLight97
      Hi guys,
      I would like to contribute to a game project as a developer (open source possibly). I have some experiences in C/C++ in game development (perso projects). I don't know either unreal or unity but I have some knowledges in opengl, glsl and shading theory as I had some courses at university regarding to that. I have some knowledges in maths and basic in physics. I know a little how to use blender to do modelling, texturing and simple game assets (no characters, no animation no skinning/rigging). I have no game preferences but I like aventure game, dungeon crawler, platformers, randomly generated things. I know these kind of projects involve a lot of time and I'd be really to work on it but if there are no cleary defined specific design goals/stories/gameplay mechanics I would like to not be part of it x) and I would rather prefer a smaller but well defined project to work on that a huge and not 'finishable' one.
      CircleOfLight97
    • By gamesthatcouldbeworse
      Hi, I finally released KILL COMMANDO on gamejolt for free. It is a retro-funsplatter-shooter with C64 style. Give it a try.
    • By phil67rpg

      void TimerFunction(int value) {  glutPostRedisplay();  glutTimerFunc(1000, TimerFunction, 1); } void drawScene() {  glClear(GL_COLOR_BUFFER_BIT);      drawScene_bug();  TimerFunction(1);  eraseScene_bug(); // drawScene_bug_two(); // eraseScene_bug_two(); drawScene_ship(); drawScene_bullet();  glutSwapBuffers(); }