You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that, in iRacing, it's necessary to define Per car overrides for each car to get the proper shift point rpm. Because the iRacing SDK does not provide accurate shift points; the data provided in the raw values is quite off compared to the behavior of the in-game steering wheel (sometime off by 1000 rpm!)
And because this is an elaborate task to figure out the correct rpm values for each gear for each car, it would be nice if we could export our values to a json file and share it with the community so they can simply import the settings.
Potential solution: Two simple Import / Export buttons (next to "Forget all cars" button) that would read / write a json file with all the per car overrides settings.
I don't think there's currently a workaround.
The text was updated successfully, but these errors were encountered:
Hi you can get all the files at once by copying the files from C:\Program Files (x86)\SimHub\PluginsData{gamename}\Cars (ie C:\Program Files (x86)\SimHub\PluginsData\AssettoCorsaCompetizione\Cars) to make it easy to merge etc ...there is one file per car.
The problem is that, in iRacing, it's necessary to define Per car overrides for each car to get the proper shift point rpm. Because the iRacing SDK does not provide accurate shift points; the data provided in the raw values is quite off compared to the behavior of the in-game steering wheel (sometime off by 1000 rpm!)
And because this is an elaborate task to figure out the correct rpm values for each gear for each car, it would be nice if we could export our values to a json file and share it with the community so they can simply import the settings.
Potential solution: Two simple Import / Export buttons (next to "Forget all cars" button) that would read / write a json file with all the per car overrides settings.
I don't think there's currently a workaround.
The text was updated successfully, but these errors were encountered: