I will test for you, I like raw, so maybe I will be happy.
I use 2022.5
1 Like
Has anyone experienced an āError: 140404 Overvoltageā while running rfactor 2? I did today. First time it has happened (never with any other game). I reset using the e-stop and it seems to be working, but I havenāt tried running rfactor 2 again. Any insight appreciated.
-Monti
Canāt be sure this this is exactly what happened in your case but this fault can appear if you happen to have been turning the wheel as the servo was booting up.
1 Like
Thanks Paul,
That may be the case. I wasnāt paying too much attention until it wasnāt working. It hasnāt happened since, so hopefully that was the answer.
-Monti
1 Like
rFactor 2 has to be one of the most frustrating games Iāve ever used. It just hates the user I think.
Anyway, in the process of trying to get it to work today for the first time in a couple of months (After switching back to VR from triples), I had a bunch of issues trying to load up a server, and ended up needing to delete a bunch of things and switch versions and some other stuff. It was a long ordeal, as usual, because rFactor 2 is torture sometimes.
Anyway, somewhere in that process my force feedback has become super awful and grainy, or notchy. It almost feels like thereās velcro in the wheel? or like you can feel the individual magnets or something?
I found this thread in a google search and I tried some different json files I found further back and Iāve had to try to use those and Iāve remapped my controls and recalibrated these things enough times now Iām about to pull my hair out, because itās not making any difference at all. is there a place to find the most up to date one? Or is there a known cause for this issue that I can address?
I dont have this in any of my other games, and I didnāt have it in rF2 at all until today. Just feeling confused and defeated. Just frustrating when you know it worked fine before and now nothing you do can solve it.
3 Likes
When I last encountered ffb issues or inconsistencies in rF2, hereās what I did.
- Delete the SimuCube2 ffb-preset and run Steam rF2 file verification to download a fresh version.
- Move, delete or rename your current custom controller profile.
- Run rF2 and load the SimuCube2 controller preset.
- Setup your controller axis and buttons and be sure to save (or export) your new controller preset using a unique name.
- Exit / Restart rF2 and be sure your newly created controller profile is loaded.
- Test the ffb to see if improved.
4 Likes
with a very high FFB multiplier (more than 35%) and TD panel at 100% with a SC2 pro, no way to reduce the bumps/kerbs harschnessā¦itās always too much strong.
The only fix could be if the s397 devs add a special FFB filter.
There are some others games which use better a high FFBā¦without too much harschness like rF2.
1 Like
I see it the same way: there is stuff you canāt really use all torque: dirt rally, r2F, F1 titles are also something I donāt use full torque.
I struggled for quite some time, what is better: TD high/in-game low, TD low/in-game high.
I definitely prefer TD high and in-game low (if high high is not practicable). I tried it the other way aswell. But IMO to have TD at the highest torque level is just better, if I donāt have to make compromises with damping, friction and inertia. I just donāt like what their results are, or my steering wheels just donāt need them
I think differences between the high-TD / Low game-ffb and inverse approach, is largely placebo. Iāve tried both in various titles and canāt detect any significant difference in feel (so long as clipping is not a factor).
Where Low-TD approach is advantageous is with safety. People may falsely believe that errant spikes in ffb signal are limited to the game-ffb strength level but, I donāt think that is accurate. The ultimate force limiter is dictated by the SC2 output setting.
I find a good balance of Friction & Damping solves any issues related to strong bump forces, oscillation, steering instability, torque-steer, etc. I also think the overall steering behavior is more realistic as a result but, then again, I donāt have RL experience driving race cars. 
1 Like
Can we all agree that rf2 is broken like too much kerb effect with a very high ffb??
1 Like
What do you consider very high ffb?
At the ffb levels I run, curbs are certainly no issue at all in rF2.
Have you tried using Slew Rate? I think that may be useful for reducing such effects.
Damping makes the wheel feel heavier to move and helps when you steer too much.
Friction is slowing down the wheel movements around the shaft. It helps preventing the wheel to start oscillating. It also makes it easier when you facing problems to hold a steady position
That said my conclusion is that none of them were made for the purpose you actually use them.
RF2, with its harshness, is the perfect simulation for a thing called static force reduction. This setting let you maintain the FFB strong without experiencing āshock momentsā were a spike starts scarying you.
To keep it overall safe you can, of course, limit slew rate. Itās your life insurance in massive crashes.
I would consider to stop using damping and friction (especially for the purpose you are using it).
The source of FFB is the simulation. All simulations I know offer the possibility to limit the strength. Why? You need a certain amount of FFB coming from the physics, tyres Aso. If you have in-game FFB at 0, that means FFB is off. You can add 100 torque from TD and the result is still O. Best approach is to get the right dosis from the simulation and then gain from the Simucube. Seeing it in this light itās not placebo.
I donāt have any experience with RF2, apart from peeking in a few times. I think @Tony is right. There maybe is a way to find good or very good settings. It will be very time intensive, Iām afraid.
hi,
whats about this .json(?) file, i remember to read about changes there to tone those harsh bumbs a bit downā¦ i,m confused, is this working,or not?
Iāve heard reports (in rF2 forums) of recent changes to how ffb and controller json interact but, I donāt recall any specific information. It suggested that certain file parameters may be disabled or locked.
Iām well aware of how Friction and Damping work but, thanks anyway.
My methodology works great for me. Guess Iām just lucky.
Regarding High-TD strength / Low-game strength: I used 100% TD / 50% Game vs 50% TD / 100% game strength in my testing. To me, the results felt the same.
1 Like
If I use ACC with 100% FFB and 50 of the Simucube, wonāt this lead to clipping, or at least increase the risk to experience clipping?
And 50% FFB from ACC with 100% from TD, isnāt this the opposite?
By setting TD to half of the force the maximum torque will be less than 9Nm for my Sport, no matter how strong the incoming FFB signal is. Everything above will cause clipping. If I have TD at 17.7Nm, then clipping occurs not at 7.9 but at 17.7 Nm. I have a problem in seeing this as equal. Is there anything I am missing?
I believe itās accurate to say that 100% in TD / 50% in game eliminates any chance of signal clipping. The inverse settings will almost certainly produce clipping, at least in certain cases. The 50% figure is an example case.
Of course, we need to take into account game output signal clipping, either by monitoring via app or reducing the game-ffb output to lower levels. I generally start by using something like 60% / 60% (TD / Game-ffb) but, make some adjustment from there.
Iām not convinced that 100% in TD brings any benefit to the quality of the ffb beyond addressing clipping but, there are other ways to keep that in check, while also reducing the risk factor. Of course, if one wants to maximize forces to the limits, then 100% TD will have to do.
I just prefer a more balanced approach for risk / reward, and Iām not that strong. 
I found that TrueDrive Clipping Notification is very useful for me to achieve the right balance between ingame optimal force and TD forces.
The SC2 beeps when 100% force is sent by the Game so I try to minimize beeps lowering ingame FFB and then adjust TD force to my liking
Im Happy when SC2 beeps on Hi load corners but only when touching kerbs or bumps
Clipping is a phenomena that occurs when game sends constant 100% force. It can occur when the strength from device driver software is set at 100% or at 10%. I can happily set my Simucube to not clip at all at 10% force - clipping is controlled by in-game settings.
2 Likes
Now that you say it, it makes sense. Why else would Assetto Corsa have an in-game app named FFBCllip.
And if TD or the Simucube could somehow influence clipping, there should also be a corresponding setting. I should really start thinking before I write anything.