-
Did you have rF2 closed when you changed steering wheel maximum rotation default to 1440?
-
Did you change this setting in the Controller.JSON file in the UserData\player folder, as per the instructions, or in the OSW_Simucube profile file in the UserData\Controllers folder?
Yeah rF2 was closed anytime I made a change to the json file. The settings I changed are in the controller.json file, I never looked at the other one.
Somehow youāve got to get āsteering wheel maximum rotation defaultā to stick at 1440.
-
Are you using the new OSW_Simucube profile which you will see in the UserData\Controllers folder or the profile you had been using before this update?
-
Have you saved your profile in game after changing the Controller.JSON? That part of the in game screen on your screenshot above is missing.
Iām about to delete the current in-game profile and start over. Nothing else is fixing it.
Edit: Still doing the same thing. I have no idea WTF is going on.
ShouldnĀ“t be set āSteering Wheel Maximum Rotation from Driverā to false?
Yes, I think so. There is a proprietary API / USB command that a game can use to get the maximum steering angle from the driver. This is what Logitech, TM and others are using, I believe. Having searched a full day for any documentation for this, I didnāt find any, so it really must be secret.
No. Quote from Update, "If your wheel actually does support us reading the maximum rotation, you can alternatively set āSteering Wheel Maximum Rotation from Driverā to ātrueā so we will read whatever you set from the driver. We do recommend setting it to the maximum value in the driver, as we can only make the rotation less in software, not more. "
I have it set to true and all works fine. Maybe makes no difference whether true or false for SimuCUBE.
Its going to be something small and obvious.
Have you saved your new profile in the SimuCUBE firmware? Is it green or red at the bottom of the profile page?
Have you saved your profile ingame? Does it say ā(modified)ā after the name of your profile in rF2 Controls? If so, you need to save it.
Below are screenshots of both my profile JSON in UserData\Controllers (I called it OSW_Simucube1 so I could keep the default file vanilla) and my Controller.JSON in UserData\player. They are both identical as far as I can see.
āSteering Wheel Rangeā is 720 because that was the last car I tested. āSteering Wheel Maximum Rotation Defaultā stays 1440 and does not revert back to an earlier setting.
I was under the impression that āSteering Wheel Rangeā is tied to the visual-wheel in-game. I need to take a closer look at that and see if the visual wheel matches as it should.
Are you certain that you are altering the correct file? (Admin rights make a difference?)
You need to edit the custom (saved / named) json-file, not the template file (named ācontroller.jsonā)
The wording can be a bit confusing in the Roadmap the way it is written.
Both of my files look identical to yours minus one thing; āSteering Wheel Rangeā in my OSW_Simucube1.json is 540 but in the controller.json it is 400 from the last car I drove. Shouldnāt those be the same? This is driving me crazy.
The default setting is staying at 1440 in both files.
Maybe thatās what Iām screwing up.
Okay, I have confirmed that my ācontroller.jsonā does not get altered (at least not out of game).
I changed the parameters as shown below and have 100% confirmed that the Soft-lock feature works and the visual wheel and actual steering wheel match perfectly to the per-car soft-lock rotation.
I changed both the actual controller.json (as itās named in the player folder) and the one I created thatās named OSW_Simucube1. Is that where Iāve screwed up? Mine still doesnāt work correctly.
I didnāt manually change anything in the ācontroller.jsonā file at all but, hereās how it reads now:
āSteering Wheel Maximum Rotation Defaultā:1440,
āSteering Wheel Maximum Rotation Default#ā:āDefault maximum wheel range to use when not read from driver, from 40 to 1440 degreesā,
āSteering Wheel Maximum Rotation from Driverā:false,
āSteering Wheel Maximum Rotation from Driver#ā:āWhether to read the steering wheel rotation from the wheel driver, if possibleā,
āSteering Wheel Rangeā:540,
āSteering Wheel Range#ā:āDegrees of steering wheel rotation, both visual and physical (if available)ā,
āSteering Wheel Software Rotationā:true,
It appears this may be the active file, not a generic reference or template file. It doesnāt match my modified json exactly but, as I said, itās all working here.
Well thereās my problem so now it works! I changed the āSteering Wheel Max Rotation from Driverā to true in that json and that was the wrong one to change. I took what they posted literally and didnāt realize I wasnāt supposed to change that exact one. Thanks everyone for the help!
Another question. Noticed all the FFB for each car is now reset back to 1.00 as a default but even when turning it down almost 50% on a couple cars the forces are still much higher than before this update. Are there some more changes I need to make in any files for a DD wheel that may have defaulted back?
On simucube profile i set the overall strength to 45%, DirectInput damping 45% and DirectInput spring 45%.
They did the OSWpreset.json ready to use those DI effects as they are activated on their .json.
I have 20Nm motor , y guess the 30Nm one needs 30%,30%,30% values.
i have to say since the changes using the OSW profile ive been running the mclarens mp4-8 and 13 and even the 23 and i have to say its transformed the feel of the OSW for me now it feels fantastic.
All i did was what was said above i set 1440 in simucube and made sure same was showing in those 2 files and made sure wheel rotation set to true. For me and i could be nuts but it feels great now. Maybe its just these cars i dont know but im really digging it.
Having the proper steer-lock can help the FFB sit in itās pocket for each car. Although, having an extra dose of placebo may help a bit too. 
Either way, itās nice to have things working as intended now.
If you are now using the OSW_Simucube profile that Studio-397 created for this update, you will probably find that there are quite a few FFB settings which are different from those in the profile you were using previously.