Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.1.8f1
Issue ID
1061587
Regression
No
[WindowsMR] Graphics debugging fails for a Windows Mixed Reality app
Steps to reproduce:
1. Download attached project
2. Change platform to UWP
3. Enable XR support
4. Build VS solution
5. Debug -> Graphics -> Start graphics debugging (Make sure you installed the optional graphics tools with VS)
6. The Unity app window may pop up full screen, move it and accept the UAC elevation prompt
Expected results: Graphics debugging works.
Actual results: Graphics debugging doesn't update Frames per second and Frame time graphs
Reproduced with: 2018.3.0a9, 2018.2.5f1, 2018.1.8f1, 2017.4.9f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment