dirt rally 2.0 No Force feedback Dirt Rally 2.0

[FleX13 2]

On 2/23/2019 at 10:21 AM, EnsiFerrum said:

The temporary fix is pretty easy.

Open "..\Steam\SteamApps\common\DiRT Rally 2.0\input\devices\device_defines.xml" with any kind of text editor. (Needless to say to make a backup first!)

It should look like this (starting at line 77):

<device id="{038E0EB7-0000-0000-0000-504944564944}" name="ftec_clubsport_v1" priority="100" type="wheel" />
  <device id="{00010EB7-0000-0000-0000-504944564944}" name="ftec_clubsport" version="2" priority="100" type="wheel" />
  <device id="{00040EB7-0000-0000-0000-504944564944}" name="ftec_clubsport" version="3" priority="100" type="wheel" />
  <device id="{0E030EB7-0000-0000-0000-504944564944}" name="ftec_csl" priority="100" type="wheel" />
  <device id="{00050EB7-0000-0000-0000-504944564944}" name="ftec_csl_ps4" priority="100" type="wheel" />
  <device id="{18390EB7-0000-0000-0000-504944564944}" name="ftec_clubsport_pedal" priority="100" type="pedal" />
  <device id="{183B0EB7-0000-0000-0000-504944564944}" name="ftec_clubsport_pedal_v3" version="3" priority="100" type="pedal" />
  <device id="{1A920EB7-0000-0000-0000-504944564944}" name="ftec_clubsport_shifter" priority="100" type="shifter" />
  <device id="{1A930EB7-0000-0000-0000-504944564944}" name="ftec_clubsport_handbrake" priority="100" type="handbrake" />
  <device id="{B65A044F-0000-0000-0000-504944564944}" name="tm_f430" priority="100" type="wheel" official="false" />
  <device id="{B677044F-0000-0000-0000-504944564944}" name="tm_t150" priority="100" type="wheel" />
  <device id="{B66E044F-0000-0000-0000-504944564944}" name="tm_t300_rs" priority="100" type="wheel" ffb_force="0.9" />
  <device id="{B689044F-0000-0000-0000-504944564944}" name="tm_ts_pc" priority="100" type="wheel" ffb_force="0.9" ffb_friction="1.5" />
  <device id="{B667044F-0000-0000-0000-504944564944}" name="tm_t80" priority="100" type="wheel" />
  <device id="{B67F044F-0000-0000-0000-504944564944}" name="tm_tmx" priority="100" type="wheel" />
  <device id="{B671044F-0000-0000-0000-504944564944}" name="tm_f458" priority="100" type="wheel" official="false" />
  <device id="{45030738-0000-0000-0000-504944564944}" name="mc_pro_r" priority="100" type="wheel" official="false" />
  <device id="{B65E044F-0000-0000-0000-504944564944}" name="tm_t500_rs" priority="100" type="wheel" ffb_force="0.9" />
  <device id="{B662044F-0000-0000-0000-504944564944}" name="tm_t500_rs_f1" priority="100" type="wheel" ffb_force="0.9" />
  <device id="{B660044F-0000-0000-0000-504944564944}" name="tm_shifter" priority="100" type="shifter" />
  <device id="{C262046D-0000-0000-0000-504944564944}" name="lg_g920" priority="100" type="wheel" />
  <device id="{C24F046D-0000-0000-0000-504944564944}" name="lg_g29" priority="100" type="wheel" />
  <device id="{10201DD2-0000-0000-0000-504944564944}" name="sim_steering" version="1" priority="100" type="wheel" ffb_force="0.5" />
  <device id="{22301DD2-0000-0000-0000-504944564944}" name="sim_steering" version="2" priority="100" type="wheel" ffb_force="0.5" />
  <device id="{22331DD2-0000-0000-0000-504944564944}" name="sim_steering" version="3" priority="100" type="wheel" ffb_force="0.5" />
  <device id="{804C1FC9-0000-0000-0000-504944564944}" name="simxperience_accuforce_pro" priority="100" type="wheel" />
  <device id="{00110EB7-0000-0000-0000-504944564944}" name="ftec_csr_elite" priority="100" type="wheel" official="false" />
  <device id="{01970EB7-0000-0000-0000-504944564944}" name="ftec_porsche_wheel" priority="100" type="wheel" official="false" />
  <device id="{C294046D-0000-0000-0000-504944564944}" name="lg_driving_force_ex" priority="97" type="wheel" official="false" />
  <device id="{C29A046D-0000-0000-0000-504944564944}" name="lg_driving_force_gt" priority="96" type="wheel" official="false" />
  <device id="{C298046D-0000-0000-0000-504944564944}" name="lg_driving_force_pro" priority="98" type="wheel" ffb_friction="0.15" official="false" />
  <device id="{C216046D-0000-0000-0000-504944564944}" name="lg_dual_action" priority="94" type="pad" official="false" />
  <device id="{C218046D-0000-0000-0000-504944564944}" name="lg_f510" priority="94" type="pad" official="false" />
  <device id="{C219046D-0000-0000-0000-504944564944}" name="lg_f710_and_cordless_rumblepad_2" priority="94" type="pad" official="false" />
  <device id="{C299046D-0000-0000-0000-504944564944}" name="lg_g25" priority="100" type="wheel" />
  <device id="{C29B046D-0000-0000-0000-504944564944}" name="lg_g27" priority="100" type="wheel" />
  <device id="{CA03046D-0000-0000-0000-504944564944}" name="lg_momo_racing" priority="100" type="wheel" ffb_friction="0.15" official="false" />
  <device id="{0034045E-0000-0000-0000-504944564944}" name="ms_sidewinder_ffb" priority="100" type="wheel" ffb="enabled" official="false" />
  <device id="{00030E8F-0000-0000-0000-504944564944}" name="sl_strikefx" priority="94" type="pad" />
  <device id="{910511C0-0000-0000-0000-504944564944}" name="sl_torid" priority="94" type="pad" />
  <device id="{B323044F-0000-0000-0000-504944564944}" name="tm_dual_trigger_3_in_1" priority="94" type="pad" official="false" />
  <device id="{B655044F-0000-0000-0000-504944564944}" name="tm_fgt_3_in_1" priority="100" type="wheel" official="false" />
  <device id="{B653044F-0000-0000-0000-504944564944}" name="tm_rgt_ffb_pro" priority="100" type="wheel" official="false" />
  <device id="{B669044F-0000-0000-0000-504944564944}" name="tm_tx" priority="100" type="wheel" />
  <device id="{00080E8F-0000-0000-0000-504944564944}" name="grid2_pad" priority="100" type="wheel" official="false" />
  <device id="{05C4054C-0000-0000-0000-504944564944}" name="ps4_pad" priority="100" type="pad" />
  <device id="{0BA0054C-0000-0000-0000-504944564944}" name="ps4_pad" priority="100" type="pad" />
  <device id="{B678044F-0000-0000-0000-504944564944}" name="tm_usb_adapter" priority="100" type="pedal" />
  <device id="keyboard" name="keyboard" priority="2" type="keyboard" default="true" />
  <device id="mouse" name="mouse" priority="1" type="mouse" default="true" />
  <device id="xinput_pad" name="xinput_pad" priority="5" type="pad" default="true" />
  <device id="xinput_wheel" name="xinput_wheel" priority="99" type="wheel" ffb_force="10" default="true" />
  <device id="pad_virtual" name="pad_virtual" priority="0" type="pad" default="true" />
  <device id="lib_direct_input" name="lib_direct_input" priority="5" type="unknown" default="true" />
  <device id="lib_direct_input_pad" name="lib_direct_input_pad" priority="5" type="pad" default="true" />
  <device id="lib_direct_input_wheel" name="lib_direct_input_wheel" priority="99" type="wheel" default="true" />
  <device id="{C626046D-0000-0000-0000-504944564944}" name="space_navigator" priority="0" type="not_supported" />
  <device id="{046DBEEF-0000-0000-0000-504944564944}" name="space_navigator_driver" priority="0" type="not_supported" />
  <device id="{B695044F-0000-0000-0000-504944564944}" name="tm_tss_hb" priority="100" type="handbrake" />
  <device id="{B692044F-0000-0000-0000-504944564944}" name="tm_ts_xw" priority="100" type="wheel" ffb_force="0.9" ffb_friction="1.5" />
  <device id="{B684044F-0000-0000-0000-504944564944}" name="tm_t_gt" priority="100" type="wheel" ffb_force="0.9" ffb_friction="1.5" />
  <device id="{B681044F-0000-0000-0000-504944564944}" name="tm_t_gt" priority="100" type="not_supported" />
  <device id="{62040EB7-0000-0000-0000-504944564944}" name="ftec_csl_pedals" priority="100" type="pedal" />

