Codemasters Dirt Rally Plugin 2.0.0.3

The truth is that for now I have given up waiting for this weekend to try the movement system in Dirt Rally 2.0, and you give me a joy when you say that this works perfectly, at least one can enjoy 100 % of the simulation ...

A greeting.



La verdad es que ya de momento he desistido a la espera de este fin de semana probar el sistema de movimiento en Dirt Rally 2.0, y me das una alegria cuando dices que en este te funciona perfectamente, por lo menos en uno podremos disfrutar al 100% de la simulación...

Un saludo.

I finally got this working, not sure what was the fix but this is what I did.

Ran the game from Steam instead of Sim Commander
Once in the menus of Dirt Rally I then opened Game Engine and then Game Manager and it attached itself right away

Joined a rally and lo'n'behold she had movement!

I guess it could have been Sim Commander making drt.exe forward its telemetry to port 10001 instead of 4123 which this plugin uses, but I could of sworn I had tried running through Steam directly before and also the UDP port forward in Sim Commander.

None the less I got it working and I am happy, now to tweak the settings some more. Going over jumps is quite the sensation I had Pitch and Roll set backwards because I copied my Pcars2 axis assignments for Dirt Rally, and man did that feel weird in VR having the car lean forward going up hill and roll to the right going over bumps on the right side lol.

Ha!!!!
I came here to report the same thing, only using a different method in order to figure it all out.
Weird that we both managed to do it on the same day.

It looks like using more than one UDP-based telemetry program was our issue.
But why all of a sudden...it always worked perfectly up until a few weeks ago without any manual intervention or settings changes???

I was wondering why it worked fine if my DiRT hardware_cfg file was set using port "4123" when running DiRT Rally directly from Steam, but whenever I'd either start the game from Sim Commander, or ran Sim Commander after starting the game from Steam ("wait on" mode), nothing would work.


I kept going back into the hardware_cfg file after every restart and I'd see that the port would be overwritten to "10001" again.

Finally I left it that way, and in Sim Commander under the DiRT Rally game settings I changed the Port Forward option from "0" to "4123".

Then went back and launched it from Sim Commander....and EVERYTHING is working as it should....FINALLY!!!!


I've also added a Wait On "drt-vr.exe " in the game's Advanced Settings tab of Sim Commander.


This problem only popped up a few weeks ago, so I'm not sure which element had changed.
It seems that the common issue was the multiple UDP telemetry apps either stealing or overwriting the ports.

I guess that if I were to add a Dashboard app using my tablet, it had better have additional UDP port forwarding abilities as well.
That is unless I can add an additional forwarded port in Sim Commander.


NOTE : I've also done the same setup now with DiRT Rally 2.0, in case anyone was having issues with that title.

Both games are now rockin' as they should be!

EDIT : After figuring this out, I've also concluded that it's the EXACT same issue which I was having with Forza 7 on the PC.
Fixed it, and now both SimTools & Sim Commander are playing nicely with the game.

It sounds like this issue may have originated on either CodeMaster's or SimXperience's end.

People using the Next Level Racing v3 Motion Platform are also reporting that they aren't getting movement in the original DiRT Rally anymore.

All I know is that for my setup, the entry for port# "4123" in the hardware_cfg.xml file kept randomly changing to "10001".



For now, the two fixes I've come across work for those of us using SimTools + Sim Commander (SimVibe or SimXperience DD wheels) are listed below.

Fix #1 (SimTools + Sim Commander):

Keep the port# as "10001" in Dirt Rally's hardware_cfg.xml, and change the UDP Port Forwarding feature for DiRT Rally's game settings in Sim Commander from "0" to "4123".

OR

Fix #2:

Simply make sure that these two highlighted lines are in your DiRT Rally's "hardware_cfg.xml" under "<motion platform>":

<motion_platform>
<dbox enabled="false" />
<udp enabled="true" extradata="3" ip="127.0.0.1" port="4123" delay="1" />
<udp enabled="true" extradata="3" ip="127.0.0.1" port="10001" delay="1" />
<fanatec enabled="false" pedalVibrationScale="1.0" wheelVibrationScale="1.0" ledTrueForGearsFalseForSpeed="true" />
</motion_platform>


port = 4123 is for SimTools motion
port = 10001 is for SimVibe in Sim Commander



NOTE : If you aren't getting any motion in DiRT Rally when using Simtools alone, just make sure that your "hardware_cfg.xml" file has these entries at a minimum:
(the highlighted entry is for SimTools motion)

<motion_platform>
<dbox enabled="false" />
<udp enabled="true" extradata="3" ip="127.0.0.1" port="4123" delay="1" />
<fanatec enabled="false" pedalVibrationScale="1.0" wheelVibrationScale="1.0" ledTrueForGearsFalseForSpeed="true" />
</motion_platform>

Thank you very much for the information, as soon as I have a free time I will look if with what you have explained I can make my platform of movement work.

It is true that I, for example, started the games through SimHub and it is possible that when I have done some work the movement system has started the game through Steam. Let's see if at one time I am able to solve the problem.

Thanks and best regards




Muchas gracias por la información, en cuanto disponga de un rato libre miraré si con lo que has explicado puedo hacer funcionar mi plataforma de movimiento.

Es cierto que yo, por ejemplo, inicio los juegos a través de SimHub y es posible que cuando he hecho funcionar alguna vez el sistema de movimiento haya iniciado el juego a través de Steam. A ver si de una vez soy capaz de solucionar el problema.

Gracias y un saludo.

My thoughts exactly.

It took a while to figure out, as sometimes I'd launch DiRT Rally using Sim Commander so that both the game & SimVibe would start with one click.
Other times I'd launch the game from Steam, and have Sim Commander "listen" for the game in order for SimVibe to start.

