steviejay69

You will need to change the privacy of that dxdiag @Quirk50 or just attach it to the forum?

Post a dxdiag as me and @TeenierNeilb69 run very similar wheel hardware the only issues we have (apart from gameplay) are the wheel vibration in the MP lobby. Fanatec have flagged this as a CM issue, still not addressed. He has the CSW2.5 and I have the CSL-E, we have both run with the 373 drivers and firmwares on Formula v2 wheels. I have CSL-E LC pedals on RJ12 and he has CSP v3 on USB. We have both updated to 380 drivers and firmwares without any apparent issues. We also use Fanalab v1.47

Then your board is H61M-D2H rev 1.0 with F1 BIOS, here is F5 use Q-FLASH. The GPU is EOL - Fermi is 391.35 you have this installed according to dxdiag, but DDU and reinstall if this was not a Nvidia download and was installed by WU. As you have no further updates I recommend trying the game in DX12 then DX11. You should be prompted that your drivers are older than the recommended minimum. Also, make sure you do not set any particular option in the driver before testing. Try disabling fast shutdown in the Power options. Delete the hardware_settings_config.xml before trying each variant.

Nice to know I'm not going mad 😉 be happy to take another look. It is my hope to cut down the noise of misconfigured PCs so we can help CM get to the actual issues faster. I'm not sure this open forum is actually working. There is no CAPTCIHA.

Again, as I've already said, the hardware is DX12 native. Trying to run a title in DX11 is like running in compatibility mode. DX is a subset / superset model. All you achieve is doing more work to get to the end result, thereby reducing performance. Vega 8 is somewhere between GTX950M and GTX1050M in performance, so you need all you can get. I've done a search and F1 2018 DX12 on that hardware was about 55FPS on Medium settings, so all the rest is optimisations from driver maturity and by CM making DX12 the primary API.

I can't even find your dxdiag on this thread unless you've edited it. I look at hundreds of these files a week. Guess that's one less I'll look at. Someone's dxdiag was trying to start the game at 2160 on a GTX1060. You sound spiteful. Nvidia churn out garbage drivers, the sooner you fanboys start to lay blame where it's due - I give you the crashing 3080s as a very recent high profile example.

A lot of the support issues on here are because the users do not know or just do not bother to update their technology. Just because it works on day 1 does not mean what you ask of it remains the same. I don't know of much tech now that is not released with some features either pending or future planned. The game has been updated to add features but I guess if you could run the older patch you could use it like that when it worked. P.S. I don't know how you access the forum so I don't know if you have signatures turned on. I don't work for Codemasters and I give my time for free so I can't continue to help people who can't help themselves by recognising the obvious, especially when it is highlighted, not just in your own post but recommended on others.

No your problem is not the same, one user is using Windows 7 and another has an unsupported CPU so probably lacking a BIOS update so not remotely the same. Plus one is using a single display.

Processor is n/a, so please furnish more info. H61 is Series 6 so supports SandyBridge / IvyBridge LGA 1155.

Windows 7 is an unsupported OS.

Are you being deliberately dense? That is two displays. Good luck.

Your dxdiag is showing two monitors. Turning it off is not enough, unplug the cable. Please remove the helmet mod. And post in English, that is the forum rule. I'm almost at the point now where I won't fight people, I'll just stop with the offer of help.

There is no reason not to use DX12 it is the preferred API. The majority of reported errors with DX12 are poorly configured systems or small demographic with esoteric or specific (newer) hardware. I can't translate the screenshots as they are pictures and I can't read beyond basic German. I do not have a dual screen setup. For troubleshooting perhaps it is better to play on the laptop screen and disconnect the external screen as I said. Upload the crash dump from the EGO Dumper error (not the EGO dumper log file, please). Instructions on how to do this are in the main troubleshooting thread. I appreciate that English is not your first language, but at least you can copy and paste with a translation tool. Can't do that with pictures (unless someone knows you can and shares the link!).

