I'm surprised this isn't already a recorded issue, but there's an entire subset of VR Missions where you play in first person moving around freely, but neither stick will let you strafe despite the first mission testing your ability to do that with a bunch of targets hidden in cubbies. (Also there's a mod to make the whole game play in that perspective though that doesn't seem like a good idea...)
The game's config lets you separately remap keys for that mode because of how differently it controls, but there it just makes the difficult task of keeping track of what button does what on a PS2 controller because the config gives you that instead of telling what each button does for mapping even worse. Trying to remap the settings in the config also overwrite's the v's control setup, and resetting them in v'sfix in overwrites both control schemes again, so currently you have to figure out which ini file stores what, which button does what in that mode, and then edit that through a series of trial and error and ini backing up/overwriting to try and come up with a more fitting control scheme just for that mode.
It feels like what's needed is:
A list of which mapping does what in which perspective be kept to make it possible to set the controls without trial and error
One of the stick inputs be set to strafe instead of turn
An option for V's Fix to not overwrite the first person mode's mappings.
I'm surprised this isn't already a recorded issue, but there's an entire subset of VR Missions where you play in first person moving around freely, but neither stick will let you strafe despite the first mission testing your ability to do that with a bunch of targets hidden in cubbies. (Also there's a mod to make the whole game play in that perspective though that doesn't seem like a good idea...)
The game's config lets you separately remap keys for that mode because of how differently it controls, but there it just makes the difficult task of keeping track of what button does what on a PS2 controller because the config gives you that instead of telling what each button does for mapping even worse. Trying to remap the settings in the config also overwrite's the v's control setup, and resetting them in v'sfix in overwrites both control schemes again, so currently you have to figure out which ini file stores what, which button does what in that mode, and then edit that through a series of trial and error and ini backing up/overwriting to try and come up with a more fitting control scheme just for that mode.
It feels like what's needed is: