When we appear on the track and turn on MFD, we can adjust the brake and differential settings NORMALLY (i.e. decrease or increase from the value we set in the garage). But when we appear on the track and do NOT turn on MDF, but immediately press the mapped buttons for the brake and differential settings (increase or decrease), for example, the brake balance setting jumps to the minimum value of 50% (even though a different value was set in the garage) and we adjust from this value. It should work as in the first case. Adjustment should start from the previously set value. The same with the differential. In previous F1 games it was just as BAD.
Ideas
4 Comments
Yup - been that way for a long time. Just part of the large but annoying collection of minor bugs and design flaws that gets copied over each time and will never get fixed because never enough resources. The new features take priority. But the base is stale and needs a rewrite both functionaly and aesthetically
But this year is an improvement over 24 so thx for that
If you have a shortcut on rotary encoders or something similar to adjust +/- for that, remove it. Then test whether the bug still occurs. If it doesn’t, try assigning it to a different encoder/buttons or try it with the same. That worked last time
If I remove the shortcut, I won't be able to check how the shortcut works. And I have several control profiles and I use different buttons and knobs. It doesn't matter. The problem is that the FIRST time I use the shortcut, it doesn't work properly. The next time I use the shortcut, it works fine. The solution is to press MDF during the FIRST adjustment and then adjust. And I want the shortcut to work properly right away. This is useful in online races where you can't change the settings. Then you can only change the brake and differential on the track while driving.
yep, this bug exists since f1 2020, and it has been reported so many times, and it's still ignored. I reported this bug since f1 2020 to f1 23. Nobody even replied to my reports, so I gave up, and stopped reporting this issue.
