SC2 Pro Lost (almost) all its force

Yes, I do have it opened.

Totally, @EsxPaul Make sense. I do not have another pc, because I work only with Macbook. Maybe I will ask a friend to check it out.

Now we come closer.
You are running the Simucube on a Macbook with Bootcamp or something?

1 Like

No no! Im running in a separate PC, just for simracing :slight_smile:

All good. :slight_smile:
It sounded like this :rofl:

haha thats my bad :joy:

We would first have to identify this being a software issue in the wheel base, and we typically do not take devices with software issues to service, as how would we know what is wrong?

It doesn’t matter. I have been using SC2 from alpha/beta days and never had issues with TD open or closed. Not sure where the guys get this notion that it must be one or other, or even things started in sequence.

Nonsense ideas, tbh. Having been using it in all sorts of modes, never had issues in this respect.

OP’s problem is something else like Mika says.

@Mika Does it makes sense for him to sent device diag report to you?

1 Like

I do not think that the the debug log that can be downloaded from device contains anything relevant on this. Same answer regarding the debug log that True Drive application generates.

One thing that I would want to check, is that the maximum motor current parameter, that is visible in True Drive on one of the tabs, shows the expected amount of current. For Pro, it should be 22.5 A if I remember correctly.

I’ll put this here for reference.

Current

Ha, all good. It almost sounds like there is one parameter, ie motor current or %torque or something set to zero after restart, when he next opens device and adjust slider and safe, some value is written.
But like you say, almost impossible scenario.

I just had the same problem, that after loading into the iRacing Sim the force feedback was gone.

E-stop on and off does not work.
Turning the force feedback off and on in iRacing did work though.
Had the problem today for the first time.
Maybe something was changed in iRacing since the last patch.

Hey, I want to reactivate this thread here. It has been some time (which I’ve been waiting for a new firmware release or something), but the issue still continues for me. Since I don’t see anyone bringing this same issue I’m assuming something maybe be wrong with my unit.

Just a little background. If I turn on my pc, my base and enter iracing there’s no feedback. I feel just a little bit (almost nothing) until I enter true drive, edit the force feedback (lets say from 100% to 99%) then its live again and everything works fine. I’ve been doing that for around 3 months since I wrote here for the first time. EVERY TIME haha it requires some patience and I was ok doing it, but I really want to fix this.

Anyway, if anyone wants to go in the thread and read, but I basically tried everything… Some new Iracing releases happened, some other computers formatting later. That is the only thing that made it work (what I just wrote).

Just out of curiosity.
I always have my True Drive software running because it is required for the base to activate.

Only then do I start the sim of my choice.

1 Like

Yeah, I’ve tried doing things in all orders…

Base On > Open TD > Join Iracing
Open TD > Base On > Join Iracing

Everything is dead until I open my TD profile, change the strength settings and save again.

That is indeed strange.

Have you reset the default profile to the device? It would isolate the cause if that helps.

If you are saying the button (Reset FFB Default State) in the Advanced Info Tab in True Drive, I already tried that, @Mika.

I also just tried creating a new profile from scratch. It doesnt work until I get in the profile and edit the strength and save it again. The wheel move 1 or 2 degress when I do that, so it seems it was not receiving any data and then when I do that it lives again.

No, I meant “save this as default” which is available in the paddock profile via the menu, or the offline profile list as well.

wow! i think that solved the issue, @Mika I will do some more tests later today, but at first I restarted my computer and it worked without me having to edit the ffb strength.

Thanks!