Search Issue Tracker
By Design
Votes
0
Found in
5.3.1f1
Issue ID
757592
Regression
Yes
Combined static batched mesh changes UV coordinates when playing the scene
To reproduce the issue follow the steps:
1. Open StaticBatchingBug scene from attached project.
2. Notice how it looks in scene view.
3. Press "Play".
4. You will see texture shifts and uv is slightly different
Regression from 5.2
Reproduced in 5.3.1p1 (7d3d8e90548b), 5.3.1f1 (cc9cbbcc37b4)
Not reproducible in 5.2.2p3 (75b999ee8bfd), 5.1.2p2 (207c2b8718a4)
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
JakeTurner
Apr 26, 2016 05:28
Internally in the batching code Unity assumes UV2 will be used for lightmaps. Hence when batching the meshes in the test scene it is applying the lightmap scale & offset to the UV2 stream for those meshes which are included in the lighting mapping process. The fix for this use case is for the mesh with the custom UV2 stream and custom shaders to be disabled from the lightmapping generation process then its lightmap scale & offset will be 1,1,0,0 (identity) and texture will not shift when it is batched. Click the "Static" dropdown menu on the mesh to mark it is as static for all of areas except Lightmapping.