Access custom keymapping for pitstop?
With adding Moza Wheel and Pedals to the supported Inputs I came across the preset actionmaps you can find here: ...\F1 22\actionmaps It's basically no rocket science to read the XML-Files and ...
Forum Discussion
@HazamelI think I’m wrong as don’t use a wheel. But can you not rebind buttons in the games controller settings menu?
I’m asking because I read that because the game doesn’t officially support moza wheels yet. The game recognises your wheel as a pad.
I’m sorry if I’m talking complete nonsense and no help
What’s more thinking about it. I can’t even remember seeing a turn in option to bind a key to when editing settings.
They do since last update. Wasn’t mentioned anywhere and caused a lot of trouble for moza users. You‘re Not able to bind all keys (accept seems to be locked when there‘s default Schema for example)
Moza Wheels with less buttons than GS and FSR also have issues because buttons are locked that don’t even exist on those wheels.
Current Fix is to remove the preset from the folder and use your custom mapping.
my idea was to add the pitstop line to the custom mapping to finally have immersive pitstops. This button is only hardcoded in the default schemas and nowhere in the settings
- @Hazamel Well on a more positive note. I have noticed some wheels are having the same problem. So did flag the issue with my EA handler and he has asked Codemasters to look into adding more binding options on wheels with fewer buttons. That’s not to say they are going to add it but at least they are looking into it.
I watched a deep dive review off Moza just the other day. Had buttons and many many switches? Do they not count as buttons?All the Wheels that aren't supported with a Default-Schema have the same issue. Most users I know have a keyboard nearby and hit the according button for immersive pitstop or use third party Software to map Wheel-Buttons to keyboard inputs.
There are several threads and bug reports about immersive pitstop like this one: https://answers.ea.com/t5/Technical-Issues/Turn-in-to-pits/m-p/11598775#M1848
I'm fine with the keyboard workaround but having to remap and relearn half of my Buttons on the Wheel is quite a bummer. It's not like with PS-Wheel or Controller that you see a Symbol and know what button it is. The buttons are just numbered. Like "Push button 35 to confirm". Most of the numbers are clustered but with no specific order. So you've to work a lot with a cheatsheet for lesser used buttons 😉
It's just weird that you can set all your buttons like you want as long as your wheel is not offically supported. After that some actions are locked. The only benfit of a supported wheel is that it works out of the box in the way Codemasters thinks it's best.
In my case the button I used for MFD is now the Accept-Button and my Accept-Button is now the Abort-Button which was quite confusing.
The number of buttons depends on the wheel you use. The formula-style GS and FSR have 8 "Button"-buttons, two pressable thumbwheels and the pressable sticks. The five rotary switches on the faceplate can be changed from just turning left or right as a Button-Klick (e.g. for changing Engine-Mapping) to individual "Buttons" for each selection. In theory 60 Buttons 😉 in search for the magic pitstop button I played around with that and the Button-Test-Function and ended up with the result that Button 107 is the highest I got when I was half way round one of the rotary buttons. Seems like other games have the same issue.
Unfortunately Moza has also the ES and CS wheel with way less buttons. They're more like the Logitech-ones with the gamepad-amount of buttons. But they seem to be recognized as "Moza Wheel" excpecting to be an FSR/GS-Wheel. Not like Thrustmaster or Fanatec where you've specific settings for different wheels. Full circle to locked keymappings: Button 35 is hardcoded for Accept and you can't change it. ES/CS-Wheels don't have a Button 35, can't change it, because there's a preset for Moza-Wheels and you're not allwoed to change it 😉
The current solution is to remove the two Moza-Files from the actionmaps-folder and map the buttons as you like and loose the immersive pitstop-option.And because the default-schema is just a plain XML-File my developer-brain hoped for custom-settings beeing also a XML-File anywhere on the filesystem and sneak in that pitstop-settings there.
Featured Places
