If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-08-22
Oops! Didn't check this more than a year old post. Sorry :(
You probably won't read the answer but here it goes as other users might encounter the same problem:
Long time since I played DR2 and I'm not sure but I seem to recall that I had the same problem and then fixed it.
So can't remember exactly what was the problem but it's not important as even fixed it won't do much by itself since Codemasters has changed it's code and now gives the same crappy heavy steering filtering for all xinput devices (be it a gamepad or wheel, dunno if it's a bug from them or a new "feature", still didn't test F1 2020 tho, so dunno if they corrected it or not but probably not xD).
So for gamepads users no more tricking the game that you got a wheel instead and for xinput wheel owners it's now not just the forced deadzone that might be the problem.
I remember trying to finish the first stage without a roll barrel or not going out of the road and it was almost impossible with the ingame filtering. Then I found a way to get raw input and it was a child's play. Night and day, incredible.
To get raw input read the post I posted on "Question about raw data". But now that I think of it if it gives an error you can't use this utility to disable xinput (or disable the steering axis), and if I'm not mistaken DR2 needs to have it disabled (as Dakar 18 or Spintires do I think...) as it gives priority to xinput devices.
So I'll see if I finally release the updated version but it probably be months before it since I currently don't have an usable graphic card (my 5 year old gpu stopped working some months ago) and since next gen consoles are around the corner (and I wasn't playing that much anyway) I've been waiting for what's needed to at least match them before I buy a new one. Until then I have hard time to test or retest modern games to see if everything is working correctly as the fps are just unbearable for some xD.
But maybe the main reason I still didn't released it is that it's a pain in the ar** to do a new release as each game has it's needs, so each time I have to retest them all to check if everything works correctly and the changes didn't introduce new bugs, update the readme each time accordingly and provide presets so users aren't lost when testing it, lots of annoying work/testing.
Was hopping that the vJoy route (as described in the quoted thread above) could be an universal fix and strip the utility of a big chunk of it's code but the damn pCars1/2 don't correctly work with it, grrr xD
Cheers,
Dwayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So DiRT Rally 2.0 is simply crashes for me if I try to use dx ACE.
(For DiRT 4 it works perfectly!)
I attached the error message.
Please help if you can to find a way to fix this!
Oops! Didn't check this more than a year old post. Sorry :(
You probably won't read the answer but here it goes as other users might encounter the same problem:
Long time since I played DR2 and I'm not sure but I seem to recall that I had the same problem and then fixed it.
So can't remember exactly what was the problem but it's not important as even fixed it won't do much by itself since Codemasters has changed it's code and now gives the same crappy heavy steering filtering for all xinput devices (be it a gamepad or wheel, dunno if it's a bug from them or a new "feature", still didn't test F1 2020 tho, so dunno if they corrected it or not but probably not xD).
So for gamepads users no more tricking the game that you got a wheel instead and for xinput wheel owners it's now not just the forced deadzone that might be the problem.
I remember trying to finish the first stage without a roll barrel or not going out of the road and it was almost impossible with the ingame filtering. Then I found a way to get raw input and it was a child's play. Night and day, incredible.
To get raw input read the post I posted on "Question about raw data". But now that I think of it if it gives an error you can't use this utility to disable xinput (or disable the steering axis), and if I'm not mistaken DR2 needs to have it disabled (as Dakar 18 or Spintires do I think...) as it gives priority to xinput devices.
So I'll see if I finally release the updated version but it probably be months before it since I currently don't have an usable graphic card (my 5 year old gpu stopped working some months ago) and since next gen consoles are around the corner (and I wasn't playing that much anyway) I've been waiting for what's needed to at least match them before I buy a new one. Until then I have hard time to test or retest modern games to see if everything is working correctly as the fps are just unbearable for some xD.
But maybe the main reason I still didn't released it is that it's a pain in the ar** to do a new release as each game has it's needs, so each time I have to retest them all to check if everything works correctly and the changes didn't introduce new bugs, update the readme each time accordingly and provide presets so users aren't lost when testing it, lots of annoying work/testing.
Was hopping that the vJoy route (as described in the quoted thread above) could be an universal fix and strip the utility of a big chunk of it's code but the damn pCars1/2 don't correctly work with it, grrr xD
Cheers,
Dwayne