Dirt 3 CE and GFWL crashes when finish line is crossed

[ApexVGear]

The GFWL version was installed several months ago. It was working fine until...

I installed the CE version a couple of days ago.

Currently, both versions are still installed--this could be the problem, please advise.

Every time I finish any race, the SECOND I cross the finish line...

The audio freezes, the screen goes black, and I have to CTL-ALT-Delete to get to the task manager to select Dirt 3 and End Task.

Once I've loaded the Task Manager, I can see there are two Dirt 3 windows on the task bar. If I roll the mouse over them, I can see one is an error message, and if I roll over it, I can see this message...

"sendto failed with error 10038: An operation was attempted on something that is not a socket."

Someone on another forum suggested that it might be a problem with FanaLED (I used this with my previous wheel, a Fanatec CSR Elite). I've checked to make sure FanaLED isn't running, and the problem persists.

It has also been reported to me that this is a "motion/telemetry" bug. I don't have SLI/Motion/Sim Vibe on my PC.

System
Pentium G3220 3.00GHz
8GB RAM
Windows 7 Pro 64 bit
GPU: GeForce 750ti

Thrustmaster TX, Firmware 48.B9, Driver 2.8.16.0
TH8A, Firmware 22.0, Driver 1.4.3.0

[Avenga76]

That is the motion/telemetry bug. Are you using any kind of SLI/Motion/Sim Vibe?

It was introduced way back in Dirt 3 1.2. I have asked codemasters many times for a fix but every time they say they will not fix it.

I started a thread about it on the Codemasters forum. http://forums.codemasters.com/discussion/183/dirt-3-telemetry-and-motion-simulator-bug

Please bump that or PM Justbiglee and hopefully we can get it fixed

If you are not running any kind of motion or SLI then the motion settings could have been switched on by accident at some stage.

Check your hardware_settings_config.xml file in your \Documents\My Games\DiRT3\hardwaresettings folder

If it is set to this then you will get that crash

<motion enabled="true" ip="127.0.0.1" port="20777" delay="1" extradata="1" />

Change it to

<motion enabled="false" ip="127.0.0.1" port="20777" delay="1" extradata="0" />

This will disable motion/telemetry so you won't get hit by the bug

[ApexVGear]

I just checked the file, and it's showing...

<motion enabled="true" extradata="3" delay="1" port="30500" ip="127.0.0.1"/>

It's odd that extradata is 3.

I think I know what has happened. When I installed the new CE version, it wrote a new file in my settings folder.

[Avenga76]

Port 30500 and Extradata=3 is default settings for FanaLEDs. Maybe you had that installed at some stage.

If you have it set to <motion enabled="true" extradata="3" delay="1" port="30500" ip="127.0.0.1"/> then you will get the crash.

Just turning the motion on is enough to crash the game.

set it back to <motion enabled="false" ip="127.0.0.1" port="20777" delay="1" extradata="0" /> and it will work

[DuC]

Damn, I was hoping that steamworks edition would solve this problem. Anyone got a Simvibe solution to work on Dirt 3 Complete Edition?

[Avenga76]

I am in the same boat. I have Sim Vibe, a GS-4 and an Accuforce.

As a work around you could probably use the Dirt 2 plug in and manually change the hardware settings xml file and game settings.

You will still have to live with the game crashing over the finish line

[Jonathan]

It seems there's a fix if you don't mind modifying your exe