Dirt Showdown crashing with Nvidia

[MichaelM]

I got the demo when I had 6970 CF and it would play without issue but now I switched to a GTX 670 it has not worked at all. It will load up with a red tinted screen and stuck in anaglyph 3D mode without 3D being enabled in the control panel or any options ingame for it to be disabled. Ignoring this or using 3D vision it will start a race, countdown and then about 1 second into the race the game crash's every time.

After switching hardware the following was done but the problem still persists,

Clean system drive install (301.42 drivers)
Deleting and re-downloading the demo
Verifying the demo install
Deleting setup files and verifying the demo install
Enabling and disabling 3D Vision


The problem persists no matter what I have done so I'm here to ask if it's just Nvidia and everyone gets this problem? I would like to get the full game but there is no point if I can't play it obviously.

 

[T345]

not tinted screen, but gives me random re boots, have a 9500gt, any help?

 

[Cleeecooo]

Try ctr+T to toggle 3D vision

Also, use driver sweeper to get rid of the AMD driivers

 

[BassPunk]

I had these issues when I first tried the demo on my 3d Vision laptop. I fixed the crashing by turning the graphic setting "water" down to low.

The full game had neither issue.

 

[MichaelM]

Try ctr+T to toggle 3D vision

Also, use driver sweeper to get rid of the AMD driivers

Cheers but it seems I have to do it every time the demo starts

I had these issues when I first tried the demo on my 3d Vision laptop. I fixed the crashing by turning the graphic setting "water" down to low.

The full game had neither issue.

Putting water to low does solve it cheers and that's reassuring to know the full games not affected.


Thanks

 

[Space Monkey]

Full game runs great on AMD and Nvidia (I've tried both)

 

[Gregster]

It will be something to do with drivers. I have on my start menu "enable 3D vision" and "disable 3D vision" all I have to do is choose if I want to play in 3D or not.

Maybe this is a bug in the demo but doubt it.