Force feedback disabled or violently throwing the wheel on new update
Everything was completely fine yesterday, but today on v1.25 at random times (seemingly after retrying/resetting a session or a session change) the force feedback breaks and starts violently throwing the wheel from one side to another. Turning the wheelbase off and on sometimes fixes it or just disables the force feedback. The wheelbase is a Fanatec CSL DD. No similar problems on any other game.
The noise that helps you find your grid spot keeps playing.
I've been playing through the My team mode on PC as Victor Martins and during the formation lap at Shanghai I collided with my teammate, Pepe Marti. After this the AI took over control of both cars and drove them back to the grid before disqualifying Marti. However it seemingly didn't park my car properly in my grid spot and that meant that I had to listen to the noise that plays to help you find your spot throughout the entire race and until I quit the My team mode. Has anyone else experienced this issue?Crash to desktop (CTD) without error code after Patch 1.26 (Win 11 26H2)
Product: F1 25 (2026 Season Pack) Platform: PC (Windows 11, version 26H2) Game Version: Patch 1.26 Description: Since the latest 1.26 update, the game crashes directly to the desktop at completely random moments during gameplay. There is no freeze, no warning message, and no error code generated - the game process simply closes instantly.Telemetry FFB & pedal haptic feedback vibrating violently while idle and in menu
Hi EA team, When I use F1 25 with MOZA's telemetry-based force feedback and pedal haptics, the vibration works correctly while driving. As soon as the game is not actively simulating (pause, replay, or main menu), the vibration does not stop. It gets stronger the longer I leave it. My setup Platform: PC (Windows 11 Pro) Wheel base: MOZA R12 with MOZA Pit House software Pedals: MOZA CRP2 with MOZA pedal haptic feedback kit What happens Driving: everything works as expected. Pause: wheel and pedals keep vibrating, and the intensity keeps rising while I do nothing. Replay: vibration does not stop. It keeps ramping up for as long as the replay is open. Quit to the main menu mid-session: vibration continues in the menu. 5It seems to get worse after each pause or replay I enter. What I expected Vibration should stop completely, or drop to zero, whenever the car is not being driven. That includes pause, replay and menus. I am also reporting this to MOZA, since their software processes the data Thanks!Opponents break lights not showing
Hi All, I am reporting an issue regarding the break lights for other cars are not showing to me, since I first played the game. I tried reinstalling the game, resetting all graphic settings, updating NVIDIA, and I even try it with other screens and graphics settings and it not showing at all. --- MY PC Specs Windows 11 Pro AMD Ryzen 7 7800X3D (4.2GHz, 8-core) 32GB RAM 5200 MHz NVIDIA RTX 5070Ti (16GB VRAM) Thanks!F1 25 loses ALL input after opening SteamVR Dashboard with Steam Frame
Hello, I have found a 100% reproducible input problem when using a Steam Frame with SteamVR and F1 25. The problem occurs specifically when the SteamVR Dashboard is opened using the Steam button on the Steam Frame controller. SYSTEM / SETUP Headset: Steam Frame PC: Windows 11 Connection: Steam Frame connected to the PC using Steam Link VR runtime: SteamVR Game: F1 25 (Steam version)VR: F1 25 running in VR mode using SteamVR/OpenVR Controller: Xbox controller connected to the PC IMPORTANT: F1 25 VR previously worked correctly on this same PC with a Meta Quest headset. REPRODUCTION STEPS 1. Start SteamVR on the Windows PC. 2. Turn on the Steam Frame and wait until it is connected. 3. Start F1 25 from Steam in VR mode. 4. Enter a playable session, for example Time Trial. 5. The Xbox controller works normally. 6. I can drive the car normally. 7. Press the Steam button on either Steam Frame controller. 8. The SteamVR/Steam Frame Dashboard opens. 9. Close/resume the game from the Dashboard. RESULT Immediately after pressing the Steam button, F1 25 loses ALL input. The game does NOT crash. The VR image continues rendering normally. The game remains running and the cockpit is still visible. However, F1 25 no longer receives input from ANY of the following: - Xbox controller - PC keyboard - PC mouse -Steam Frame controllers The Steam Frame controllers themselves still work for interacting with the SteamVR Dashboard, but once the Dashboard is closed, F1 25 receives no input. For example, I can point at "Resume Game" in the SteamVR Dashboard, but after returning to F1 25 the game does not respond to the controller, keyboard, mouse, or Frame controllers. The only way I have found to regain control of F1 25 is to restart the game. EXPECTED RESULT After opening and closing the SteamVR Dashboard, F1 25 should continue receiving input and I should be able to resume playing normally. ACTUAL RESULT Opening the SteamVR Dashboard causes F1 25 to permanently lose all input for that session while the game continues rendering normally. ADDITIONAL TESTING I have reproduced this multiple times with the exact same result. I have also tested the following: - F1 25 works normally in non-VR mode. - Xbox controller works normally in Windows. - Keyboard and mouse work normally in Windows. - Xbox controller works inside F1 25 VR before opening the SteamVR Dashboard. - Keyboard and mouse also work before opening the Dashboard. - The problem occurs immediately when the Steam Frame Steam button is pressed. - The game continues rendering after input is lost. - SteamVR itself continues running. - The Steam Frame remains connected. - Restarting F1 25 restores input until the SteamVR Dashboard is opened again. - Steam Input for F1 25 has been disabled. - The problem is therefore not limited to the Xbox controller; keyboard, mouse and Frame controllers all stop working in F1 25 at the same moment. - I previously used a Meta Quest headset 2 with this same PC and F1 25 VR worked correctly. I have intentionally stopped further troubleshooting because the Dashboard button provides a reliable and repeatable trigger for the problem. This makes the issue very easy to reproduce: F1 25 VR working ↓ Press Steam button on Steam Frame ↓ SteamVR Dashboard opens ↓ Return to F1 25 ↓ F1 25 still renders but receives ZERO input Please investigate whether opening the SteamVR Dashboard on Steam Frame is leaving the OpenVR application (F1 25) in a state where application input is no longer delivered after the Dashboard is closed. CONTROL TEST WITH OTHER VR RACING GAMES To determine whether the Steam Frame/SteamVR Dashboard itself was causing the problem, I performed the same test with other VR racing games. Using the exact same PC, SteamVR, Steam Frame and Xbox controller: Project CARS 2: - Started from SteamVR Home. - Xbox controller works normally. - Entered VR gameplay. - Pressed the Steam button on the Steam Frame controller. - SteamVR Dashboard opened normally. - Closed the Dashboard. - Returned to Project CARS 2. - Xbox controller continued working normally. Assetto Corsa 2 - Started from the same SteamVR Home environment. - Xbox controller works normally. - Entered VR gameplay. - Used the Steam Frame Steam button to open the SteamVR Dashboard. - Closed the Dashboard. - Returned to the game. - Xbox controller continued working normally. Therefore, opening and closing the SteamVR Dashboard does NOT generally cause Xbox controller input to be lost on this PC/SteamVR/Steam Frame setup. The problem is reproducible specifically with F1 25. This is also not limited to the Xbox controller. When the problem occurs in F1 25, keyboard and mouse input are also lost, and the Steam Frame controllers cannot interact with F1 25 either. F1 25 continues rendering normally and does not crash. The exact trigger remains: F1 25 VR + Xbox controller working ↓ Press Steam button on Steam Frame ↓ SteamVR Dashboard opens ↓ Return to F1 25 ↓ F1 25 still rendering ↓ ALL F1 25 application input is lost Thank you.
F1 25 does not launch — EA Javelin Event ID 1000 / 0xC0000005 / Windows 11 25H2
Hello, I cannot launch F1 25 on PC through Steam / EA Play. The game does not reach the main menu. Launch flow: Steam starts the game → EA App opens → EA Javelin AntiCheat starts → F1 25 closes/crashes. Event Viewer shows: EA Javelin Anticheat Event ID: 1000 f1_25.exe exited unexpectedly Code: 0xC0000005 System: Windows 11 Pro 25H2 Build: 26200.8737 GPU: NVIDIA RTX 4060 Ti NVIDIA driver: 32.0.16.1062 Steam AppID: 3059520 Secure Boot: Enabled TPM 2.0: Present and Ready Already tried: - EA App reinstall - Steam Verify Integrity - EA AntiCheat / EA Javelin repair - Secure Boot / TPM check - NVIDIA Overlay / FrameView disabled - FACEIT Anti-Cheat fully removed - Checked other anti-cheat services/drivers - VC++ Redistributables checked - Recent Windows updates removed and tested - Memory Integrity / HVCI disabled and tested - Shader cache / F1 25 user folder reset - Multiple reboots and clean launch attempts Nothing helped. I also contacted EA Help multiple times. The chats were repeatedly disconnected by timeout, and I was asked basic scripted questions despite already providing diagnostics, DxDiag, and Event Viewer details. This does not look like a normal installation issue. It looks like an EA Javelin AntiCheat compatibility/crash issue on Windows 11 25H2 / build 26200. Please escalate this to the EA Javelin / F1 25 technical team. If anyone has the same issue or found a working fix, please reply here.G29 rotation problem still not fixed
No matter what the rotation is on ghub or the game the car doesn’t turn like it used to something is broken and the only way to fix it is raising the saturation over 50 which ends up ruining trail breaking. I am not even alone on this or just imagining things here is a reddit post with many having the same issue so please ea fix it the game is currently unplayable https://www.reddit.com/r/F1Game/s/xM15j8fmqm
