Massive FPS drop when using FFB on G29

Hello, I am. using my G29 on RaceRoom and it goes smooth at 60FPS without FFB and when I turn it on its drops to 5FPS and although my PC can handle all the graphics, I turn down all CPU intensive graphics and still it won't go more than 10FPS. Is there a way to make the G29 work with FFB without having a poor FPS ?

Thank you!

 

Normally this shouldn't happen. I'd try a clean reinstall of Logitech software.

 

It is up to date. I tried unistalling and reinstalling but it just won't get better FPS. And I always clear everything.

 

I use a G29 with ffb 100% and never experience that issue and my pc rig would be considered old at 9 years.

 

How come? What settings of graphics do you have?

 

It's not a matter of graphics settings if the game runs fine without FFB. Something's wrong but I'm not sure what can cause it.

 

Curtesy of ChatGPT......

1. Update or clean-reinstall Logitech G HUB, then check for a G29 firmware update. Logitech has shipped fixes for DirectInput crashes and wheel firmware updates in recent G HUB releases, so an old or corrupted install can absolutely cause weird FFB behaviour.
2. Disable the Windows “GameInput Service” as a test. There’s a known Windows issue where broken or duplicate GameInput installs can cause massive frame drops whenever a controller is active, and users with Logitech wheels have reported that disabling GameInput immediately restored normal FFB/control behaviour.
3. Test the wheel with G HUB running, but close everything else that hooks controllers or overlays: Steam Input for non-wheel devices, DS4Windows, Xbox accessories software, ReShade overlays, recording overlays, etc. If FFB is the trigger, another input layer fighting with the wheel is a strong possibility. That’s an inference from the symptom pattern, but it fits better than a rendering bottleneck.
4. Delete and recreate your RaceRoom wheel profile, then start with conservative FFB settings. Use the Logitech preset if available, then keep overall FFB strength moderate first and test. A bad profile usually won’t tank FPS by itself, but it can make a driver conflict show up consistently.
5. Try another USB port directly on the motherboard, not a front-panel port or hub, and disconnect other controllers while testing. This is basic isolation, but worth doing after the software checks.

 

Thanks, il try it.