Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
918266
Regression
No
Same shader looks differently in Game and Scene views if Batching is not disabled
How to reproduce:
1. Open the attached "RayTrails" project and "Demo" scene
2. Inspect the Cylinder, Cylinder (1), and Cylinder (3) GameObjects
3. All three of them uses custom "TrailShader"
4. Compare on how they are rendered in Scene view and Game view
Expected result: Game view and Scene view look the same
Actual result: Meshes that use "TrailShader" are rendered differently
Note - This happens due to Batching and it converting all coordinates to world space, adding "DisableBatching" = True" to shader's tags fixes the issue
Reproducible with - 2017.2.0a1, 2017.1.0b8, 5.6.1p3, 5.5.3p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment