Wreckfest and DD2 2.0
Robert Mezzone
Member
I posted settings for Wreckfest which at the time I thought were good but looking back they weren't. Since then I've learned a lot about configuring a wheel and Wreckfest and came up with the following. This is for a DD2 and R300 not sure how they will work with other wheelbases, my guess is fine with DD1, ymmv.
This game is very finicky, including in game tuning. I posted in game settings for a couple of tracks to test with.
DD2 with 400 Driver, R300 wheel.
You should make backups of the two files prior to making any changes.
I would restart the game after making any changes.
Once its setup properly imo this game is as good as Dirt Rally or any other game I've played.
Looks like a lot but takes a minute at most once you locate the files.
Would appreciate any feedback.
Jim
Open file explorer navigate to your Steam Library\steamapps\common\Wreckfest\tools
Holding down shift, right click anywhere in the folder and select "Open Powershell Window here"
"dir" to confirm DeviceOut.exe is in the current directory.
./deviceout.exe >deviceoutOUTPUT.txt
notepad .\deviceoutOUTPUT.txt (or type "notepad devi" hit the tab key until it displays the complete file name followed by enter.
you need the instance GUID number and ProductName for your wheel
"index": 0,
"size": 1100,
"instance": "{D291D870-545C-11EB-8001-444553540000}",
"product": "{70EB7-0000-0000-0000-504944564944}",
"type": "DI8DEVTYPE_DRIVING (0x16:0x3)",
"instanceName": "FANATEC Podium Wheel Base DD2",
"productName": "FANATEC Podium Wheel Base DD2",
"FFGuid": "0x3CCED46F",
"usagePage": "Generic_Desktop_Page(0x1)",
"usage": "0x4",
"isXInput": false
Using notepad open "Steam Library\steamapps\common\Wreckfest\customWheels.json"
replace productname EXAMPLE and productGUID GUID with the info recorded above
"productName": "EXAMPLE",
"productGUID": "{GUID}"
In my case customwheels.json looks like the following
"productName": "FANATEC Podium Wheel Base DD2",
"productGUID": "{D291D870-545C-11EB-8001-444553540000}"
Save and close the file.
==================================================
To test if the game is detecting your wheel do the following
Navigate to "\Steam Library\steamapps\common\mods"
make a new folder called temp
"\Steam Library\steamapps\common\Wreckfest\mods\temp"
navigate to
"\Steam Library\steamapps\common\Wreckfest\data\vehicle\shared\physics\forcefeedback\"
copy forcefeedback_dd.vffb to the the temp folder you created in the previous step "\Steam Library\steamapps\common\mods\temp
navigate to
"\Steam Library\steamapps\common\Wreckfest\bagedit"
open BagEditCommunity.exe
"file" "open" "\Steam Library\steamapps\common\Wreckfest\mods\temp\forcefeedback_dd.vffb
Move the slider to Wheel Friction to a value of 200.
File, Save.
Right click on the file in the display pane and select "Show In Explorer"
Copy forcefeedback_dd.vffb to "\Steam Library\steamapps\common\Wreckfest\data\vehicle\shared\physics\forcefeedback\" overwriting the existing file.
Test, wheel should be tight.
Revert back to 0 when done.
Now you can open the vffb file and edit the FFB settings directly.
PC mode
Wheel Properties
540
49
On
6
2
Off
Off
20
100
100
100
Off
Off
In game settings
83
0
74
-30
0
90
0
80
0
41
0
0
0
0
0
Audio - crazy as it sounds, this is one of the most important settings.
Engine - 13 (this allows you to appreciate the mayhem of this game)
forcefeedback_dd.vffb
Wheel Friction -10
In game tuning
Tristar (Race engine etc.)
Rockfield Roughspot
3
2
5
3
Savolax Sandpit
1
4
3
3
Firerock Raceway
5
4
1
3
Comments
Forgot to explain what the above does.
First step runs a Wreckfest utility to extract the DD2 GUID information from the windows registry.
You take that value and add it to customwheels.json so Wreckfest can better communicate with the DD2.
The next part isn't necessary its just a quick test to confirm that the above step is working, you should feel a difference if you change wheel weight to 200.
You have to move the FFB file to a temp folder located under mods in order to edit the file. Any other location it's read-only.
The rest is self-explanatory.
Because I included the full path to each file it seems like a lot but takes like 30 seconds.
After adding the GUID to the json file you should feel a noticeable difference in FFB.
I don't see why this wouldn't work with a DD1 after extracting the GUID.
If anyone with a DD2 follows this procedure I'd be curious if your GUID is the same, I believe it should be.
Jim
This wasn't necessary with my DD1.