Sign in to follow this  

OpenGL OpenGL hangs in Visual C++ Express

Recommended Posts

When I try and run an OpenGL app in C++ Express it hangs most of the time. What's up with that? [EDIT]I've added more code

#include "File1.h"
#include <windows.h>
#include <gl/gl.h>
#include <gl/glu.h>

#pragma hdrstop

BOOL				InitInstance(HINSTANCE, int);

char szTitle[10] = "test";					// The title bar text
char  szWindowClass[10] = "test1";

const unsigned short SCREEN_WIDTH = 800, SCREEN_HEIGHT = 600;
COGL ogl;
#pragma argsused
WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
	MSG msg;

	WNDCLASSEX wndclassex = {0};

	// Fill the fields we care about
	wndclassex.cbSize = sizeof(WNDCLASSEX); = CS_HREDRAW | CS_VREDRAW;
	wndclassex.lpfnWndProc = WndProc;
	wndclassex.hInstance = hInstance;
	wndclassex.lpszClassName = szWindowClass;
	wndclassex.hbrBackground = (HBRUSH)GetStockObject(BLACK_BRUSH);
    //wndclassex.hCursor = (HCURSOR)LoadImage(NULL, "images/Cursor1.cur", IMAGE_CURSOR, 0, 0, LR_LOADFROMFILE);
    wndclassex.hCursor = LoadCursor(NULL, IDC_ARROW);


	if (!InitInstance (hInstance, nCmdShow))
		return FALSE;

	GLuint texture_id;
	glGenTextures(1, &texture_id);

	// Bind the texture to the texture arrays index and init the texture
	glBindTexture(GL_TEXTURE_2D, texture_id);


	GLint internal_format = GL_RGB8;    

	const unsigned int image_width = 512;
	const unsigned int image_height = 512;
	const unsigned int cui_tmp = image_width*image_height*3; 
	GLubyte *image_data_tmp = new GLubyte[cui_tmp];
	for(int i=0; i<cui_tmp; ++i)
		image_data_tmp[i] = 0;

	glTexImage2D(GL_TEXTURE_2D, 0, internal_format, image_width,
            image_height, 0, GL_RGB, GL_UNSIGNED_BYTE,

     delete[] image_data_tmp;

		if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
			if(msg.message == WM_QUIT)

		}//end if		
				//ref_playingobj.ogg_mmplayer.playMM(b_endofplayback, ref_playingobj.quad_coords);	

				glBindTexture(GL_TEXTURE_2D, texture_id);	

				glColor4f(1.0f, 1.0f, 1.0f, 1.0f);		

				glTexCoord2f(0.0, 0.0); glVertex2s(0, 0);
				glTexCoord2f(0.0, 0.9375f); glVertex2s(0, 600);
				glTexCoord2f(0.6875f, 0.9375f); glVertex2s(800, 600);
				glTexCoord2f(0.6875f, 0.0); glVertex2s(800, 0);

         }//end else		
	} // end of while

	ReleaseDC(ogl.hwnd, ogl.hdc); // Be sure to free up the window's HDC
    wglMakeCurrent(NULL, NULL); // Set render context back
    wglDeleteContext(ogl.hglrc); // Delete render context
    ogl.hglrc = NULL;
	ogl.hdc = NULL;
	UnregisterClass(szWindowClass, hInstance); // Free up the WNDCLASSEX

	return 0;
