Jump to content

steviejay69

Members
  • Content Count

    5,115
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by steviejay69

  1. steviejay69

    Crash to Desktop during solo races

    I suggest you use a recommended driver rather than the latest optional. 20.9.1 (or the one I use, 20.5.1 this has proved to be stable on my old RX580 and my RX5700XT) AMD chipset drivers are important as is the updated AGESA but I need the board make and model (some kind of ASUS B450/B550/X570) The EGO dumper log file is less helpful than the actual crash dump. Noticed and old driver for a TP-Link WiFi adapter in the dxdiag, try looking for an update or playing wired.
  2. steviejay69

    [PC] Textures not working properly

    Install the IDSA the latest driver build is 8853 - you may need to play with the settings as this is an Intel Graphics controller. DX12 should work fine the UHD 630 is DX12 hardware. But this is a desktop PC (MSI Z370 PC Pro? UEFI) you should have a PCI-E graphics card like AMD or Nvidia....
  3. Seriously, can you not Google?
  4. steviejay69

    Will F1 2020 look better on PS5?

    Cutscenes are **** on PC too. It's not framerate it's the way those cutscenes have the textures added. It's highly unoptimised to be kind to it.
  5. steviejay69

    [PC] Textures not working properly

    This is a Systems and Connectivity issue, not Gameplay. Post a dxdiag
  6. steviejay69

    G29 does not work at all on F1 2020

    You need to post a bug report and dxdiag
  7. steviejay69

    Failed to verify game files - F1 2020

    A very strange approach, but yes IDK why F1 seems to hammer GPUs unless you do introduce some kind of capping. Never tried to mess with CPU utilisation / core affinity. I'm not sure you should.
  8. You should provide a dxdiag. Hybrid systems there may well be issues that need a patch. The more systems that are posted when affected gives a scope for a fix.
  9. steviejay69

    F1 2019 not working with new Nvidia 3080

    This is a workaround. Did the users DDU when updating or just shove the 30XX in a 10xx system (lucky they had time to shut the machine down with all the actual excitement)? If this is an Nvidia issue with the libraries then....oh dear. They're only interested in telemetry and not in FUBARing systems then.
  10. steviejay69

    NEED HELP with F1 2019 PC Settings....PLEASE

    https://forums.codemasters.com/forum/12-technical-assistance/
  11. It is a shame, but yes, always a possibility.
  12. steviejay69

    [Deleted]

    Again, for TA please use the template.
  13. This is an English language forum, please follow the rules.
  14. You need to post in English and follow the template, thanks.
  15. steviejay69

    NEED HELP with F1 2019 PC Settings....PLEASE

    You need to post in the right section, with the TA template. I've flagged this to the moderators.
  16. steviejay69

    Patch 1.12 | PATCH NOW LIVE

    The first picture I believe does have the side of the tub black. It's obviously a change for subtlety.
  17. steviejay69

    Game stutters

    DDU and reinstall a known working (Nvidia) driver. (Un)Fortunately, I use an AMD card to play F1, so am unable to comment beyond 446.14 DLSS on 20xx cards is not bug free on this game. 30xx cards are unstable. But these newer Turing and Ampere cards need to use W10 2004 or higher and 450/455.xx branches (456.71 is latest).
  18. GHub is required for FFB, it installs the C:\Program Files\LGHUB\legacy_forcefeedback_x64.dll
  19. steviejay69

    Need help setting up G923

    You need to post a template for technical assistance. There are many threads detailing the setup of the G923, you should have installed GHub software and you will perhaps need to wait for a patch containing full G923 support.
  20. steviejay69

    Failed to verify game files - F1 2020

    You need to fill out a template for technical support. However, most likely the files you have modified do mean that reinstalling the game is the quickest route. Be aware that care must be taken with mods and the caveat is that unless they are tested that you should most likely expect they are more suited to offline play not online (only you will see the modifications). Any files shared in the online environment MUST be tamper-checked (and I'm not claiming that all ARE successfully). The other possibility is the settings on the PC or faults in the system like hardware (hard drive or memory errors), firmware or software issues. Please make a template and attach the relevant files (like a dxdiag and the hardware_settings_config.xml) or any crash dump. If you can get the game working without modification, then proceed with modding and testing on a trial by files basis.
  21. steviejay69

    Patch 1.12 | PATCH NOW LIVE

    You can see the Williams livery on this page of the website. https://www.williamsf1.com/news/2020/10/portuguese-grand-prix-practice
  22. steviejay69

    PC Forum Championship - Season 2

    Are we Russian to be online at 4pm?
  23. Don't have LGS and GHub installed together. Use the Logitech Driver Cleaner or Geek Uninstaller to remove registry entries. Use USB DeView to check the USB configuration and remove redundant or duplicate entries. For the sake of repetition, have the game closed when you do the verification and removal of files. GHub is the replacement for LGS, at the moment they use the same FFB .dll but under different names (for G29/G920) I expect G923 to change that, but don't know for sure.
  24. steviejay69

    Dolby Atmos not working on PC

    Have you selected a default audio device in Windows (hint: should be the one supporting Dolby Atmos)? Have you selected an audio output device in game? Menu|Settings|Audio Settings|Advanced Audio Settings(?) Please post a dxdiag and your hardware_settings_config.xml, it might be useful to also see a confirmation of the in-game audio settings.
  25. steviejay69

    the game changes controller settings

    Wheels don't disconnect as they are wired and independently powered. Entirely different class of issue. Good spot, please fill out the template would hate for this one to be missed or not investigated.
×