Search Issue Tracker
Fixed
Fixed in 1.11.2, 7000.0.0
Votes
0
Found in [Package]
1.11.1
Issue ID
ISXB-708
Regression
No
”NavigationSubmitEvent” and “NavigationCancelEvent” events are called multiple times in the Editor when the Input System’s Update Mode is set to “Process Events In Fixed Update”
How to reproduce:
1. Open the user’s attached “uitest1.zip” project
2. Enter Play Mode
3. Press the ESC or enter button
4. Observe the Console window
Expected result: a total of 4 logs are logged
Actual result: a total of 12 logs are logged
Reproducible with: 1.7.0, 1.8.0-pre.2 (2021.3.33f1, 2022.3.16f1, 2023.2.4f1, 2023.3.0a19)
Reproduced on: macOS 13.6.1 (Intel)
Not reproducible on: No other environment tested
Notes:
- not reproducible with “Process Events In Dynamic Update” Update Mode
- not reproducible in Standalone Player (macOS)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 7000.0.0):
Fixed event handling when using Fixed Update processing where WasPressedThisFrame could appear to true for consecutive frames [ISXB-1006](https://issuetracker.unity3d.com/product/unity/issues/guid/ISXB-1006)
Resolution Note (fix version 1.11.2):
A fix for this issue will be available in the next 1.11.x release of the Input System.