Search Issue Tracker
By Design
Votes
1
Found in
6000.0.29f1
6000.1.0a6
Issue ID
UUM-90468
Regression
Yes
Lighting is overexposed when upgrading the project to Unity 6 and rebaking
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/Tower/TS.1.unity” Scene
3. Open Game view
4. Generate Lighting (Window > Rendering > Lighting)
5. Observe the Game view
Expected result: Lighting is the same as with older Unity versions
Actual result: Lightning is overexposed
Reproducible with: 6000.0.11f1, 6000.0.29f1, 6000.1.0a6
Not reproducible with: 2022.3.53f1, 6000.0.10f1
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- Undoing Animator Parameter name change breaks references to it
- Crash on BV4_OverlapBoxAll when moving in play mode
- Custom mesh water surface normal map fades out when Y Position increases
- Sprite renderer does not issue draw calls correctly when using SRP Batcher
- [Android] Flickering artifacts when using "ScriptableRenderer.EnqueuePass(RenderPassEvent.BeforeRenderingPostProcessing)" multiple times
Resolution Note:
The reason for this turned out to be that lightmaps generated in Unity 6 had their type set to "Default" instead of the expected "Lightmap". The reason this happens in the attached repro project is that the project has a TextureImporter preset which has Type=Default. Since this preset has no filters, Unity will apply it whenever a texture is added to the project, including the when lightmap textures are added at the end of a lighting bake. The reason this only happens in Unity 6 is that in prior versions presets were not applied to lightmap textures.