Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
1.0.0-preview.6
Issue ID
1229146
Regression
Yes
[InputSystem] Reordering of ActionMaps in Input Action window fails and throws "Should have drop target" error
How to reproduce:
1. Open attached project "InputTests.zip" (or create a new project and import Input System package)
2. In Project window, right-click -> Create -> Input Actions
3. Open newly created Input Action
4. In Input Action window, create ~6 "Action Maps"
5. Try to reorder action map 2 with action map 3
Expected result: the action map switch places
Actual result: the action map 2 goes down to the bottom of the list, an error is thrown "Should have drop target"
Reproducible with: 2019.1.14f1 (0.2.6, 0.2.10, 0.9.0), 2019.3.7f1, 2020.1.0b3, 2020.2.0a4 (1.0.0-prev.6)
Not reproducible with: 2018.4.20f1, 2019.1.14f1 (0.2.1)
Could not test with: 2017.4 (New Input System was not yet implemented)
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
- EditorGUILayout.PropertyField foldout icon inside Vertical Layout Group has an incorrect indent when used with OnInspectorGUI()
- [Android] [iOS] "NullReferenceException: Object reference not set to an instance of an object" throws when entering the Play Mode/opening the application
- The Player freezes on load when building Web platform
- Animator "Conditions" tab breaks when the only Parameter is deleted and another one is created
- "Shader error in 'Universal Render Pipeline/Lit': maximum ps_5_0 sampler register index (16) exceeded" error thrown after a build is completed when the "LOD Cross Fade" parameter is enabled
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1107
Verified in: InputSystem (1.0.0-preview.7)