Search Issue Tracker
Duplicate
Votes
1
Found in
5.6.0b3
Issue ID
869946
Regression
Yes
Surface shader compilation breaks when using worldPos
To reproduce:
1. Open attached project;
2. Open "Test" scene;
3. Look at the "Test" shader in the Inspector panel.
Expected result: there are no shader errors when using worldPos input.
Actual result: pink textures, Inspector and console throws errors:"UnityGetRawLightMaskOrProbeOcclusions': no matching 2 parameter function at line 180 (on d3d11)" and "Invalid subscript 'worldPos' at line 180 (on d3d11)".
Reproduced on versions: 5.6.0b3.
Not reproduced on versions: 5.5.0f3.
Comments (1)
-
Venryx
Jan 24, 2017 13:56
I have this issue in my project as well, after upgrading from 5.4 to 5.6.0b4.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
This is a duplicate of issue #872014