Search Issue Tracker
Active
Under Consideration for 6000.6.X
Won't Fix in 6000.3.X
Fix In Review for 6000.5.0b5
Votes
0
Found in
6000.3.11f1
6000.4.0f1
6000.5.0a9
6000.6.0a2
Issue ID
UUM-137250
Regression
Yes
Crash on Umbra::QueryExt::queryStaticShadowCasters when baking a custom Reflection Probe with the minimum Near Clipping Planes value
How to reproduce:
1. Open the attached “IN-135293” project
2. Open the “OutdoorsScene“
3. In the Hierarchy, click on the Reflection Probe
4. In the Inspector, click “Bake”
5. Observe the crash
Reproducible with: 6000.3.0a3, 6000.3.11f1, 6000.4.0f1, 6000.5.0a9
Not reproducible with: 6000.3.0a2, 6000.0.71f1, 6000.6.0a1 (“Failed to build mask for shadow culler. ErroCode: 3” error occurs instead)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note: If the crash does not occur the first time, change Cubemap the in the Inspector of the Reflection Probe and bake again
First few lines of the stack trace:
0x00007FFF85495F2E (Unity) Umbra::QueryExt::queryStaticShadowCasters
0x00007FFF8547EA30 (Unity) UmbraModule::CullShadowCastersWithUmbraThreaded
0x00007FFF82CDBC64 (Unity) CullDirectionalShadowCastersJob
0x00007FFF8312A7A5 (Unity) ujob_execute_job
0x00007FFF831297FB (Unity) lane_guts
0x00007FFF8312CF09 (Unity) worker_thread_routine
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
- HDRP Light shadows switch Type from Soft to Hard after re-enabling the Shadow Map option
- [AI Assistant] Banner content is clipped and inaccessible when Assistant window is docked or narrow
- Crash on CheckDeviceStatus when opening a UI Panel in Play mode on a specific project
- Redundant Warning message is thrown when multi selecting Package Manifest files in the Project Window
- Point light Cookie texture is rendered incorrectly with Deferred renderer path when used together with multiple Directional lights
Resolution Note (fix version 6000.5.0b5):
Fixed in 6000.5.0b5
Resolution Note (6000.3.X):
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.