[Bug Report] FC26 – EAApp Overlay & Input subsystem's Causing Input Lag/Stutter

[Bug Report/workaround] — FC26/EAAPP and Input Services/subsystem's  Interaction Causing Input Lag and Stuttering in FC26

Summary
There appears to be an unintended interaction between FC26/ EA App, Windows input subsystem and Game Input Service (GameInputSvc), resulting in micro stuttering, input lag, and input device refresh events being triggered during gameplay.

Details
During user-side investigation of FC26 issues, I observed that, intermittently — typically when the match is paused or the EA App overlay is opened — the EAPP displays the message:

“New input connected”

This occurs without any actual hardware change (no new controllers or input devices connected/disconnected).

Each time that message event happens introduces a short but noticeable micro stutter or frame-time spike and a subsequent input delay for the rest of the game session.

While monitoring my system, I noticed that some events related to the input system were triggered when the message appeared, some of them related to Game Input Service.

After disabling the service and repeating the same in-game scenarios, the behavior changed:

The repetitive “New input connected” messages stopped appearing repeatedly and causing micro stuttering. 
The message is still being displayed one time when opening the EAapp overlay for the first time.

There was a small but noticeable improvement in overall input latency  and overall game stability.

So I try disabled the EAapp overlay, which resulted in another small improvement.

This suggests that FC26 (and/or the EA App ) is making unnecessary or redundant input device polling calls (not only through GameInputSvc), causing I/O overhead and input/synchronization delays.

Workaround

1 -  disabled the EAapp overlay (This may cause some limitations in game, such as purchasing FC points or accept game invites, but the overall game will continue to function normally.)
*I suggest that users disable any other platform overlays if they purchased FC26 through Steam, Epic, etc.

To disable the EA overlay, open the EA app, click on the three lines or your profile icon to access Settings, and then go to the Application tab. Scroll down to the In-game overlay option and toggle it off.
Also uncheck all notification options.

2 - I created 3 BAT files (attached to post) s to make it easier to disable and re-enable the GameInput Service, since this service is required by other games and Microsoft services. (that is a temp workaround for  users can test it and see if the symptom improves on their systems.)

1 disable
2 enable and set service start to auto
3 Enable and set service start to on demand
(always Run as Administrator.)

Use the "disable_GameInputSvc" script before running the game and run one of the two Enable options when closing the game.
(Other games and applications use this service to function properly.)

Expected Behavior

The game and EA App overlay should not trigger “New input connected” events unless a real input change occurs.
Input device polling remain stable and avoid redundant refreshes.

EA enable option to players disable mouse/keyboard in game if have a joystick/gamepad connected, to avoid input override , wrong input device select by game, etc.  and reduce the number of unused input devices being monitored. (The code for disabling the keyboard/mouse already in game, only need be "unlocked" by EA side)

Test environment

Game: FC26 (Previous and latest version)
Platform: Windows 10 / Windows 11 (I tested it on two different computers)
EA App Version: Latest
Input Devices: Xbox Series controller (USB cable), Quick fire Keyboard (Cherry MX_black switch) and Logitech G700 mouse (no hot-swap or cable's reconnect events)

Virustotal verification of script files
www.virustotal.com/gui/file/e5d97c855f3ee2acc763186be14a06ded80b68a3071c478da07570634237f8f4

*Note*
This seems to be only a small part of the input lag problem and a temporary workaround for players.

These interactions may also be related to the new anti-cheat system, something I haven't investigated so as not to put my account at risk, but it has already happened with other games that used the Frostbite engine and other anti-cheat systems (EAC, Punkbuster).

If the Dev team needs more information, I can provide it.

Take care,
W0LF