Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-preview.1
Issue ID
1276106
Regression
No
[Input System] Control Schemes are not resolved when copying bindings between InputActionAssets
Reproduction steps:
1. Open the attached project ("Case_1276106-ActionCopying.zip")
2. Create a ".inputactions" asset with one action and binding
3. Add a control scheme and assign the binding to it
4. Create another ".inputactions" asset with one action but without a Control Scheme
5. Copy the binding from the first asset’s action to the second asset’s action
Expected result: Control Schemes are resolved
Actual result: Control Schemes are not resolved, and so bindings don't work in play mode
Reproducible with: 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Couldn't test with: 2018.4 (minimal package version is not supported)
Reproducible with package versions: 0.9.0-preview, 1.1.0-preview.1
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
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Resolution Note (fix version 1.3.0):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1445