[Feature/Sugestion] "Auto" tyre and breake heatmaps
Sasker opened this issue · comments
How about adding a "heatmap_auto" option to the heatmap related widgets to try to automatically set heatmaps for the class car?
I think that could be a useful addition, because changing the heatmap option every time you race another mod can be forgettable and slow.
I was thinking of extending the classes.json functionality to add autoheatmap and autobrakemap to each known class and then use this (if available) to change the heatmap dynamically.
For example, from this:
"LMP1": { "LMP1": "#FF00AA" }, "GT3": { "GT3": "#229900" },
to this:
"LMP1": { "LMP1": { "color":"#FF00AA", "autotyreheatmap":"tyre_optimal_90", "autobrakemap":"brake_optimal_700" } }, "GT3": { "GT3": { "color":"#229900", "autotyreheatmap":"tyre_optimal_70", "autobrakemap":"brake_optimal_400" } },
Yes, I know, this will only be useful if we add the most popular mods and theoretical heatmaps.
I can code it in my fork if you believe in it.
(Sorry for my english)
Thank you for your suggestion.
However there is already the preset manager where you can duplicate a single preset (by right click on a preset in preset list to bring up context menu) with preferred overlay setting to create multiple copies and assign different heatmaps to them. And this way you can name preset differently for different cars/events/race types as you wish, which is more simple & flexible.
So currently there is no reason to add additional auto selection function to heatmap or other similar stuff.
Additional note:
Auto-selection system is not reliable against situations like user typo, mods updates or changes, or receiving potential wrong API data, which unintended mismatch can happen without user knowing.
Adding additional layer on top of base customization system will also create confusion and editing difficulty for average user. The system will become triple or more layers of complexity (preset -> heatmap option -> classes <- auto selection), where a lot variables are involved. There is no guarantee that what user sets is what user gets. For example, user may forget which one of the system is in effect; or whether the classes or heatmap setting still matches certain vehicle mods; or whether heatmap matches new vehicle physics update, etc.
Thus, the customization system should remain straight forward and easy use, which user has full control of how things displayed when configured correctly, and not affected by variables that may be out of user control.
Ok.
But you can't assign a preset directly/auto to cars/tracks, so you need to change manually.
Understood