• Advertisement
Sign in to follow this  

OpenGL Confuse with OpenGL, SFML, and its library

This topic is 1930 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

Hi guys, I am a beginning to enter the world of game development.

Lately, I researched that "[b]OPENGL[/b]" is one of the tools to use in graphics,
then I found out about "[b]SFML[/b]" (I think that its a library or something that uses opengl).


I am so confuse because all books/ sites said using "GLUT",
but many people/fellow developers said that I must use a more updated one like "SFML"
but sfml has few/none tutorials.


What I am trying to say is "how to create own library or something like your own glut or sfml",
and why does opengl has no source code? And how can I use the EXACT(not glut/sfml) opengl in my c++
program?

I am so confuse....

Share this post


Link to post
Share on other sites
Advertisement
Look at is as layers of an onion. At the very center you have the graphics hardware. The interface to the hardware (the hardware functions and things that make it tick... or make it go boom, in many cases) are vendor-protected trade secrets. They don't want you mucking with these, really. On top of the hardware sits a vendor-created software layer called a driver. Again, this layer is vendor-protected, but it provides an outward-facing API of sorts, by which an interested party can communicate with the hardware. On top of this layer sits OpenGL and Direct3D. They act as go-betweens in between the application and the driver interface, providing an easy to use interface that is maintained and standardized across hardware vendors so that the application developer can count on some consistency regardless of the hardware his end users are using.
On top of OpenGL and (frequently) Direct3D sit multiple third-party libraries and APIs such as Glut, GLFW, SFML, SDL, etc... The purpose of these libraries is much more varied, and their implementations can be vastly different. One state purpose of them is often to abstract away the details of the underlying API. For example, Ogre, Irrlicht, Urho3D, etc... they all provide API-specific backends upon which sits API-indifferent front-end code. You can select (whether at run-time, at compile-time, or whatever) whether to use Direct3D or OpenGL on the backend, but the front-end code remains the same due to the abstraction layer. The library developer takes care of the specifics of dealing with the different APIs so you don't have to.

Some libraries, though, like SFML deal only with the one API (OpenGL, in this case). However, its stated goals are a bit different than just abstracting away the graphics API. SFML purports to be mainly a 2D library, and so it provides various abstractions to facilitate 2D tasks. Whereas in OpenGL, there is no concrete concept of a sprite (you can do sprites, it just requires building a bit of foundation code), in SFML you can deal in Sprites and Shapes, and all the foundational stuff is done for you.

It's all about abstraction. That's pretty much what games are: layers of software sitting on top of other layers of software that abstract away lower level details, exposing a higher-level interface.

Edit:

There is OpenGL code available (of sorts). Google for Mesa3D. It is an open-source software version of OpenGL. However, the hardware versions are typically also created by the hardware vendor as a convenience for developers, or provided by the operating system. Seeing the source code of OpenGL really isn't a productive thing; it's complex, rife with hardware specifics and implementation dependencies, and just not a useful learning tool.

As far as just using OpenGL in your application (no third party libraries), this is highly dependent upon the OS, as you will need to use OS-specific functions for creating a window, initializing the message queue, obtaining an OpenGL context through OS-specific calls, etc... It's at once both a simple and a complex process, and is a task that is made vastly easier using one of the aforementioned third-party libraries. For example, with SFML you can use the library to create the window and set up OpenGL, then just use basic OpenGL calls from then on. You are not forced to use any of the other abstraction stuff.

Also, by the way, SFML has plenty of [url="http://www.sfml-dev.org/tutorials/"]tutorials[/url]. More than enough to learn the library. Go ahead and work through the 1.6 tutorials as well, since most of that stuff is still relevant, with a few API changes. Edited by FLeBlanc

Share this post


Link to post
Share on other sites
overwhelming thanks.. :)

I find many knowledge in your answer.
in the other forums, one said about "Rendering Context"
What is it, and is it even platform-specific and what is the product of using rendering context?

Share this post


Link to post
Share on other sites
The rendering context in OpenGL is a chunk of data that represents the current "state" of the renderer. It maintains current texture, current buffers, blend settings and all that. Any time you call an OpenGL call, it either sets/gets values to/from the context, or it operates on data held within the context. If you bind a texture, there is a data field somewhere in the context that is set to reflect that.

Share this post


Link to post
Share on other sites
Now I understand (a bit),
First of all, Thanks for taking time for my questions. I find myself that I must master C++ before venturing in opengl,
thank you, hope to meet you again online when I finish my first game :)

Share this post


Link to post
Share on other sites
[quote name='FLeBlanc' timestamp='1349533190' post='4987395']
There is OpenGL code available (of sorts). Google for Mesa3D. It is an open-source software version of OpenGL. However, the hardware versions are typically also created by the hardware vendor as a convenience for developers, or provided by the operating system. Seeing the source code of OpenGL really isn't a productive thing; it's complex, rife with hardware specifics and implementation dependencies, and just not a useful learning tool.
[/quote]

Some clarification of a common misunderstanding needs to be added to this. The "open" in OpenGL does [u]not[/u] stand for "open source"; it means that it's an open [i]standard[/i]. It has a published specification which vendors implement in their drivers (or purely in software in the case of Mesa) but OpenGL itself is [u]not[/u] software and it's quite meaningless to speak of source code for OpenGL. One can speak of source code for an OpenGL [i]implementation[/i], such as NVIDIA's, AMD's, Intel's or Mesa, but this source code would be vendor-specific and utterly useless outside of the vendor's own driver. Edited by mhagain

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