Controllers are not detected in player when plugged in before the Splash Screen is shown, but after the Player boots up

Unity: Input

Input Manager

Won't Fix

6.0.X

2023.3.X

2023.2.X

2020.3.X

We won't be able to prioritize a fix for this any time soon. So we are closing it for now. The issue is not present in the newer Input System.

Cancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

[Internal link] is fixed for the New Input System but the Input Manager still has the issue.

How to reproduce:
1. Open the attached project "ControllerBug.zip"
2. Open the Build Settings (File > Build Settings...)
3. Build And Run
4. Plug in the controller as soon as the Player boots up, but before the Unity logo Splash Screen shows up

Expected result: The controller is detected and is usable
Actual result: The controller is not detected and is unusable

Reproducible with: 2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a13,

Tested with: Xbox One controller (USB C), Dual Sense controller for PS5 (USB C)

Notes:

The controller is still not detected after unplugging it and plugging it back in
The issue only appears when plugging in the controller at the right time

Controllers are not detected in player when plugged in before the Splash Screen is shown, but after the Player boots up

Unity: Input

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Controllers are not detected in player when plugged in before the Splash Screen is shown, but after the Player boots up

Unity: Input

Statuses

Won't Fix

Resolution Notes

6.0.XWon't FixWe won't be able to prioritize a fix for this any time soon. So we are closing it for now. The issue is not present in the newer Input System.

2023.2.XWon't FixCancelling this 2023.2 tech release issue since the support for this release has come to end of life. Cancelling this 2023.2 port case does not affect any LTS or Unity 6 Beta/Preview that remain open.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?