Search Issue Tracker

Not Reproducible

Votes

1

Found in [Package]

1.8.0-pre.2

Issue ID

ISXB-691

Regression

No

“Exceeded budget for maximum input event” error appears when entering Play Mode if setting “InputSystem.settings.maxEventBytesPerUpdate” to more than 0

Package: Input System

-

The steps bellow don't actually reproduce the problem the user is having. 
The project below sets the maxEventBytesPerUpdate to a value smaller than a device input event which is expected to raiser an error.

The customer's problem is having ~10MB of input events to process in a InputSystem.Update() call.

There are no reproducible steps for this bug.

See full conversion in [http://supportstats.hq.unity3d.com/history.php?tid=1699172]

-How to reproduce:-
-1. Open the user’s attached “Repro_2023.1.20f1.zip” project-
-2. Open the “SampleScene” Scene (Assets/Scenes)-
-3. Enter Play Mode-
-4. Observe the Console window-

-Expected result: no error-
-Actual result: “Exceeded budget for maximum input event throughput per InputSystem.Update()” error appears-

-Reproducible with: 1.7.0, 1.8.0-pre.2 (2021.3.32f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16)-

-Reproduced on: macOS 13.5.2 (Intel)-
-Not reproducible on: No other environment tested-

-Notes:-
-{-}not reproducible if setting “InputSystem.settings.maxEventBytesPerUpdate” to 0{-}
-{-}reproducible in the Editor and Standalone Player (macOS){-}

  1. Resolution Note:

    We could not find reproducible steps to this issue. However, we plan to look into the input event queuing area and improve error logging to know what causes problems like this.

Comments (3)

  1. Knarhoi

    Jul 19, 2024 07:52

    I get the same error and it happened only after I imported the Unity Character controller package, that used the new input system, whereas my project used the old system until then.

    As I have the game running in the editor, the error occurs after a while of running.

    I manually deleted the imported package from the assets folder and checked that Player Settings>Player>Other Settings>Active Input Handling is set to "Input Manager (Old)".

    Curious though, as today when I started Unity, the error still occurs, and I noticed, that the aforementioned setting was back to "Both". Very annoying.

  2. gooby429

    Nov 30, 2023 22:12

    Sorry for the double comment, but I forgot to mention it causes the client to crash.

  3. gooby429

    Nov 30, 2023 22:11

    I can also confirm it happens on Windows standalone builds (2022.3.12 LTS, input system 1.7.0)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.