I've written a lighting shader (vertex and fragment ones) based on phong-model. My shader calculates ambient, diffuse and specular light components, taking into account the attenuation of lights with distance also. My scene has the one mesh node (table) having three materials with different textures and two point light sources radiating light from the fixed positions. My problem is that the light on that table is not blended with its textures, and total textures look just monotonous:
How my textures look like:
What do I do here wrong? I also tried to multiply gl_Color with the total color (I use GLSL 1.1), but that only did the model look like fully dark.
You need to give access to the link (edit: works now). But my very first guess from just seeing the image and no further info would be bad uv's. Looks like you might only use a single pixel from the texture. To test you can put some really strange colors on all 4 corner pixels of your texture and see if you get one of those.
Nice. I noticed while looking at my shaders that I don't use gl_TexCoord but a custom varying variable. It seems gl_TexCoord was deprecated after version 1.2. So if you want to use ES2 or any newer shader version you should probably no longer use gl_TexCoord either.
For example in many shaders your first line will be something like: #version 430 compatibility
That allows you to access newer shader functionality, but variables like this one will no longer be there.
And if you need more examples in Irrlicht, check out the media/Shaders folder in the ogl-es branch of Irrlicht. Thought it only does vertex lighting I think (as it just tries to emulate old fixed-function pipeline).
CuteAlien wrote: Mon Jul 10, 2023 10:37 am
Nice. I noticed while looking at my shaders that I don't use gl_TexCoord but a custom varying variable. It seems gl_TexCoord was deprecated after version 1.2. So if you want to use ES2 or any newer shader version you should probably no longer use gl_TexCoord either.
For example in many shaders your first line will be something like: #version 430 compatibility
That allows you to access newer shader functionality, but variables like this one will no longer be there.
And if you need more examples in Irrlicht, check out the media/Shaders folder in the ogl-es branch of Irrlicht. Thought it only does vertex lighting I think (as it just tries to emulate old fixed-function pipeline).
Yes, I know that varyable is deprecated and even was deleted in 3.3 afaik. My reason why I selected 1.1 for shaders is I don't know how to pass varying varyables from OnSetConstants() to them. IMaterialRendererServices has methods setting only contants (uniforms), but like not varying.
Also, I suppose does GLSL 1.1 not support multiple render targets for that reason there is the only output (gl_FragColor) in the fragment shader? It would be useful to me for implementation of the bloom effect.
gl_MultiTexCoord0 is still used even in newer GLSL. So the difference with newer shader is basically that you create a varying in your vertex shader and copy it into that one instead of into gl_TexCoord as above. And well, in newer glsl there is also no longer "varying" - it's now "out" in vertex shader and "in" in pixel shader.
MRT's... hm, would have to look up, not sure right now if I have an example for those. None in Irrlicht examples. Maybe search forum, I'm pretty sure I've seen it discussed once. But in theory you should be able to use glFragData[0] and glFragData[1] to write different values to different render targets.
