Sign in to follow this  
m4rqz

OpenGL Using OpenGL shaders with GLFW

Recommended Posts

m4rqz    122
Hello folks! This is my first post to these forums :) I'm developing a little game using glfw/opengl and I wanted to try out vertex/fragment shaders. The problem is that I can't compile my code.. either the functions needed to use shaders are not found (when I include only GL/glfw.h) or the linking fails when I #define GL_GLEXT_PROTOTYPES and include GL/glext.h .. I know my video card (radeon 9600 mobile) supports shaders, so what can be wrong here? Do I have to use glfwGetProcAdress to get shader functions when glfwGetGLVersion return 2.0 ? Btw, I want to use glfw, so don't tell me to switch unless glfw can't handle shaders. Also, I'm not running windows, but I have official ATI video drivers, let's leave it there. Cheers

Share this post


Link to post
Share on other sites
bubu LV    1436
Quote:
Original post by m4rqz
Do I have to use glfwGetProcAdress to get shader functions when glfwGetGLVersion return 2.0 ?

Yes.

Quote:
Btw, I want to use glfw, so don't tell me to switch unless glfw can't handle shaders.

GLFW is just for Window creation, input reading from keyboard/mouse and some other stuff which doesn't connects to shaders and OpenGL in general at all.
All OpenGL calls are made through OpenGL library not GLFW.

Share this post


Link to post
Share on other sites
nefthy    184
Quote:
Original post by Kalidor
If you're on Windows, everything beyond OpenGL 1.1 needs to be accessed as an extension. Read the Forum FAQ for information on using extensions.


He said that he is not running windows :)

getProcAddress is the right way to do it. You can define GL_GLEXT_PROTOTYPES but make sure that it is defined before any GL headers get included. Its probably the best to pass it as a compiler option (-DGL_GLEXT_PROTOTYPES if you are using gcc). But be aware that there are some drawbacks to this methode.

Share this post


Link to post
Share on other sites
Kalidor    1087
Quote:
Original post by nefthy
He said that he is not running windows :)
Whoops... sorry about that. [embarrass]

EDIT: You should still be able to use GLee or GLEW for easing the use of extensions, however.

[Edited by - Kalidor on April 17, 2006 12:27:12 PM]

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now