0
Fixed

A0.12 (Mac) - Errors when turning on LightMap Support

Andrei Nadin 11 years ago updated by Freya Holmér (Developer) 11 years ago 0

I get errors in the console with this shader on the Mac when I turn on Lightmap Support


Updating Assets/ShaderForge/Example Assets/Shaders/OpaqueSpecWrap.shader - GUID: d0ae98075f63349529af218e29b2d046...

Unsupported: Shader Forge/OpaqueSpecWrap

Unsupported: Shader Forge/OpaqueSpecWrap

 done. [Time: 2622.830078 ms] 

Shader 'Shader Forge/Examples/OpaqueSpecBumpedWrap': fallback shader 'Shader Forge/Examples/OpaqueSpecWrap' not found

Unsupported: Shader Forge/OpaqueSpecWrap

Shader warning in 'Hidden/Radial Blur Effect Shader': Program 'frag', Temporary register limit of 8 exceeded; 11 registers needed to compile program at line 14

Keywords:  (compiling for flash)

(Filename: RadialBlurEffect Line: 14)

Shader warning in 'Hidden/Radial Blur Effect Shader': Program 'frag', implicit cast from "half4" to "float3" at line 79

Keywords:  (compiling for flash)

(Filename: RadialBlurEffect Line: 79)

Shader error in 'Shader Forge/OpaqueSpecWrap': Shader program had errors at line 21

(Filename: OpaqueSpecWrap Line: 21)

Shader error in 'Shader Forge/OpaqueSpecWrap': Program 'frag', unable to find compatible overloaded function "mul(float3x3, error)" at line 81

Keywords: DIRECTIONAL, LIGHTMAP_ON, DIRLIGHTMAP_ON, SHADOWS_OFF

(Filename: OpaqueSpecWrap Line: 81)

Shader error in 'Shader Forge/OpaqueSpecWrap': Program 'frag', unable to find compatible overloaded function "saturate(error)" at line 81

Keywords: DIRECTIONAL, LIGHTMAP_ON, DIRLIGHTMAP_ON, SHADOWS_OFF

(Filename: OpaqueSpecWrap Line: 81)

Shader error in 'Shader Forge/OpaqueSpecWrap': Program 'frag', undefined variable "normalLocal" at line 81

Keywords: DIRECTIONAL, LIGHTMAP_ON, DIRLIGHTMAP_ON, SHADOWS_OFF

(Filename: OpaqueSpecWrap Line: 81)


https://dl.dropboxusercontent.com/u/4780157/ShaderBug/OpaqueSpecWrap.shader


Its just a copy of the example wrap shader with the tick box on and the bump map removed. With this shader, if you add a Texture2D node to the normal slot the errors go away.



Answer

Answer
Fixed

This is now fixed in alpha 0.13 :)