Yes, I think that is a perfectly valid complain, and not the first one along these lines. Believe me, I'm trying to offer these additional functions and features in the best form I can make them. But there are things I cannot influence. These are mainly the data available from server to Airio.
For example there are car positions reported by the server, lets say 10 times a second. Are they exact? No way, they are approximate, projections of expected car positions from last known client data. There are some indications that client data are updated just about 2 times a second, so 8 out of these 10 reported positions are just expectations. But there is nothing else available.
The reported positions are used to check the race path. There is nothing like Airio racing line. For the race path check special files from LFS developers are used. Some of those are slightly adjusted, but always in driver-friendly way, making the proper racing path in fact wider or just correcting some obvious mistakes (such as on KY3 and KY3R).
There are routines running that allow the car to be seen shortly outside the proper path without invalidating the lap – they often help to cover for some small lags, but at the same time they need to be strict enough not to allow obvious cutting. Hard to find a balance.
Overall, sometimes people say that AIRW check for clean laps are stricter than LFSW checks. But they both work with different data. For example I hear LFSW needs to see 2 tyres on track. AIRW needs to see the car center on the track, it cannot reasonably check tyre positions and contact. AIRW cannot check touches of walls/objects, because such events are not reported (pity, it would be a nice addition).
So, the check is strict, yes. Also it cannot be perfectly equal for everyone, lags and luck do play a certain role. There are 2 things you can do to raise your chances for a "clean" lap. 1) Activate for yourself the Path Check display in !opt screen. Then you will see where the lap was actually announced not clean and why. 2) Ask server admins to be sure to use the latest path files. As mentioned, KY3 and other tracks offered slightly incorrect paths which I had to correct.
I understand the frustration. Be assured that I really tried to make equal conditions for everyone, but there are limitations to what is possible. Also, it will be pretty hard to make clean laps on populated servers. Much better would be to try an empty server with Airio PROS allowing all cars and track. We've had this Genuine Hotlapping server running specifically for this purpose, I must check if it is still online, and if not (as it seems), check if we can make it run again.
For example there are car positions reported by the server, lets say 10 times a second. Are they exact? No way, they are approximate, projections of expected car positions from last known client data. There are some indications that client data are updated just about 2 times a second, so 8 out of these 10 reported positions are just expectations. But there is nothing else available.
The reported positions are used to check the race path. There is nothing like Airio racing line. For the race path check special files from LFS developers are used. Some of those are slightly adjusted, but always in driver-friendly way, making the proper racing path in fact wider or just correcting some obvious mistakes (such as on KY3 and KY3R).
There are routines running that allow the car to be seen shortly outside the proper path without invalidating the lap – they often help to cover for some small lags, but at the same time they need to be strict enough not to allow obvious cutting. Hard to find a balance.
Overall, sometimes people say that AIRW check for clean laps are stricter than LFSW checks. But they both work with different data. For example I hear LFSW needs to see 2 tyres on track. AIRW needs to see the car center on the track, it cannot reasonably check tyre positions and contact. AIRW cannot check touches of walls/objects, because such events are not reported (pity, it would be a nice addition).
So, the check is strict, yes. Also it cannot be perfectly equal for everyone, lags and luck do play a certain role. There are 2 things you can do to raise your chances for a "clean" lap. 1) Activate for yourself the Path Check display in !opt screen. Then you will see where the lap was actually announced not clean and why. 2) Ask server admins to be sure to use the latest path files. As mentioned, KY3 and other tracks offered slightly incorrect paths which I had to correct.
I understand the frustration. Be assured that I really tried to make equal conditions for everyone, but there are limitations to what is possible. Also, it will be pretty hard to make clean laps on populated servers. Much better would be to try an empty server with Airio PROS allowing all cars and track. We've had this Genuine Hotlapping server running specifically for this purpose, I must check if it is still online, and if not (as it seems), check if we can make it run again.
Your explanation contains some facts i didn't know, i'm getting the picture how it works now.
, but i find fun in hotlapping when there's no close racing on server.. anyway tnx for the tip.
