What I'm trying to achieve is to make reasonably sure that when Airio recognizes some open track + layout configuration as a custom track, it will indeed be that one specific custom track, the same one on all Airios. When you have standard AS1 track, the game itself makes sure it is everywhere the same track, using the same parts of the AS site. However, this is more complicated with custom tracks. But still e.g. A11 should be the same under all Airios. But because it uses a layout, that anyone can change, making sure it really is A11 requires sometimes layout adjustments and always layout checks.
True, the path files can to a large extent make sure the "official" custom track lap times are consistent and correct, that WRs stored on AIRW are indeed the correct times. But path files alone cannot make sure the loaded layout conforms to A11 (or whatever) specifications. And I do not think you'll be happy to join a server with A11 (as reported by Airio Servers page), finding out it is actually a different track. Also, I can imagine ways some people may inadvertently or on purpose change the path files, with possible dire results for AIRW data. And moving splits in layouts will always have highly negative results, because split times or WRs are very important for good times reporting.
I'm not sure how much those AIRW data for custom tracks will be used. But there seem to be quite a few people loving all kinds of stats. When I some time ago removed all custom car lap times, because an inconsistency was discovered, I received some really unhappy comments. With the layout checks I'm trying to avoid these possible future problems. I hope this explains why I'm going quite deep into layouts, moving splits a bit sometimes, adding restricted zones at other times, and then checking these major parts of layouts in Airio.
True, the path files can to a large extent make sure the "official" custom track lap times are consistent and correct, that WRs stored on AIRW are indeed the correct times. But path files alone cannot make sure the loaded layout conforms to A11 (or whatever) specifications. And I do not think you'll be happy to join a server with A11 (as reported by Airio Servers page), finding out it is actually a different track. Also, I can imagine ways some people may inadvertently or on purpose change the path files, with possible dire results for AIRW data. And moving splits in layouts will always have highly negative results, because split times or WRs are very important for good times reporting.
I'm not sure how much those AIRW data for custom tracks will be used. But there seem to be quite a few people loving all kinds of stats. When I some time ago removed all custom car lap times, because an inconsistency was discovered, I received some really unhappy comments. With the layout checks I'm trying to avoid these possible future problems. I hope this explains why I'm going quite deep into layouts, moving splits a bit sometimes, adding restricted zones at other times, and then checking these major parts of layouts in Airio.