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.Right impulse-trigger rumble never rumbles
Title: F1 25 (PC): right impulse-trigger rumble never fires — USB capture proves the game sends RT magnitude = 0x00 (left trigger and body motors work fine) Platform: PC (Steam) Steam version build ID: 22074649, latest available version on Steam from 2026-03-02 Game modes affected: All (Time Trial, Grand Prix, Career, Multiplayer) Controller: GameSir-G7 SE (wired, Xbox/GIP mode, firmware 6.6.4) SUMMARY Only the LEFT impulse-trigger motor (LT) ever vibrates in-game. The RIGHT impulse-trigger motor (RT) never vibrates under any condition. Body rumble motors and the left trigger work normally. I captured the USB traffic and the game literally never sends a non-zero value to the right-trigger motor. STEPS TO REPRODUCE 1. Connect an Xbox-layout controller with impulse triggers. 2. Settings > Vibration & Force Feedback: Vibration ON (full strength), Trigger Vibration ON, Adaptive Triggers OFF, On Track Effects 100. 3. Assists: Traction Control OFF (so wheelspin occurs) 4. Drive: brake hard (should buzz LT) and provoke wheelspin on throttle (should buzz RT). EXPECTED RT vibrates on loss of traction under throttle, symmetrically to LT under braking. ACTUAL LT and body motors vibrate. RT is completely silent at all times. PROOF (USB bus capture, USBPcap + Wireshark) The GIP rumble command (endpoint OUT 0x02, command 0x09) carries separate magnitude bytes: 09 00 <seq> 09 00 <mask> <LT> <RT> <mainL> <mainR> <dur> 00 <rep> (magnitudes 0..100) - Reference (a standalone Windows.Gaming.Input "trigger-rumble" test, NOT the game), right trigger at full power: 09 00 2f 09 00 0f 00 64 00 00 ff 00 eb -> RT byte = 0x64 -> the controller's right trigger vibrates correctly. So the hardware and the OS rumble path drive RT perfectly. - In F1 25 (full play session, 904 rumble packets captured): LT byte > 0 in 525 packets (max 0x1a) main motors > 0 in 535 packets (max 0x64) RT byte > 0 in 0 packets -> RT byte = 0x00 in EVERY packet The game modulates the left trigger and both body motors, but never writes the right-trigger channel. Not once. CONCLUSION This is a game-side bug: F1 25 never actuates the right impulse-trigger motor. The controller is proven fully functional (the reference command above makes RT vibrate). SYSTEM Windows 11 Pro; Steam; Steam Input disabled for the title (verified; behaviour identical with Steam Input enabled).F1 26 Power drop glitch
I’ve recently had issues in career mode on ps5 on a Logitech wheel where the power cuts about halfway despite full throttle where battery will not burn or deploy and straight mode may even flick on and off rapidly. It fixes itself after a corner or two but I lose so much time and it’s very unpredictable. It’s only happened as of the recent update and I have no idea what to do. The video below I am full throttle but power is cut so a certain point.Bug Report – VR / PS VR2 – F1 25 (PC/Steam)
Platform: PC (Steam) Headset: PS VR2 via official PC adapter + SteamVR CPU: Intel Core i5-14600K | GPU: RTX 9060 XT Issue: When entering gameplay (garage or driving), the left and right eye rendering becomes misaligned and uncalibrated, causing severe distortion and an uncentered view. Resetting the VR position does not fix the issue. The problem occurs exclusively in F1 25 — all other VR-compatible games work correctly with the same headset and setup, without any additional configuration. Steps to reproduce: 1. Connect PS VR2 via official PC adapter 2. Launch SteamVR 3. Launch F1 25 in VR mode 4. Enter any gameplay session (garage or on track) Expected behavior: Both eyes render correctly aligned, providing a stable and centered stereoscopic view. Actual behavior: Each eye points in a diverging direction, causing distortion and an unplayable experience. Additional notes: - Editing hardware_settings_config_vr.xml (stencilMesh, TAA, post-processing) did not resolve the issue. - Disabling Motion Smoothing and setting SteamVR to 120Hz did not resolve the issue. - The bug has been reported by multiple users on the EA Forums and Steam Discussions, suggesting it is a systematic issue with PS VR2 + SteamVR on F1 25, not an isolated case.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/xM15j8fmqmNo Force Feedback on SIMAGIC Alpha EVO Pro / “simpro_1.dll” Untrusted File Error
I am experiencing an issue with Force Feedback in F1 25 while using a SIMAGIC Alpha EVO Pro wheelbase. When I launch the game, I get the following error message: “This untrusted file was not able to be loaded: C:\Program Files (x86)\simagic\simpro3\bin\simpro_1.dll” After this message appears, the game launches normally, and my wheel, pedals, and buttons are all detected and work correctly. However, Force Feedback does not work at all. There is absolutely no FFB from the wheelbase while driving. Other racing games work normally with Force Feedback, so the problem seems to be specific to F1 25. I have also tried reinstalling SIMPro Manager and F1 25, but the issue still remains. Could this simpro_1.dll untrusted file error be preventing F1 25 from using Force Feedback? Is there any way to allow this DLL, fix the compatibility issue, or restore Force Feedback? I have attached a screenshot of the error message.Vibrations turning off on controller
Randomly in online races, usually when someone in the lobby is lagging, all vibrations either reduce to a low setting or completely stop on PS5 and it makes the car extremely difficult to drive. A quick fix is to pause and un-pause the game, bringing back vibrations momentarily until they break again, usually within a lap. An easy fix would be to make vibrations client side if possible to avoid lag breaking them. This has been happening for the whole of F1 25, but since the 2026 DLC released it seems to have gotten worse. As far as I know this only affects PS5.Game crashing during online lobbies
In my league, several drivers on both PC and console have experienced their games crashing, mainly when moving between sessions, such as from qualifying to the race. At first, we thought the formation lap might be causing the issue because drivers often crashed as it began. However, it has also happened when the formation lap is disabled and the race starts immediately. We do not really understand what is causing it. It has happened with different people hosting the lobby, so it does not appear to be related to one host or their connection. Has anyone else experienced these issues?