Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.19f1
2021.1.22f1
2021.2.0b13
2022.1.0a10
Issue ID
UUM-2707
Regression
No
Unity is altering lightmap UVs for non-statically batched objects in Player
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.
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.