Mklink /j "C:\ProgramData\Codemasters\DIRT Rally\DataCache\\replay" "E:\Games\Steam\steamapps\common\DIRT Rally\replay2" You need to type EXACTLY what follows, just change the folder names and the folder path to what you chose to. In the Start Menu, click Run and type "cmd" (or Search "cmd"). For me, I created a folder called replay2 in E:\Games\Steam\steamapps\common\DIRT Rally (there's already a folder named "replay", just name yours "replay2")ģ- Now here's the tricky part: you need to do a symbolic link with Command Prompt. It's important at this point that there's no folder called "replay", just one called "replay_old", otherwise the fix won't work.Ģ- In your HDD, go anywhere to create a folder called whatever you want. You need to rename the FOLDER "replay", not the 2GB file inside (it's a temporary file, it may not be there when you check). The folder path is C:\ProgramData\Codemasters\DIRT Rally\DataCache\. I recommend to start with workerMap4Core.xml - but if this doesn´t work, then try out the other profiles and please report your results here.ī) /// thx to scotchtape20 /// - only works if you have a 2 drive (SSD, HDD) configurationġ- You need to rename the "replay" folder to something like "replay_old". There are profiles for the following number of cores: 2,3,4,6,8 (and the corresponding xml files workerMap2Core.xml, workerMap3Core.xml and so on). In my case I have an 8 core cpu, but it only works if I use the 4 core profile (which is workerMap4Core.xml). Important: By changing this line you´ll force the game to use a certain cpu-core profile. Save (Make a backup of it before, we never know) Go to Program Files/ Steam/ SteamApps/ common/ Dirt Rally/ System/įind the file named hardware_settings_config.xml Thx !Ī) /// thx to Guillaume, edited by me /// Please TEST them and post your RESULTS here. But you should start one by one and then test after each workaround. You can also try to combine all workarounds. There are actually 4 known workarounds for this problem. UPDATE: Please try workaround A at first. What were you doing specifically when the crashed occurred?Ībout one hour, but happens in every sessionĮDIT: Workarounds for testing (not official, make backups, be careful) Which stage were you within the championship\custom event? Start game => start ANY event => drive => slowdown happens for about 5-10 seconds
#DIRT SHOWDOWN HACKED INSTALL#
Hell I would even mail my machine to Codemasters.ĪMD FX8320, Asrock 990FX Extreme 3, 16GB DDR3, Samsung SSD 840 256GB system drive, Samsung HD103SJ 1TB game install drive, Radeon HD7890 2 GB with Samsung 52" LCD via HDMI, Windows 7 圆4, Here is my configuration and I´m willing to provide any information needed to solve this. And I´m not the only one that has this problem, as you can see if you scroll down the forums. I really hope that the early access phase of DIRT RALLY will solve this problem once and for all.
I have reported this on GRID AUTOSPORT too but there was no solution. This seems to be a problem with the EGO engine, as it happened in exactly the same way in GRID AUTOSPORT and DIRT 3.ĪND this is a CODEMASTERS SPECIFIC problem as it DOESN´T happen in ANY other game.
#DIRT SHOWDOWN HACKED 1080P#
Generally the game runs fine in 1080p with high graphic details when driving within a stage.īUT then there are heavy slowdowns / stuttering for about 5 - 10 seconds where the frame rate drops below 10 frames and the game is pretty unplayable then.īUT this isn´t a normal bug. WORKAROUNDS: SEVERAL, BUT NONE SOLVES THE ISSUE