Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b4, 6000.5.0a5
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.2f1
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130512
Regression
No
Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
Steps to reproduce:
- Create any URP Project
- In the Package Manager select the "Universal RP" Package
- In the Samples section download and import the "URP Package Samples" Sample
- Select the "Lighting Data" that's under the "AmbientOcclusion" folder
- Observe the "Scene" field in the Inspector
Actual results: The field is missing a Scene attached and Warning is logged "[Worker4] Lighting data asset ‘LightingData’ is incompatible with the current Unity version because the scene it was baked for was not serialized. Please use Generate Lighting to rebuild the lighting data, or assign the target scene to the Lighting Data Asset in the inspector."
Expected results: The Ambient Occlusion Scene is attached to the Lighting Data Asset
Reproducible with versions: 6000.0.62f1, 6000.2.13f1, 6000.3.2f1, 6000.4.0b2, 6000.5.0a3
Tested on (OS): Windows 11
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
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
Resolution Note:
Editor: Fix Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
Resolution Note (fix version 6000.5.0a5):
Editor: Fix Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1