Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.15.0
Issue ID
ISXB-1720
Regression
Yes
Project-wide Action Maps are disabled when Play mode setting is set to "Do not reload Domain or Scene” or “Reload Scene only”
Reproduction steps:
1. Open the attached “IN-119060.zip” project
2. Navigate to Project Settings > Editor > Enter Play Mode Settings
3. Make sure “When entering Play Mode” is set to “Do not reload Domain or Scene” or “Reload Scene only”
4. Open the “SampleScene”
5. Enter Play mode
6. Open the Input Debugger Window (Window > Analysis > Input Debugger)
7. Observe the dropdown list under “Actions”
Expected result: “Player” and “UI” actions are visible
Actual result: Only “Debug Menu” actions are visible
Reproducible with: 1.14.1, 1.15.0 (6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2)
Not reproducible with: 1.14.0 (6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2)
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: no other environments tested
Notes:
- Does not reproduce if the “When entering Play mode” property in ‘Project Settings > Editor > Enter Play' Mode Settings is set to “Reload Domain and Scene” or “Reload Domain only”
- Actions in the Player and UI maps also do not work unless the map is explicitly enabled via script
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This problem is due to Input System's lack of support for not using Domain Reloads. We have ongoing work in this area and are aware of the issue. See https://github.com/Unity-Technologies/InputSystem/pull/2016 to track changes in this area.
However, the fix that changed the behavior cannot be reverted. We cannot force enabling project-wide actions on entering play mode. On 1.14.0 enabling these actions happened at a different time compared to a Player build and doesn't allow users to disable them during Start(), OnEnable() and Awake(). So we removed to be consistent between Player standalone builds and Editor workflows.
Also, my personal opinion is that project-wide actions shouldn't be all enabled by default at all (or users should select which map they want enabled by default). This currently leads to a lot of problems. An example is if you want to do UI and have the Player action map disabled on startup, using PlayerInput; etc.
If you want project-wide actions enabled by default, please call it on Start(), Awake(), or OnEnable() and select the action map you want to enable.
Duplicate of another internal issue: ISXB-1085: Input system does not support fast enter play mode (fepm) on U6