Search Issue Tracker
Fixed in 2023.1.0a20
Fixed in 2022.2.X, 2022.2.2f1, 2023.1.X
Votes
0
Found in
2022.2.0b10
Issue ID
UUM-15675
Regression
Yes
Lightmap baking fails when URP Template content is put into a subscene
Repro steps:
- Check out latest 2022.2/staging (tested with git commit 62ca96eb270df00114e34114a5155944030c179f)
- Check out latest DOTS master (tested with git commit c15f5229c91b3e0d202461b8ea1870159b59d9ee)
- Extract the attached test project into a sibling folder of the DOTS checkout
* E.g. if DOTS is in C:\UnitySrc\dots, the test project should be in C:\UnitySrc\EntitiesLightmappingBug, so the relative package path works
- Open the scene Assets/Scenes/SampleScene.unity
- It's the default URP template, but with the assets moved into a DOTS subscene
- Click Window > Rendering > Lighting > Generate Lighting
- GI baking goes into an error loop, repeatedly giving this error message:
{noformat}
Integrate failed on Write Lighting Data job.
{noformat}
** The editor becomes unresponsive due to the error loop
Expected behavior: GI gets regenerated, and Entities get updated with the new lightmaps
Actual behavior: GI baking repeatedly fails with an error
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2023.1):
Resolved with https://github.cds.internal.unity3d.com/unity/unity/pull/16902