BOOL InitInstance(HINSTANCE hInstance, int nCmdShow)
   HWND hWnd;

   hInst = hInstance; // Store instance handle in our global variable

   RECT rect = { 0, 0, SCREEN_WIDTH, SCREEN_HEIGHT }; // Desired window client rect

	//DWORD winStyle = WS_CAPTION | WS_SYSMENU; // Window style
        //DWORD winStyle = WS_MAXIMIZE;

	// Adjust window rect so it gives us our desired client rect when we
	AdjustWindowRectEx(&rect, winStyle, false, winStyleEx);
   hWnd = /*CreateWindow(szWindowClass, szTitle, WS_OVERLAPPEDWINDOW,
                                rect.right - rect.left,
                                rect.bottom -,

   if (!hWnd)
      return FALSE;

   ogl.hwnd = hWnd;
   ogl.hdc = GetDC(hWnd);

		UnregisterClass(szWindowClass, hInstance); // Free up the WNDCLASSEX
	   	return EXIT_FAILURE; // Something bad happened
   }//end if


   ShowWindow(hWnd, nCmdShow);

   return TRUE;
//  PURPOSE:  Processes messages for the main window.
//  WM_COMMAND	- process the application menu
//  WM_PAINT	- Paint the main window
//  WM_DESTROY	- post a quit message and return
	int wmId, wmEvent;
	HDC hdc;

	switch (message)
		return DefWindowProc(hWnd, message, wParam, lParam);
	return 0;
// Message handler for about box.

bool COGL::initOGL(const BYTE &colorBits,
				   const BYTE &depthBits)
        // Set the pixel format
	if(!setPixelFormat(colorBits, depthBits))
		return false;

	// Set the render context
		return false;

     return true;
bool COGL::setPixelFormat(const BYTE &colorBits, const BYTE &depthBits)
        // Declare a pixel format descriptor
	        sizeof(PIXELFORMATDESCRIPTOR),  // size of this pfd
	        1,                     // version number
	        PFD_DRAW_TO_WINDOW |   // support window
	        PFD_SUPPORT_OPENGL |   // support OpenGL
	        PFD_DOUBLEBUFFER,      // double buffered
	        PFD_TYPE_RGBA,         // RGBA type
	        24,                    // 24-bit color depth
	        8, 0, 8, 0, 8, 0,      // color bits ignored
	        8,                     // no alpha buffer
	        0,                     // shift bit ignored
            0,                     // no accumulation buffer
	        0, 0, 0, 0,            // accum bits ignored
	        16,                    // 24-bit z-buffer
	        0,                     // no stencil buffer
	        0,                     // no auxiliary buffer
	        PFD_MAIN_PLANE,        // main layer
	        0,                     // reserved
	        0, 0, 0                // layer masks ignored

	// Choose a compatible pixel format (storing the pixel format index in "result")
	int result = ChoosePixelFormat(hdc, &pfd);
        // Error Check
        if(result == 0)
                return false;

	// Attempt to set the pixel format
	if(!SetPixelFormat(hdc, result, &pfd))
		return false;

	return true; // Success
bool COGL::setRenderContext()
        // Create the OpenGL render context
	hglrc = wglCreateContext(hdc);

        // Error Check
        if(hglrc == NULL)
                return false;

	// Make it the current render context
	if(!wglMakeCurrent(hdc, hglrc))
		DWORD ii = GetLastError();
		return false;
	}//end if

        //set view port
        glViewport(0, 0, SCREEN_WIDTH, SCREEN_HEIGHT);


	glOrtho(0.0, (GLdouble) SCREEN_WIDTH, 0.0, (GLdouble) SCREEN_HEIGHT, -1.0, 1.0);
	//gluPerspective(60.0f,(GLfloat)SCREEN_WIDTH/(GLfloat)SCREEN_HEIGHT, CAMNEAR, CAMFAR);


	return true; // Success
void COGL::setupOGL()
        glClearColor(1.0f, 1.0f, 1.0f, 1.0f);

        //glPixelStorei ( GL_UNPACK_ALIGNMENT, 4 );
        //glPixelStorei ( GL_PACK_ALIGNMENT, 4 );        

        //let mouse be in the middle of the window
        SetCursorPos(int(SCREEN_WIDTH  >> 1), int(SCREEN_HEIGHT  >> 1));        

[Edited by - miminawewe on January 30, 2008 6:03:48 AM]

Share this post

Link to post
Share on other sites
Yeah try pressing the 'pause' button when you're debugging to see where you are, and you can use the call stack view to see where your code has been.

Just a minor note here .. Using try / catch on OpenGL calls wont catch any errors because it's a C-style API. Try / catch are C++ style structured exception handling, the use of which in your main game loop may incur a serious performance penalty. Try to keep try / catch outside of your main loop.

Share this post

Link to post
Share on other sites
The loop runs a couple of times then it hangs. The hanging is irregular so breaking might not work.
The try / catch was for some c++ code which I have commented out. I thought it only slows down an application if an exception occurs but if none occurs then it's OK.

Share this post

Link to post
Share on other sites
Which is why you wait for it to hang before hitting pause to break into the app.

with regards to the exceptions, the issues is that when you enter a 'try' block the compiler has to do some setup in order to unwind the stack properly when an exception occurs; if you move the try block outside of the main loop this setup is only done once instead of every time.

That said, for one entry per-loop this may not be a problem (certainly unlikely to be a bottle neck with your current app) so I wouldn't worry too much about it right now, just keep it in mind for the future.

Share this post

Link to post
Share on other sites
The problem is also in borland turbo C++. I think the problem is the graphics adapter. It's an S3 prosavage/twister v1.1 2.40.103 It seems like if I set GL_CLAMP, Windows hangs, and if I don't set it or set GL_REPEAT it works.
Is there a place where I can see issues that various cards and adapters have? I think this will be a very important resource for anyone developing graphics applications especially OpenGL/DirectX.

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