Search Issue Tracker
Fixed
Votes
0
Found in
2021.3.12f1
2022.1.20f1
2022.2.0b12
2023.1.0a14
Issue ID
UUM-19624
Regression
No
"Command buffer Render SSR contains at least one command that is not suitable to be executed in async compute" errors in Player when disabling ray tracing in custom Camera settings in Script
Reproduction steps:
1. Open the user’s attached project
2. Remove the Cinemachine package
3. Build the project
4. Run the project
Reproducible with: 2021.3.12f1, 2022.1.20f1, 2022.2.0b12, 2023.1.0a14
Could not test with: 2020.3.41f1 (CS0246 errors)
Reproducible on: Windows 10
Expected result: the Player looks like the Game view
Actual result: the Player looks black and an error is thrown:
“Command buffer Render SSR contains at least one command (command type: SetRenderTarget) that is not suitable to be executed in async compute: (previous command: WaitOnGPUFence)”
Notes:
1. Screen isn’t black in 2021.3.12f1
2. Sometimes the issue isn’t reproducible. Seems to depend on what option it was built with (Build/Clean Build/Build and Run). Haven’t tested properly because of long build times
3. Ray tracing is disabled and enabled in PauseMenu.cs
4. Not reproducible in Play mode
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-3342