• Advertisement
Sign in to follow this  

OpenGL How Could I Learn OpenGL ES 3.0?

This topic is 1967 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 am new to graphics programming, but am by no means new to programming. I might not be the seasoned veteran and trusted expert on C/C++, but I think my knowledge is sufficient. I am currently reading the book [u]Real Time Rendering, 3rd Edition[/u], and while it is very helpful, it does not teach a graphics API (I knew it didn't beforehand, and didn't expect it to). Seeing as OpenGL ES 3.0 spec was just released, I thought, "Why would I learn ES 2 when I can just learn the fully PC-compatible ES 3?" So, how would I learn it, when the specification was just ratified fairly recently, read the specification? And, while I'm at it, how do you program with OpenGL? I realize that it is a specification and not a full API, but I can't say I know anything about how to implement it.

P.S: Sorry for the annoying n3wb question [img]http://public.gamedev.net//public/style_emoticons/default/wink.png[/img]

Share this post


Link to post
Share on other sites
Advertisement
[quote name='MrJoshL' timestamp='1345174178' post='4970410']
Why would I learn ES 2 when I can just learn the fully PC-compatible ES 3
[/quote]

Because what matters are the underlying concepts. The core graphics concepts of sending geometry and creating shaders to process the geometry data probably hasn't changed much.

A common newbie mistake is hearing that professionals are using a Shiny Tool and think that if they use the Shiny Tool that it will make them like professional in a meaningful way. It won't. What you need to do as a new programmer is make sure you grasp the foundational concepts of graphics programming and can apply them in a well structured and scalable way.

Share this post


Link to post
Share on other sites
I agree that you should learn the underlying concepts, I would check out the nvidia opengl sdk, it has a wealth of knowledge (but you must understand that those are quicky demos and if you wanted a full engine you wouldn't mimic some of the things they do).

I also highly suggest checking out Humus' Framework3, It is a great reference for looking at the ins and outs of the various apis.

Share this post


Link to post
Share on other sites
@Lazy Foo I am not a "that's a shiny tool" person, or I would be using OpenGL 4.3. I am using OpenGL ES 3.0. I was going to do everything in OpenGL ES 2.0, but my main reason is functionality not "I want to be a shiny professional," because frankly, I have no interest of being a professional programmer in the graphics field or even a professional programmer at all (I'm getting an engineering degree). I just wanted (like almost everyone else) to have minimal code changes across different machines. That's all. I just wanted to know how I would learn such a recent specification. Should I read ES 2.0 books? Should I read the ES 3.0 specification? Both? That is all. And I might be a far shot from expert, but I wouldn't say I'm a complete beginner in C programming. I know how to do a few things at least.

@AverageJoeSSU Is the nVidia OpenGL SDK a full implementation of OpenGL? Does it come with a shader compiler?

Share this post


Link to post
Share on other sites
[quote name='MrJoshL'']Seeing as OpenGL ES 3.0 spec was just released, I thought, "Why would I learn ES 2 when I can just learn the fully PC-compatible ES 3?"[/quote]

OpenGL ES 2.0 is a good starting point because it is forward compatible with OpenGL ES 3.0, meaning the applications you develop for OpenGL ES 2.0 will work (with minor modifications in the vertex and fragment shading code) on OpenGL ES 3.0, as well as desktop OpenGL 2.1, OpenGL 3.x and OpenGL 4.x.

[quote name='MrJoshL'']So, how would I learn it, when the specification was just ratified fairly recently, read the specification?[/quote]

If you have a graphics card that supports OpenGL 4.3 (NVIDIA has released OpenGL 4.3 beta drivers), you can use an OpenGL ES 3.0 emulator. The Adreno 3.0 SDK for Windows and the Mali Developer SDK for Windows include an OpenGL ES 3.0 emulator. If you do not have an OpenGL 4.3 compatible graphics card, you could artificially restrict yourself to the OpenGL 3.3 core API to get an idea of what OpenGL ES 3.0 programming would be like.

If you are doing mobile development, OpenGL ES 3.0 for the iPhone likely will not be available until iOS 7 next fall, possibly later (Apple didn't support OpenGL ES 2.0 until 2 years after it was released in 2007). For Android, it's said to be already available from select vendors who sell debugging devices, but it probably won't be available for the mainstream user until early next year.

[quote name='MrJoshL'']And, while I'm at it, how do you program with OpenGL? I realize that it is a specification and not a full API, but I can't say I know anything about how to implement it.[/quote]

OpenGL is normally implemented by the graphics hardware vendors.

Share this post


Link to post
Share on other sites
[quote name='MrJoshL' timestamp='1345174178' post='4970410']
I am new to graphics programming, but am by no means new to programming. I might not be the seasoned veteran and trusted expert on C/C++, but I think my knowledge is sufficient. I am currently reading the book [u]Real Time Rendering, 3rd Edition[/u], and while it is very helpful, it does not teach a graphics API (I knew it didn't beforehand, and didn't expect it to). Seeing as OpenGL ES 3.0 spec was just released, I thought, "Why would I learn ES 2 when I can just learn the fully PC-compatible ES 3?" So, how would I learn it, when the specification was just ratified fairly recently, read the specification?[/quote]

Unless you have a good real-world ES3 device or platform to run your code on, I think it would be unnecessarily difficult to learn Open GL via jumping straight into its newest, only-just released iteration instead a version that currently sees vastly more widespread use. There's a wealth of easy and quick tutorials around the web for learning Open GL ES2, and I would highly recommend supplementing any reading you do with a good amount of tinkering to see what's what. I would expect anything you learn in ES2 to carry across to ES3, and in some respects being familiar with the history of an API can lead to a more robust grasp of its newer iterations.

[quote name='MrJoshL' timestamp='1345174178' post='4970410']
And, while I'm at it, how do you program with OpenGL? I realize that it is a specification and not a full API, but I can't say I know anything about how to implement it.[/quote]

It's really just a matter of instructing the GPU to perform certain tasks, provided with certain data. In a nutshell, you prepare buffers (this is already a complex area) for various processes - e.g. the one that'll be presented to a device's display for starters. Next, you prepare the shader programs that tell the GPU what to do with the data you'll be throwing at it, and lastly you supply vertex, uv, color, and various other information to the GPU so that it can be rendered.

^ nb: above is an extreme oversimplification - only intended to provide a rough idea. Each part of that process can run extremely deep in its complexity, depending on what you want to do.

Half the battle in OpenGL is often finding ways to create an image efficiently with minimal wasted/repeated/redundant effort on the hardware's part, but to start with, just get some stuff on your screen and learn the anatomy of the whole process incrementally.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • 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?
    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
  • Advertisement