Search Issue Tracker
Fixed
Fixed in 1.11.2
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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.
Resolution Note:
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)