Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.3.0
Issue ID
ISXB-51
Regression
No
InputActions from Mouse are sometimes skipped
The original bug was for Android, but after testing on Editor, I think something's wrong with input actions themselves
Repro steps:
* First take a look at video attached below, it was taken with Unity 2020.3.26, input system package 1.2.0 in Editor on Dell Laptop with Touch Screen monitor
- I am first drawing with mouse, and the drawing lines are supper jaggy, seems like half of input actions events from mouse are not coming through
- Then drawing with touching the screen, even though laggy, the drawing is much more smoother
- Again drawing with mouse, it seems like no input actions are coming through for the first 2-3 seconds, then the drawing starts appearing again, but lines are supper jaggy
* Open case_1339170-DrawReproSmall.zip (It's a trimmed down repro with Debug.Log entries removed, the original one was 500 MB and had Debug.Log)
* Run in Unity 2020.3, preferably on a PC with touch screen monitor hooked, so you can compare touch versus mouse drawing
* Launch the scene in editor
* Draw with mouse
* Draw with touch
* Drawing with mouse looks horrible, looks like half of the input actions are simply not coming through
Expected: Input is drawn correctly
Actual: Input isn't drawn correctly
BELOW STEPS are for Android, leaving it for references.
Repro steps:
1. Open attached project 'DrawRepro'
2. Build and Run to an Android device with a stylus
3. Draw on the screen alternating between fingers and stylus
Expected: Input is drawn correctly
Actual: Input isn't drawn correctly
Reproducible with: 2020.3.13f1 - Input System 1.0.2, 2021.1.14f1 - Input System 1.0.2,
2021.2.0b2 - Input System 1.1.0-pre.5, 2022.1.0a1 - Input System 1.1.0-pre.5
Couldn't test 2018.4 and 2019.4 due to not being able to build the project
Tested and reproduced on these devices:
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
-
paulnoujaim
Dec 14, 2021 15:38
Brief update, but I have revisited this item using Unity version 2020.3.24 with version 1.2.0 of the input system and it is still occurring.
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
No longer reproduces in Input System 1.4.1+