FuzzyFassbender
Registered
Thanks @The Iron Wolf. As for temp suggestions, I haven't had enough time with the Radical to come up with good thresholds. The CC values seemed incorrect as originally stated hence why I've gone down this path of testing/overriding the CC default temps.@FuzzyFassbender as I said earlier I'll check why user defined class doesn't work, but I will also add Radicals to our builtin classes. If you have temperature range/brake type suggestions, let me know, otherwise I'll treat them as prototypes. Overrides of builtin classes works for sure, so people will be able to override temps to their tastes.
Question, do tire temp thresholds need to be under a tire type structure as in the json example below (AC)?
"acTyreTypeData": {
"Trofeo M Slicks (M)": {
"maxColdTyreTemp": 75,
"maxWarmTyreTemp": 90,
"maxHotTyreTemp": 120
},
"Trofeo H Slicks (H)": {
"maxColdTyreTemp": 75,
"maxWarmTyreTemp": 100,
"maxHotTyreTemp": 140
}
Or, can they be as below - if there is only a single tire choice:
{
"carClassEnum": "Radical SR3 RSX",
"rf2ClassNames": ["Radical SR3 RSX"],
"maxSafeWaterTemp": 105,
"maxSafeOilTemp": 140,
"maxColdTyreTemp": 75,
"maxWarmTyreTemp": 90,
"maxHotTyreTemp": 120,
"timesInHundredths": true,
"enabledMessageTypes": "ALL",
},
Also, I "assume" that if the CC hot "Celsius" temp is 120, but I'm using Fahrenheit in rF2, I will hear the warning when I see 248 degrees F, correct?