## Recommended Posts

Hello, I have a 2d opengl game (orthogonal projection) that I am working on. I want to mess around with shaders so I attempted to implement CG into my program. I can compile and set the shaders just fine, however I am having some trouble actually altering anything with shaders. When I apply a shader to a quad for example, it tends to just disappear completely. I have a feeling this is because I am using orthogonal projection, do I need to tell CG my screen coordinates for example? Additionally I am not attempting any complex shaders, just things that should alter the color of a quad. Any help is appreciated.

##### Share on other sites
When using shaders, you have to apply the modelview and projection matrices yourself, i.e. in your shader.

The output will be a coordinate in screen coordinates, i.e. in range [-1,1] for x and y and [0,1] for z. If a vertex lies outside that range it will be clipped away. If all of your quad's vertices lie outside, your quad might get clipped away completely.

As a short test (to get your shaders working) render a triangle with coordinates (-0.5,-0.5,0.0), (0.5,-0.5,0.0), (0.0, 0.5, 0.0) which should appear right in the center of the screen if you don't apply any transformations in the shader (note that this assumes that front facing polies are CCW wound).

##### Share on other sites
Thanks for your reply. When I disabled orthogonal projection, I was able to render the triangle like you suggested. This worked, my shader turned the triangle green.

But how would I apply the modelview and projection matricies when using orthogonal projection?

##### Share on other sites
Generally it works the same way. Your orthogonal projection matrix might be faulty, however. How did you set it up?

##### Share on other sites
Hi, the following is my code to enable 2d.

GLint iViewport[4];
glGetIntegerv( GL_VIEWPORT, iViewport );
glMatrixMode( GL_PROJECTION );
glPushMatrix();
glOrtho( iViewport[0], iViewport[0]+iViewport[2],
iViewport[1]+iViewport[3], iViewport[1], -1, 1 );
glMatrixMode( GL_MODELVIEW );
glPushMatrix();
glPushAttrib( GL_DEPTH_BUFFER_BIT | GL_LIGHTING_BIT );
glDisable( GL_DEPTH_TEST );
glDisable( GL_LIGHTING );

But I think it's like you said, I need to apply the modelview and projection matrices myself in my shader. Right now the shader I am using doesn't appear to be handling any of that. I am using a sample shader provided with the cg library. I am just unsure how to have the shader modified so that it outputs the correct screen coordinates. Right now when I apply the shader to a quad in 2d mode the quad appears a lot bigger than it should be, it's green, but the location and size is not what it should be.

The following code is my shader, if anyone can give me any help with getting this to work I would appreciate it, even if it's just the commands required to get it to work, as right now I am almost completely clueless.

// This is C2E1v_green from "The Cg Tutorial" (Addison-Wesley, ISBN
// 0321194969) by Randima Fernando and Mark J. Kilgard. See page 38.

struct C2E1v_Output {
float4 position : POSITION;
float3 color : COLOR;
};

C2E1v_Output C2E1v_green(float2 position : POSITION)
{
C2E1v_Output OUT;

OUT.position = float4(position,0,1);
OUT.color = float3(0,1,0);

return OUT;
}

[Edited by - evilsanta on June 25, 2009 1:04:29 AM]

##### Share on other sites
First, your shader need the modelview and projection matrices as uniform parameters, next you need to apply them. Since the combined modelview projection matrix (mvp) doesn't change during shader execution you might calculate it on the CPU and pass the result to the shader.

// This is C2E1v_green from "The Cg Tutorial" (Addison-Wesley, ISBN
// 0321194969) by Randima Fernando and Mark J. Kilgard. See page 38.

struct C2E1v_Output {
float4 position : POSITION;
float3 color : COLOR;
};

C2E1v_Output C2E1v_green(float2 position : POSITION, uniform float4x4 mvp)
{
C2E1v_Output OUT;

OUT.position = mul(mvp, float4(position,0,1));
OUT.color = float3(0,1,0);

return OUT;
}

##### Share on other sites
Hello again,

I modified my shader code to match yours. I still seem to be having trouble getting it to work though. The following is my code that multiplies the two matrices. It seems like it is correct, am I using the correct set parameter command?

GLfloat modelview[16];
glGetFloatv(GL_MODELVIEW_MATRIX , modelview);

glMatrixMode(GL_PROJECTION_MATRIX);
glMultMatrixf(modelview);

GLfloat output[16];
glGetFloatv(GL_MATRIX_MODE, output);

cgGLSetParameterArray4f( mvp,0,16,output);

##### Share on other sites

If you don't activate a vertex shader, fixed function pipeline will take care of the projection matrices for you.

##### Share on other sites
You might use cgGLSetMatrixParameterfc(...) or - for simplicity - cgGLSetStateMatrixParameter(<your parameter>, CG_GL_MODELVIEW_PROJECTION_MATRIX, CG_GL_MATRIX_IDENTITY); With the second, CG will handle the reading and multiplication for you.

##### Share on other sites
Quote:
 Original post by Lord_EvilYou might use cgGLSetMatrixParameterfc(...) or - for simplicity - cgGLSetStateMatrixParameter(, CG_GL_MODELVIEW_PROJECTION_MATRIX, CG_GL_MATRIX_IDENTITY); With the second, CG will handle the reading and multiplication for you.

I use that and it works great... saves a lot of math for me... although the inverse modelview matrix calc was broken until last release.

##### Share on other sites
cgGLSetStateMatrixParameter worked perfectly!

Thanks for the help.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
627719
• Total Posts
2978790
• ### Similar Content

• Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
So, here's what the plan is so far as far as loading goes:
Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!

• I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks

• A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

-What I'm using:
C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.
-Questions
Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.

• 9
• 21
• 14
• 12
• 42