Search Issue Tracker
Not Reproducible
Not Reproducible in 1.14.X
Votes
0
Found in [Package]
1.14.0
Issue ID
ISXB-1572
Regression
No
UI menu navigations stuck going up indefinitely in a Release build with the New Input System
Reproduction steps:
1. Open the attached “IN-101945.zip“ project
2. Open the “SuperUnityBuild” Window (Window > SuperUnityBuild)
3. Click “Perform All Enabled Builds (1 Builds)”
4. Open the .exe once built
5. Observe the main menu
Expected result: No indefinite scrolling is observed
Actual result: The menu navigation is scrolling up indefinitely
Reproducible with: 1.14.0 (2022.3.61f1)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Not reproduced by CQA
- Related Steam Discussions: https://steamcommunity.com/app/3138350/discussions/0/595148763657442441/
- More information in the Internal Notes
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Hey, we've tried to reproduce this locally on quite a few different setups and were unable to. From the information you've given us it seems related to a guitar hero receiver for the PS3 which we do not support, sadly there's not much we can help with at this time but it seems like a workaround is available by instructing users to remove that peripheral. If any additional information becomes available, logs, etc, feel free to reopen this case and we'll take another look.
Resolution Note (1.14.X):
Hey, we've tried to reproduce this locally on quite a few different setups and were unable to. From the information you've given us it seems related to a guitar hero receiver for the PS3 which we do not support, sadly there's not much we can help with at this time but it seems like a workaround is available by instructing users to remove that peripheral. If any additional information becomes available, logs, etc, feel free to reopen this case and we'll take another look.