Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

18 New Car Smell

Gaming Setup

  • Platforms
  • Peripherals
    Steering Wheel
  • Steering Wheel

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Another stage broken after driving off in last sector. Stage this time: Annbank Station As with previous report, Personal Best is broken, and the stage is permanently stuttering from the place where I went off, and until finishline. In the 1st video, you can see the Ghost that triggered the BUG, and where it went off. Take note of the time. It's about 03:18.xxx. At 0:58 in the video, you can see the new Personal Best time and Split Times. PB is 03:18.108. This matches the time for where the Ghost went off. This is exactly same as I have reported before. In the Split time screen at 1:01, you can see that Split 4 is only 00:37.301. In the 2nd video, at 3:35, you can see the correct PB time and Split Times: PB Stage Time 03:35.863 and time for the 4th Split is 00:57.478, which is about 20 seconds more then it show now. In the 3rd video, you can see how the Frametimes is doing crazy spikes at the last part of the stage. The steady interval of spikes to around 17ms have been there since day 1, and is different every time I restart PC/Game. I'm sometimes lucky and get it down to 10ms, which seems smooth compared to 17ms. I have given up on you fixing this, but I mention it because it just might be related. In the 4th video, I reinstall the game, and after starting the game again, the PB time showed at start is still wrong. In the 5th video, you see the ghost (a bit better this time, and you can actually see that it disappeares at exactly 03:18.108 ) is still the wrong one, the stutter form where I drove off still apparent, and PB time and split time still wrong. Leaderboard is still corret. Video 1: Video 2: Video 3: Video 4: Video 5: I don't expect you to fix it since you havn't been able to fix any of the other very serious problems, like stutter, or even try to work with us to fix it, or even reply to any of the endless hours spent on trying to help you improve the game by writing reports and making videos. BUT I DO EXPECT YOU TO AT LEAST REPLY AND TELL ME HOW TO FIX THE BROKEN TIMES AND STAGES!!! I spent a whole day making the previous report about this problem, and not a single response from you about how to fix my stages and the PB times, not even a simple THANK YOU for wasting a hole day of my precious time making a thorow report! I have spent many hundred hours writing reports and helping other users with their problems, keeping the load off your shoulders. It is very hard to stay friendly with your no-response , no THANK YOU attitude! Cheers :)
  2. Eagleizer

    DiRT Rally 2.0 - Share your Videos!

    This stage have some seriously difficult turns. Drop a note in the comments on YouTube if you beat it. Cheers 😉
  3. No. Very hard only. I did not do them in any particular order, so some of the first ones, 1984-1989 and 1991-1994, was done after most of the other ones. I did the long ones last. (4 - 5 stages) I can find the order for most of them (maybe all) as I have screenshots, if it will help... Cheers :)
  4. Achievement not unlocked...
  5. Thanks! Download the fix here: https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi I think that is the same as in your "Short version" step 3. I did not have to do anything after installing only that. KB can be found here: https://www.catalog.update.microsoft.com/search.aspx?q=kb3140245 (The one you linked to had no download). Cheers :)
  6. Location: Thailand Steam ID: Eagleizer OS: Win 7 No connection with server since 2:05PM UK time, 6. February. (26+ hours ago), except a few minutes about 3 hours ago.
  7. No words from Codies as usual. Not a word on Twitter or anywhere else. It happened 2PM UK time, so why was this not fixed yesterday?
  8. Eagleizer

    DiRT Rally 2.0 - Share your Videos!

  9. How about showing some respect for the time people put in, making world records?? Surely you could do this differently by having new leaderboards, and chose if you want to drive with cuts or not. You released the game in the state it was, with all the stupid shortcuts. Who is paying for my wasted time, making top times on the leaderboards? Not a rhetorical question! We are talking 100'ds of hours! This is outrageous!
  10. This happened to me in New Zealand also now, at Te Awanga Sprint Forward. I would expect to get a solution after almost a month!!! I need to know how I can get the PB deleted for the stages this happens to. In New Zealand, at Te Awanga Sprint Forward, this have also lead to severe stutter at the end of the stage. It will not go away even If I reinstall the game. How is this even possible? If I drive the full stage (Te Awanga Forward), there is no severe stutter in the same part of the stage.
  11. Check previous post on the subject and my reply. It have similar picture to yours. (Previous page. Sorry, there are no number on the posts here, and I cannot get multi quote to work :P) Could you please take a picture of the Frametimes you have while playing? If you use Afterburner or some other logging software. I am curious as to if you have same problem as I have, since I have same CPU. If you could PM it to me. Cheers :)
  12. DR2 - BUG - Personal Best time is wrong. After crashing out in Jezioro Lukie, the game registered the time as my PB time, and all Split Times got messed up, leaving last sector as done in 13 seconds. Luckily it did not register on the Leaderboard, but further improvement of my setup and time is now very difficult as I am racing against slow 3 first sectors, and an impossible 4th sector. I want to know how I can get the PB deleted for this stage. Below is 2 videos. The first is showing the wrong PB time (skip to end of video). The second is showing the Ghost when the BUG was triggered. There is a timer in the top left corner. The Ghost disappears pretty much on the time 2:28.077, which is the wrongly registered PB time. Specs in my signature
  13. I have sent 100's of these since february 2019. I'm sure the report is just ending up in a place where Codies never check, or is read by people who have no clue what they are looking at. However, there is a solution that can help you reduce how often they will appear though: The game is loaded with bad code, and one of the places is after a stage, when you choose Replay, you get the confirmation screen that say "YES/NO". This screen will try to fry your GPU with bad code, and is therefore excellent to use to get a stable clock on your GFX card. Use Afterburner (or your preferred monitoring GFX soft), and look at the temp going up while in that screen (YES/NO). Wait until the game crashes, and take note of what the temp was. This may take a few minutes depending on how close you are to the limit. (There is a chance you already have low enough clock, and that you are experiencing an unrelated BUG, but I highly doubt it). Lower your clock/voltage on the GPU, (maybe also back off a bit on the RAM). Make sure you set so low clock that you can stay in the YES/NO-screen for 5 minutes without having the game crash. Now, work your way up by checking with the temp and make it close to where the game crashed during your first test, and leave it there. This should reduce how often you get those crashes. Cheers :) TO CODEMASTERS: Don't go ahead and fix this screen now!. You need to fix all the other bad code first! This screen is the only good tool we have to get a somewhat stable game.