Need some real help / insight on a Simucube 3 Pro issue – not a basic setup problem
I just switched from Simagic to Simucube 3 Pro (Link wireless wheel) and I’m running into something that I cannot pin down, and it’s honestly making the system unusable right now.
System:
- 5090 (liquid cooled)
- Triple 4K (11520x2160)
- everything clean, no interference, already stripped everything down to test
What’s happening:
- FFB works at first (feels great actually)
- Then randomly cuts out completely (wheel goes dead, zero resistance)
- iRacing F bar sometimes spikes red, but NOT always when it fails
- Sometimes it runs half a lap, sometimes less
- When it fails, I usually have to restart the base or even the whole PC to get it back
Other weird behavior:
- Very slight monitor “shading/flicker” every few minutes (subtle but noticeable)
- Seems like some kind of system/driver interaction when FFB events happen
- Not something I ever saw with Simagic
Important:
- I had FFB adjustment bound (rotary/keys) and that DEFINITELY caused instant failure/spikes, so that’s now removed
- Even with no bindings, it still eventually cuts out
- This is not a constant clipping issue — it can fail without any obvious spike
What I’ve already tried:
- Clean iRacing FFB setup (25 Nm, ~6 strength, no auto)
- Removed all FFB adjustment bindings
- Power cycles, restarts, fresh sessions
- Simplified rig (even unplugged extras to rule out interference)
At this point I’m trying to figure out:
Is this:
- Simucube Link (wireless) dropping / faulting?
- iRacing FFB recalculation bug?
- Driver / GPU interaction (5090 + high load)?
- Something known with SC3 Pro protection behavior?
Because right now it feels like something is tripping the base into a shutdown state, but not always from obvious clipping.
If anyone has seen anything like this or has SC3 Pro + iRacing experience at high resolution setups, I’d really appreciate direction.
Not looking for generic “turn strength down” advice — I’ve already stabilized that side.
Just trying to figure out what’s actually causing the shutdown.
Thanks.