Search Issue Tracker
Active
Votes
0
Found in
1.5.0-exp.2
Issue ID
UUM-134943
Regression
No
Inconsistent "Mock HMD Loader" naming in the "Project Settings"
Steps to reproduce:
- Create a Unity project
- Go to "Edit -> Project Settings"
- Select the "XR Plugin Management"
- Click the "Install XR Plugin Management" button in the details window
- Check the "Mock HMD Loader" in the "XR Plug-in Management" window
- Observe the newly displayed "MockHMD" setting
Actual results: In the "XR Plugin Management" window, it is listed as "Mock HMD Loader". In the "Project Settings" list, it is listed as "MockHMD". Inconsistent naming.
Expected results: In all the places naming should be the same "MockHMD" as this one is listed in the Package Manager as the package title
Reproducible with versions: 1.5.0-exp.2(6000.3.10f1, 6000.4.0b10, 6000.5.0a7)
Not reproducible with versions: 6000.4.0b8
Tested on (OS): macOS - Tahoe 26.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment