Fanatec Wheel crashes on stage load, game breaking problem

[|Luas|]

This started happening only a couple months after the game's release but I just haven't made the effort to find a fix. Everytime I load a stage my wheel gets disconnected. This doesn't happen in iRacing, or rFactor, or any other racing games. I've even switched to a new PC with a new install and the problem still persists. If anyone could help resolve this it would be greatly appreciated.

[MystaMagoo]

which fanatec?
pedals too?
more info needed.

using a fanatec here and no problems in any games

[CarDr]

First things to check; unplug any other USB controllers (game pads & flight sticks). Plug wheel into a USB2 connector (green) on motherboard- do not use a USB hub. Remapping the pause button has caused problems for a few.

Need to reset to default settings, delete the controller config save file found in ' c/documents/mygames/dirtrally/hardware' folder. The game will create a new one when launched.

Sometimes 3rd party controller apps like V-joy can cause issues.

If you still have problems additional info needed; OS, Fanatec driver & firmware numbers, system specs.

[|Luas|]

Originally posted by MystaMagoo:

which fanatec?
pedals too?
more info needed.

using a fanatec here and no problems in any games

V2 base and clubsport V2 pedals

[|Luas|]

Originally posted by CarDr:

First things to check; unplug any other USB controllers (game pads & flight sticks). Plug wheel into a USB2 connector (green) on motherboard- do not use a USB hub. Remapping the pause button has caused problems for a few.

Need to reset to default settings, delete the controller config save file found in ' c/documents/mygames/dirtrally/hardware' folder. The game will create a new one when launched.

Sometimes 3rd party controller apps like V-joy can cause issues.

If you still have problems additional info needed; OS, Fanatec driver & firmware numbers, system specs.

I'll give this a try and get back to you

[|Luas|]

Originally posted by CarDr:

First things to check; unplug any other USB controllers (game pads & flight sticks). Plug wheel into a USB2 connector (green) on motherboard- do not use a USB hub. Remapping the pause button has caused problems for a few.

Need to reset to default settings, delete the controller config save file found in ' c/documents/mygames/dirtrally/hardware' folder. The game will create a new one when launched.

Sometimes 3rd party controller apps like V-joy can cause issues.

If you still have problems additional info needed; OS, Fanatec driver & firmware numbers, system specs.

The issue still persists.
OS: W10 64Bit
Driver: v289
System: i5 7600k, GTX 1070, 500GB SSD, msi MOBO

[CarDr]

The other games working tells us your PC is not all FUBAR, but Codemasters EGO game engine (CM titles only) can be more sensitive to small problems that others may overlook. Corrupt or broken drivers (audio/video) are problems the EGO engine will pick up on, keep this in mind- but I would try some other things first.

They added Fanatec’s SKU into this title during EA and offers full support for their wheels including the V2 that was in production at that time. V2.5 & CSL may need some slight file modes for full support as their drivers were not created back then. FWIW, I picked this title up on day 1 of EA; CSWV2 , CSPV2, CSSSQV1, & CSHBV1, driver 205 or 219, W8.1 pro, ASUS X99MB & 970, I7 5820k – and never had a problem. I know this does not help much, but the problem you have will be something on your side. DR, Fanatec, W7, 8.1 or 10 will work.

You state the wheel disconnects, from the game or your PC? You would hear the windows chime though your sound system if it was a PC/USB disconnect. For wheel settings: DR's Wheel config save will reset to default IF you use KB or M to enter the game after the first splash screen. You must use a button on the wheel to “continue” at that splash screen. Using the BMW rim this will be the purple button on the lower right for enter/yes/cont. The gray button just above for no/menu back.

Are you able to select the wheel in the in game controller menu and complete the advanced wheel settings, calibration and save? You should be able to work all of the in game menus from the wheel when it’s setup (BMW &F! rims. I do not have a universal hub for testing but they should be OK). Run the wheel in PC mode, not XB1 or G25/PS modes.

Controller issues I’ve seen reported with other titles: settings within Steam big picture mode and W10 game setting for MS/Xbox gaming. Settings selected within those apps can override in game selections. Open those apps and unselect everything. Do you have the proper USB drivers for W10 installed from MSI website?

[MystaMagoo]

latest driver is 2.92 afaik which I'm using.

[|Luas|]

Originally posted by CarDr:

The other games working tells us your PC is not all FUBAR, but Codemasters EGO game engine (CM titles only) can be more sensitive to small problems that others may overlook. Corrupt or broken drivers (audio/video) are problems the EGO engine will pick up on, keep this in mind- but I would try some other things first.

They added Fanatec’s SKU into this title during EA and offers full support for their wheels including the V2 that was in production at that time. V2.5 & CSL may need some slight file modes for full support as their drivers were not created back then. FWIW, I picked this title up on day 1 of EA; CSWV2 , CSPV2, CSSSQV1, & CSHBV1, driver 205 or 219, W8.1 pro, ASUS X99MB & 970, I7 5820k – and never had a problem. I know this does not help much, but the problem you have will be something on your side. DR, Fanatec, W7, 8.1 or 10 will work.

You state the wheel disconnects, from the game or your PC? You would hear the windows chime though your sound system if it was a PC/USB disconnect. For wheel settings: DR's Wheel config save will reset to default IF you use KB or M to enter the game after the first splash screen. You must use a button on the wheel to “continue” at that splash screen. Using the BMW rim this will be the purple button on the lower right for enter/yes/cont. The gray button just above for no/menu back.

Are you able to select the wheel in the in game controller menu and complete the advanced wheel settings, calibration and save? You should be able to work all of the in game menus from the wheel when it’s setup (BMW &F! rims. I do not have a universal hub for testing but they should be OK). Run the wheel in PC mode, not XB1 or G25/PS modes.

