• Announcements

Archived

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

OpenGL How to get OpenGL 1.5 SDK?

Recommended Posts

hello, I am updating my OpenGL API and I''ve read that v1.5 is out for sometime now. Now I am looking all over but can''t find a link to download from... any help will be rewarded with a place in heven. while on the subject, do we know when is v2.0 due? (cause I don''t) be brave and strong!

Share on other sites
I didn''t think v1.5 was out yet, oh well, I''m not really up-to-date w/ this, so if neone knows plz tell

Share on other sites
Forum FAQ

"Sneftel is correct, if rather vulgar." --Flarelocke

Share on other sites
quote:
Original post by Tera_Dragon
I didn''t think v1.5 was out yet, oh well, I''m not really up-to-date w/ this, so if neone knows plz tell

The 1.5 Standard was finalised last June iirc, we might get a 1.6 in June, however as the 2.0 Standard might be announced in Auguest thats looking less likely

Share on other sites
afaik, 3DLab''s OpenGL 2.0 isn''t going to ever "come out", since the glslang (the core of GL2) is now available in 1.5. Correct me if I''m wrong

Still, the ARB may release a 2.0, but who knows.

My Website | Everything you need to know about 3D Graphics | Google | Search the Forums

Share on other sites
You are wrong (2/3rds down the page), there is no ''3dLabs OpenGL2.0'', 3DLabs proposed some bits but any OpenGL2.0 spec has to be approved by the ARB, which as i said, looks like being August.. i so hate having to repeat myself..

Share on other sites
I was at the 3d labs shader master class in montreal and they hinted they would have a OpenGL 2.0 implementation this summer (no uber buffer support though). Some guy asked him about 2.0 and thats what he said, though he was a bit vauge.

[edited by - _walrus on March 29, 2004 10:03:14 AM]

Share on other sites
yeah, uber-buffers looks to have not made it into the first OpenGL2.0 spec, hopefully it''ll be avalible shortly afterwards as an EXT at least
My guess is 3DLabs will have a driver for the current state of OGL2.0, which probably wont under go any huge changes between now and aug, and if it does it probably wont be a hard job to make the changes afterwards, guess it all depends on their def of a ''summer'' release, they could well mean aug post standardisation..

Share on other sites
quote:
Original post by _the_phantom_
yeah, uber-buffers looks to have not made it into the first OpenGL2.0 spec,

Gah, that sucks *so* much. I need them for my curved reflections. Damn. They better ARB/EXT them quickly after releasing 2.0.

Share on other sites
having had a read of the OGL.org forums it would seem that VBO and PBO are all a part of the super/uber-buffers spec/idea, its just a matter of making sure all the specifics are sorted out so that blocks of memory can be used transparantly for one thing or another and until they have that sorted the driver side of things wont get done, as someone said, you wouldnt like to try to impliment this at a driver level, spend all that time doing it and then find out you have to redo it..

Share on other sites
Yeah, I figured they would implement them as part of the buffer object memory management concept. That''s a good idea (yay for standarized interfaces), but look how long it took the ARB members to get VBO done. Granted, there was a whole concept behind this spec (while PBO and uberbuffers would merely be an extension to it), and Microsoft was still on the team happily blocking everything. But still, uber buffers will be a little more involved than, eg, PBO. They need new opcodes / entry points to vertex programs/shaders, in order to access uber buffers at vertex level. Probably some form of ARL, but taking two arguments (or even three, 3D uber-buffers ?). They also need new texture targets, etc.

I''m afraid it will take a while before everybody gives his OK for all this.

• Partner Spotlight

• Forum Statistics

• Total Topics
627663
• Total Posts
2978521
• 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
• 10
• 12
• 22
• 13