Sign in to follow this  
sion5

OpenGL Software Rendering

Recommended Posts

Hi people, I have been given the task of developing my own software renderer which must have a custom-built maths library to include and demonstrate all basic vector operations, matrix manipulation and perspective transformations. NB. The OpenGL and GLut libraries may only be used to open up a graphics window and to draw single points, for example GL_POINTS. I have Vectors and Matricies implemented as fully functional data types with overloaded operators, copy constructors and accessors. They support add, subtract, scalar divide and multiply, cross and dot products, transpose etc. I can succesfully apply rotations and transpositions to points and using OpenGL's gluOrtho2d() display the results. But when I try to apply my worldView matrix (orthographic) to the points the display is blank :-s The .h and .cpp's can be obtained from the address below: http://www.mediafire.com/?sharekey=92f8e0beba89b27491b20cc0d07ba4d2877a2105c2c5a22c The problematic code is in the Render.cpp draw() function, along with 1 line in main() in the main.cpp. The draw function works as follows: 1. Recieve a vector<Vector3> vertices; 2. Apply currentMatrix (holds transformations) to modelView matrix 3. Apply modelView matrix to vertices, store in an intermediate array 4. apply worldView matrix (orthographic) to the intermediate array 5. use GL_POINTS to draw intermediate array The matrix i have implemented for othographic view is in the matrix4.cpp and was taken from the opengl redbook Any help with this would be much appreciated :-D HAPPY HOLIDAYS ALL

Share this post


Link to post
Share on other sites
No, I won't fix your computer.

Seriously now, you're not asking the right questions. You can't expect people to make your homework or do your job. You have to show that you've really tried hard, analyzed the problem thoroughly, and searched for answers on your own.

Your problem looks like a real 'pencil and paper' problem to me. That is, take a pencil and some paper, and do the math. Then run your application with the debugger and check that every variable you calculated on paper corresponds with the value your program produces.

If that doesn't lead you straight to the problem, feel free to ask a specific question. But don't just say: "Here, fix this"!

Share this post


Link to post
Share on other sites
I own 2 books that I remember off the top of my head that covers this in detail and would help one of them being Lamothe's "Tricks of the 3D game programming gurus" the other one being "3D graphics programming games and beyoned" by Savchenko.
See if you can get a copy of those in your library and check them out.

Share this post


Link to post
Share on other sites
C0D1F1ED - I have not asked you to do anything except point me in the right direction, I have read a million books but cant solve the problem and unfortunately my lecturers are unavailable because of the holiday period, the forums where my last resort.

"Any help with this would be much appreciated"

Definition of help: give help or assistance; be of service;

Nowhere there does it say "will you do this for me"

Share this post


Link to post
Share on other sites
> I have not asked you to do anything except point me in the right direction

That means getting the files, reading the code, and if nothing obvious pops up, compile and debug. I did the first two steps and haven't found anything obviously suspicious. But I'm NOT going to break out the debugger. That's YOUR homework, not mine.

> But when I try to apply my worldView matrix (orthographic)
> to the points the display is blank :-s

You are debugging both your SW rasterizer and OpenGL commands at the same time. I suggest you use a frame buffer instead of drawing points immediately to a window. You can examine the frame buffer's content at any moment, or dump it to a file for further examination. Once you have validated the SW path, you can always replace the piece of code that draw points with an OpenGL version and make sure you get the same results.

-cb

Share this post


Link to post
Share on other sites
Ok, well my appologies then I have misunderstood the purpose of these forums. I was hoping that it would be an obvious problem that I had overlooked and was easy to find to the trained eye.

Share this post


Link to post
Share on other sites
Quote:
Original post by sion5
I have not asked you to do anything except point me in the right direction...

Sure, you didn't ask it directly. But you did dump your code here in the hopes that someone will dig though it and pinpoint the problem and either tell you the solution or "guide you in the right direction". You have to realize that this is a lot of work, and telling you the solution or guiding you takes equal effort since the bulk of the task is in locating the exact issue. So intentional or not, you did ask for us indirectly to fix your code.
Quote:
I have read a million books but cant solve the problem and unfortunately my lecturers are unavailable because of the holiday period, the forums where my last resort.

Reading more books will not help one bit. This is a debugging problem. Something for which you need to roll up your sleeves. And I believe that's the whole point of your assignment. To learn some skills through hard work.

Now, if you were seriously stuck and pinpointed the problem yourself and had already tried everything to come up with a solution and showed that to us, we would be more than happy to try to tell you what you're doing wrong and which approach might be more succesful.

And I believe that's exactly what I'm already trying to do here. See, although this thread's title says "Software Rendering", it has practically nothing to do with it. There are a million ways to implement a software renderer (and each of the million books you read probably has a different one). If you understand the math and you have an implementation that 'should' work but doesn't, this is nothing more than a debugging problem.

And it's one that asks for a pencil and paper approach. Take some input data that you know should end up at a certain location on screen. Make it as simple as possible, like a cube that's half the size of your screen width. Set all the matrices you don't need to the identity matrix. It's just you against the orthographic projection matrix then. Calculate on paper that it works as intended. Then check whether your code does the exact same calculations and outputs that on the screen.

Either this will pinpoint the issue, or it will show that you don't fully understand the math yet. I doubt it's the latter since you read a million books and you dumped the code on us not the math, but still, if you do need a hand in the math area we'll be more than happy to help if you have any specific questions.
Quote:
Ok, well my appologies then I have misunderstood the purpose of these forums. I was hoping that it would be an obvious problem that I had overlooked and was easy to find to the trained eye.

Don't sweat it. ;) Everyone makes that mistake at least once. You just have to understand that the "trained eyes" on this forum are payed to do tedious debugging during their daytime job. It's even more annoying when looking at other people's code. They're happy to help you out with any actual technical problem though, the exciting bit. Debugging is just something each has to do himself, and you can only learn this skill through practice and by taking generic advice (there is no single recipe for successful debugging)...

Good luck!

Share this post


Link to post
Share on other sites
Quote:
Original post by C0D1F1ED
Everyone makes that mistake at least once. You just have to understand that the "trained eyes" on this forum are payed to do tedious debugging during their daytime job. It's even more annoying when looking at other people's code. They're happy to help you out with any actual technical problem though, the exciting bit. Debugging is just something each has to do himself, and you can only learn this skill through practice and by taking generic advice (there is no single recipe for successful debugging)...


Originally I disagreed with C0D1F1ED but then I downloaded your code and completely lost interest. There's just too much to go through, and too many places an error could be present. I don't see a glaring error but I only spent 5 minutes looking.

I suggest you check your matrices against some reference... perhaps matrices produced by opengl functions? Piece by piece take something that definitely works and compare it against your own code. If you find a discrepency and you legitimately can't figure out why... post the relavent code here and I'm sure people will be able to explain it to you.

-Kiran

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
      628314
    • Total Posts
      2982024
  • Similar Content

    • 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.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now