Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.54f1
Issue ID
UUM-111729
Regression
No
Errors “Render Graph Execution error” and "KeyNotFoundException" are thrown and Scene/Game views are not rendered when RenderGraphBuilder has AsyncCompute enabled
How to reproduce:
1. Open the attached “IN-107983” project
2. Open the “TestScene”
3. Enter Play mode
4. Notice an effect is applied to the quad
5. Exit Play mode
6. In the project tab, select the “PC_High_Renderer” asset
7. In the Inspector, find and expand the “Custom Render Feature“
8. Toggle on the “Run Async” property
9. Observe the Scene/Game view and the Console
Expected result: No errors are thrown, Scene/Game view are rendered and the effect is applied when entering Play mode
Actual result: Scene/Game views are not rendered and two errors are thrown in the Console
Reproducible with: 6000.0.0b15, 6000.0.54f1, 6000.1.0b4, 6000.2.0a1
Not reproducible with: 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Could not test with: 2023.1.0a1, 6000.0.0b14 (multiple namespace errors)
Fixed in: 6000.1.0b5, 6000.2.0a2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Errors “Render Graph Execution error” and “KeyNotFoundException: The given key '0' was not present in the dictionary.” are thrown
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
There are no fixes planned for this Bug