Before I get into details, let me say I absolutely love the concept, but the execution leaves a lot to be desired. Firstly, when starting a test, the timer almost always has between a few dozen to a hundred or two milliseconds on it before ever accelerating.
Second, there seems to be either a bug or a very badly implemented method of capturing the exact time the vehicle hits the desired velocity (e.g. 60mph), because I've seen it take as long as ~600ms to not just display, but CAPTURE the time. In other words, I see the speedometer hit 60, and it takes at least half a second before the time displays. I.e. times are always off by a variable, non-trivial amount, so it can't even be compensated for by just subtracting a certain amount from all times. i know it's hard to be extremely precise with this stuff when there's so many factors to consider like framerate, in-game speed modifiers, etc., and a few milliseconds early or late is understandable, but hundreds of milliseconds means I can't trust any time this mod displays.
Third, as much as I love that it writes the results to a text file and that you can add your own waypoints, using a standard text file format like CSV (or tab-separated if necessary) would make a lot more sense to me and could easily be imported to Excel and the like. So instead of the "[name]<name>[start]<coords>[end]<coords>" format you have now, it would be the key names on the first line (like columns), and values on each line thereafter. Assuming the key names don't change, it's also very redundant to include them in every line.
Last, and i'm not sure if this is a bug i'm experiencing or something that simply isn't functional, but the 60-120 result is never captured. After about two dozen tests, all surpassing 120mph, i have yet to see a single result. It also writes the total time in that field instead of leaving it blank, making it ambiguous as to whether 120mph was reached at the exact same time as hitting the end marker or if it was EVER reached.
I hope you'll take this on board, because I really, really love the idea, and afaik, no other mod does this sort of thing beyond simple 0-60 and max speed displays.
5mods on Discord
Before I get into details, let me say I absolutely love the concept, but the execution leaves a lot to be desired. Firstly, when starting a test, the timer almost always has between a few dozen to a hundred or two milliseconds on it before ever accelerating.
Second, there seems to be either a bug or a very badly implemented method of capturing the exact time the vehicle hits the desired velocity (e.g. 60mph), because I've seen it take as long as ~600ms to not just display, but CAPTURE the time. In other words, I see the speedometer hit 60, and it takes at least half a second before the time displays. I.e. times are always off by a variable, non-trivial amount, so it can't even be compensated for by just subtracting a certain amount from all times. i know it's hard to be extremely precise with this stuff when there's so many factors to consider like framerate, in-game speed modifiers, etc., and a few milliseconds early or late is understandable, but hundreds of milliseconds means I can't trust any time this mod displays.
Third, as much as I love that it writes the results to a text file and that you can add your own waypoints, using a standard text file format like CSV (or tab-separated if necessary) would make a lot more sense to me and could easily be imported to Excel and the like. So instead of the "[name]<name>[start]<coords>[end]<coords>" format you have now, it would be the key names on the first line (like columns), and values on each line thereafter. Assuming the key names don't change, it's also very redundant to include them in every line.
Essentially, the format would look like:
name,start,finish,heading
Airport Drag,-1731.868|-2899.304|12.72205,-1356.221|-2245.473|12.68831,327.7671
Airport Circle,-1354.81|-2242.927|12.7231,-1275.375|-2228.509|12.65361,147.5489
...etc. Same for each results file.
Last, and i'm not sure if this is a bug i'm experiencing or something that simply isn't functional, but the 60-120 result is never captured. After about two dozen tests, all surpassing 120mph, i have yet to see a single result. It also writes the total time in that field instead of leaving it blank, making it ambiguous as to whether 120mph was reached at the exact same time as hitting the end marker or if it was EVER reached.
I hope you'll take this on board, because I really, really love the idea, and afaik, no other mod does this sort of thing beyond simple 0-60 and max speed displays.