# OpenGL OpenGL 3 on a 2.1 device

## Recommended Posts

I have searched, but nobody seems to be asking this question, nor have I found an answer. Is it possible to run a program containing OpenGL 3 code on a machine that only supports up to 2.1? I would be most interested in some sort of software that wraps around the program and simulates any calls that the hardware cannot handle.

I'm doing some OpenGL 3 development on my X201 and the intel graphics cannot correctly run many of the examples in the OpenGL SuperBible, 5th edition (see attached screen shot, which is supposed to depict a sphere). These examples work correctly on my GTX 460. If it were possible to get a small expresscard slot graphics adapter that provided support for OpenGL 3, that would be excellent, but I don't think such a device exists (besides the ViDock, which is not practical on the go).

[img]http://img.photobucket.com/albums/v295/Muftobration/OpenGL21failure.png[/img]

##### Share on other sites
If your driver doesn;t support it then you can't do it. The software option is not really an option - the only real software implementation is [url="http://www.mesa3d.org/"]Mesa3D[/url], that only goes up to OpenGL 2.1, and in any event if any parts of the fragment pipeline get software emulated you typically end up with less that 1 frame per second.

##### Share on other sites
Ah, that's a shame. Thanks anyway.

##### Share on other sites
[url="http://developer.nvidia.com/nvemulate"]http://developer.nvidia.com/nvemulate[/url]

Don't expect performance to be usable though....

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627681
• Total Posts
2978611
• ### 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?

• 13
• 12
• 10
• 12
• 22