Search Issue Tracker
Fixed in 2019.3.X
Default preset is ignored when adding StandaloneInputModule through the Event System component
How to reproduce:
1. Open the user-submitted project ("EventSystem Creation Errors.zip")
2. In the Project Window click on the "StandaloneInputModule" object and observe the Submit and Cancel button fields being different from the default (You should see "SecondarySubm" and "SecondaryCanc")
3. In the Hierarchy create a new empty object, add an event system to it and click "Add Default Input Modules"
4. Observe the added module's Submit and Cancel button fields again
Expected result: the fields are the same as the "StandaloneInputModule" file in the Project Window as it is set to be the default (You should see "SecondarySubm" and "SecondaryCanc")
Actual result: the fields are not the same, they are "Submit" and "Cancel" instead. These are default Unity values, not the default set by the user.
Reproduced in: 2019.3.0a6, 2019.2.0b6, 2019.1.7f1, 2018.4.2f1
Couldn't test with: 2017.4.28f1
Note: The correct default module is added when adding the component manually through the "Add Component" button. The issue only reproduces with the Event System's "Add Default Input Modules" button.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- 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