GRID Autosport feels closer to an entry in the Forza series than it does the previous GRID games, especially when it comes to the feel of driving with a wheel. Whereas the earlier titles treated the wheel as just a joystick, Autosport feels much more like driving an actual car. The return of the cockpit view, even if it still leaves a lot to be desired, is much appreciated.
Unfortunately, when you try to play with a Logitech G29 or G920, you can barely even navigate the menus because the default bindings are completely wrong for a wheel and pedal set. The menu constantly scrolls unless you hold down the throttle, which makes it nearly impossible to bind the pedals to accelerate and brake. You could rightfully assume that the game is just broken when using an unsupported wheel.
Thankfully, with a little text file editing, we can fix all of those problems and you will have a very nice force feedback wheel to play with. In this guide, I will show you how to make GRID Autosport support these wheels and what settings to use in G HUB and in-game to provide the best experience.
Device Action Map Files
Every supported input device has a file (called the device action map) that defines it and its button bindings. In order to add support for new wheels, we need to make a new action map file for the device.
When GRID Autosport doesn't recognize a device, as is the case for the G29 and G920, it uses a default control scheme simply called the "Direct Input Device." This could be either a gamepad or a wheel and, unfortunately, it is very much setup for a gamepad, leading to the constant menu scrolling problem.
In order to get the buttons configured on the wheel properly, we need to replace the Direct Input Device settings file.
Device Action Map
Download the device action map file for your wheel:
Place it into Steam Library\steamapps\common\GRID Autosport\input, replacing the existing file.
Force Feedback Settings
We can improve the force feedback effects a little bit by editing the following file in your Steam Library:
Edit the default device listing as follows:
<FFBDevice name="default" scaleForce="1.2" scaleFriction="0.3" baseFriction="0.05" maxFriction="100.0" scaleEffects="1.19" delay="0.0"/>
These are the settings defined for the G27, which is the closest wheel to the G29 or G920 that existed at the time.
G HUB Settings
Unlike previous entries in the series, this game plays with a far more realistic steering control, allowing us to use a much larger steering angle than the 180° I used for those. I found that 540° works well for all the cars except the open wheels, where I prefer 360°.
Create a new profile for GRID Autosport (GRIDAutosport_avx.exe) with the following settings:
|Operating Range||540° / 360° (Open Wheel)|
GRID Autosport Settings
Until you can load the new Direct Input Device settings, you will have to hold the throttle pedal part way to stop the menus from scrolling constantly.
In Options & Extras > Options > Controls:
Choose the "Direct Input Device" preset. Now that you can navigate the menus properly using the wheel, feel free to customize the buttons as you see fit.
In Options & Extras > Options > Controls > Advanced Options:
Make sure to set the Steering Deadzone to 0%, as the default is 20%, which makes the wheel feel completely broken.
In Options & Extras > Options > Vibration:
Vibration Strength controls the vibrations you feel, mostly based on the texture of the road surface. Setting this much higher will make the wheel very noisy.
Wheel Strength controls the main force feedback you feel. This is how you will feel the amount of grip your tires have.
Wheel Weight is a damper force that adds a constant weight to the wheel. Setting this too high makes the wheel feel very sluggish. I prefer to turn it off as it doesn't add anything useful to the force feedback.
Game Progress Not Saving?
While I was figuring out how all of this worked, I thought GRID Autosport had a horrible bug that would prevent the game from saving any data, whether it be control settings or actual game progress. I saw that many other people had this problem, and the one thing they had in common was that they all had modified the game files in some way. This isn't a "bug" at all, but rather an anti-cheat mechanism the game has built in to it. I had added several files, trying out different settings, which had triggered this mechanism.
Thankfully, modifying the two files we need does NOT cause this to happen, just make sure not to add any additional files into those folders, like creating a backup copy of the original files.
When I initially got this game and couldn't get the wheel to work, I was very disappointed and didn't really play it. Now that I put the time in to get this to work, I've found a whole new appreciation for this game series. There is a lot of fun to be had here.
Let me know if you have any comments or questions.