Sign in to follow this  
Paddon

OpenGL GLSL Question

Recommended Posts

Paddon    128
Hey all, I am using the Irrlicht3D engine to develop a Visualization application for my current research. However, since I am developing on a mac I am using OpenGL rendering with Irrlicht. I have written my own, basic shader to use with irrlicht but I am not quite sure how I communicate from within the program, to the shader. Essentially I want to be able to draw a 3d cube (or sphere) and control the color and alpha value of it from within my program. Does anyone know how I do this? Here are my working vertex and fragment shaders, and everything looks exactly how I would like it to, all that is left is figureing out how to mesh it with my code. Vertex Shader:
	void main() {
	
		vec3 normal, lightDir;
		vec4 diffuse;
		float NdotL;
		
		/* first transform the normal into eye space and normalize the result */
		normal = normalize(gl_NormalMatrix * gl_Normal);
		
		/* now normalize the light's direction. Note that according to the
		OpenGL specification, the light is stored in eye space. Also since 
		we're talking about a directional light, the position field is actually 
		direction */
		lightDir = normalize(vec3(gl_LightSource[0].position));
		
		/* compute the cos of the angle between the normal and lights direction. 
		The light is directional so the direction is constant for every vertex.
		Since these two are normalized the cosine is the dot product. We also 
		need to clamp the result to the [0,1] range. */
		NdotL = max(dot(normal, lightDir), 0.0);
		
		/* Compute the diffuse term */
		diffuse = gl_FrontMaterial.diffuse * gl_LightSource[0].diffuse;
		
		gl_FrontColor =  NdotL * diffuse;
		
		gl_Position = ftransform();
	}
Fragment Shader:
void main()
	{
		gl_FragColor = gl_Color;
	}
Any help would be greatly appreciated. Thanks.

Share this post


Link to post
Share on other sites
mrbastard    1577
Uniforms In your case you want 1 vec4 uniform - colour + alpha

IIRC Irrlicht supports GLSL uniforms through video::IMaterialRendererServices::setVertexShaderConstant and video::IMaterialRendererServices::setPixelShaderConstant.

Irrlicht didn't treat sampler (texture) uniforms correctly last time I tried though, so watch out! It also has no VBO support...

Share this post


Link to post
Share on other sites
Paddon    128
I think that is ok because I am really just looking for the basics. This application (probablly) will never invoke textures or anything beyond efficent alpha blending.

Share this post


Link to post
Share on other sites
Paddon    128
So essentially, in my fragment program I can just have a uniform vec4 named "color". Then set it gl_FragColor = color. And use the setPixalShaderConstant() function to assign this variable color the color and alpha values I choose?

Also, which matricies do I have to set. I notice in the ittlicht tutorial they set the mInvWorld, mWorldViewProj, mLightPos, mLightColor, mTransWorld. What are the neccessary, analogous ones for GLSL?

Share this post


Link to post
Share on other sites
mrbastard    1577
sounds like you have the gist of it. Though if you wanted to keep your per vertex lighting you'd want to have the frag colour = NdotL * colour

you could also pass through the colour as one of the material parameters - say GL_DIFFUSE. This would mean you could leave your shaders as they are.

I'm not sure how Irrlicht matrices map to opengl ones. Irrlicht is heavily based around d3d, so I'd guess it'd be something like that. If your current shader is working though, it means you have the correct modelview and projection matrices already.

Share this post


Link to post
Share on other sites
MARS_999    1627
Quote:
Original post by Paddon
So essentially, in my fragment program I can just have a uniform vec4 named "color". Then set it gl_FragColor = color. And use the setPixalShaderConstant() function to assign this variable color the color and alpha values I choose?

Also, which matricies do I have to set. I notice in the ittlicht tutorial they set the mInvWorld, mWorldViewProj, mLightPos, mLightColor, mTransWorld. What are the neccessary, analogous ones for GLSL?


I have no exp with ittlicht, but those matrices are for DX/HLSL. GL/GLSL doesn't use them per se. They are upload to GLSL from OpenGL and you call matrices like


worldMatrix = gl_ModelViewMatrix
worldInverseTranspose = gl_ModelViewMatrixInverseTranspose
worldViewProjection = gl_ModelViewProjectionMatrix


Share this post


Link to post
Share on other sites
V-man    813
You could always define those matrices in your GLSL shader and set them with Irclics functions.

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