Moderator: Moderators
Code: Select all
Pixel.R = 0.1 + GroundColor.X * 0.2;
Pixel.G = 0.1 + GroundColor.Y * 0.2;
Pixel.B = 0.1 + GroundColor.Z * 0.2;
Pixel.A = 1;Code: Select all
void main(void)
{
vec4 v = vec4(gl_Vertex);
gl_Position = gl_ModelViewProjectionMatrix * v;
}Not really, the RenderMesh component automatically enables & disables the client state for all used vertex attributes, so you'd have to write your own RenderMesh function that allows you to control which attributes you want to use ( or add this feature to the RenderMesh component ).
If you want to use shaders on Android make sure to check out GLES2Demo.zgeproj in the Projects folder that comes with ZGE.
That's exactly what I was looking at while you were respondingIf you want to use shaders on Android make sure to check out GLES2Demo.zgeproj in the Projects folder that comes with ZGE.
Try adding "#version 140" at the top of each vertex & fragment shader source in that example. Shader compilers have become a lot more strict over the past years ( if you're using recent GPU drivers ).
Weird, looks like there's some text-encoding issue going on ( at least with the errors ). Anyway, can you try removing the precision statements? It probably won't work on Android then, but perhaps that will make it work on Windows.
That demo doesn't have any precision statements. But it shouldn't work when switching to ES2/GL3 though .. what GPU do you have?
Are you running ZGameEditor in Wine or did you build a Linux standalone? And did you get the same results when trying ShaderDemo.zgeproj on Windows ( in case you tried that as well )?
Weird .. the "precision" statements should just be ignored unless you're running on ES or Vulkan. Quoted from the GLSL spec ( 1.3 and up ):
That doesn't make sense .. try switching to ES2/GL3 then saving the file as ShaderDemoES2 and then reloading it. Maybe it's using cached shader objects or something.
