Archived

This topic is now archived and is closed to further replies.

Bagpuss

OpenGL OpenGL & 2d - Example given does not work, any ideas ?

Recommended Posts

Hi, I have kept quiet for a week or 2 now, and think I have learnt a fair amount of the basic stuff I need to know. Now, I am stuck again, and it has to be something really simple, probably a case of not seeing the wood for the trees ! I am trying to set up my drawing area for a coordinate based system that I can relate to (i.e. 640 * 480), and not just the seemingly abitrary opengl units. (I got teh example from someone on heres source code, just to see how it was done) My code below however does not work, when I think it should. I even copied someone elses code that does work using a similar method, and can''t get that to work either. Here is my initialisation function.
  

	PIXELFORMATDESCRIPTOR pfd;
    int         n;
	HGLRC		hrc;
	GLfloat     fMaxObjSize, fAspect;
	GLfloat     fNearPlane, fFarPlane;

    ASSERT(m_pDC != NULL);

    if (!bSetupPixelFormat(m_pDC))
        return;

// Interrogates the Pixel Format to see if a Palette is needed.

    n = ::GetPixelFormat(m_pDC->GetSafeHdc());
    ::DescribePixelFormat(m_pDC->GetSafeHdc(), n, sizeof(pfd), &pfd);

//If a Palette is needeed, then create one.(256 Colours Only)

//Detect if Needed by Anding the Value in the Data flags and the Need Palette Flag

	if ((pfd.dwFlags & PFD_NEED_PALETTE)) 
	{
								
		CreateRGBPalette(m_pDC);
	}
	
    // create a rendering context and make it current

        
    hrc = wglCreateContext(m_pDC->GetSafeHdc());
    wglMakeCurrent(m_pDC->GetSafeHdc(), hrc);

	//Clear the Depth Buffer

    glClearDepth(1.0f);
	//Enable OGL using the Depth Buffer for comparisons

    glEnable(GL_DEPTH_TEST);


//Initialise OpenGL for 2d


	glViewport(0,0,640,480);
	glMatrixMode(GL_PROJECTION);
	glLoadIdentity();
	glOrtho(0.0f,640.0f,0.0f,480.0f,-10.0f,10.0f);
	
	glMatrixMode(GL_MODELVIEW);

	glShadeModel(GL_SMOOTH);							
	glClearColor(0.0f, 0.0f, 0.0f, 0.5f);			
	glClearDepth(1.0f);									
	glHint(GL_PERSPECTIVE_CORRECTION_HINT, GL_NICEST);	
	glEnable(GL_TEXTURE_2D);

	//Select the GL Projection Matrix (Stack)

    glMatrixMode(GL_PROJECTION);
	//Reset Identity Matrix

    glLoadIdentity();	
	
}
  
and my draw scene function...
  
int CMyOgl::DrawGLScene()
{
	
    static BOOL     bBusy = FALSE;	
	if(bBusy)
        return TRUE;

    bBusy = TRUE;

	//Setup Drawing Area Back Colour

	glClearColor(m_BackColour.fRed, m_BackColour.fGreen, m_BackColour.fBlue, m_BackColour.fAlpha);
    glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
	//Reset the Drawing Point to the Centre of the screen

	glLoadIdentity();	
	

  glColor3f(0.5f,0.5f,0.5f);
	glBegin(GL_LINES);
		glVertex3f(160.0f,120.0f,0.0f);
		glVertex3f(480.0f,120.0f,0.0f);

		glVertex3f(480.0f,120.0f,0.0f);
		glVertex3f(480.0f,360.0f,0.0f);

		glVertex3f(480.0f,360.0f,0.0f);
		glVertex3f(160.0f,360.0f,0.0f);

		glVertex3f(160.0f,360.0f,0.0f);
		glVertex3f(160.0f,120.0f,0.0f);
	glEnd();
	
	
	
	SwapBuffers(wglGetCurrentDC());

    bBusy = FALSE;
	
	glFlush();	

	return TRUE;
}
  
If anyone can offer me any hints or even fix my probelm I''ll be very greatful. As an aside, if I set my system up in this manner and draw in teh z plane at 0, is there an easy way of finding out how the coordinates I have set will change if I draw in another z plane, or have I misunderstood something fundamental ? TYVMIA, Bp.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
at least part of your mistake is in your initialization.

you setup a nice viewport and projection.
then you setup some model view stuff.

then you clobber your projection!

<code>
glClearDepth(1.0f);
//Enable OGL using the Depth Buffer for comparisons
glEnable(GL_DEPTH_TEST);
//Initialise OpenGL for 2d
glViewport(0,0,640,480);
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
glOrtho(0.0f,640.0f,0.0f,480.0f,-10.0f,10.0f);

