Losing FFB in game

[BackwoodsNC]

Greetings, I’m losing force feedback during a racing session. I only use this for iracing, and it happens at various times.

It has happened four times in a race and twice going from qualifying to race. During the race the force feedback goes away completely, but the steering input still works. No damping effects, the wheel is just dead. To correct this i have to restart the wheel and FFB returns.

Things I have done to remedy this issue. I have replaced the usb cable, changed the usb ports on the pc and checked the power (source 120volts) coming from the outlet. Oh, i also updated to the lastest software and firmware.

Hardware: Simucube 2 sport

Here is a copy of the event log while I lost FFB, hope it helps.

Event log:
Timestamp : 2033

Wireless: State change : 2

Simucube Boot : 1

Simucube Boot : 0

Simucube Boot : 18

Flash settings data loaded : 0

First-time drive initialization : 0

Initial config has been previously performed. Initializing Drive. : 0

State: Initializing Drive : 0

Drive Firmware update : 0

Drive firmware updated successfully : 0

Timestamp : 3792

Wireless: State change : 3

Command: Request profile number : 0

Command: Request profile name for profile : 0

Command: Request profile byte data for profile : 0

Command: Request profile number : 1

Command: Request profile name for profile : 1

Command: Request profile byte data for profile : 1

Command: Request hardware settings : 0

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 0

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 1

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 2

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 3

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 4

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 5

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 6

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 7

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 8

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 9

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 10

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 11

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 12

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 13

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 14

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 15

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 16

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 17

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 18

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 19

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 20

Command: Set calibrated analog axis mode : 0

Drive init stage 1, position : 1550450

Read MMC value from Drive : 15500

Read Motor Resistance value from Drive : 1200

Read CPR from Drive : 4194304

Read Drive Version ID from drive : 40000

Simucube 2 Serial Number : 449

SM Watchdog disabled successfully : 0

Successfully applied DRC data to Drive : 0

Read MMC value from Drive : 15500

Read Motor Resistance value from Drive : 1200

Read CPR from Drive : 4194304

Read Drive Version ID from drive : 40000

Simucube 2 Serial Number : 449

Waiting for servo to be ready : 0

Drive init stage 3, position after faults cleared : 1263097

Drive init stage 4, phasing, current position : 1261349

Drive init stage 4, phasing, current position : 1322606

Drive init stage 4, phasing, current position : 1474363

Drive init stage 4, phasing, current position : 1726892

Drive init stage 4, phasing, current position : 1600697

Drive init stage 4, phasing, current position : 1381603

Drive init stage 4, phasing, current position : 1701172

Drive init stage 4, phasing, current position : 1602052

Drive init stage 4, phasing, current position : 1461718

Drive init stage 4, phasing, current position : 1540207

Drive init stage 4, phasing, current position : 1539784

Drive init stage 4, phasing, current position : 1538463

Drive init stage 4, phasing, current position : 1552913

Drive init stage 4, phasing, current position : 1550536

Drive init stage 4, phasing, current position : 1548048

State: Drive initialization was successful : 0

State: Set baudrate : 0

SM Watchdog enabled successfully : 0

SMBus baudrate initialized successfully : 4500000

State: Before operational - calculating new constant values : 0

State: Operational : 0

event 260 : 0

event 261 : 0

event 262 : 0

Command: Event log download request : 0

[Mika]

Event log does not show anything other than that the device has just restarted. Is there any fault codes visible in the True Drive when you loose FFB?

[phillip.vanrensburg]

Is this when you first enter the sim, or after a while whilst driving?

[Mika]

It can also be seen that the wheel turned while the device restarted itself. Does your wheel somehow move left/right when you normally start the system? Simucube 2 should not be doing that.

[BackwoodsNC]

No errors are showing in true drive that I have seen.

When I enter a session it works, seems to only loose FFB under usage.

Yes, I turned the wheel during the reboot session. I was on pit road under caution during a official race session and rebooted. Worked fine the rest of the race.

[phillip.vanrensburg]

Please post screenshots of your settings in True Drive. I suspect some hands-off sensitivity setting issue.

[Mika]

It is also possible that, for some reason, the PSU is somehow acting strangely and the overcurrent protection trips. Would be the first one on the Sport model.

How high FFB settings are you using?

[BackwoodsNC]

True Drive is set to 100% (17.1Nm). Iracing strength is set to 7.1 and wheel force is set to 17 Nm.

I am going to run some indy 500 events this weekend and report if I have more issues.

[phillip.vanrensburg]

Click on the text in iracing GUI, on the ‘strength’ and it should change to NM. What is it (max force) set at then in NM?

[BackwoodsNC]

displayLinearInNm:1 that is the setting that needs to be changed. After changing that it reads 33Nm at my normal levels.

[phillip.vanrensburg]

You don’t have to manually edit the ini file anymore. Do like I say above, it does the same thing, just quicker and easier, no need to restart iRacing

[phillip.vanrensburg]

Anyway, those settings are reasonable, the unit should perform without any disconnects et al. You still have not posted hands-off detection etc settings, please show a screenshot of those

[BackwoodsNC]

I’ve always ran 99% of the settings at stock. Never really felt like i needed to change anything, always felt good from the start.

Thanks again for the help!!!

[BackwoodsNC]

I figured out what was causing the issue. If I click on overwolf (teamspeak addon) while in game the force feedback goes away then. So, that’s great news! This whole time I was worried that i had a hardware issue.

Again, thanks for all the help!!!

[Raimond]

Yeah, Overwolf did that to me as well, right on the start grid for a league race
I use another much simpler app now, TSnotifier
Works like a charm and has better config options too IMO

[Mika]

Does that software cause similar issue in other games?

[Raimond]

It apparently causes problems for different kinds of wheels in different kinds of games/sims, so nothing SC2 specific.