Then there were the times I'd play in VR on the Rift, using either of the above methods to start them game.
Every time things would change as far as platform movement was concerned....very frustrating to say the least.
Have you ever seen a dog chase it's tail?

Add to this, the theories on the forums of switching resolutions while in the game, or alt-tabbing could be the issue...my head was spinning, LOL!!!!

There were two ways to fix it, either by altering the game's XML file, or port forwarding in Sim Commander.
I chose the first since I also have other devices which require additional UDP ports to be available. (Symprojects Fan Wind Simulation)

All is well, and thanks @yobuddy for confirming that things were all OK on your end and that the plugin was NOT the issue.

I still have not had time to try it, but as has happened to me in Dirt Rally 2, when using SimHub, it seems that I corrupted the movement, and as some users commented, it was a problem to rename the ports. In Dirt Rally 2 has been doing that and solve the problem, I hope that in this when I have a while I can do it and confirm it, but it looks like the same problem for something similar happens that you know ...

A greeting.


Todavía no he tenido tiempo a probarlo, pero tal y como me ha pasado en Dirt Rally 2, al utilizar SimHub, parece que me corrompía el movimiento, y tal y como comentaban algunos usuarios era un problema con renombrar los puertos. En Dirt Rally 2 ha sido hacer eso y solucionarse el problema, espero que en este cuando tenga un rato lo pueda hacer y confirmarlo, pero tiene pinta de ser el mismo problema para el que le pase algo parecido que lo sepa...

Un saludo.

Yes, today I have been able to prove it and the movement is already working correctly with SimHub, it is a joy and it is that until now I played without movement, but now with a brutal movement the feeling of the rallies. I repeat, as I say it was renaming the ports, since with SimHub Simtools was incompatible.

A greeting.



Pues sí, hoy he podido probarlo y el movimiento ya funciona correctamente junto con SimHub, vaya gozada y es que hasta ahora jugaba sin movimiento, pero ahora con movimiento brutal la sensación de los rallys. Repito, como digo era renombrar los puertos, ya que con SimHub era incompatible Simtools.

Un saludo.

Ok I have two issues with this game, not sure if its related to this plugin or not but hoping people here might have solved this before.

(Solved) Lowered graphics settings a bit and fixed this issue
1. The game is freezing/stuttering for a half second or so while driving. It seems to happen just before a big landing off a jump, or just before a hard turn where I am coming in hot.

2. My pitch movement breaks after a race or two, and just starts seemingly doing its own thing tilting my cockpit forward and backward. It seems to love tilting the cockpit back when going downhills, but will rotate back and forth rather violently doing it. I have to restart the game and sim tools to fix it.

I'm glad to see that you've managed to solve issue #1.

As far as issue #2 (motion), I've tested the plugin for a couple of hours tonight, and it appears to be working correctly.
I cannot seem to replicate your issue with it breaking/changing after every race or two.
Now, I DID have a very similar issue before, and the culprit was another app/program changing my DiRT Rally "hardware_settings_config.xml" file whenever that program was activated (SimXperience's "Sim Commander" app).
Please see my previous posts for that particular fix.

Here is my current DiRT Rally config file settings in the "<motion_platform>" section of the file for UDP-based apps, with all of the appropriate apps having their own assigned UDP ports.
DO NOT use it for your game, as it's very specific to my setup, but it should give you some ideas as to what may be different or changing after every race with yours.

<motion_platform>
<dbox enabled="false" />
<udp enabled="true" ip="127.0.0.1" port="20777" ExtraData="3" Delay="1" />
<udp enabled="true" ip="127.0.0.1" port="4123" ExtraData="3" Delay="1" />
<udp enabled="true" ip="127.0.0.1" port="10001" ExtraData="3" Delay="1" />
<udp enabled="true" ip="127.0.0.1" port="50000" ExtraData="1" Delay="1" />
<fanatec enabled="false" pedalVibrationScale="1.0" wheelVibrationScale="1.0"

In my case:
20777 is for an Android tablet Dashboard app (RPM + Gear Indicators)
4123 is for SimTools Motion (my diy 2dof seat mover)
10001 is for SimXperience (Simvibe)
50000 is for my Symprojects Fan Controller (wind simulation)

Hope that helps in tracking down whatever may be changing your config file after every race.
Trust me, I've been there too (see previous posts).

Good luck!!!

Thankyou for this another great plugin .

I'm trying to patch my Dirt Rally and I get an error. It refuse the path of the game. My game is in the steam app directory.



What can I do?

You have to select the path inside your Documents folder.

"C:\Users\your_user\Documents\My Games\DiRT Rally"

Thanks @llluis. I should have seen it from the example path.

hey, @Pierre Lalancette did you ever get Dirt Rally to Work?
i am also having trouble now
:/
i was able to patch after running one race, but after patching
every time i run the game from steam, the game just exit to desktop

when i remove the patch, game is ok..

what am i doing wrong?

Hi sim racers! I have racing hard (completing races) to patch Cod y's games like F1 and Dirt Rally 2. It's so annoying to see that one developer games requires such a thing. Then with F1 I get this bug even after completing an entire race in Mexico. The game simply does not want to patch. Arrghhh! Could anyone here know what this could be?

I had to erase the config file. For some reason whatever I was changing was not saved hence Simtools could not access that file. Don’t know why but it worked. Thank you for your support

I guy i have the same problem with somme games and the problem is with window defender : he block the patch : i have fix this : i have stop the protection for the ransowware and after i make the patch and it's ok

i hope that can help you

Sébastien