glMatrixMode(GL_MODELVIEW);
glShadeModel(GL_SMOOTH);
glClearColor(0.0f, 0.0f, 0.0f, 0.5f);
glClearDepth(1.0f); // note -- you already did this.
glHint(GL_PERSPECTIVE_CORRECTION_HINT, GL_NICEST);
glEnable(GL_TEXTURE_2D);

//Select the GL Projection Matrix (Stack)
glMatrixMode(GL_PROJECTION);
//Reset Identity Matrix -- clobbers projection!
glLoadIdentity();

</code>

i don''t know why you''re selecting the projection matrix at the end. after you''ve initialized, everything you do will be (probably) in the modelview matrix.

step 1) don''t clobber your projection matrix.

another note. depending on whether you use single or double buffering, you maybe should call glFlush() before the SwapBuffers. it makes more sense that way.

i''m not a windows guy, really, so i don''t know if you''re doing it on purpose. (calling glFlush after SwapBuffers) but in general i don''t think it makes sense. you may need it before Swap, though, to get your card to actually draw (since you''re using just a few vertices.)

thanks,
ryan.

Share this post


Link to post
Share on other sites
OK, so following Ap''s comment, I now have the following...


  
PIXELFORMATDESCRIPTOR pfd;
int n;
HGLRC hrc;

ASSERT(m_pDC != NULL);

if (!bSetupPixelFormat(m_pDC))
return;

// Interrogates the Pixel Format to see if a Palette is needed.

n = ::GetPixelFormat(m_pDC->GetSafeHdc());
::DescribePixelFormat(m_pDC->GetSafeHdc(), n, sizeof(pfd), &pfd);

//If a Palette is needeed, then create one.(256 Colours Only)

//Detect if Needed by Anding the Value in the Data flags and the Need Palette Flag

if ((pfd.dwFlags & PFD_NEED_PALETTE))
{

CreateRGBPalette(m_pDC);
}

// create a rendering context and make it current


hrc = wglCreateContext(m_pDC->GetSafeHdc());
wglMakeCurrent(m_pDC->GetSafeHdc(), hrc);

//Enable OGL using the Depth Buffer for comparisons

glEnable(GL_DEPTH_TEST);

//Initialise OpenGL for 2d


glViewport(0,0,640,480);
glMatrixMode(GL_PROJECTION);
glLoadIdentity();
glOrtho(0.0f,640.0f,0.0f,480.0f,-10.0f,10.0f);

glMatrixMode(GL_MODELVIEW);
glShadeModel(GL_SMOOTH);
glClearColor(0.0f, 0.0f, 0.0f, 0.5f);
glClearDepth(1.0f);
glHint(GL_PERSPECTIVE_CORRECTION_HINT, GL_NICEST);
glEnable(GL_TEXTURE_2D);

//Select the GL Projection Matrix (Stack)


glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
// glLoadIdentity();


//Set up the viewing angle

// gluPerspective(0.0f, fAspect, fNearPlane, fFarPlane); //Setup Perspective Matrix


//Initialise Matrix Mode

glMatrixMode(GL_MODELVIEW);
glLoadIdentity();

///Temporary code


// glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);


glColor3f(1.0f, 0.0f, 0.0f);

glBegin(GL_LINES);
glVertex3f(160.0f,120.0f,0.0f);
glVertex3f(480.0f,120.0f,0.0f);

glVertex3f(480.0f,120.0f,0.0f);
glVertex3f(480.0f,360.0f,0.0f);

glVertex3f(480.0f,360.0f,0.0f);
glVertex3f(160.0f,360.0f,0.0f);

glVertex3f(160.0f,360.0f,0.0f);
glVertex3f(160.0f,120.0f,0.0f);

glEnd();

glFlush();

SwapBuffers(wglGetCurrentDC());


And still just the white screen, no lines.

This is driving me nuts, it has to be obvious, so what am I missing ?

TIA,

Bp.

Share this post


Link to post
Share on other sites
Not certain about this .. but try drawing the lines at a +ve Z coord, rather than 0.

glBegin(GL_LINES);
glVertex3f(160.0f,120.0f,5.0 f);
glVertex3f(480.0f,120.0f,5.0 f);
glVertex3f(480.0f,120.0f,5.0 f);
glVertex3f(480.0f,360.0f,5.0 f);
glVertex3f(480.0f,360.0f,5.0 f);
glVertex3f(160.0f,360.0f,5.0 f);
glVertex3f(160.0f,360.0f,5.0 f);
glVertex3f(160.0f,120.0f,5.0 f);
glEnd();

I think the problem is that the camera is at Z=0 and so are the lines, so nothing gets drawn.

Not 100% certain, tho, so E&OE

Edit: Ignore me. I had a play around with some glOrtho stuff and anything within Z=-10 -> Z=10 should get drawn fine. sorry for being no help

[edited by - SimbobX on October 1, 2002 7:21:51 AM]

Share this post


Link to post
Share on other sites

  • Announcements

  • Forum Statistics

    • Total Topics
      628320
    • Total Posts
      2982057
  • 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