• Advertisement
Sign in to follow this  

OpenGL OpenGL book reccomendation

This topic is 3622 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 All, I am considering getting OpenGL Programming for the X Window System but the reviews on amazon and the date it was published seem to indicate that this book is a little out of date. Is this the case and or does anyone have any more current suggestions for linux/OpenGL programming books? Thanks. -H

Share this post


Link to post
Share on other sites
Advertisement
Well OpenGL is cross platform, the only thing you might need to learn that is platform specific is the 'glx' family of functions, aside from them you can pick any OpenGL book, I recommend "OpenGL Game Programming" by Dave Astle, it's considered to be the gold standard around here.

I develop on linux actually, and I have NEVER touched glx myself(though I've looked it over), I just let SDL handle it for me, that's the method I personally endorse :-), but again, everything else will be cross platform (and the everything else part is far more important for creating fun and exciting games). Learn OpenGL, use either SDL (my vote), GLut, or glfw to handle initilialization, if you ever feel in the future that you (for whatever reason...) need to use glx directly (trust me, you don't need to, and you don't want to) you can just learn that family of functions.

Share this post


Link to post
Share on other sites
Quote:
Original post by Ademan555
Well OpenGL is cross platform, the only thing you might need to learn that is platform specific is the 'glx' family of functions, aside from them you can pick any OpenGL book, I recommend "OpenGL Game Programming" by Dave Astle, it's considered to be the gold standard around here.

I develop on linux actually, and I have NEVER touched glx myself(though I've looked it over), I just let SDL handle it for me, that's the method I personally endorse :-), but again, everything else will be cross platform (and the everything else part is far more important for creating fun and exciting games). Learn OpenGL, use either SDL (my vote), GLut, or glfw to handle initilialization, if you ever feel in the future that you (for whatever reason...) need to use glx directly (trust me, you don't need to, and you don't want to) you can just learn that family of functions.


Thanks for all the help guys. I currently own the red book and the blue book both of which are totally amazing books.

I was using SDL but unfortunately a feature I need (outputting opengl in full screen mode from a application across multiple monitors) is only tentatively supported in the very latest version which you need to grab/compile you're self from subversion (1.3).

At the moment I have managed to get dual head OpenGL going with xlib and glx. Xlib is pretty tricky and unintuitive to work with and trying to find out how to do something specific with the docs/examples is a bit of a nightmare. I eventually gave up reading articles and just looked at the source for xterm and pieced things together from that. Hence my feeling that I need a book on working with glx/xlib.

The main reason I don't want to play with sdl 1.3 is:

http://www.gamedev.net/community/forums/topic.asp?topic_id=380142


"SDL 1.3 is the experimental branch of SDL, where we will be breaking
binary compatibility and upgrading the API to fix a few shortcomings and
support new functionality. At one point SDL 1.3 had experimental render
to texture support, but it wasn't possible to maintain the same GL context
semantics on each platform, and it has been phased out in favor of the
OpenGL vertex buffer object extension. The original render to texture
code is in bugzilla as a patch relative to 1.3, for historical interest."

My ideal solution would be something that does dual screen and is cross platform has a decent timer and can handle very basic input.


My current bet is that writing my own wrapper for OSX/LINUX/Windows will probably be less work and easier to debug than dealing with the random stuff thats bound to come up with SDL 1.3. Any comments on this strategy? Anyone care to suggest another library?

Share this post


Link to post
Share on other sites
Ah, I see, you already knew what you were talking about then :-D.

Anyways, I don't really know what the best way to go about things is. I think you're *probably* right that you've got the best way to go about things (unfortunately). I'm not entirely sure if it's possible to setup "true" dual head support with glx without Xinerama, but I'm not very well versed in Xlib so I'll shutup now :-p.

I didn't really provide any useful information, but I'm going to post anyways, just in case me tossing around the name Xinerama actually turns out to be relevant information lol.

Share this post


Link to post
Share on other sites
I dont know about dual screen but GLFW has a very good timer(QueryPerfCounter) and handles input just fine.

Share this post


Link to post
Share on other sites
The latest "OpenGL SuperBible" 3rd edition I think, is a great book, it covers Linux, Win32, OSX

Share this post


Link to post
Share on other sites
Thanks guys, its great to get feedback and I really appreciate the sanity (or in the case of xlib insanity ;P ) check .

How I manged to get dual screen going with xlib/glx, was to use grandr under debian to create a 2048X768 virtual screen from my 2 1024x768 lcds. I then created two windows each with their own opengl context (dimensions of each being set to 1024 x 768). I then told x to move one window to 1024 using the xmove macro and then sent a full screen event/message to that window. I then created the other window at 0,0 and told it to fullscreen using the same technique. This seems to work and I can get opengl graphics going across both screns. I am not sure if this is the correct or even a nice way to do things but it's the only way I have found so far. Any suggestions or xlib code snippits would be most appreciated. I am planning on looking at how http://www.pyglet.org/ handles multiple screens cross platform to see if their is a better way to interface/do this with xlib.

Right now everything works fine provided I don't try to pole for events within my main loop. My problem is that trying to capture events using xlib and the next event function causes my application to only update when I move a mouse or press a key. Now I am guessing that this has something to do with the way the callback function for events works in xlib.

I have yet to figure out how glx informs x whenever it swap a buffer. One solution I am considering is creating an expose event (event triggered when one window moves over another in x) every time I need to swap a buffer. Now I don't think an event should be triggered every time a buffer is swapped and I don't think I need to add threads to my application just to pole for a few key presses. Hence I think I am doing something wrong and I should go read a good book or something.

So I guess a question would be, has anyone written any opengl applications which polled for events using glx/xlib. I am currently using the XNextEvent to check for key presses. Also could I use some other library/technique to check for inputs on linux?

Share this post


Link to post
Share on other sites
Quote:
Original post by MARS_999
The latest "OpenGL SuperBible" 3rd edition I think, is a great book, it covers Linux, Win32, OSX



Yeah I have that (the blue book), I started from the example in chapter 21 and modified it to work across 2 screens. Its a brilliant book but the chapter on linux is like 20 pages long and parts of that deal with glut. The main focus on the chapter is GLX; it gives you everything you need to setup a window that displays opengl which reacts to a mouse moving around. It doesn't really cover much of how xlib handles events (this is not really a flaw of the book just a reflection of how complicated xlib is). I am trying to have animated sprites moving on the screen and have xlib poll for events. The example in the book is a set of eyes that point where ever you move the mouse. The eyes only move when the mouse does.

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