Archived

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

Deokhee Lee

OpenGL When we meets OpenGL 1.3?

Recommended Posts

I''m waiting for OpenGL 1.2 first.... it might take some months till it''s available on Windows Systems.. OpenGL 1.3? maybe a few years?

cya,
Phil

Visit Rarebyte!
and no!, there are NO kangaroos in Austria (I got this questions a few times over in the states

Share this post


Link to post
Share on other sites
What do you mean 1.2 will take months? Ive been using it for years.

The software driver that comes with windows is only 1.1, but the drivers for most (if not all) hardware is upto 1.2.

Share this post


Link to post
Share on other sites
I dont know if this will work on non nvidia cards but if you want to use opengl 1.2, you can enable it through an extension. GL_VERSION_1_2 is the name of the extension. I use it and it works great.

-SirKnight

Share this post


Link to post
Share on other sites
It''s only OpenGL1.1 on windows systems, but drivers are made for 1.2 and you can access 1.2 features through the extensions mechanism, however it''s not 1.2.

If it was 1.2 you shouldn''t have to access standard 1.2 functions through extensions.

OpenGL1.3 should be out soon, I hope they''ll release new Red and Blue books very soon after availability.

M$ just don''t like to have to deal with something they have no control over, that''s why they don''t update the OpenGL version in windows.
(They promote DirectX that way)


-* So many things to do, so little time to spend. *-

Share this post


Link to post
Share on other sites
I thought they were releasing 1.3 at siggraph next weekend.

The fanatic is incorruptible: if he kills for an idea, he can just as well get himself killed for one; in either case, tyrant or martyr, he is a monster.
--EM Cioran

Opere Citato

Share this post


Link to post
Share on other sites
*sigh* I really wish I could attend this kind of stuff... And, since I can''t, I really wish they could tell us all this stuff on some geek only channel... And since they can''t, I really wish I could attend this kind of stuff.

But, really, OGL 1.3 is nice in concept, but, how long until windows (the dominant OS) is going to even give us 1.2. I mean, without Windows... OGL will lose some programmers.

------------------------------
Trent (ShiningKnight)
E-mail me
Shining Darkness- A division of Chromesphere Studios

Share this post


Link to post
Share on other sites
IIRC multitexturing is a standard feature on OpenGL 1.2...The reason its still accessed through the extention mechanism is that OpenGL for Windows is still at 1.1, despite the 1.2 spec being finalized since forever.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
It is not a problem if Krosoft does not release an OpenGl 1.2 implementation!

If you have a decent graphic card, her driver support it.

If you have an old hardware, you can use the MESA software implementation.

And if you''re not happy with Billou, simply install Linux or buy a Mac!

Share this post


Link to post
Share on other sites
why don''t some smart programmers... (I''d volunteer) write an installer & build an implementation of OGL 1.2 for windows? If the support for 1.2 is in the opengl video drivers, can this be that hard?

Ranger

Share this post


Link to post
Share on other sites
quote:
Original post by Ranger_One
why don''t some smart programmers... (I''d volunteer) write an installer & build an implementation of OGL 1.2 for windows? If the support for 1.2 is in the opengl video drivers, can this be that hard?


SGI already did. Microsoft won''t let them release it, and just ignores it. Microsoft wrote one too, it''s been going through ''testing'' for way over a year now (from what I read in the ARB meeting notes).

[Resist Windows XP''s Invasive Production Activation Technology!]

Share this post


Link to post
Share on other sites
What? What''s this I hear?

Wow...from all the talk in the OpenGL vs DX debates, I was under the impression OpenGL only had one version and that it supports everything that''s coming out in the next 300 years...

G''luck,
-Alamar

Share this post


Link to post
Share on other sites
quote:
Original post by Alamar

What? What''s this I hear?



Wow...from all the talk in the OpenGL vs DX debates, I was under the impression OpenGL only had one version and that it supports everything that''s coming out in the next 300 years...




OpenGL supports anything that can be made into an extension in any version. New versions mean that extensions become standard features, and you can always expect a 100% complient set of drivers to have that feature instead of testing for it first .

[Resist Windows XP''s Invasive Production Activation Technology!]

Share this post


Link to post
Share on other sites
u c there is one problem with opengl ... its too bloody good!! i meen look at it version 1.1 has been around since about 1995 and has been desighed in such a way that this veriosn could posibly go on forever (still want 1.3 though) just goes show how u should create software!!!

~prevail by daring to fail~

Share this post


Link to post
Share on other sites
Sarcasm about something you do not understand is not a good idea. I have the impression that Alamar thinks the new version is about support for new features like a new version of DX.

Share this post


Link to post
Share on other sites
I stopped caring about microsoft. If we all develop games or other programs with 1.3 and windows isn''t supported then we''ll have to develop for linux and other operating systems. Microsoft will learn sooner or later

-----------------------------------------------------------
"People who usualy use the word pedantic usualy are pedantic!"-me

Share this post


Link to post
Share on other sites
Yeah,

I know that like most of the people are using Windows, so if you develop for another OS, you won't make a lot of sales / get popularity, but if you want Microsoft to change, going along with their schemes isn't going to help. I too have finally given up on caring about MS, I just use their stuff. I hope MS has a change of heart (yeah, right), and decides to make available 1.3. Where's a good OpenGL chat? I've given up on NeHe's... =[
but who am I to tell you all what to do? I still program for Windows (because I don't have Linux).

IT'S TIME TO START A REVOLUTION!

_Buster_

oh by the way Buster != _BUSTER_


dotspot.cjb.net
______________________________
Check out my for sale domain name!

http://www.Theatermonkey.com



Edited by - _BUSTER_ on August 16, 2001 3:29:39 AM

Share this post


Link to post
Share on other sites

  • Announcements

  • Forum Statistics

    • Total Topics
      628388
    • Total Posts
      2982403
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • 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.
  • Popular Now