Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.33f1
2022.3.14f1
2023.1.2f1
2023.2.0a21
2023.3.0a3
Issue ID
UUM-41560
Regression
Yes
[HDRP] rendering from this custom pass only works with render graph viewer window open in editor
Steps
1. open project and open custom-vertex-buffer-blit-shader scene
2. enter playmode
3. press tab key to change SRP
- first press enables custom rendering effects
- second press switches to HDRP (custom rendering effects off)
- third press switches to HDRP (custom rendering effects on)
Expected: custom rendering effects are rendered in HDRP (with custom rendering effects on)
Actual: last render result is seen and no further updates
Repro (workaround helps): 2023.2.0a21 on Windows (MacOS blocked by another bug)
Repro (workaround doesn't help): 2023.1.2f1 on windows
No repro: 2022.3.4f1
Workaround: open Window > Analysis > Render Graph Viewer
NOTES:
- checked in RenderDoc - seems related to UAV access in the shader for custom rendering (worked before, broken in later versions)
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
I believe the issue is caused by a separate command buffer being used in HDRP's custom pass system. This is not supported because it means that the command buffer you're executing inside your custom pass will run on the GPU before HDRP starts rendering which will cause several problems if you try to access HDRP GPU data.
Resolution Note (2023.3.X):
I believe the issue is caused by a separate command buffer being used in HDRP's custom pass system. This is not supported because it means that the command buffer you're executing inside your custom pass will run on the GPU before HDRP starts rendering which will cause several problems if you try to access HDRP GPU data.