Sign in to follow this  
Mariusz Pilipczuk

GLSL Vertex Shader error

Recommended Posts

Hello, I get an error while compiling my vertex shader. Here is the code for my shader:

GLSL vertex shader used by Madd Engine
void main()
gl_TexCoord[0] = gl_MultiTexCoord0;
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;

When I run my application, it outputs the InfoLog to a file, here it is:

Vertex info
(0) : error C0000: syntax error, unexpected $end at token "<EOF>"
(0) : error C0501: type name expected at token "<null atom>"

The same error occurs even if I comment out the entire shader code. Does anyone know where the problem is?

P.S. The fragment shader works as it should, here is the code:

GLSL fragment shader used by Madd Engine
uniform sampler2D tex;
void main()
vec4 texel = texture2D(tex, gl_TexCoord[0].st);
gl_FragColor = gl_Color * texel;
[/CODE] Edited by Madd

Share this post

Link to post
Share on other sites
BitMaster    8651
Is it possible you have invalid characters in the file? Depending on the editor an invalid character can easily slip with a copy'n'paste or accidental hotkey. A lot of editors will then pick a suitable encoding to encode the undesired character and it will often be invisble to the naked eye then.
Have you tried explicitely forcing ANSI encoding on the file (for example in Notepad++ Encoding->Convert to ANSI)? If the problem is a rogue character it will usually show up in an obvious way (the not-in-font symbol or 'weird' symbols).

Share this post

Link to post
Share on other sites
Here's the code for the loader:

[source lang="cpp"]
void meEnableShaders()
/* load the fragment shader */
char *frag_buffer, *vert_buffer;

FILE *fp = fopen("MaddEngine.frag", "rb");
int frag_size;
fseek(fp, 0, SEEK_END);
frag_size = ftell(fp);
fseek(fp, 0, SEEK_SET);
frag_buffer = (char*)malloc(frag_size);
fread(frag_buffer, 1, frag_size, fp);

/* load the vertex shader */
fp = fopen("MaddEngine.vert", "rb");
int vert_size;
fseek(fp, 0, SEEK_END);
vert_size = ftell(fp);
vert_buffer = (char*)malloc(vert_size);
fread(vert_buffer, 1, vert_size, fp);

me_fragment_shader = glCreateShaderObjectARB(GL_FRAGMENT_SHADER_ARB);
glShaderSourceARB(me_fragment_shader, 1, &frag_buffer, &frag_size);

me_vertex_shader = glCreateShaderObjectARB(GL_VERTEX_SHADER_ARB);
glShaderSourceARB(me_vertex_shader, 1, &vert_buffer, &vert_size);

me_shader_program = glCreateProgramObjectARB();
glAttachObjectARB(me_shader_program, me_fragment_shader);
glAttachObjectARB(me_shader_program, me_vertex_shader);
me_fragment_shader = glCreateShader(GL_FRAGMENT_SHADER);
glShaderSource(me_fragment_shader, 1, &frag_buffer, &frag_size);

me_vertex_shader = glCreateShader(GL_VERTEX_SHADER);
glShaderSource(me_vertex_shader, 1, &vert_buffer, &vert_size);

me_shader_program = glCreateProgram();
glAttachShader(me_shader_program, me_fragment_shader);
glAttachShader(me_shader_program, me_vertex_shader);

It is compiled without the ARB_SHADER macro (so it uses the standard OpenGL functions).

I edit the files with gedit under Ubuntu, which uses UTF-8. Edited by Madd

Share this post

Link to post
Share on other sites
L. Spiro    25619
After setting the stream to the end of the file and calling ::ftell(), you never set the stream back to the beginning of the file before you try to read it.
On the vertex shader.

L. Spiro

I stopped reading as soon as I saw the problem. Even if it was just one last post with a single sentence explaining the solution.
[/EDIT] Edited by L. Spiro

Share this post

Link to post
Share on other sites
V-man    813
Even if the problem has been found, it isn't a good idea to read a text file as binary because on some systems (Windows), end of lines are in the form of \r\n or was it \n\r.
It is better to open the file this way
FILE *fp = fopen("MaddEngine.frag", "r"); //changed the "rb" to "r"

and the library will automatically convert all the \r\n to \n (newlines).

and it is a good idea to NULL terminate the file string yourself.

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