Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.4p5
Issue ID
958135
Regression
No
Floating Point precision issue of Color Channel after Static Batch
To reproduce:
1. Download attached project "142338-538f1-lightmap.zip" and open in Unity
2. Open "lightmap_bug" scene
3. Mark the GameObject named 'ScaleRoot' as Static
4. Enter Play mode
5. Observe that there are different render result between Static and nonStatic
Notes:
- This issue appears both on Windows and OSX
- The UV of 'ScaleRoot/village_r01_caodi' are changing because of after static batch, the color channel of mesh has floating point precision issue
Reproduced on Unity 5.5.5p1, 5.6.4f1, 2017.1.2p1, 2017.2.0f3, 2017.3.0b4 and 2018.1.0a1
Add comment
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
Resolution Note:
Minor / rare usecase