I just deleted all in my SimBin…/UserData/ControlSet folder. Then started R3E, turned the SC2 on, chose the default Simucube profile, exited game. Same issue as I describe above.
I’ll try deleting my SC2 profiles next.
It cannot have anything to do with FFB profiles in Simucube.
It is to do with game leaving some FFB effects with strange parameters running on exit.
I haven’t managed to repeat it yet.
Makes sense. Sector3 think it’s a simucube issue. See their discord - help channel.
I can reproduce this consistently if you and/or Sector3 want me to do some debugging.
Hi Mika, I thought earlier you were mentioning this is related to bump stop effect as R3E sends bumpstop range values to SC2 based on the car in use.
Yeah, it was just a guess with no means to get to see it happening.
When it happens, can you guys check if the debug value is at 1, 0 or -1 on the last tab in True Drive, and also if there are any created FFB effects running there?
One post above the one I linked in last reply
Was that log before or after you restarted the servo to fix it? The log is cleared on device restart…
Before, taken at the same time as TD screenshot.
OK.
I still cannot seem to be able to repeat it.
What Simbin? I can’t find any simbin folders on my PC. The game is not developed by Simbin.
Looks like I was able to repeat it now
- turn off simucube
- start r3e to menu
- turn on simucube
- exit game
- spin
Investigating it.
warning: I would not recommend anyone to try this with high torque mode on 
3 Likes
RaceRoom Racing Experience is a free-to-play racing simulator for Microsoft Windows, developed by Sector3 Studios, (formerly known as SimBin Studios) and published by RaceRoom Entertainment AG.
What a screen, holly shit:100:
well technically it is, sector3 was part of simbin. doc folder structure is still doc/my games/simbin
hi, what changes from eg. SC2 Pro Alex GTE and LMP now that all previous ffb parameters have been erased? I assume only gain and max force, or whatever is called now
Not sure what you mean. But that screenshot is after I put all the .rcs files back. Each profile probably has identical FFB - they’re just different control mappings for my different wheels.
1 Like
OK, so this is what happens:
On Raceroom exit, the game sends two packets to Simucube:
- packet to set steering range to 0 degrees (!)
and then right at the next possible slot in USB communications, - packet to set the steering range to follow the one set in user’s Simucube profile.
This 1) causes some… shall I say it, strange calculations to happen in the firmware, and endstops activates fully on. And, some things that try to calculate speed of the wheel (needed for Damping) do not seem to recover at point 2).
So, it is a firmware issue AND a game bug, and we are fixing it from the firmware side.
11 Likes
Fix is out for Simucube 1.
Simucube 2 release branch is in a bit of a state right now with some unfinished things, so that will be in for the next release.
5 Likes
Awesome, thanks a lot Mika, one less issue to worry about when playing R3E! 
2 Likes
This is a strange problem that I don’t remember ever having before. Just fired the game up for the first time in months and it seems like the game is controlling the bumpstop range on the SC2.
I wouldn’t mind that so much if it was doing it in a way that makes sense. For example, it’s auto setting the bumpstops so I only get 180 degrees total DOR for the Corvette GT3 even though it shows something like 480 in the setup tab.
I switched to the 911 GTE and it’s sets somewhere around 220 degrees total DOR.
I alt tabbed into TD and I noticed “Angle set by game” which I don’t remember seeing before
Any ideas what might be happening?