Yeah no need to mention that
Is it generally recommended to have an in-game FFB smoothing greater than zero for rFactor 2? If using a reconstruction filter within True Drive between 3 and 5 for instance, I figured that would count as âsmoothingâ, so I initially thought that FFB smoothing should be at zero in-game, but I see a lot of people with SC2 wheelbases running FFB smoothing at 4 in-game, so I am curious if there is a generally recommended practice.
a smoothing value lower than 4, maximum 3 causes too much unwanted noise, and it is always suggested to use the lowest recon filter to avoid input delay.
Reconstruction Filter does not affect input delay (Simucube to PC) in any way.
thanks Mika good to know, I always thought it was the case, also heard a lot of people saying that many times.
Now those true drive settings was amazing ! From the vid. Did not try the json file tho.
@Mika You mentioned in the ACC thread that the DOR for rF2 should now be set at 1080 per the latest files they released. However, it appears that in the file the âSteering Wheel Maximum Rotation Defaultâ is 900, so does that mean we should set True Drive to 900? Sorry for a dumb question, I just wanted to make sure I understand things. Also, do you happen to know if Studio 397 used the default rF2 profile within True Drive to develop the latest JSON they released? Just curious. Thank you so much for your time.
you can set any value in TD and into the json file for dor, as long as they match. I have it at 1440, as suggested some time ago by S397.
Okay, I tried the JSON file and settings combo from the vid. And wow! It is really good! Am so happy with the settings now. Before wheel felt so limp at low speeds. Itâs more springy and you can feel the tire-angle way better IMO.
Happyness ffb check list
Iracing :check
Ac : check
Acc : check
RF2 :check
Raceroom :meh
@SuperMonaco_GP - regarding the DORâŚ
I had my first real shot at racing with my Pro and rf2 yesterday with some friends. We ended up with a track/car combo that Iâd had no chance to practice with (with this wheel - races them months ago on the T500RS though without problems)âŚ
The âvehicle setâ DOR is 576 degrees (Porsche 917K mod) and I found myself needing excessive wheel rotation - particularly in the tight hairpin at Rouen-les-Essarts with the TD (and JSON) set to 1440.
Second race, I tried setting TD to 576 - which was better, but very twitchy - presumably as Iâd not remembered to change the JSON to matchâŚ
So, should I (generally) be matching DOR in TD/JSON to whatever the âvehicle setâ value is? I never had to worry with the T500RS and could drive slidey historics and grippy moderns equally well without crazy steering inputsâŚ
Thanks!
you could either make multiple json profiles with different wheel rotation and just load them ingame (works even when loading inside the track) or fix your json settings to do that for you. read âSoftware Wheel Rotation Explainedâ here: https://www.studio-397.com/2018/11/roadmap-update-november-2018/
just remember in order for changes in the controller.json to save permanently , when you edit the file you have to keep the game and itâs launcher closed.
you need to also set steering range into json to 1440, otherwise you wonât have auto lock.
@Loukas_Bourdas - thanks for that, Iâll check my settings. I would probably have skipped over that announcement back in the day.
Right, on to the next noob questionâŚ
Iâm running @SuperMonaco_GPâs profile just now in TD. As Iâve said (I think) before, I most drive historics such as the Howstons, 917k etc. and these donât tend to generate huge FFB loads in cornering.
Consequently, I have been running the max torque and in-game FFB quite high to maximise general feel - but a consequence of this is that âspikyâ forces (e.g. certain kerbs, the cobbled section at Rouen-les-Essarts etc.) can be overwhelming and feel disproportionately strong.
I know there are JSON entries for kerb effects, running off track etc. - (seems like a daft question when I spell it out, butâŚ) should I be looking there first rather than touching TD, knocking them down a bit?
âŚitâs just that I know you can set the shape (sine, sawtooth etc.) of the effects in the JSON and also noticed specific filters for sine etc. in TD advanced settingsâŚ
Thanks once again.
I never use more than 0.45x on the ffb multiplier, with some cars even lower. whenever I start a new car, I always set the multiplier to 0.50 as starting point before the 1st drive.
if set near to 1.00, spykes and overall ffb forces would be way too hard.
so my advice is try to lower the multiplier to 0.50 and then move it from here.
Iâm a newbie here as well, and unfortunately i canât decipher @SuperMonaco_GP .ini file. Is there a way to make this file slightly more âidiot proofâ and easier to understand for me please?
I apologize for being rather useless at this kind of thing guys
hi, the only thing you should do with the .ini file is adapt the wheel force value to your base (17 for sport, 25 pro and 32 ultimate). dor and other stuff are already set into the file, you donât need to edit except for that value above. (dor into the file matches the one in the TD profile I shared, if you want you can edit the value but keep in mind .ini and TD dor must always match - and donât go lower than 900).
paste the file it into rf2/user data/controller and then once ingame load the file and map your inputs, thatâs it.
Donât forget that Device names also have to change in the ini according to their base.
âDevice Name 1â:âSimuCUBE 2 Sport=#16d00d61â,
âDevice Name 1â:âSimuCUBE 2 Pro=#16d00d60â,
âDevice Name 1â:âSimuCUBE 2 Ultimate=#16d00d5fâ,
thank you kindly sir, imported your settings in the TDâs import feature and adjusted the force value for my PRO and wow the difference to what i was using is absolute night and day
Wonderful settings especially when you tinker with your aforementioned FFB multiplier, i find it most comfortable between the 0.40 to 0.50 region
Hi, where is the [rF2_2020.09.05_18.15.ini.txt] located in the rfactory2 folder?