-
Content Count
5,344 -
Joined
-
Last visited
-
Days Won
2
Posts posted by steviejay69
-
-
12 hours ago, alejandroramos said:I use and works perfectly the f1 2019 same requirements
11 hours ago, dani42195 said:I decided to post my report in that topic too because there are more with similar issues
Decription: The game crashes before the main menu after the push any button sign
2. Version: 1.03
3. at launch
4. This has happened all the times i launched it
5. I've updated the graphics driver tried safe mode turned off steam overlay tried dx11 and dx12 too, with the same experience
6. Logitech G29
7. I'ce attached the dxdiag a video and the crash dumpYou are both running unsupported CPUs. They are 10 years old. Thery do NOT meet the MINIMUM REQUIREMENT and did not last year either. Saying the game ran is not a response, you got lucky.
Intel recently retired their Sandy Bridge and Ivy Bridge CPUs at 9 and 8 years old respectively. Intel's performance is way ahead of AMD at that point. They are also out of the MINIMUM REQUIREMENT which is Haswell i3-4130. Haswell is simply more efficient and has extra instructions. I have a test build with an I5-3470. It is Ivy Bridge and the game runs at 100FPS but I can see frame dropping in some corners at some tracks despite being paired with a GTX1060. I don't expect it will run F1 2021 optimally, if at all. These are the signs. It does not technically meet the minimum specification but there are no errors (other than gameplay), exactly what you had with F1 2019.
It's time to upgrade, your experience will be all the better for it.
I'm not just saying it, newer CPUs have instruction sets that older CPUs just can't utilise, especially with the maths needed for games. The CPU is often overlooked as a factor in games.
-
1
-
-
-
In the acclimatisation program, the gates are 'by design'. It's a game.
-
1
-
-
I might get a chance to reconnect my AMD machine tomorrow, I'll look at the driver issues but I think they may be game related.
20.4.2 is the minimum recommended driver but I got crashes too. CTD and EGO Dumper, they seem to have stopped on the Nvidia machine but the game is glitching in TT.
-
It's definitely not Steam overlay. I haven't disabled it and as yet have had no crashes with it enabled.
As per my other thread the stutter is when you beat your rival, not just setting a fastest lap
.
-
-
24 minutes ago, Elfster85 said:no, I have a program called Logitech Profiler to change the wheel settings. Should I try LGS?
It is my understanding that the DGFT is supported by LGS 5.10 which is linked in my earlier post. The LGS allows for profiles.
Delete the in-game schemas you have created. Uninstall the software you have with Geek Uninstaller.
Reboot and install LGS, attaching the wheel and rebooting as necessary.
Check for correct operation in LGS, delete the hardware_settings_config.xml and verify Steam files. Launch the game and configure the wheel as you want in game.
-
12 minutes ago, MrRatchet said:1. When playing with a thrustmaster tmx every button works except the throtle which is as "o"
2. f1 2020 latest version
3. Any gamemode
4. Start game, choose race, actual race, throtle not recognised
5. Reinstalled the drivers, still nothing, but it works in other games
6. Thrustmaster tmxYou may have the clutch and throttle inverted on the wheelbase, the clutch should be '0'. Hold 'Mode' for two seconds, the indicator should be Red. If it's Green the pedals are swapped, so repeat the hold 'Mode' for two seconds.
-
5 minutes ago, manwell02 said:Is there any news or updates on this yet?
Its happened all day and I still can’t play, there’s no updates on twitter or anything. I can’t find anything else on the forums either.
Today I’ve relaunched the game countless times and restarted the Xbox ect all for the issue still to be their.I get that there’s a lot of things you guys and the developers have to address and look in to, but I’ve had this issue now for nearly 24 hours. And personally I feel like a game breaking issues like this shouldn’t still be in the game. I’m not trying to have a go or take out frustration on you guys or the devs, I’m just disappointed and upset that this is happening.
I am more than happy to provide you a video of what’s happening, if you do require it.
Post the video. Take a look at my signature, I'm helping on a purely voluntary basis because of my love for the game and I'm on PC so there's ultimately very little I can do about XBox issues other than make suggestions.
-
1
-
-
2 hours ago, Elfster85 said:Hi,
1. Whenever I start a race in solo/career or multiplayer, the camera is always facing the rear when the light sequence begins. Then just before the lights go out, it switches back to the front TV pod which is what I set in the settings. The rear camera is also shown on flashbacks and just before the lights go out on a flying lap.
2. 1.03
3. Multiplayer, Career and Solo races
4. Happens every time. I don't know what the recreation steps are.
5. I tried unbinding the 'Look Back' button assignment on all enable inputs (i.e. wheel and keyboard). I recently got fanatec pedals several days after f12020 release and if I remember correctly before the new pedals the problem wasn't there. However, I tried unplugging the pedals and the problem still persists.
6. Wheel - Logitech Driving Force GT, Pedals - Fanatec CSL Elite (no loadcell)
7. https://youtu.be/j1A12TBaUe4Hope you can help me!
Thanks!
Are you using the LGS for the DFGT?
Also what is the Fanatec driver you are using for the CSL Elites (and assuming you are using the Clubsport USB adapter)? Should be at least v311x64
-
1 minute ago, CardConvict said:I'm honestly trying anything I can to stop stuttering and yes you did point out and I understood what you said, still doesn't change the fact I have issues in F1 code master games were developers don't seem to be wanting to help or point me and others in a direction.
They can't deal with all the issues at once. It's frustrating but this issue is quite important. Game crashes will be prioritised over stuttering issues. I'm afraid we have to try to figure out the issues then when we have them replicated clearly they can see the issues and fix them quicker. It's not going to happen for a couple of patches at least.
The game does not support all the new toys Nvidia are pushing. So the choice is clear, revert to an older driver or an older version of Windows.
Personally (and I'm quite an early adopter normally) the noises I'm getting from 2004 are that it's an update best avoided like 1809 and others before it, but I understand that not everyone will easily be able to revert to 1909. To revert the graphics driver, you should DDU. This is best done in Safe Mode with your internet disconnected.
The new driver should be loaded and you should delete the hardware_settings_config.xml file to recreate an out of box detection.
Currently I'm working with the older more stable branch (442.74 was stable with F1 2019) and I've not been able to force a crash.
You should try framelimiting and I've been syncing the desktop refresh to the same value as the in-game. I'm also using Fullscreen (Windowed) as it's easier to drop in and out of the game with less hassle. I've not had any audio drop-outs or major loss of FFB (except online in one race).
e.g. I'm running a 144Hz display but from benchmarking can see that the system can hold 100FPS mostly so I've set the cap at 99FPS and the desktop at 100Hz. This ensures my GPU is utilised but not nailed. V-SYNC was awful for input lag, but V-SYNC OFF capped seems better.
It's frustrating as there were hardly any graphics issues with the beta (and I'm going to say that now, not bothered if it's against anything I signed) yet the released game is a crapshoot in exactly that area.
It's interesting the two game areas that crash the most are the ones not tested, TT and MyTeam. I understand the reasons for their non-inclusion but this (and the final beta week build) have been an absolute slap in the face for all those directly involved at the sharp end of testing.
So believe me, I am super frustrated by what's been served up by the devs but it's not the fault of the beta testers nor the dev liaison. This is squarely on those responsible for the game code.
I'm hopeful that at least some of the issues found in beta will make the next couple of patches, all this release day build stuff is going to be a long haul because it's new to this game, but old to the title.
-
It's after you beat your rival. If you just set a personal best time but do not beat your rival, it does not crash.
If you can show me something to the contrary it would help (also your hardware_settings_config.xml and dxdiag.txt if you cannot provide the crashdump (.zip) )
This would help immensely and shortcut some of the time I'm spending personally trying to pinpoint the issue. Accept people on console can't really assist in that regard.
-
37 minutes ago, CardConvict said:Tried DLSS and got the black screen as others have reported so going to try the CS Culling option and see how I get on
I think I pointed out in the other thread that DLSS requires developer support. It won't be added to the F1 game as the development time won't benefit anything other than a small subset of users. Same reason that VR is not in the title year on year.
-
Tighter is better. Oh yeah.
-
2
-
-
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.
-
I agree the white balance or brightness is off.
Always hated that TT defaults to Midday instead of Official.
At Bahrain you need RayBans to see the track let alone anything else.
-
1
-
-
2 minutes ago, Hengz said:here it is
You have multiple sound sources.
For testing can you;
Remove the webcam, uninstall any audio or sound processing software.
Pick a default playback and default communications device in Windows, disabling any unused ones (e.g. GPU Audio driver)
Delete the hardware_settings_config.xml when not running and relaunch the game.
Check the audio options in F1 2020 match your default.
Thanks.
-
3 minutes ago, NeoSephiroth said:Well I got another hint and it worked. I updated my wheel firmware from 5.4 to 5.6 and now my wheel gets recognized from the game.
Works superfine ingame. Win7 not supported ok, but it works. Screw Win10.^^
Just goes to prove, you should always update.
-
Post dxdiags!
-
2 minutes ago, hardbaked said:On PC ver 1.04 I dont see any of the cars rear lights flash during energy recovery or in wet.
-
2 minutes ago, hardbaked said:how do you change from DX12 to DX11 mode when launching the game? it only asked this on the first load after install, how do you change it now?
If you start from the Steam Library you get the choice. If you start from the desktop shortcut it throws you into DX12.
-
1
-
-
8 hours ago, kenzieretro64 said:one major issue that's grinding my gears and driving me up the wall is going through races while not being involved in any accidents.
just did a race in vietnam as one of the podium pass challenges (still waiting on my 15k coins) is do a race in vietnam without being involved in an accident (which i did) and yet, progress in the squeaky clean achievement didn't happen (still stuck on 30% - 3 out of 10) and the vietnam challenge did not show up as complete.
codemasters, explain please
Worked for me, this might have been due to online services being up and down. But as @1512marcel says, you need to log it as a bug to get it fixed. Include your gamertag.
-
This thread might have answers or confirm the issue
-
This is a reported bug. I'll flag it to be merged.



Crashing Dx11 and 12, egodumper, freezing
in Systems and Connectivity TA
Posted
I think the game is just unstable in TT as I also complete races without issue. XB1 and PS4 are also getting the TT crashes.
The default driver I referred to previously was for the GPU (432.00 for 1909 it is the Inbox/WU driver). Also I let the ASMedia controllers do the same. HTH. But I am currently running 442.74. The advice about DDU is sound.