As far as I can tell, the ADU only supports 5 user defined tracks. None of the inbuilt tracks are in Australia so I have to rely on entering them myself. This is no problem, except for the limit of 5, I race at more than 5 tracks and it is a serious limitation to only have five.
We also have tracks with multiple layouts, which are in effect different circuits (length) and sometimes different start/finish lines,
You can send me some Australian tracks that you are interested in, including the start/finish line coordinates and length, and we can add those tracks as predefined ones.
Problem is that they have multiple layouts and start finish lanes all predefines do not have any sense only making that confusing because you need to made a custom track with biggest radius to get priority over predefined. button defined is excellent solution in my opinion.
Sure, but if such a track is predefined, there is a possibility of getting three layouts for the same track – the first predefined, the second user-defined from the client, and the third defined by the button.
But in general, I agree, the button-defined option is the best.
If I use the button method, does it carry over on power down (i.e. retain the start finish line and track length) or do I need to do it each time I’m on the track
It will remember coodrinates until next track will be configured or you delete them . So even if you week later on the same track coordiantes and track lenght is still there.