Controller issues I’ve seen reported with other titles: settings within Steam big picture mode and W10 game setting for MS/Xbox gaming. Settings selected within those apps can override in game selections. Open those apps and unselect everything. Do you have the proper USB drivers for W10 installed from MSI website?

I enter the game through a button on the wheel and am able to configure it. The disconnect is from the PC when I am placed into a stage. Where can I make sure its in PC mode? I've never heard of that before and it seems to be the only issue I can think of from what you've said.

[CarDr]

If you don’t know, than most likely you are using it in PC mode- normal startup. G27 emulator (PS3 mode) requires holding 2 buttons down after startup. The PS3 mode may have been removed from the later firmware – conditions required from Sony for the PS4 contract.

XBO mode requires the 2nd gen universal hubs or specified rims with button press for connect/mode change. You can DL manuals from Fanatec’s web site for the base and each wheel you have.

Any chance you are confusing this disconnect with the ‘hold handbrake option’? If selected within the game options, you will sit at the stage line and no countdown to start until handbrake signal is received.

Edit: it’s called automatic launch control in the preferences menu. Turn it on if you are not using handbrake.

[MystaMagoo]

did you try driver 2.92?
correct os version installed?

[CarDr]

Your Fanatec driver app does have trouble logs. Search your C drive for “ FW-error.log ” and “ FW-FFB.log “. If it has anything stored it will list the latest event first. Call: Date and time stamp near the top left and the game title should be in the next line down.

edit: on my system it was under users - public

[|Luas|]

Originally posted by CarDr:

Your Fanatec driver app does have trouble logs. Search your C drive for “ FW-error.log ” and “ FW-FFB.log “. If it has anything stored it will list the latest event first. Call: Date and time stamp near the top left and the game title should be in the next line down.

edit: on my system it was under users - public

Got it to start a stage but then it crashed after a couple seconds :p

Endor FW Forcefeedback Driver
Build: Apr 4 2017 18:19:29
Call : 1/30/2018 19:57:49

SystemInfo PROCESSOR_ARCHITECTURE_INTEL (x86)
OSVersionInfo Version Number = 6.2
OSVersionInfo Operating System =
OSVersionInfo CSD Version =

** FW-FFB Error tracing for C:\Program Files (x86)\Steam\steamapps\common\DiRT Rally\drt.exe **

[START TRACE]

[CarDr]

You can file a report with customer service with Fanatec and/or CM. include your specs and this log with one full trace event, each new event will start with date/time stamp. Your problem is rare, I only found one other report with no response, but I did not search CMs offical site.

http://steamcommunity.com/app/310560/discussions/1/359543542236070623/

Having a log file shows you are experiencing a conflict between DR and your wheel driver. Possibilities I can think of; corrupt files, broken drivers, another program causing interference.
Program interference; AV programs like Malwarebytes have caused problems for some. 3rd party controller mapping apps, steams controller settings, and W10 MS/Xbox gaming app also have controller settings that can cause problems with some titles. For W10 and steam, un-selecting all options should solve those issues. G-force experience from NVidia has caused some problems at times.

Corrupt game files; verifying the game files should do the job, verifying more than once may be required. Worse case would be removing the suspected file before verification allowing a fresh install of that file.

Broken drivers; this problem happens when your system tries to update an existing one. Some of your old files may remain detectible on your HD when they should have been deleted or overwrote. A lot of titles may overlook them, but some may try to activate those causing troubles. Normal un-install of those drivers will not remove those rogue files, a driver cleaner app will search them out for you or you can try a manual search on your own. A lot of the steam error code 41 during EA was caused from broken GPU drivers.

W10; some players had problems with the W7/8 to W10 update and had to do a complete fresh W10 install. Some have forgotten to update their MB drivers for chipset and USB drivers. Best location is you MB manufactures web site.

Tech support may be able to send you in the right direction with the log file, saving time. An OS reinstall would cover a lot of possible problems if you want to take that route.

[|Luas|]

Originally posted by CarDr:

You can file a report with customer service with Fanatec and/or CM. include your specs and this log with one full trace event, each new event will start with date/time stamp. Your problem is rare, I only found one other report with no response, but I did not search CMs offical site.

http://steamcommunity.com/app/310560/discussions/1/359543542236070623/

Having a log file shows you are experiencing a conflict between DR and your wheel driver. Possibilities I can think of; corrupt files, broken drivers, another program causing interference.
Program interference; AV programs like Malwarebytes have caused problems for some. 3rd party controller mapping apps, steams controller settings, and W10 MS/Xbox gaming app also have controller settings that can cause problems with some titles. For W10 and steam, un-selecting all options should solve those issues. G-force experience from NVidia has caused some problems at times.

Corrupt game files; verifying the game files should do the job, verifying more than once may be required. Worse case would be removing the suspected file before verification allowing a fresh install of that file.

Broken drivers; this problem happens when your system tries to update an existing one. Some of your old files may remain detectible on your HD when they should have been deleted or overwrote. A lot of titles may overlook them, but some may try to activate those causing troubles. Normal un-install of those drivers will not remove those rogue files, a driver cleaner app will search them out for you or you can try a manual search on your own. A lot of the steam error code 41 during EA was caused from broken GPU drivers.

W10; some players had problems with the W7/8 to W10 update and had to do a complete fresh W10 install. Some have forgotten to update their MB drivers for chipset and USB drivers. Best location is you MB manufactures web site.

Tech support may be able to send you in the right direction with the log file, saving time. An OS reinstall would cover a lot of possible problems if you want to take that route.

Thanks mate, I've filed a report and my OS is a fresh install. I'll start going through the rest of the list and report back if anything works.

[MystaMagoo]

make sure to install 64bit drivers as you say you have win10 x64.

latest Fanatec is 292 not 289