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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment