Search Issue Tracker
By Design
Fixed in 2017.1.X
Votes
1
Found in
2017.1.0f1
Issue ID
937196
Regression
No
UV maps are corrupted for static objects with custom shader when Static Batching is enabled
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure Static Batching is enabled in Player Settings
3) Generate Lighting in Lighting settings
4) Build and Run 'Theme1_Map3' scene
Expected result: UV maps should not be corrupted when Static Batching is enabled (check attached image 'expected.png')
Actual result: UV maps are corrupted when Static Batching is enabled (check attached image 'actual.png')
Reproduced with:
5.6.3f1, 2017.1.0p2, 2017.2.0b5, 2017.3.0a2
I wasn't able to test with 5.5.x version of Unity because shader didn't worked
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