## Recommended Posts

I've attached the (small) Visual Studio 2010 project with all the source inside it.
[attachment=4299:CaT.zip]

I'm trying to create a simple window (in Windows) with openGL capabilities. I've done it before, but for some reason this time, no matter what I try I can't get it to work. And by work I mean actually quit the program when the window is closed.

From what I have been able to figure out, the Windows function ChoosePixelFormat (is in the file window.cpp in the zip) creates a new thread when it is called, and this thread refuses to exit once the main thread finishes. I have no idea how to fix it, spent hours on it and have gotten nowhere. Hoping that someone here can help!!

##### Share on other sites
I've never heard of that behaviour of ChoosePixelFormat, and have never encountered anything like this when using it. I [i]have[/i] encountered the same symptom as you, but it's always been attributable to my own screw-up, so that's where I'd look first.

There are a number of things wrong with your code. Using both main and WinMain and not returning 0 from WM_DESTROY are two I've found from a brief look through it (I'd also advise changing your "running = false" line to a simple "break"). I'd advise you to fix these first and get it working the way a well-behaved Win32 app should work before even looking at the OpenGL side of things.

##### Share on other sites
Hmmm, seems to work when I just put the entry point as WinMain and skip over all the main stuff, which is odd cause I've managed to do that before. I had had it that way to try and make it so it would be more portable in the end. Thanks muchly for your help!!

##### Share on other sites
int WINAPI WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
#else
int main (int argc, char *argv[])
#endif[/code]
In all honesty, your window creation and video startup code is going to be completely differrent for different platforms anyway, so you may as well have different entry points too.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627657
• Total Posts
2978471
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 12
• 22
• 13
• 33