For me the guages resolution/sharpness is the same Y0 > Y22 >> Y24.
I'm guessing they had already set a higher MIP BIAS on text/interface slider (like 0.0) and when they changed to Y24 the Mip Bias went to a lower setting (like -1.5) making the number clearer.
Perhapse they had Y0 and went to Y24 and the MIP Bias slider appeared for text so they could make it clearer.
The only difference I see is the Central Circle on the needle
How much work would it be to add a "ilegal lap" bit? Isn't that the "HLVC legal" byte in RAF-fiels?
Could be nice to see if the lap would have been valid in hotlapping mode. Now I check invalid myself (result is that it's not 100% the same as in hotlapping mode), but having that bit would make insim life much easier
UPDATE - When I join the track the LAG bit is active for 1 whole second. Is this a bug or a feature? When I put car in first gear before end of this first second the LAG bit toggles off.
UPDATE - Sorry ;-) This was with Y22 client on Y24 host. Using Y24 client gives no "illegal lag" ;-) Nice feature though :-D
Nice patch Yeah but that bug that I reported in Y18 is still here with the AIs...
In Kyoto,Aston and Westhill, when you put 20AIs and put " pit stop requiered " they just pit too late...
If you have time for this bug and want a replay just ask
Well I did ask for specific ways to reproduce that but got no answers. So I figured out a possible issue and fixed that.
Your description is missing some vital information, so I still cannot reproduce the bug. If you could provide this information it would be very helpful.
1) Which track configuration?
2) Which cars are your AI drivers using?
3) How many laps?
Also, if you could reproduce the bug with less AI drivers that would be very helpful, because if I run in the debug version, everything runs slow, so the MINIMUM way to reproduce the bug would be best, to increase the chances that it can be fixed. I'm very, very busy so cannot spend all day trying to reproduce one bug. What I need is the EXACT information, to reproduce it in the simplest way possible. When I can reproduce a bug, I can usually fix it.
Oh I didn't see the post for Y22 :P
I'll do my best to help you and I'll post the other informations after my 4 LFS sessions finish the test
I tested with 1-2-3 hours of race and the problem is still the same I'm testing to see if it happens with a number of laps fixed
But actually I'm sure that: That problem doesn't exist in:
-Frern bay Tracks with all cars
-Blackwood Tracks with all cars
-South City Tracks with all cars
With TBO,LRF,miniGTR and GTR it does exist here:
-Aston North,Aston National,Aston Historic,Aston Grand touring, Aston Grand prix
-Kyoto National and long