Jump to content
Codemasters Community

steviejay69

Members
 View Profile  See their activity

  • Content Count

    5,305

  • Joined

  • Last visited

  • Days Won

    2

Posts posted by steviejay69

  3. Posted

    @KawaGreen Astros need eliminating (USB dongle needs updating or removing entirely). The Nahimic audio drivers need to be the DCH versions. Consider updating the AMD chipset drivers and post the ASUS motherboard model so I can check for UEFI updates.

    451.67 well you probably have updated those by now but consider DDUing and installing the latest WHQL DCH release. 2004 did mess with base level drivers.

  6. Posted

    23 hours ago, Chaynay said:

    Hi @BarryBL

     I’m not sure I understand. Are you saying that you don’t have a setup to try and confirm this and try and further help with our issue?

    Or are you saying that it is not possible for us to have two rigs work on split screen?

    He's saying it's not possible for two wheels to work on split screen.

    This is possibly due to the way the wheels are identified in-game. On PC, the drivers are really meant to control one wheelbase and peripherals. Two identical wheelbases would have the same ID. Then if the pedals were separate, how would the game determine which pedalset belongs to which wheelbase (usually consoles prefer base-connected pedals)? Two different wheels might be successful.

    Maybe they only tested it with two pads or a pad and a wheel. Or a keyboard and either.

  7. Posted

    You need to check basic connectivity and be more forthcoming with the information in the template. I applaud you for having a go but it's insufficient for any kind of diagnosis. 

    Be wired connection if possible and reset your router. Check your net speed and connection to friends in the lobby (colour bars and if the asterisk appears where they would show ready).

  10. Posted

    10 minutes ago, FedeArg said:

    Okay, I'll give it a shot and come back to you Stevie!

    Thanks a lot for the help, I know its a minor error but can be quite annoying. Also, really appreciate you took the time, I can see you really know for F1 2020 🙂 

    Motherboard is MSI Z370 PC Pro, just for the record.

    Cheers and stay healthy mate!

    UEFI 1A lots of updates since the board was released if it's never been done.

  11. Posted

    On 10/30/2020 at 11:53 PM, MYOB said:

    Okay, I've updated the drivers for my motherboard and uninstalled LGS (I had both LGS and GHub installed, so I'm sure there was a conflict there), but the game still doesn't recognize my wheel even though GHub and Windows 10 home does. What else can I try?

    Did you try deleting the hardware_settings_config.xml and verifying the files on Steam?

  12. Posted

    1 hour ago, FedeArg said:
    • Textures inside the Paddock Pass and the Driver of the day and starting grid appear black, as if "locked" or unavailable.
    • PC
    • Version 1.12
    • All of them.
    • We need to be able to make your problem happen internally so we can fix the issue. Can you make the problem happen again? Not really, no.
    • How do you make the problem happen? No idea, it's been there since I got the game.
    • What troubleshooting have you attempted? Ambient obscuration, switching DirectX version, tweaking the advanced graphics options.
    • What peripherals are you are using? PS3 Controller DualShock 
    • Screenshots included in the post. 

     

    Cheers for the answer, did what you asked. I can't really install the last update because it makes a lot of games crash and/or reduces FPS drastically. I've talked with Intel and they suggest sticking with the current build.

    Thanks for the help! 🙂 

    DxDiagPC1.txt

    You almost answered my question right there!

    You CAN use DDU to remove even Intel GPU drivers. The IDSA will attempt to offer you the latest build (8853 IIRC).

    But, I know from my own experience Intel drivers do not always work well with all the hardware it is supposed to support. Also, the MSI board designation is 300 series for MS-7B49, if you could confirm your board model then I can maybe recommend a UEFI update that may well address SOME graphical issues.

    So, I would update the BIOS, test again, then DDU and finally then attempt the latest driver again.

    I would also primarily test in DX12 as the 630 Graphics are DX12 hardware. Delete the hardware_settings_config.xml to redetect the hardware after each new change.

  13. Posted

    I just want to add a note of caution here. MOST SOHO (small office, home office or domestic) routers can have odd problems with port forwarding.

    Wherever possible, you should use uPnP for your firewall as sometimes, setting specific port forwarding can disable the uPnP functionality. You then can have port forwarding issues for every device on the network as they are undefined. 

    I advise contacting your ISP to ensure you are running the latest firmware for the router and also advise a hardware reset once upgraded, entering ONLY the settings required to connect to your ISP that they either specify or automatically send to your router (pre-configuration or distributed settings).

    Bear in mind that not all devices are current and if they are misbehaving you might want to look at 3rd party devices, but remember that support will be your responsibility. If you are with a common ISP, you can often pick up the same or newer variants of your ISPs preferred equipment if they are not willing to upgrade it for you. Sometimes direct substitution like for like can reveal faulty or underperforming equipment.

    • Agree 2

  15. Posted

    On 10/30/2020 at 9:32 PM, Elliott1 said:

    I bought the game well before the wheel. When they advertised the wheel they said it would be compatible with the new F1 game. Yes the force and wheel works, the rev counter doesn't and if it did it would add a whole new element to the game. 

    https://www.logitechg.com/en-gb/products/driving/g923-trueforce-sim-racing-wheel.html

    Compatible does not mean all features supported. But, to be fair the consoles have always been a bit like this. This may be a Microsoft limitation. Can't speak for PS4.

    For F1 2020 it does not say Trueforce is supported and it says the dual-clutch function will not work (game limitation as the 'clutch' is a button).

    For PC support it would seem an action map for the wheel would not be a huge departure from the existing G920 or G29 action maps especially seeing as Trueforce isn't supported this time. But allowing the wheel to be detected by the game would at least get users up and running if they manage to install GHub.

    Unless the reason by CM is that to add full support they want to do it all at once and properly but it's possibly not that far up the to-do list.

  17. Posted · Edited by steviejay69

    3 minutes ago, Quirk50 said:

    @steviejay69  No - It was my bad.  I left out the M when I told you before and the USB headers appear to be different, but its ok, because I used the USB3_4 front panel connector to plug in my wheelbase, and then pedals connected to wheelbase via RJ cable.
     

    Thanks.

    There would have hopefully been a file mismatch warning or somesuch in Instant BIOS! 🙂

    4.30 contains 0xCA but it seems there are issues using the mod tools on Asustek boards to get you 0xDE uCode

  18. Posted · Edited by steviejay69

    22 minutes ago, Quirk50 said:

    Your Image is for the Bios section of z390 Pro4,   and I have the z390M Pro4 - So I think I have the latest.

    Any settings in Fanalab that I should use or avoid?

    image.thumb.png.06a71a49beddf2f1e778e90062a2d7b4.png  

    My bad. The whole of the rear USB is USB 3.1, the only USB 2.0 is from the USB3_4 and USB5 Case Front Panel connectors.

  20. Posted

    15 minutes ago, Quirk50 said:

    @steviejay69

    Thanks.  I used the ASRock Bios update tool, but it did not load a newer bios.  Where are you seeing that there is a newer bios than the one I have? If you could point me to it, so I can download it, I would appreciate it.  Here is the download page for my motherboard  which is the asrock z390m pro4    :

    https://www.asrock.com/MB/Intel/Z390M Pro4/index.us.asp#Download

    image.thumb.png.b06901cb5b7c1ca8fc216b089912d49e.png

    Click where it says BIOS on the Downloads screen

    image.thumb.png.b22aa6e49ed7d286aceecc82f004d811.png

  21. Posted · Edited by steviejay69

    He needs to maybe even update the headset USB, without a dxdiag this is not possible to diagnose. As you can see from the template the peripherals list is incomplete. No mention of audio equipment with an audio bug.

    Also the suggestion from my earlier post is not in the troubleshooting attempted section of the template.

    "Is it plugged in and turned on?"

  23. Posted

    4 hours ago, Quirk50 said:

    Thanks @steviejay69  Ok - I have Bios 5.0000 running now, and wheel and pedals are attached to computer with USB 2 Cable in header 3__4.  USB headset is now in USB 3 port.  I am attaching new dxdiag.  

    I've installed the 380 RC driver, updated all the firmwares, including pedals via direct USB, and installed latest fanalab.  ....in my spare time.  I'll do some testing now.  Let me know if there is anything else you think I should check.

    DxDiag.txt

    There is no BIOS 5.00. The version 5.00 refers to AMI Aptio V (roman numeral for 5). The BIOS you have has a build date of 12/03/19 commensurate with a release date of build 4.00. The extracted file needs to be transferred to the root of a FAT/FAT32 USB stick and use the Instant Flash utility in the BIOS to update.

  24. Posted

    2 hours ago, Quirk50 said:

    Ok - Now running 20H2

    Motherboard is ASROCK z390 Pro4

    UEFI BIOS 4.50 (you need to be running at least 4.00 for proper CPU support and there have been microcode updates since then, from your BIOS date it looks like you may be running 4.00).

    So, after referring to the manual the 'safe' USB ports are the ones under the LAN socket on the rear panel and any case Front Panel USB connected to USB_3_4 (or the single USB_3_5 headers). Connect the Fanatec equipment to these ports, especially if you are going to do the v380 driver update and the firmwares.

    USB3_3_4 & USB3_5_6 are USB 3 headers so can be used to connect the Logitech Unified Receiver.

    The USB headset might be worth removing (any sound card dongle) or just try with the onboard audio alone for troubleshooting.

     

  25. Posted

    You should install the W10 update. 1809 is EOL in a few days. 

    457.09 drivers are suited to WDDM 2.7 and your version of W10 supports only WDDM 2.5

    Also, make and model of motherboard for further suggested updates please.

    Make sure you have the Fanatec in a USB 2.0 port and the Logitech wireless receiver away from it. I can make further suggestions once I know the motherboard make and model.

     

×