I know this won't ever be looked into but I'll post it anyway.
In several battles now I have experienced total loss of input/flight controls. In the 2 most recent occasions I have had the opportunity to experiment with it.
Symptom.
Game is playing fine, randomly complete loss of control occurs. This seems to happen at respawn.
it does not seem to matter how many games you have played when this occurs. I have seen it happen during really long sessions and this most recent occurance was during the 5th battle of the day.
Observations.
It was possible to get into the config menu (therefore the keyboard actually still works)
While in the config menu I can access the "signal correction" part of the menu. Viewed here my axes are registered correctly. Joystick, Throttle, Rudder inputs all look fine.
It was possible to restore fire control (trigger) by rebinding the same input from joystick.
Making changes to signal correction/axis input did not restore control of any of the axes themselves.
Unfortunately there is no field to actually BIND axes in the settings menu. You can bind "keys" but flight control input binding is (mouse, joystick, gamepad etc) is somewhat automated and no manual option exists that could have forced the game to read those Axes.
Required a Ctrl/Alt/Del escape to desktop and kill/restart of the game client to fix.
Environment (hardware/software)
Windows 10 x64 1903
i7 8086k, 32Gb, 1080ti
Virpil Constellation Alpha + WarBRD base.* (X & Y Axes)
Virpil War BRD Rudder pedals (rZ Axis)
Virpil MongoosT-50CM2 Throttle (Slider Axis. All other hardware axes are inhibited in virpil software)
*This issue has been observed also with Virpil MongoosT-50 grip + T-50 base. May also have been observed with Thrustmaster T16000 joystick.
I am not using any vJoy type driver/softwares to present the hardware to windows/game. It works fine natively.
Thoughts.
It is as if the game decided to not read the config file for controls when I respawned.
These controls are pretty damned solid otherwise. This is a rare bug which I only see very rarely in WoWp. The hardware is NOT at fault, it works very well in pretty much every other sim I use it in and (usually) works fine with WoWp.
This bug costs the player money (unable to kill + repair cost for deaths results in a net loss) which is annoying.
Edited by Ziptop, 14 September 2020 - 10:36 AM.