steviejay69

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).

GHub is required for FFB, it installs the C:\Program Files\LGHUB\legacy_forcefeedback_x64.dll

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.

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.

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

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.

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.

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.

Do away with rejoin then people would sort poor connections out. Or they'd be more honest about how poor multiplayer is. The amount of bugs that are probably created by a rude disconnect, incomplete file sync and by killing the executable is intangible. Loss of FFB, incorrect setups, delta errors, problems with the results, inconsistent penalty application, the knock-on list is not exhaustive.

Thought it might be DLSS but you are on the 1070 so this should be merged with all the other Nvidia issues.

I'm astounded. All the modes should use the same data, it's becoming clear that they do not. If this methodology is employed across the entire game there is no wonder the code is messy (not to mention bloated). IANAP but I'm beginning to think I should retrain to save the franchise 😉

Can you expand on that? I only ever use Mercedes or now the Custom Team in TT as the others have 2020 performance (not sure if the update now reflects this or it was just for Career / My Team as I've seen another bug listed about no quali races reverting to 2018 performance). The Merc TT indicator that worked in TT is not the same as the one on Bottas' car in Grand Prix if that's what you mean.

1. A detailed description of the issue. Please include any error codes here. On the Mercedes and Force India when using cockpit the on-screen wheel dash leds light a single light on the right to indicate DRS available and becomes two when DRS is active. This is working OK in TT and Multiplayer but not in GP (no lights are shown). 2. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.03 3. Game-mode? Grand Prix 4. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. Every time. Step 1 gives you enough detail. 5. What troubleshooting have you attempted? Please always try to attempt to fix the issue Not sure it can be fixed by the player except using another camera view or a telemetry app (SimDash is not updated yet AFAIK) 6. What peripherals are you are using (gamepad, wheel make & model etc) Fanatec CSL Elite, Clubsport Formula Wheel F1 2020 Limited Edition, CSPv1 pedals. 7. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears. Not recording at present as trying to prove / eliminate GFE as a cause of crashes.

Were you leading, because this was in earlier revisions of the game also, I don't think it is a new bug.

Hi @mattw404 LGS 9.xx.xx is abandonware by Logitech, as proven by the LGS 5.10.127 x64 for wheels prior to G29/G920/G923 so I suggest for updates you choose to use GHub.

Post a dxdiag.

You need to fill out the bug report template. If you're on PC (which we can't tell from this post) then include your dxdiag when it's edited.

I think you need to delete the custom control schema, verify the Steam files and delete the hardware_settings_config.xml Check also the Steam controller setting is not enabled. It looks like the wheel rotation is being treat like a switch, left goes -100 and right +100 rather than an axis. @LogiUK

Yeah just a bump to say it's still not fixed but affects the first driver in a team (e.g. Hamilton not Bottas). Not fully tested, but accept the anecdotal evidence of the other posters. I will check My Team when I reach Bahrain practice.

Yes so far this looks very good

When you go with XBL, PSN or Steam, you go with XBL, PSN or Steam. I think EA are a bigger concern that can afford to run their own servers and operate via more online platforms. Although, the online services are effectively CM servers, so I suppose what you say would be possible. Just thinking out loud. 🙂

Get your bug reports in. As an aside, I recently changed graphics cards from RX580 to RX5700XT and everything went smoothly, no issues. (DDU'ed 20.5.1 and reinstalled) I then observed an (unrelated) drop in NVMe performance and I did a complete rebuild in software (1909 and same drivers) and started getting EGO dumper crashes after a rebuild. On drill down the only differences were the network driver (newer) and the sound driver (configuration). I now have the 'Voice control unavailable' message, despite a restore and first run of the game, so I don't know. I did a manual refresh of the contents of the Steam folders related to the game as I don't trust Steam cloud sync when it is removed suddenly (as is Steam's want to go FUBAR at any given moment). Recently though, I have had a couple of instances of having to kill the game's executable as I was in a locked or hung lobby. That is a bug that needs addressing and pronto.

Honestly, I haven't played the mode at all. Gimmick 🙂

A detailed description of the issue. Please include any error codes here. When attempting an F2 Race Weekend the lack of "front wing change only" ruins the gameplay because the game changes your tyres to a used set when pitting in the sprint or uses your sprint race set of primes in the feature on a second stop. Street circuits like Monaco (this example), Baku and Singapore are more examples because of the likelyhood of contact with the barriers. Hanoi could also be the same and maybe Russia but they're a bit more like part circuits. Platform PC What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.10 Game-mode? F2 2019 Unranked Multiplayer We need to be able to make your problem happen internally so we can fix the issue. Can you make the problem happen again? Yes, it's not difficult. Go as fast as you can and push hard at a street circuit. How do you make the problem happen? Make an additional pitstop in either race and be given another tyre. What troubleshooting have you attempted? Please always try to attempt to fix the issue You can't without the option to have a nose cone only pitstop. IRL the team would change only the wing. What peripherals are you are using (gamepad, wheel make & model etc) Not relevant as it's gameplay. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears. I could show you the wear on the used set fitted when I pitted in the sprint on Saturday but I think it's clear to understand.

Suggestion: When using the G series wheels in F1, you need to start with a DOR of 360 and tweak from there. The G series wheels are 900 DOR by default. Profiles for F1 2020 are advisable. Suggestion: When using assists the braking assist is very difficult to understand with a wheel, I think it should be restricted to pad players. Suggestion: The G series wheels use potentiometer pedals, please check for full registration against pedal travel in GHub. Modifying the brake pedal by removing the rubber is not advisable as the extra travel is not recorded. Also the potentiometers can become dirty, so please check and clean them (be careful when opening the pedals as the signal wire is clipped against the pedal body with not a lot of spare travel). Suggestion: If cleaning the pedals is not enough, use the deadzone to eliminate a bit of 'flicker' (pedal registering without input) but bear in mind the pedal will need to be pressed further to start to register. Suggestion: If the pedal does not meet full travel after cleaning / inspection you can use saturation to increase the input response from the same travel. Suggestion: Linearity can be used to adjust how fast the pedal swings from not registered to full registration (adding Linearity means the initial response will be slower, allowing finer control on the first part of travel with smaller braking effort). It will also adjust the rate of response as the pedal approaches full travel. None of the settings are mutually exclusive, you can combine all of them. Check also the calibration settings in Windows Control Panel (this may only apply to those still using LGS - haven't owned a G wheel since GHub replaced LGS). Sometimes deleting the in-game custom control schemas, verifying the game files and deleting the hardware_settings_config.xml (on PC only) can rectify a misconfigured pedal. Using Geek Uninstaller, Logitech Driver Cleaner or USBDeView can remove software issues regarding USB detection. Always use the latest software drivers and update your PC.