Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 New Car Smell

Gaming Setup

  • Platforms
    Xbox 360
    Playstation 3
    Playstation 4
    Nintendo Switch
  • Peripherals
    Steering Wheel

Recent Profile Visitors

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

  1. I'm 99% sure I've solved it. At least in my case. SOLUTION: Changing the mouse or disconnecting it before launching the game. I wasn't able to play for the las 2 weeks but yesterday I was able to try some new things. I changed the mouse and keyboard and started playing without issues. Then I connected my mouse (Microsoft SideWinder Gaming Mouse, the original one) and the crashes started again. Switched the mouse again and no problems. I played for 3 hours yesterday without an issue. So changing the mouse before playing it's a little tiresome. Today I tried disconnecting it before launching the game, and it works perfectly. Also you don't have the mouse pointer appearing randomly during a stage. So there seem to be a problem with some mouses, in my case it was the Microsoft Sidewinder, but this may be happening with other ones. I haven't tried the solution on the original Dirt Rally so I'll try it later.
  2. So. Another day and a half of tests and no luck. No clear solution yet. Yesterday'd and today's tests: First, as I've mentioned on the last post, I've made a clean Windows install. After the setup I installed the MoBo drivers so the Device Manager doesn't show any driver missing. My new MoBo is a Aorus Z390 Pro (no WiFi). The BIOS it's upgraded to the last version (F9) and I downloaded the latest drivers. After installing the drivers I downloaded the Logitech Gaming Software (LGM), the latest version. I went for it instead of Logitech GHub because the GHub doesn't show the wheel. I don't know why. The moment I install LGM the wheel is detected in both programs. But to have the cleanest setup possible I went for LGM alone. So no, I downloaded Steam, logged in and started downloading Dirt Rally 2.0. I left the computer downloading overnight. I'ts important to mention that I didn't download anything else. No NVidia Gaming Experience, no additional programs , not even Chrome. I didn't configured anything aside the screen resolution. Also, I stopped Windows from updating. Also. I didn't uninstall anything from Windows. I just left the intsall as is. This is an image of my Programs and Features window before I started playing the game. So. A very clean Windows to start the tests. Again, the only hardware attached is the Screen, Keyboard, Mouse and Logitech Wheel. TEST 1: Results So. After playing for a while, everything seemed to work fine. No crash so far. But after about 30 minutes. I was in the garage before a stage. I decided to quit the game, so I selected the Quit To Main Menu option and... First Blood. Well First Crash. The same one. Again I went into the game and played for a while with no crashes. In the afternoon I started playing again. I opened the game and immediately crashed, no in the intro screens. Opened the game again and it crashed during a stage. Again, now it crashed just after the loading to the garage. So, this doesn't seem to be a problem with some software I had installed. TEST 2: Results So It doesn't seem to be a software problem. ¿What now? I tried some changes related to hardware. Nothing to fancy. Just making sure everything was as it is supposed. I disconnected the wheel from the USB 3.0 and connected it to a USB 2.0 port. Tried the game and it worked fine for a while. Then it crashed again. So the port doesn't seem to be the problem. Then I entered the game and calibrated the wheel again. After calibrating, I found a section in the game called Device History, there was my Wheel listed, but there was another HID Device which I decided to delete. After this I was able to play for about an hour. I didn't crashed. My hopes where hight. I thought I've might found the problem. Si I closed the game, turned off the computer and went to sleep. So today I booted the computer. Immediately started the game and... The Same Crash again. This time during the intro videos. I tried again and it crashed again, now while navigating in the main menus. Third time and the same, but now in the garage. I turned the computer off and went to work. In the afternoon I tried playing the game with mixed results. It crashed some times, but was able to play for like an hour after various tries. After that I resume installing all my things in the computer. Software doesn't seem to be the issue. I'm really bummed. I'm gonna try changing the mouse and keyboard. That's next in my list but I won't be able to try until the weekend. Maybe I'll try changing the audio output to the MoBo card. But after that I won't be trying anything else. I'll go back to other games. I've found people reporting the same problem for Dirt 4 and F1 games. I understand it is not easy to catch this kid of bugs, but I really hope Codemasters gives the problem the attention it deserves.
  3. So, I've been looking all over for people with the same problem. There are some comments on Reddit, but I couldn't find any similarity with their setups and mine. Not in software nor in hardware. The only thing is all of them are using Wheels to play. Different models from different vendors. Also I've seen a lot of people in Youtube playing with the G29. And none of them report the same error. But I don't think we can discard the hardware in general as a problem yet. Based on the fact that I have the same problem on the old computer, I've made a list of the things I think might be the issue. Some software installed on the computer. As I usually hace the same software installed on my computers there might be something causing the problem. There might be problems with sound outputs. I'm using the TV as the sound device, via the HDMI, so I'll try changing the output to the MoBo and using some speakers. A really weird incompatibility with come of the other Peripherals. The keyboard, the mouse and the screen. I'll try with different keyboards and mouses, but I really don't think that might be. I'll try to get another monitor to test with. This won't be easy so I'll leave it as a final option. A very weird defect on my wheel. I happen to have other wheels (all of them Logitech). But I'll try. So, based on that list, I started some tests. 1. I found in Reddit some people with the same problem, although with different Wheels. Some of them said they found the problems when they where running a VMWare VM on the same machine while playing the game. I don't have VMWare or any other virtualization SW on my machine, but it gave me the idea that there might be a problem with software that installs virtual hardware. So: I uninstalled PrimoPDF (a virtual printer to print to PDF). I uninstalled Visual Studio 2019. It installs some virtual hardware for mobile development. I stopped Google Drive File Stream before playing. It works as a virtual hard drive. I stopped Dropbox. It doesn't install virtual hardware but it was the only other thing running in the machine at this time so decided to stop it. Results: No luck. Same problem. 2. Just to try, I changed the G29 switch from PS4 to PS3. The wheel works fine in the game. But again the same problem. Logitech says that the wheel should be in PS4 mode so I think we can discard this as a problem. Result: Same problem. So no luck so far. Now, since some weird software might be the issue. I decided to make a clean Windows install and try playing the game. Without anything else installed, just drivers, steam and the game. It's a little tedious because I have to download and install Dirt 2.0. But I'll try. Last night I reinstalled Windows with all the drivers, and left Steam downloading the game overnight. Today I'll start testing. @CM_Ads If I can help you with any additional information, memory dumps, hardware or software details, just ask. I'm willing to help with anything you need. I know this is no generalized problem, but the problem is out there, so please make everything you can help me solve it.
  4. The game closes with the same error screen as the first post. It never happens on the start menus. Sometimes it happens after the loading screen (just before the game shows your car in the garage) Sometimes it happens just when the stage is starting (when your car parks before the start lights) Sometimes it happens in the middle of the stage. Sometimes at the end. I always send the report. I have to open the game again and try to play again. I've checked and all my drivers are up to date. Including Logitech GHUB. Something important to mention. About 1 in every 12 o 15 times I try to play, the game works fine. No crashes. Additional details. I used to have the same problem with the original Dirt Rally in my old computer. This problem in Dirt Rally 2.0 also happened with my old computer (Core i5-4670 and GTX 960) The only things I've migrated to the new computer are the Keyboard, the Mouse, the Screen and the Logitech G29. Everything else (MoBo, RAM, SSD, Video Card, Power Supply and Box) is completely new. That's the reason I think the problem has to do with the G29 wheel. I'm using a Comfort Curve Keyboard. A Microsoft SideWinder Gaming Mouse. And a Samsung 4k TV as montior.
  5. I have the same problem since the Original Dirt Rally. I have a Core i9-9900k and a GeForce RTX 2080. I use a Logitech G29 wheel. Only the wheel, keyboard and mouse connected to the PC. The same happened with my old Core i5 with a GTX 960. I thought it was my video card (it was a 2GB version) so I updated the whole computer. The problem with DR2 is much worse. I cannot finnish any stage because the game breaks. I've sent about a thousand of bug reports and nothing. I've tried everything. All games overlays (steam, xbox, nvidia) are off. I've tried disconnecting the keyboard. I've tried disconnecting the mouse. I've tried running the game in administrator mode. In compatibility mode. And a thousand things more. Every other game I play (WRC7, Forza Motorsport) runs without a problem. I really think it has to do with the G29 wheel. But i'm using the latest driver and not using the wheel is not a solution. Why Codemasters don't admit there is a problem. Please HELP.