• Advertisement

Archived

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

OpenGL Newer OpenGL API?

This topic is 5875 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I have downloaded Dev-C++ and started learning OpenGL. The readme.txt in the OpenGL section says that the gl files are from Windows 95. Do I need newer versions of these files? I''m working on a NT ServPack 6 system. If so, where can I get them? I can only access the internet through a browser, so I don''t think the GLsetup.exe is going to work. subnet_rx

Share this post


Link to post
Share on other sites
Advertisement
Microsoft hasn''t released a new OpenGL MCD for Windows in ages, so you probably have the newest. What you do probably need, however, is the newest OpenGL drivers for your video card (for NT, of course). GLsetup just automatically detects and then installs the detected video drivers anyway.

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

Share this post


Link to post
Share on other sites
quote:
Original post by subnet_rx
Ahh, so eventhough my video drivers are OpenGL 1.3 compatible, the API is the same as was in 1.1?

In Windows, yes. If you read the OpenGL ARB notes, they have been mad at Microsoft for not updating the MCD for a while. SGI offered to write it for them, but Microsoft wants to ship their personal updated MCD with Windows (if any at all). I''m not sure, but I think SGI already wrote one for Windows. Most other OS''s have an OpenGL 1.2 (if not 1.3) implementation already. This is sore point of mine, in case you haven''t noticed .

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

Share this post


Link to post
Share on other sites
so, how would you implement the 1.3 specification yourself? Or is all OpenGL games in Windows running under 1.1?

Share this post


Link to post
Share on other sites
quote:
Original post by subnet_rx
so, how would you implement the 1.3 specification yourself? Or is all OpenGL games in Windows running under 1.1?

They all technically run in OpenGL 1.1, but they can call features that were standardized in 1.2/1.3 through extensions.

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

Share this post


Link to post
Share on other sites
In Linux, is the latest MESA 4.0 compliant with the OpenGL 1.3 API?

I''m still a little confused as to the difference between using MESA vs. OpenGL. I realize that the syntax is the same, so is the difference mostly legal? I.e., I don''t need to procure a license to distribute a game?

I''m also wondering if I use certain game SDK''s such as ClanLib if it can be used with MESA. In other words, wherever I can use OpenGL I can use MESA as it is transparent to the system?

Share this post


Link to post
Share on other sites
ok, the way I understand it is. The OS makes a platform available for OpenGL. In Microsoft Windows, Microsoft makes OpenGL available, in Linux, MESA makes the libraries available. Apparently, MESA keeps up with the OpenGL specification, MS does not.

subnet_rx

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
> I''m not sure, but I think SGI already wrote one for Windows

I already heard that several times. Does anybody know, where to get this SGI implementation ?

Share this post


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

I''m still a little confused as to the difference between using MESA vs. OpenGL. I realize that the syntax is the same, so is the difference mostly legal? I.e., I don''t need to procure a license to distribute a game?

I''m also wondering if I use certain game SDK''s such as ClanLib if it can be used with MESA. In other words, wherever I can use OpenGL I can use MESA as it is transparent to the system?


Hi,

Mesa is work alike for opengl but its not opengl itself.

Regarding license you might want to look at this link.
http://www.opengl.org/developers/license/license.html

By the way games fall into the application area.

Share this post


Link to post
Share on other sites
Mesa is really a OpenGL implementation with a different name. You do not have to worry about any license. I think that compiling Mesa yourself so it will take advantage of hardware acceleration (DRI) can be difficult.

If your version is 1.3 do you also have software implementations of functions that your card does not support. The difference between the extensions and software core functions is speed (surprised ) and often other limitations like just smaller textures being supported. I would say you are using 1.3 but you have to get entry points for core functions the same way as for extensions.

Intel made a little library that will make using the latest version and extensions a little easier special on Windows. It is available here
http://oss.sgi.com/projects/ogl-sample/sdk.html

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
> Intel made a little library that will make using the latest version and extensions a little easier special on Windows

Intel ? You mean SGI

Share this post


Link to post
Share on other sites
Yeah like the Anon Poster said... Every body mentions that SGI has made there own OGL 1.3 libs is this true and where can you get them?

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Hmm, isn''t that funny, everybody always talks about those ''newer SGI libs'', but no one seems to have them or be able to point to a D/L location.

I''m starting to believe, that all this is nothing but a myth, used by Windows OGL programmers to justify their lack of recent OGL support when talking to Linux/Irix/Mac/Solaris users.
aka:

Linux_User: ''Hey, look, I''ve a nice OGL app. Do you want the source ?''
Windows_User: ''Sure, it looks good, and with minor modifications, I''ll compile it under MSVC++ !''
Linux_User: ''No, you won''t. It uses recent technology. OGL 1.3. You Windows users only have access to the obsolete 1.1 version due to Microsoft-stupidity''
Windows_User: ''Hmmm.. yeah I know,.. but.. uh.. uhm.. *cough*.. SGI is making an OGL 1.3 release !!''

Share this post


