Track Sectors - Divide the track in sections 1.42

Thank you, I'm so glad I was able to make an impact on the way you play the game.

Ah yes.. the Nordschleife. Let me briefly explain why that behaviour probably appears. You see, in the available information when running the code, there isn't such a thing as a progress value, but instead, there is a data component that can be between 0-1 which represents where exactly a player is on the track spline. This thing is mainly used for creating racing lines for AI, but i adapted it to instead use it as progress. Now generally, you would expect that a value of 0 means the start of the track and 1 would mean the finish line, but this is not necesarrily the case, it's arbitrary to whoever made the map. For example, due to this, it was a struggle to add handling for custom maps since they could for example put the start at 0.4 if they wanted and finish at 0.8, the game engine would allow them. Now kunos devs were nice and for the most part they kept the standard of 0-start, 1- finish, but not for all of the maps. I think that i remember particulary while i was developing the app the was some other app where someone had made some separate handling for the tourist nordschleife, as i think the actual start for the tourist version starts at a very high value of around 0.98, if my memory serves me right, then as you get to the first corners it starts from 0 and then continues increasing. So this issue you're describing is probably the fact that you're placing the first sector during that high initial value of about 0.98 then for the next corners it 0.00 something. I might later try to introduce some handling for this, but as of right now I don't plan on updating this app too soon as i have IRL commitments. I hope though the explaination is helpful.

There are 2 types of lap times, the normal lap time and theoretical lap time which is simply the sum of the times of all the best sectors, this generally tends to be faster than the assetto corsa time, as you would be quite the good driver if you managed to obtain all your fastest sector times in the same lap :) . Although, the theoretical lap time is more a guiding instrument than an absolute to be reached, because racing is so complex, you could use a line for a sector so that you would obtain a faster time than previous, but it might result in a slower next sector. Think for example how we often prefer to use a line to keep the most speed in a corner leading to a straight, thats because, even though you're probably travelling at wider arc, therefore longer distance, during the corner to keep more speed, this will most likely be neglected by the higher top speed during the straight. Now lets say you put the sector end at the end of that corner. You could actually take a line to get the fastest time for that particular corner and it will be stored in the best sector timing, but then you will most likely have an overall worse lap time because youre losing more time on the straight. That being said, please think of the theoretical lap time more as an intuitive intrument for speed rather than an absolute.

Hello, i've sent you a message some time ago to reach and try to help you. I'm stil open to offer you help.

That's pretty weird, ironically enough this app was made specifically because I wanted to do time attacks on that map, I literally tested it on Akina 2017 today and it works as intended on my end. Anyhow, I'm thinking of rewriting the whole due to the new possibilities csp offers now, if you have suggestions I'm willing to listen.

A theoretical best lap time wouldnt be too hard to implement, but i dont think it has too much relevance, let me give you an example: sector 1 is composed of slow corners , sector 2 has a straight right after sector 1. Lets say you take a V line in the last slow corner of sector 1 that way you can have the maximum acceleration for the straight line, this will give the best sector 2 time, but the sector 1 time will be a bit worse. The idea is you cant really just sum up all the best sectors because it can be unrealistic sometimes, if you want to get the best possible time for sector 1 you will have overall worse time in sector due to different exit in the last corner of sector 1, and arguibly, if your car has a bit of horsepower, the time you will gain from the straight will be more than the loss you will have from sector 1 at the last corner. So in this case if you use both theoretical bests , its just gonna be unreachable. This is kinda a nieche example, but it goes to show how just putting the theoretical bests might lead you into error.

Im thinking to rewrite the app, cant promise anything though, but if i ever get around to it, i will probably add a theoretical best option as a toggleble for those who want it.