artifacts using custom lighting model #pragma glsl w deferred lighting

I noticed that (on my mac) i get these artifacts when i use a custom lighting model, #pragma glsl, deferred lighting, a directional light.
Interestingly, on the same machine in win bootcamp the issue is not there. nor is it in forward rendering.

its not the lighting model itself because as a test i copied it exactly from the Lighting.cginc file.
it isnt using #pragma hlsl either. it is only when i use both together.(I do need to use a custom lighting model glsl)

I think it is my video driver (nvidia hasnt updated in two years) but is a shame because i need to get a new machine to work and also others w my set up will see the issue. forcing the shader to render in forward mode does not fix it. only turning off receive shadows fixes it.

another interesting bit is that if i use Pass{anything} the spots turn black.

has anyone seen this behavior? i could continue to develop but i don't want to screw people with my set up.

 

Do you have some vertex displacement or tessellation in there?
If it's the same issue I have, if you translate all the vertices in the vertex shader you'll see a second sphere.

 

nope, no vertex manipulation.

 

Hey, I can confirm this.

Getting the same error on mac(OSX) when using #pragma glsl.
Even the most basic shader, regardless if its a vertex/fragment shader or a surface shader.
Strange streaking blobs and artifacts appear on the surface of the model.

Would be great if someone could shed som light on this.

Cheers

 

I'm having this exact same problem. Even with the simplest of shaders, just adding #pragma glsl causes this artifacting. Any ideas?

 

bump

 

le me necro bump this thread.
Just curious did this issue is fixed? anyone have a fix for this?

 

The related issue with custom lighting models and vertex displacement is fixed in Unity 5, so I guess this one is too? I doubt they'll fix it in 4.x though.

 

Damn.....well that's kinda annoying, then what happen with some developer that stuck in Unity4 and developing for Mac :/

 

I'm just guessing because it's probably fixed in U5 indirectly together with other changes in the area. If you fill a bug report they may fix it anyway.

I'm not sure if it'll work, but as a workaround you may try adding a depth offset of a pixel in your shader.

 

Using depth offset are working, thanks for reminding me about that .
I'll test it out any further.