Link to post
Share on other sites
I'm not aware of any SGI version of OpenGL 1.3 for Windows, but at one point SGI *did* write their own OpenGL implementation, back in the 1.1 days. It was significantly faster than Microsoft's OpenGL implementation when doing software rendering..But then A) everyone got 3D hardware, making the software rendering speed pretty meaningless (and it was still pretty slow if you did anything complex, just a lot faster than MS's software rasterizer) and B) Microsoft and SGI joined forces on Farenheit, a set of 3D APIs which were supposed to replace D3D and OpenGL, with both immediate and scene graph mode (Like the old D3DRM) APIs. Farenheit fell apart sometime a year or two ago and nothing much came of it. IIRC Microsoft did eventually release the scene graph part of Farenheit to a limited audience, but I havent heard anything about it in a long long time so I'm guessing they killed that off too.

I just did a quick google search and it looks like you can still get the SGI OpenGL SDK here:

http://www.berkelium.com/OpenGL/

Its completely unsupported though (and hasn't been supported since Windows 95, IIRC) and it has a few major known bugs that cause crashes. So all in all you don't want to use it.




If SGI does have a new 1.3 implementation, I haven't seen it. And yes, it is rather annoying that Microsoft has been dragging their feet so much on OpenGL. And its clearly all political (make OpenGL look dead on Windows to try and get more support for D3D).



Edited by - gmcbay on December 21, 2001 5:04:33 AM

Share this post


Link to post
Share on other sites
Umm us windows opengl coders have no problems accessing the 1.3 features.

As for the SGI libs, from what Ive heard, microsoft refuses to let them release the libs, most likely in a vain attempt to get more people using d3d.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
> Umm us windows opengl coders have no problems accessing the 1.3 features.

No, you have to do it via extensions. Not all features are accessible that way, and even worse, it isn''t compatible with legacy 1.3 code.

> As for the SGI libs, from what Ive heard, microsoft refuses to let them release the libs, most likely in a vain attempt to get more people using d3d.

Microsoft can not stop anyone releasing OpenGL libs. Especially not SGI, since they developed OpenGL, and have all the rights, patents (if there are any), and trademarks. Releasing OGL libs doesn''t involve *any* M$ source. See Mesa.

I just don''t believe that SGI has actually written 1.3 libs for Windows. It''s more likely it is a ''Windows OpenGL user justification legend''.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Ok, guys.

SGI has written only one OpenGL implementation(v 1.1) for windows in year 1995.
There doesn''t exist any implementation of v1.2 , not saying v1.3
for Windows.
All functions of v1.2, v1.3 must be querried by glGetProcAddress as extensions.
Intel(Intel, not SGI!!!) has written a library, something like GL... howewer, I forgot. Idea is that this library is querring v1.2 funtions for you.

Best wishes.

Zengar.

Share this post


Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By reenigne
      For those that don't know me. I am the individual who's two videos are listed here under setup for https://wiki.libsdl.org/Tutorials
      I also run grhmedia.com where I host the projects and code for the tutorials I have online.
      Recently, I received a notice from youtube they will be implementing their new policy in protecting video content as of which I won't be monetized till I meat there required number of viewers and views each month.

      Frankly, I'm pretty sick of youtube. I put up a video and someone else learns from it and puts up another video and because of the way youtube does their placement they end up with more views.
      Even guys that clearly post false information such as one individual who said GLEW 2.0 was broken because he didn't know how to compile it. He in short didn't know how to modify the script he used because he didn't understand make files and how the requirements of the compiler and library changes needed some different flags.

      At the end of the month when they implement this I will take down the content and host on my own server purely and it will be a paid system and or patreon. 

      I get my videos may be a bit dry, I generally figure people are there to learn how to do something and I rather not waste their time. 
      I used to also help people for free even those coming from the other videos. That won't be the case any more. I used to just take anyone emails and work with them my email is posted on the site.

      I don't expect to get the required number of subscribers in that time or increased views. Even if I did well it wouldn't take care of each reoccurring month.
      I figure this is simpler and I don't plan on putting some sort of exorbitant fee for a monthly subscription or the like.
      I was thinking on the lines of a few dollars 1,2, and 3 and the larger subscription gets you assistance with the content in the tutorials if needed that month.
      Maybe another fee if it is related but not directly in the content. 
      The fees would serve to cut down on the number of people who ask for help and maybe encourage some of the people to actually pay attention to what is said rather than do their own thing. That actually turns out to be 90% of the issues. I spent 6 hours helping one individual last week I must have asked him 20 times did you do exactly like I said in the video even pointed directly to the section. When he finally sent me a copy of the what he entered I knew then and there he had not. I circled it and I pointed out that wasn't what I said to do in the video. I didn't tell him what was wrong and how I knew that way he would go back and actually follow what it said to do. He then reported it worked. Yea, no kidding following directions works. But hey isn't alone and well its part of the learning process.

      So the point of this isn't to be a gripe session. I'm just looking for a bit of feed back. Do you think the fees are unreasonable?
      Should I keep the youtube channel and do just the fees with patreon or do you think locking the content to my site and require a subscription is an idea.

      I'm just looking at the fact it is unrealistic to think youtube/google will actually get stuff right or that youtube viewers will actually bother to start looking for more accurate videos. 
    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
  • Advertisement