Unity Issue Tracker - Unity is altering lightmap UVs for non-statically batched objects in Player
Closed
UUM-2707
Unity is altering lightmap UVs for non-statically batched objects in Player
Unity: RP Foundation
Won't Fix
2022.1.X
2021.2.X
2021.1.X
2020.3.X
2022.1 has reached end of life so the issue will be fixed in a newer version.
Closing since this version is not supported anymore, and there is another port to track 2021.3 which is the supported version
How to reproduce:
1. Open “StaticBatchingUVUnityBug(1).zip” project
2. Open “SampleScene” Scene
3. File > Build And Run
Expected result: In Player, examples 2, 3, 4 matches each other and they are not the same as 1st example
Actual result: Lightmap UV of example 3 matches the 1st example in Player
Reproducible with: 2020.3.19f1, 2021.1.22f1 , 2021.2.0b13 , 2022.1.0a10
Could not test with: 2019.4.30f1, errors appeared because the project was downgraded.
Notes:
- (Expected result) If you run the project in the editor you will see that only the 1st example is using the combined mesh and has altered Lightmap UVs.
(Actual result) If you build and run a standalone, you'll see that the 3rd example also has altered Lightmap UVs even though it is not using the combined mesh.
All objects that are set to statically batch have a component (TransferLightmapScaleOffset) on them that assigns the Lightmap scale offset etc., of the first example, so that these examples share the same place in the atlas - purely to demonstrate the issue more effectively. Removing this component has no impact on this issue.
Prioritise and Follow this issue
Have a workaround or additional info about this issue?