Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
Issue ID
UUM-55677
Regression
No
The path of the Preset is not present in the Select Preset window when clicked on the Preset
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/DevDunkStudio/Advanced Mesh Interactions/Sample/Scenes/PlaygroundDemo.unity” Scene
3. In Hierarchy, select the “Left Controller” GameObject (XR Origin (XR Rig) > Camera Offset > Left Controller)
4. In Inspector, find the “XR Controller (Action-Based)” Component
5. Left to the 3 dots, click the Select Preset button
6. In the Select Preset window, click on any Preset
Expected result: The path of the Preset appears in the Select Preset window
Actual result: The path of the Preset is not present
Reproducible with: 2021.3.31f1, 2022.1.0a12
Not reproducible with: 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Fixed in: 2022.1.0a13
Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.