Closed Keith94 closed 3 years ago
Thanks for the report - I suspect this is related to https://github.com/alexstrout/foxWSFix-UT2k4/issues/4 and affects more people than I first thought.
It's possible the Steam version does things differently than retail / GOG (which this was originally developed / updated on, respectively), but it's likely something weird with the GUI override that I missed in testing.
Not sure if exactly the same issue, but I was having problems with my Steam version, and this fixed everything for me:
Basically the setting "InputClass=Class'foxWSFix.foxPlayerInput'" NEED to appear TWO times in USER.INI The first goes under the already suggested section "[Engine.PlayerController]" The second goes under the "[UnrealGame.UnrealPlayer]" section
Source: https://github.com/alexstrout/foxWSFix-UT2k4/issues/4#issuecomment-797092675
I couldn't quite replicate the crash, but I could replicate the loss of control if both UnrealGame.UnrealPlayer
and XGame.xPlayer
didn't have an InputClass line set. Note that the hierarchy in-game is PlayerController -> UnrealPlayer -> xPlayer
, so whatever's set latest will take precedence. In the main menu, only PlayerController
is used.
The latest v2.1.1 release should hopefully alleviate this issue - at the very least, it will log some useful information on-screen / to the console if something's not quite set up right. If it's a missing InputClass line, it will attempt to automatically remedy it. I've also updated the install instructions in the readme to reflect the above.
Please let me know / feel free to re-open if anyone still runs into issues with this. Thanks!
Source
I didn't experience this but thought I'd post it here.