Here is a simple slideshow demo. You load several images using the LoadTexture() (INIT script line 20) function and each texture is displayed during duration time (FRAME script lines 3 and 7).
It may be useful to know if the current OpenGL implementation supports a particular OpenGL extension. For example you have coded a cool OpenGL 4.0 demo based on tessellation shaders. It would be nice to display a different scene (actually an error scene) if the demo runs on a system that is limited to OpenGL 3.0.
Today we are going to see how to build and render a simple scene that includes a camera, a triangle, a reference grid and a GPU program (in GLSL). GLSL Hacker supports both Lua and Python programming languages. We will use Lua for this article. So let’s go!
This article describes what is GLSL Hacker and how it works.
GLSL Hacker does not come with a bloated graphical user interface. Instead, GLSL Hacker uses simple files (*.xml, *.lua, *.py, etc) to store a demo. All you need to create demos with GLSL Hacker is a simple text editor to edit these files.
I didn’t checked all possible use cases of GLSL Hacker (a huge and actually impossible task) and some sequences of drawing instructions (render calls) can generate OpenGL errors. So if you suspect something dodgy because the rendering is not what you expect, you can check the OpenGL errors after some particular instructions.
Do you know that you can use data structures as uniform variables in GLSL?
GL-Z has just been released on Geeks3D’s main blog. It’s a simple OpenGL tool that displays GL_VERSION, GL_RENDERER as well as extensions list.
This article will focus on one method to build and render a Rubik’s Cube with GLSL Hacker and can be used as a basis for a more advanced animation of the Rubik’s Cube.
Want to code a simple bouncing algorithmm? If so, read this article and play with the GLSL Hacker demos.