Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1163657
Regression
No
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.
Latest issues
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment