Jump to content

steviejay69

Members
  • Content Count

    5,008
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by steviejay69

  1. steviejay69

    F1 2020 1.05 CRASH WHEN FLASHBACK

    BIOS 2811 Update ME driver (Station Drivers) and ME. LAN driver. Although Intel Driver and Support Assistant will update the iGPU and other Intel hardware. I have been using the 20.5.1 driver but like PAC73 says if lowering the fidelity is a workaround for now then you should try that. I'm assuming not. And yes as a programmer if you program on that machine, it is not updated. 🤐
  2. steviejay69

    F1 2020 1.05 CRASH WHEN FLASHBACK

    Can you post your board make and model? I know it's 300 series and probably ASUS but sometimes Gigabyte don't fill in the OEM fields either
  3. steviejay69

    F1 2020 1.05 CRASH WHEN FLASHBACK

    Can you try a new save game? It will at least prove if this issue is related to a corrupt save?
  4. steviejay69

    Stutter Fest on F1 2020 (PC)

    Overclock. Even I only went with 1866 RAM and it is plenty fast enough. Also there is errata on the CPU that Turbo can corrupt data. Suggest Turbo set OFF in BIOS. Can issue a uCode fix for most boards of that era if you link your make and model or the shortcut is KB4497165 v4 (if running 1903/1909; maybe WU has sent that or 2004 has it built). Haven't had the opportunity to run F1 2020 on that CPU and board (or 2004) as I sold it to fund a Ryzen.
  5. steviejay69

    F1 2020 1.05 CRASH WHEN FLASHBACK

    Purely because I believe in Gigabyte's ability to release solid motherboards; Uninstall any old chipset drivers with Geek, restart and install B350 chipset drivers. Also, because I like new with new, F50d with new AGESA and SMM callout bugfix. DDU and install 20.5.1 Also, is the page file set to automatic?
  6. It's a good job that's easily recognised as Playstation. I have visions of bamboo fields. AC....so much to answer for....
  7. These aren't the answers to the template. Platform?
  8. I'm going to suggest both users DDU and reinstall their drivers. Please do not alter any settings in the driver and perform a clean installation. Do not have GFE 'optimize' your game. Delete the hardware_settings_config.xml before launching. In a previous post I have recommended 446.14 when using 1903/1909 Can't help with XB1 and the other user hasn't given any dxdiag There are under the hood changes with 2004 (450.xx driver builds) support DX12 Ultimate, DLSS 2.0, etc. none of which this game is designed to support. Once you have a working game, then adjusting your driver changes one by one will reveal the problem. Far faster for users to let CM know than CM try to figure the issues and tell the users.
  9. I'm glad you applied the correct methodology. (From your post about being a fellow tech, I kind of knew you would.) It might look like a scattergun approach, but in each instance it reduces the amount of replies within the same thread.
  10. And they're on top of things?
  11. Remove any of the ASMedia USB/SATA drivers and let WU/Inbox version install. Remove any Intel chipset drivers (although it looks like you are running default Inbox). Remove the Broadcom ac WiFi device and test over Ethernet.
  12. 1. A detailed description of the issue. Updated to 1.06, nothing else on the PC changes. DOR on CSL Elite reset to 900. In-game screenshot for error code. 2. Platform PC 3. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.06 (1.05 did it as well) 4. Game-mode? TT 5. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. Not replicated. This is a one-shot deal, once I set the DOR to 360, it will stay set, the fact is YOUR PATCH should not alter the driver setting, but IT DOES. 6. What troubleshooting have you attempted? Please always try to attempt to fix the issue. Do you have the latest drivers? Have you check your connectivity settings? Manually changed DOR back to 360. SHOULDN'T HAVE TO. 7. Please provide a video recording of your game crashing so we can see where the issue occurs? Not crashing, just MEDDLING. 8. [ For PC ] – Please add a DXDiag to your post. You can have a dxdiag, everything is as it should be. 200727_DxDiag.txt
  13. Can't replicate @BarryBL the pedals were a one-off. But they were gone in Windows as well. I'm changing pedals now anyway.
  14. steviejay69

    Patch 1.05 - Messed up wheel controls

    I'm not disagreeing with you. This game is a rerun of F1 2016 - a decent game killed by patch cycle.
  15. 1. A detailed description of the issue. Please include any error codes here. The pedals are not detected after patch 1.07 2. Platform PC 3. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.07 4. Game-mode? I went into the settings to check that the wheel was still 360 DOR after making a wheel tune in the hardware, it was, but I have no pedal registration in the Fanatec driver (v365) 5. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. 1 so far will update for any other poor saps having the same issue 6. What troubleshooting have you attempted? Please always try to attempt to fix the issue Will try later, have got new pedals coming anyway. 7. What peripherals are you are using (gamepad, wheel make & model etc) Fanatec CSL Elite wheelbase, Fanatec Formula Wheel F1 2020 Limited Edition, Fanatec CSPv1 pedals 8. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears. I might post some.
  16. steviejay69

    Patch 1.05 - Messed up wheel controls

    Although CM have said they are prioritising crashes and game-breakers, it doesn't mean they won't pick any low-hanging fruit (i.e. the fix is easy) It is also clear they will keep releasing DLC to maintain the revenue stream and obviously the Pitcoin is also another cash generator. But for this, we can and should expect a much better product overall. I've said it before the MP number fix is an important omission from the game for me but also to find my pedals not registering by the same token is highly annoying.
  17. Spoke too soon, my pedals are not registering at all in Windows and the game. ***!
  18. The forum mangled it all by itself, unless it's my browser. But no such issues here 😖 (same browser, different machine). If that glitch has gone, plus the MP number fix, then it's a patch for me.
  19. at's that glitch has gonif, I'm
  20. steviejay69

    Thrustmaster pedals

    Is that F1 2012? 🙂
  21. steviejay69

    Pc shutting down while playing

    Then again, I would suggest if there is no improvement with 1.07 try reverting (DDU) to the older 446.14 driver. Or update Windows to 2004 (patches are due for W10 tomorrow).
  22. Take it the DLSS testing didn’t pass QA? Or is it another omission from the list? Imagine how bad that must be if this is the stuff that gets passed? There...I said it.
  23. steviejay69

    Pc shutting down while playing

    I would check the hardware_settings_config.xml and see which GPU is detected. It should show up in the game settings.
  24. steviejay69

    Insanely unplayable lag/stutter after CWOS fix

    Perhaps refer to the recommended post in this thread
×