Search Issue Tracker
By Design
Votes
0
Found in
5.6.1f1
Issue ID
931119
Regression
No
Crash in OpenVR::BuildTrackedDeviceName when looping through all available applications
To reproduce:
1. Open attached project;
2. Make sure OpenVR is enabled;
3. Load the "Test" scene;
4. Enter play mode;
5. Select the 'Test' game object in the hierarchy;
6. In the inspector, check the 'debugTestInterface' boolean to test for the presence of the Applications interface;
7. In the inspector, check the 'debugPrintApplications';
Expected result: The program should loop through all available applications, printing their key as a string.
Actual result: Editor crashes.
Reproduced on versions: 5.5.4p2, 5.6.1f1, 5.6.2p4, 2017.1.0f3, 2017.2.0b3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment