Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0a3
Issue ID
1009838
Regression
Yes
Console Spamming Message: "InputEventData event is too big! (increase kMaxInputEventSizeInBytes
The console spams the following error: InputEventData event is too big! (increase kMaxInputEventSizeInBytes)
I can only reproduce this on one machine - the Macbook Pro 15 inch (2017).
To reproduce, create a new project and move the mouse using the trackpad on the Macbook Pro model above. You will see loads of console errors reading "InputEventData event is too big! (increase kMaxInputEventSizeInBytes)".
Could not reproduce in 2018.1, so it has regressed it one of the 2018.2 alphas.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment