Zandvoort - Pit lane speed limit and tyre compounds don't match real life F1
Description: The pit lane speed limit at Zandvoort from this year onwards is 80 kmph. Both in game and in the UDP telemetry, it is set to 60 kmph The tyre compounds IRL this year is C2, C3, C4. In game, it is still C1, C2, C3 Platform: PC, steam Expected Behaviour: Game to match real life standards, given that this is the official licensed game of F1 Actual Behaviour: Outdated pit lane speed limit and tyre compound choices Steps to reproduce: Fire up any mode in F1 25 game at Zandvoort (both forward and reverse layouts) Drive into pits. Observe the speed limit board and the in game HUD. Both show incorrect speed limit Also, check tyre compounds in the career mode tyre allocation section UI or check telemetry { "actual-tyre-compound": "C3", "available": false, "fitted": false, "lap-delta-time": -1378, "life-span": 38, "recommended-session": "Qualifying 3", "usable-life": 38, "visual-tyre-compound": "Soft", "wear": 0 }, { "actual-tyre-compound": "C2", "available": true, "fitted": false, "lap-delta-time": -704, "life-span": 45, "recommended-session": "Practice 1", "usable-life": 45, "visual-tyre-compound": "Medium", "wear": 0 }, { "actual-tyre-compound": "C1", "available": true, "fitted": true, "lap-delta-time": 0, "life-span": 62, "recommended-session": "Practice 1", "usable-life": 62, "visual-tyre-compound": "Hard", "wear": 0 },Triple dlss
So are we just out of luck and never going to get a fix for this after you guys advertised triple screen support. Likely the configuration to benefit the most for fps we are locked out of functionality. After being led to believe this was being investigated and now you guys are just washing you hands of this issue. Very frustratingSports Update doesn't include updated Aston Martin and Mercedes liveries
I'm making a seperate report for this, as the updated "Community Raised Issues" list doesn't include this specific issue. The updated Aston Martin and Mercedes liveries were not included in the sports update. Please refer to your OFFICIAL reddit post and compare it to what is actually in the game right now: https://www.reddit.com/r/F1Game/comments/1njgbfb/celebrating_a_decade_of_speed_in_season_3/Two-player career doesn't work
After update 1.13, the two-player career mode isn't working. My friend and I are stuck on an infinite loading screen. I play on PC Steam, and my friend plays on PS5. Every time I try to verify the game files on Steam, I get a message that three files are missing. Reinstalling the game to a different drive doesn't help.Anti-Aliasing option resets to TAA on every boot
Hello, the game seems to reset the previously selected upscaler (FSR/XeSS) and switches to TAA after starting the game again. Upon inspecting hardware_settings_config.xml , we can see that the value of TAA anti-aliasing is forced to "true" the moment you launch the game. As such, the anti-aliasing settings resets to TAA every time. <antialiasing taa="true" cas="1" dlss="false" fsr3="1" xess="false" /> The FSR3 / CAS value enabled in previous game session remains unchanged, but in-game, TAA Only is selected Relevant thread with less info: here Report code: XZXR-TTCM-CJBR-XXSGG29 Forcefeedback Issues
Product: F1 25 Platform:Steam-PC Please specify your platform model. PC Summarize your bug Hi, I just bought F1 25 and my G 29 has a problem. At certain parts of tracks in turns, my wheel turns completely to one side and locks out making me counter steer mid corner. Also, the force feedback also completely cuts out on some parts of the tracks. I've tried all of the following: opening G hub before opening F1 25, not using G hub at all when playing F1 25, restart both F1 25 and G hub, unplugging and replugging my wheel and checking if all the wires all correctly connected. I can also mention that my wheel is not broken since i tried it with every other wheel game I own. So, if anyone knows why that happens and how to fixed it I would like to know. Thanks. What peripherals are you using? Please list the exact make and model. LOGITECH G29 Which area is the bug/glitch in? On every Track Steps: How can we find the bug ourselves? CANT IF DONT HAVE LOGITECH G29 What happens when the bug occurs? Wheel completely locks out to the left or right making it impossible to drive What do you expect to see? Correctly Working ForcefeedbackRay Reconstruction forces DLSS to Balanced
I realized that if you activate RR , even on simple ray tracing or on path tracing , if you select DLSS it will be forced always on Balanced level (don't know maybe Performance?) Just to make an example : My resolution is 3440x1440 and the output resolution shown from DLSS indicator was 1720x720 It doesn't matter if you change it under settings or if you force it via Nvidia App, it will be always set like that If you turn off ray reconstruction then you can change DLSS quality without problems, it will also ovverride DLLS model from what you choose on Nvidia appFaulty liveries after Patch 1.12
1. Major error on the Red Bull livery. The car doesn't render correctly, and if you look into the engine base from behind, you can see through the livery! It can be checked easily in the Virtual Showroom. 2. The Freshworks logo on the McLaren halo is spelled "freshwor" and its placement is off. EA_Groguet Please let the team know, so they can patch these in a hotfix! These are the only livery errors I've noticed so far, but there may be more.UNPLAYABLE TIME TRIAL AND CHALLENGES
I have previously reported on this issue twice on the forum with no response or attention and I have tried contacting EA support directly with no help whatsoever and getting the same AI response to check their support forums and to report my issue here. My game continues to crash update after update and I am unable to play time trials and time trial related challengers. Because of this I cannot get the new Haas US gp livery. Upon trying to load time trials, when the game hits "saving" it freezes and the whole game quits. No error message or code, nothing. I've had this issue for well over a month and I've had no luck on fixing it. Every patch update that comes out does not highlight this issue, and I seem to be the only one experiencing it. I attached a video below which shows my issue.