Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.0.0
Issue ID
HUBX-501
Regression
Yes
Graphics debuggers not supported with Hub flow
Steps to reproduce:
1. Open RenderDoc
2. In "Launch Application", specify the editor executable
3. Click "Launch"
4. Create a new project or open an existing one
5. Notice RenderDoc disconnected beause Unity restarted itself
This breaks all workflows relating to shader debugging, and happens with other tools too. These tools depend on hooking the application as it starts, so they need to be the ones that start the process.
Workaround: use -debugHub cmd line parameter to launch 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
- Crash on memcpy when using ScreenCapture.CaptureScreenshot with superSize set to zero
- [URP] Package Samples - Missing scripts in Unity 2022+
- [URP][Package Samples] Continuous "Renderer at index _ is missing for camera _" warnings when opening sample scene
- [URP] Package Samples - Missing scripts in Unity 6
- [URP] Package samples - scenes using FirstPersonController not working in Unity 6
Resolution Note:
Issue closed, as it duplicated as product backlog