Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.2.20f1
6000.0.0b15
Issue ID
UUM-70477
Regression
No
RenderDoc Capture Frame can't be completed after Particle System is simulated
How to reproduce:
1. Make sure you have a RenderDoc installed
2. Open the user-attached project “HDRP2022”
3. Right-click on the Game view window title and click “Load RenderDoc”
4. Select the “Particle System” GameObject in the Hierarchy and let it simulate particles for some time
5. Unselect the “Particle System” GameObject and click “Capture the current view and open in RenderDoc” button in the Game view
6. In RenderDoc press the “Capture Frame(s) Immediately” button
7. Observe the results
Expected result: The frame is captured
Actual results: The progress bar gets stuck and the frame is not captured
Reproducible with: 2021.3.37f1, 2022.3.26f1, 2023.2.20f1, 6000.0.0b15
Reproducible on: Windows 11 Pro with DX11
Notes:
- Reproducible on HDRP and Built-In Pipeline projects
- The frame is instantly captured when you close the Editor
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
We were able to reproduce the issue, but could not find an explanation.
It is still possible to take RenderDoc captures from Unity, it is only from RenderDoc UI that it gets stuck.
We also noticed that opening the last capture allows you take a capture again from RenderDoc.
Whether it is on our side, or RenderDoc, or a combination of both, this is a minor issue that can easily be worked around and that it will affect a minority of users.
Closing as will not fix.