@rowland

"Weight" is a calculated force that acts against movement of the wheel in any direction. It seeks to simulate the masses that would exist in the steering system of a real-world car. Consequently the optimal value will differ from car to car. Ideally, you want just enough "Weight" applied that you can steer with a fingertip down a long straight but not so much that you can hands-off completely.

"Torque" is the value you adjust in concert with iRacing's Force settings and ideally should not be set at values that cause over-exertion.

In iRacing (or any other sim), the "Telemetry" tab is your friend for identifying clipping. FFB sessions in excess of 60 seconds are displayed in real-time with the last 4 sessions stored as historical data.

The basic principle is to run a representative lap with "Torque" set to a comfortable level. 8-10Nm is a good starting point. Use the auto setting in iRacing to get into the Max Force ballpark and run another representative lap.
Check the "Telemetry" tab for clipping in the current session. If your clipping % is higher than 0.00%, raise the Nm value to reduce the gain from the sim and raise the "Torque" value to compensate.
Ensure the FFB session is ended by disabling FFB within iRacing then re-enabling it.
Iteratively run representative laps till "Telemetry" shows 0.00% clipping
Adjust the "Weight" if required to reflect the current settings
Finally switch to the "Settings" tab and reduce the "Controller Mode" iteratively until you feel no additional benefit (the lower your "Weight" values, the lower you can run Mode values without motor noise).

@byagm

The fixes are incorporated in v21.07.01 which is being released to "Alpha" on Monday 8th November

@daytona-675

Thanks for confirming "Game Mode" better supports WRC 9 & 10. We'll update the Sim Support Matrix to reflect.

This solution has stopped working for me. I haven't loaded RBR since I first used the patch and got the FFB working a few days ago, but I can't get FFB working now, no matter what I try. I haven't changed anything as far as I can tell.

If anyone else comes up with another answer, I'd be very interested.

@whoolkan

THANK YOU SOOOOO MUCH! 👍 👍 👍 👍 👍 👍 👍

It worked a treat and now for the first time since release I have FFB on FH5!

@byagm

Not sure I've tried it since the firmware has had game mode, will have to try again. I posted this one last year

@discopooh

Thanks for confirming. Hopefully this will be the case going forward and the annual patching will no longer be needed

@ochso

Many thanks for the confirmation. I''ll get the Sim Support matrix updated to reflect

@jeanv78

Generally, you would choose Sim Mode unless the title in question requires Game Mode to function.
The Presets Installer creates both entries and leaves the choice to you.

@sim-plicity-dev I'll try these out thank you.

Hi,

though I'm quite late to the party, I might still help. 🙂
I got my SW8C+ running with DR2 using this guide: https://cdn.cloudflare.steamstatic.com/steam/apps/690790/manuals/DR2_Multi_Input_Device_Configuration.pdf

My device ID is 028A1CBE-0000-0000-0000-504944564944

@Sim-plicity-Dev Thanks for confirming.

@xB

Just had a quick play with KartKraft & would say it's not a hands-off-the-wheel type of sim.

With this in mind, it should be possible to get a realistic/useable feel without overdamping the wheel.

Can you post a screenshot of your Input Bindings screen within KartKraft as well as your Settings, Advanced and Telemetry tabs from within the SW25 desktop app

@xB Most of the steps occur outside our software and are down to whatever tool or utility you use to launch your sim environment.
The command line switch above allows 3rd party utilities to load a previously saved profile without the user having to "mouse navigate" as you would normally do.
You can thus customise the wheelbase's behaviour to suit different sims/environments without having to manually select the profiles.
Where the command is entered would be dictated by the utility in use.

@loermansa Sorry for the late reply.

Thank you. Much appreciated

Alas I cant really help you much further. The game for me is just too far down the path of the console port to hold my enthusiasm for it.. Wheels feel very much an add on after the fact.

Pure conjecture on my part but The polling rate (in game ) of the USB control device does seem somewhat lower so the wheel may well not being fed the input it desires.

Have you tried running the game with the wheel in "game mode" ?

That may well dumb down the wheel enough to hold off the feeling you have. ( like the older WRC titles) You will have to reconfigure the wheel in game as it is technically seen as a another USB wheel.

Good luck

@loermansa

The windows USB disconnect & reconnect you hear is the wheelbase attempting to recover from a monitored instability on the USB bus.

This is programmed into the firmware if a certain % of heartbeats between the PC & wheelbase fail within a defined period. It seeks to highlight USB issues rather than being the cause.

Can you post screenshots of your Telemetry page whilst in AMS2. One screenshot after you exit the garage and another after the issue occurs.

Do not switch USB modes before taking the 2nd screenshot.

Further question, when the hard left or right occurs, does the wheel remain at full power (pushing against the endstops) after the disconnect/reconnect?