Search Issue Tracker
Fixed in 1.2.0
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1321175
Regression
No
[macOS] [Input System] GetBindingDisplayString returns empty Strings for some mappings
Reproduction steps:
1. Download and open the attached project 'InputDisplay.zip'
2. Open Scene 'Bug'
3. Enter Play Mode
4. Observe Console output
Expected result: Every Input Sytem mapping has a Display String
Actual result: Some Input System mapped Display Strings are empty
Reproducible with: 1.0.1 (2021.1.0a8), 1.0.2 (2019.4.22f1, 2020.3.1f1, 2021.1.0f1, 2021.2.0a9), 1.1.0-preview.3 (2021.1.0a8, 2021.2.0a9)
Couldn't test with: 1.0.0 (2021.1.0a8) (Couldn't downgrade)
Notes:
- Issue is not reproducible on Windows
- Issue was reproducible in macOS Editor and Build
Comments (1)
-
Xriuk
Mar 09, 2023 21:21
Just to that this broke GetBindingDisplayString which previously displayed all the composite actions and now does not...
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 1.2.0):
Fixed in: 1.2.0 (2019.4.31f1)