Search Issue Tracker
By Design
Votes
0
Found in
5.4.2f2
Issue ID
851285
Regression
No
Custom Surface Shader (instanced) Not Evaluating SH Probes
Reproduction steps:
1. Open the attached project (lighting problem repro.zip);
2. Open the scene "lighting issues.unity";
3. In the game view, observe lighting difference between the sphere with standard shader and the instanced surface shader;
4. Open the ModelShader.shader script;
5. Comment the 85 line;
6. In the game view, observe that the spheres are lit identically.
Expected results: the custom instanced surface shader will work as the standard.
Actual results: objects are lit differently;
Reproduced on: 5.3.6p8, 5.4.2p4, 5.5.0f2, 5.6.0a3.
Note:
85 line: In this line is evaluated the Surface shader's occlusion:
o.Occlusion = tex2D(_OcclusionMap, IN.uv_MainTex) * _OcclusionStrength;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Add comment