Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
1
Found in
2022.3.47f1
6000.0.20f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-82262
Regression
No
Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
Reproduction steps:
1. Open the attached "repro_IN-83747" project
2. Open the "Assets/Scenes/Kokiri_LevelDesign.unity" Scene
3. Enter the Play Mode
4. Observe the crash
Reproducible with: 2022.3.47f1, 6000.0.20f1
Couldn't test with: 2021.3.43f1 - Unsolvable Console errors (mainly 'PackageCache')
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
- Reproducible in Player
- When there’s no terrain in the Scene, the crash doesn’t appear
First few lines of the stack trace:
0x00007ff728779bc1 (Unity) PrepareDrawShadowsCommandStep1
0x00007ff72877451f (Unity) ScriptableRenderContext::ExecuteScriptableRenderLoop
0x00007ff727cb5789 (Unity) ScriptableRenderContext_CUSTOM_Submit_Internal_Injected
0x0000017c8bc5b5aa (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal_Injected (UnityEngine.Rendering.ScriptableRenderContext&)
0x0000017c8bc5b4db (Mono JIT Code) UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal ()
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.
Resolution Note (6000.6.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.