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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment