Sign in to follow this  
Bad Maniac

OpenGL OpenGL mentor/code-buddy wanted.

Recommended Posts

I've been working on a software 2D library for so long I dream in ASM. And while it's nearing public release of this behemoth of 2D graphics, we're having a bit of a breather. And I've started looking at NeHe, and flicking through the pages of my "Beginning OpenGL Game Programming". And thinking about reviving an age old project of mine. So I had this idea. I'd like to create a SIMPLE game framework, maybe a first person walk around in Wolfenstein 3D style, nothing flashy. But something with rudimentary collision detection so you can walk around in a maze. And then use this to test various effects. Try coding some light and shadow effects, particle systems, bumpmapping(whatever's the top of the range bumpmapping this week). You name it, whatever either of us feels like trying. Point being that we have a "real" game framework to add it to, instead of a spinning cube. What I have: * Basic understanding of OGL from the aforementioned book, and NeHe. * A running rudimentary framework based on NeHe with parts from the book. With deltatime framerate independent movement/animation. Text output via WGL, and GLee extension support. * PNG texture loading. What I don't have: * ANY idea how 3D math, matrices and quaternions work ;) * Map/Model loading * Camera control * Well, I'm a noob at 3D and OGL... There isn't much I DO have yet. I'm looking for someone who'd like to have IM converstaions, and/or VoIP(TeamSpeak/Skype) conversations about OGL. While working together on this little project. I've found that working with VoIP and shared desktop so you both can see the code is excellent for tutoring and idea sharing, so this is my prefered method. But plain IM conversations and sharing the code would work too. I'm Windows XP based, working in Visual Studio 6, writing mainly in C (and ASM) so C would be the language of choice.

Share this post

Link to post
Share on other sites
Well I'm currently working on a Wolf3D style game so I can supply you with some code if you want it. Send me a PM and i'll e-mail the source. This is my first project, and hopefully i should get to finish it sometime soon. The code is all in java though, so this may or may not be a problem for you. Though if you can understand C then I think you should be able to understand some java code.

Here are some screenshots from the current version:

The following things in the game are more or less complete:

- Basic enemy AI: movement and firing
- Bullet hits and guns
- Simple bounding box collision detection
- Area portaling- the map gets partitioned into separate 'rooms'.
- Sound via OpenAL.
- The map renderer
- MD2 loading and animation
- Simple particles (done via a vertex shader)
- Level editor for making maps
- Doors and sliding tiles like those in WOLF3D

And I still have to do the following:

- Basic menu structure
- Map for finding your way around
- Load / Save game
- Loading screens, end of level screens, game over screens etc..
- The player doesn't die yet!
- Model some new weapons and monsters (I only have one of each at the moment)
- Add 'end of level tile' and doors locked with keys.
- Add pickupable items such as health and ammmo.

Share this post

Link to post
Share on other sites
That looks awesome if you ask me! :)
Sadly, since my understandng of 3D is limited, I doubt raw sourcecode would do me much good, especially in a "foreign" language, even if Java is similar to C in many ways.

If you would like to tutor me a bit, then I'd be interested, maybe write a C port of that game of yours, and learning by doing. What do you think? how good is your C knowledge, and would have the patience to tutor a total newcomer?

Share this post

Link to post
Share on other sites
Darragh, lookin good. Hey, would you mind sharing your md2 loading source with me? I've gone through about 3 implementations, and ive screwed it up 3 times see this thread:

Anywho, theres that bruce willis model ive always wanted to use in my game ;-) and i figure i could use a little inspiration, so i wouldnt mind takin a look at that source.

thanks a ton

Share this post

Link to post
Share on other sites
Original post by Bad Maniac
That looks awesome if you ask me! :)

Thanks man. Appreciate the comments!

Original post by Bad Maniac
Sadly, since my understandng of 3D is limited

But so is mine!.. [smile] When I first started this project a few months ago i knew nothing of 3D, nothing about AI, nothing about collision detection, nothing about sound, never done file reading/writing.. All I had was a very basic understanding of java. The most complicated program I wrote before this was a simple command line calculator for a college project. When I first sat down to write a game I decided my first project would have to be something simple like pong.

Now, halfway through making pong I got really really fed up and decided I wanted to do something less boring. I wanted 3D mazes, monsters and guns just like in my favorite games Doom and Wolfenstein. So I decided to take a leap and go for 3D, probably not a wise move- but I was determined to do it anyway.

After looking at a few tutorials on the basics of 3D (mostly here on gamedev) I managed to get some polygons rotating around in 3D. This was all done in software. A short while later I decided that I wanted hardware acceleration so I took up learning OpenGL. After that, I continued to scour the web for articles and tutorials relating to OpenGL. Bit by bit my knowledge grew and I was able to do more stuff with the game...

Ultimately, my point to you is, do not be disheartened! What you see in those screenshots is very much achievable- even for an absolute beginner.. Heck, i was an absolute beginner when I first started this! You can do it, all you need is a little determination..

Original post by Bad Maniac
I doubt raw sourcecode would do me much good, especially in a "foreign" language, even if Java is similar to C in many ways.

If you would like to tutor me a bit, then I'd be interested, maybe write a C port of that game of yours, and learning by doing. What do you think? how good is your C knowledge, and would have the patience to tutor a total newcomer?

Well if you have any questions then i'd be happy to try and answer them to the best of my ability. I'm no OpenGL expert myself and there are many on this website who know a lot more than me- but i'd be glad to help anyway. I couldn't possibly do any VO/IP conversations or anything like that since i'm only on a dialup connection, but if you e-mail me then I can try and answer your questions. Bear in mind though that I know little of the C language so I probably won't be able to help with the actual setting up of the OpenGL display, since C handles this very differently to java. But for general GL questions I may be able to help.

Darragh, lookin good. Hey, would you mind sharing your md2 loading source with me? I've gone through about 3 implementations, and ive screwed it up 3 times see this thread:

No problem. I'll send the code to you in an e-mail. There is one thing about the loader though, I think java has a different byte ordering scheme to C so I had reverse the bytes for every piece of information read from the file. I think you can ignore this part if you're writing in C...

Hopefully it should help..

Anywho, theres that bruce willis model ive always wanted to use in my game ;-)

Sounds interesting. Is it a die hard game ? [smile]

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
    • Total Posts
  • 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!
    • 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.
    • 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
      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