That's a "your issue" I start the game in DX12 and do not get EGO dumper, so please try DX12 after carrying out the steps and maybe deleting the hardware_setttings_config.xml too.

That APU will run better if it's not running two displays. Explain the 'known bug' with DX12 please. DDU is always a good idea when updating and yes the audio devices are obviously misconfigured as you have no engineer radio. From the clip you posted, yes it does have to do with graphics as you are scaling. We need to eliminate potential issues, once they are identified then maybe something can be done about them.

You are using a secondary display (and possibly scaling). Please switch your output to secondary only when playing and play at 1080. The laptop internal panel is 1366x768, if you play on the laptop display, change the in-game setting to suit, disconnect the external display completely. As for drivers you should use the latest recommended for your APU 20.10.1 If you experience issues, you should DDU and install the older Lenovo OEM driver (it's released February 2020 but is possibly based on older Adrenalin 2020 - debuted in December 2019). Installing a graphics driver may affect your default sound devices in Windows and other audio programs, set a default device and consider disabling the unused ones. Bear in mind the audio device will be different for the external display (using the Display Audio HDMI(?)) and the laptop internal display (using the integrated audio). Also you are running the game in DX11, you should use DX12.

Instead of editing the post to say you fixed it, why not share the information that corrected the issue? There are no stupid questions but there should be some pain inflicted for no or stupid answers!

Delete the hardware_settings_config.xml before launching the game. I think you are being optimistic trying to launch in 4K on a GTX1060 with a 4 year old CPU. dxdiag would be more help to me, but I think the issue is the recommended one. Try one display that runs at 1920x1080.

OK, if you have done it then the confirmation helps. Squarely with CM to sort it then possibly, because I know the Vega is architecturally different to the older GCN and not a Navi card. Remove Armoury Crate. DDU the GPU driver. Go with the recommended 20.9.1 (I think 20.4.2 was the last recommended before that if a rollback is necessary). Avoid using the ASMedia USB ports (uninstall any downloaded driver and let WU/Inbox driver install). Get the AMD chipset drivers from AMD, not ASUS (IDK where that build is from). The only other option is to nuke Windows 10 and go again but I doubt you'll have the 1909 media (I too am staying on 1909 'til the game's lifecycle is done). Don't think there's much else your end, you are using GHub and as long as you're avoiding the ASMedia USB ports there should be no latency issues. I would suggest letting the driver install vanilla and going with the highest settings in-game and the desktop refresh set as high as possible with the game set at the same refresh. Consider using FPS counter and capping if the framerate is soaring. Deleting the hardware_settings_config.xml should let everything redetect after the DDU and reinstall. Other than that CM might want to suggest which features to start disabling on the GPU from there.

As far as I can see you haven't responded to my request for information on the motherboard, nor updated those UEFI (AGESA) and drivers. Or maybe this is just a Vega GPU issue. I have absolutely no technical issues with this game on RX580 or RX5700XT (despite me being apprehensive after the RX580 ran so well). Just gameplay bugs Codemasters!!! Other things to consider are power draw (PSU) and RAM timings (again to do with the UEFI). But hey, I've only been building and maintaining PCs for about 30 years, so what do I know, right?

A fan of the 'one race' mode myself. How does that help? 🙂

They have an ideal opportunity to break the mould here. Cars frozen for 2021 and tracks missing from 2020 due to Covid, DLC? Nope. Really they could do a F1 2020 to F1 2021 update and add the tracks from this year. People will do it, the game will have longevity and they have no excuse for not fixing the bugs.

I'm guessing not but the textures issue isn't confined to PS4.

Well, not really. You bought it and the game, so do a little research.

He can compare it to Adolf Hitler's banana collection if he likes. As long as there is a relevance....and I think there is. Don't worry, there will be another update, the 2020 F2 update for one. And Xmas DLC, obviously.