Lets have a look at the comments in the very same file (line 37 - 54):

<!-- 
	[..]
	ffb (Optional)
      {
        default - Default - Uses the value returned from the drivers
        enabled - Force enables the ffb even if the drivers return disabled.
        disabled - Force disables the ffb even if the drivers return enabled.
      }
      ffb_force (Optional)
      {
        1.0 - Default
      }
      ffb_friction (Optional)
      {
        1.0 - Default
      }
      ffb_high_pass (Optional)
      {
        0.0 - Default
      }
	[..]
-->

Look for your steering wheel and add ffb_force="5.0" ffb_friction="1.5" to that line.

Should look like this:

<device id="{0E030EB7-0000-0000-0000-504944564944}" name="ftec_csl" priority="100" type="wheel" ffb_force="5.0" ffb_friction="1.5"/>

Save the file.

Start up Dirt Rally 2.0 and go to the FFB Options!

You need to lower "Self Aligning Torque"!! Otherwise your wheel will start to clip!! The "Self Aligning Torque" will override all other forces. I have mine at 10 with this workaround. 
"Steering Center Force Enabled" I have set to off.

Alter the other FFB parameters to your liking.

I have attached an edited device_defines.xml to this post.
BUT: I don't know if the numbers are the right ones for every wheel.
Try it, alter it to your liking and give feedback.

