Re: PC: Game constantly asks to setup additional controllers (I don't want to use)
@sirupflex wrote:Hi all, searched the whole HQ for answers, hope I didn't overlook and hence try to get your input here.
On my PC I am playing F1 23 (Steam) with the T248. Besides the known FFB issues the T248 seems to work fine so far (just started playing yesterday).
I also have connected to my PC some additional controllers, like a T16000 flight stick, thrust controller and the Logitech Farming Simulator side board. I don't need them in F1 23 obviously. Still, at every start-up, F1 23 tells me that I "have to" setup these controllers and does not leave me any choice but to go to the setup mode of these controllers. I then abort the setup and am in the game. And the T248 works fine. At the next start of F1 23, the same circus happens again.
Any advice on resolving this? I thought the game might have a setting somewhere to tell F1 23 not to bother with some of the controllers (like other games do) but looks like F1 23 does not have that. Any other advice? I wondered if I just go through a dummy setup with each of the controllers once, I might get rid of F1 23 bothering me. I was not sure, however, when I would assign steering, gas, brake, etc. to those controllers, if this messes up the T248 settings, so I didn't try that yet (i.e. the race wheel not working any more, which I want to avoid to get into that trouble). Any hints are welcomed!
Just to state the obvious: Disconnecting all the unnecessary controllers via USB just to play F1 23 is NOT an acceptable option for me.
And as the long-term solution, I would expect EA to have an in-game option to disable / ignore controllers you don't need.
You say 'not acceptable'. I say this is actually 'very common' advice. The way these controllers are defined (to the system) is very similar through the controller APIs.
It's often been the advice to unplug the (gamepad) controllers, they are USB connected. USB connection is versatile and designed around hot plug / unplug scenarios. Advising removal is a simple workaround. I congratulate you on finding your much longer and more difficult workaround, the advice is useful if it is ever deemed relevant by the appropriate parties.
Striking a balance between 'supported controllers' and a complete allowlist / blocklist scenario means I think it is highly likely to be disregarded. Enable / disable isn't quite as simple as the device remains attached to the system with allocated resources and power draw. And it may be called by external parties or programs without the core game. You can use 'Device Manager' to disable controllers (I've done it where I can't reach network sockets or cables easily, for example) or simply unplugging the control cable (power cables may be off the USB and external).
I've often posted that people using 'unsupported controllers' can't necessarily expect patch or future support (especially if the controller is unsupported / superceded by the manufacturer). But, to remove support entirely for non-allowlist controllers would be quite draconian.
I have given XP for the posts in the other thread about the crashing, but you'll notice I remain consistent with this thinking and would advocate the removal of the 'problem' devices one way or another. I've worked around issues with other settings in mainboard UEFI BIOS to 'resolve' other controller issues.