Codemasters Dirt 3 Plugin 2.0.0.1

This plugin conflict with simhub dashboard. Simhub work with extradata=3 while plugin only work with extradata=0. Which way to fix this?

I have a 4dof sim and my 4th axis is for traction loss but when I use the Extra1 on axis 4 in Dirt2 and 3 the motor#4 is receiving surge input from the games instead of traction loss. In Simtools it is indicated that Extra1 is for traction loss. Tuning center is also displaying surge input in the Extra1 cell when I'm accelerating or breaking. Is there an other step we need to perform to get traction loss from these games? Could the latest version of Simtools have changed the way the engine digests Dirt2 and 3 telemetry? Dirt Rally runs perfectly with traction loss. Tks!

No one has an idea why I have this error?! (see my previous comment)

No one???

Tks for your response noorbeast. The Axis 4 allocation is 80 and is not share with other motion input since the motor is used only for traction loss. System locale is English. As mentioned, the same settings in Dirt Rally and also Assetto Corsa works great with traction loss allocated to Extra 1. But Simtools interpretes Extra 1 as surge in Dirt 2 and 3.

Thanks @noorbeast. Is 200 too high even if I have 3 motors (3 independent axis) to share the pitch/heave motions? Yet these motions perform well and are very smooth with the current setting. At 50 on each dof the pitch/heave motions feel weak and incomplete.

Hi @jjanu
In the actual plugin (2.0.0.1) Traction Loss (Extra1 or Extra2) have nothing in common with surge.

Traction Loss is calculated as the delta between the speed vector and the heading of the car while surge is the longitudinal acceleration of the car.

Use 50 for pitch and heave instead of 100 and play with the values in Tuning Center.

You might want to play with your settings in Tuning Centre, if you don’t feel happy with the movements of your simulator.

Right-click on the Game Engine icon in the System tray and select Tuning Centre to open the Tuning Centre. Click on Capture Max Min to change the Max Min values. The lower these Max/Min values the more intensive the movements.

I have 4 motors (4 axis). In Dirt 2 and 3, when I hit the accelerator or the brakes, the motion goes to my axis 4 which is dedicated to traction loss (Extra1).

See my videoclip of the traction loss motion:

In Dirt Rally, Assetto Corsa, etc, gas and brakes are doing the normal pitch motion and traction loss is moving my axis4. My Simtool settings are the same in Dirt 2, 3, Rally, Assetto. I did the tuning and I'm still getting the problem. It happens only with Dirt2 and 3. Do you think it could be due to the way the latest Simtool version is interpreting these two games? They're getting old. Tks!

Nope

Ok, I'm trying to understand why gas and brakes input is triggering a motion on my axis 4 only in Dirt 2 and 3 while in the other racing games it is not. Can you please share your setting in Simtools for Dirt 2 or 3? There must be something wrong in my settings for these 2 games although they are an exact copy of what I have in Rally, which runs fine. Tks

You must set profiles for each game individually See here: https://www.xsimulator.net/community/faq/steps-to-create-a-motion-profile.228/

Agreed, but why is accelerating and braking in Dirt2 and 3 sending a motion input to my axis4 which is for traction loss (when I hit the gas my cockpit yaws left and when I brake it yaws right)? I'm putting Exta1 in Axis4, not surge. Therefore I should receive traction loss motion on that axis, not acceleration and braking. That's what I can't figure out.


Can you please send me a screen capture of your motion profile for Dirt 3, if you have one? Thanks for helping. Sorry to keep coming back but I'm really stuck and I'd like these two games to work with traction loss. I can make a video of what my cockpit is doing when using these settings.

I don't have a 4 DOF. This is what I see as sensible settings:
Also you can see the "motion" in GameEngine virtual axis.

Tks Value1. Here are my settings for Dirt3.

Good news guys, I just redid a new capture in Tuning Center for Dirt3 and it did the trick. Motions are great and the traction loss input works perfectly. Strange because I did it twice recently and still had the error. And now it works. That might have something to do with the pitch/heave that are now at 50 each instead of 100. That's the only explanation. I'll try the same with Dirt2. Thanks a lot!!