No to Codemaster:
@ChristinaMc Still not understandable for me why you haven't turned to the Early Access program as you did with DR1! I remember there was a similar FFB problem discovered in EA and you managed to get really good FFB way before the official launch. And wondering how this could slip through QA.

 

device_defines.xml

What are your wheel profile settings?

[EnsiFerrum 102]

 

[FleX13 2]

1 hour ago, EnsiFerrum said:

 

Thanks man, will definately try those.

But what I actually ment was your fanatec wheel settings: ff, dri, for, spr, dpr, sho, fei ?

[EnsiFerrum 102]

1 hour ago, FleX13 said:

Thanks man, will definately try those.

But what I actually ment was your fanatec wheel settings: ff, dri, for, spr, dpr, sho, fei ?

These are my current Fanatec settings.
For Dirt 2.0 I use the Profile "S_3".

[Hub67 18]

I'm in the same boat with my T300rs - FFB is horrible.  What I don't understand is why CM isn't answering anyone on this?  

Don't they care?  

[Algui 0]

Hello,

 With my Fanatec CSL elite PS4, no road feel, no collision, no bump ... just Force in the wheel ...

Excuse me for my english !

 

[Gauthier 17]

Is there an update about this issue?

[Tobi1234 0]

Here my opinion with the Accuforce V2. The FFB is really great with the simmcomander software. I love it.

[virgism 51]

 

On 2/26/2019 at 9:43 PM, Hub67 said:

I'm in the same boat with my T300rs - FFB is horrible.  What I don't understand is why CM isn't answering anyone on this?  

Don't they care?  

I have T300RS too - updated drivers to latest, edited XML file and applied exact settings from DR1 :

https://steamcommunity.com/sharedfiles/filedetails/?id=681336327

What i can tell - FFB is better now than DR1(they are really bad in this game) , close enough to RBR.

[gigiotto59 16]

unfortunately the wheel feedback issue  is an old problem that Codemasters shows in every racing game since many years ago. I donìt know what they do during the game test and what they mean when say " list of compatibles wheels ".  In the years I have learned the lesson, I won't buy a CM game the first day but I wait 5-6 months, price go down and patch to resolve the problems come up.

[XVinoRossoX 0]

This is pretty pitiful by Codemasters to be honest. This should have been fixed already.... Back to Asseto

[Redperil68 12]

 

I can understand PC issues but on closed platforms there is no excuse, except you wanted to get the end of year income figures up.

[KalRagnar9 2]

Same problem here with G920 on Xbox One X. No force feedback.

and not even avaible the settings of the tire slip and engine vibrations.

Please an update on this, is really disappointed

[KimJonUn 5]

Do CM not realise that there are loads and loads of people like myself who are holding off on buying DR2 because of this problem? 

There are threads on forums all over the internet saying the exact same thing.  

Madness.

[WOTcaptain 1]

Still a problem on Xbox One.  Hoping for a patch soon.  Seems like an easy fix from what people are editing in the code on PC.

[Hub67 18]

21 hours ago, KimJonUn said:

Do CM not realise that there are loads and loads of people like myself who are holding off on buying DR2 because of this problem? 

There are threads on forums all over the internet saying the exact same thing.  

Madness.

Put me in the categories of "I wouldn't have bought it if I knew the FFB was screwed up" ... and "I want my money back"!  

[Crash72 2]

WTH Codemasters??!!! Why have you not fixed this issue yet or provided an official workaround/statement? I've tried the workaround posted and it did not fix my issue. This unacceptable, the game is worthless without fbb. I didn't have to go searching for a fix with DR1. I want my money back from this unsupported garbage.

[Bailey619 9]

fix your ffb in Dirt Rally 2..... what is going on?   Why did none of the reviews say this was a problem?   why don't they answer anyone?

[Hub67 18]

I want to start a thread “Who wants a refund” ... maybe they’ll listen to that?  

[Latvalla 3]

So what, nothing new since 25 February? 

FFB trouble still there even though tweaking a bit the code. The feeling of road surfaces does not exists. 

Please, can you do something? 

[VeganZombie 2]

 

 

 

[Crash72 2]

I updated TM drivers, nvidia drivers, made change to file and still no FFB. When will this be fixed? I have t300rs

[Al66 7]

Hello Codemasters,

if no fix in this Issue, at least some Information for the Custumers?

[SirPhilMcKraken 279]

1 hour ago, Al66 said:

Hello Codemasters,

if no fix in this Issue, at least some Information for the Custumers?

 

 

[Crash72 2]

I finally got some progress with getting this hot garbage to work with my steering wheel. T300RS

Adding ffb='enabled' to the relevant line in the device file got it working. 

Feedback is strong now but still doesn't feel quite right. I hope that can be tuned in the settings.

 

Again, Codemasters, this is in no way acceptable. Most people playing the game won't even have a proper XML editor installed.

Ya'll should send money to the person that posted the XML fix info since it's clear you're doing nothing in the way of support.

This is coming from someone that works as a software consultant. Your support is weak/non-existent.