The online racing simulator
AIRIO - Advanced LFS Tracker
(2372 posts, started )
Hi EQ, i did this, it's just formatted ?
I calculate the % for each ufb league track, it's strange that there are so many differences from track and track

defaultcar=UFB is correct ?

---

# ----------------------- Car Customizations ---------------------- #

# Below you may create custom groups of cars for calculating points,
# car categories to be used in some listings and customized cars.
# Defined custom cars or car categories may be used in later items.

# Custom cars derived from standard cars using intake restriction
# and/or added mass. These cars will be processed by Airio as if they
# were real LFS cars, meaning they will have their own stats stored.
# Definition: CUST|STAND,INTK,MASS CUST|STAND,INTK,MASS ...
CustomCars=FX2|FXR,23,0 XR2|XRR,25,0 FZ2|FZR,20,0 UFB|UFR,45,0

# Car categories, where one abbreviation comprises several car types.
# You can create new entries using Category|Type+Type+... notation.
# Entries are separated by space and can be used in !sb, !tb and !nr
# commands.
CarCategories=STD|UF1+XFG+XRG TBO|RB4+FXO+XRT LRF|LX6+RAC+FZ5 GTR|FXR+XRR+FZR GT2|FX2+XR2+FZ2

# Groups of equal cars for points calculation. Separate groups by
# space and join cars in group by a plus.
CarGroups=XFG+XRG RB4+XRT+FXO FXR+FZR+XRR UFR+XFR RAC+LX6+FZ5 FX2+XR2+FZ2


# ======================== Car/Track Data ========================= #

# These config data are placed hierarchically: First are values valid
# for all tracks and cars, then follow values valid for all cars on
# specific track and then values for specific track/car combinations.
# Values specified later overwrite earlier values. Identation is not
# required.

# ------------------------ Global Options ------------------------- #

# Default car on all tracks
DefaultCar=UFB

# Speed measuring in splits of all tracks/cars
SpeedtrapNode=

# No speed limit on all tracks/cars
AllowedSpeed=-1

# No spin limit on all tracks/cars
MaximumSpin=-1

# General good/great time reporting
GoodTimesRel=200,100,50

# Disallowed passengers on all tracks/cars (rear)
NoPassengers=Left+Right

# Prohibited tyres on all tracks/cars
ProhibitedTyres=Knobbly

# -------------------------- BL1 Options -------------------------- #

# Following values apply only to this track
Track=BL1

# Different default car for this track
DefaultCar=FBM

# Restricted zones valid for all cars on this track
RestrictedZones=407,-690,7 + 44,575,8

# Limited zones valid for all cars on this track
LimitedZones=142,484,7

# Maximum allowed rotation in degrees per second
MaximumSpin=360

# Values for this track/car overwriting global/track ones
# Following values apply only to this track and car
Car=FBM

# Specific maximum allowed speed for FBM @ BL1
AllowedSpeed=230

# Specific good/great times for FBM @ BL1
GoodTimesAbs=7400,7350,7300

# FULL: Server recorded lap time licence levels.
# LicenceTimesAbs=

Car=XFG
AllowedSpeed=200
Car=XRG
AllowedSpeed=200

# -------------------------- BL2 Options -------------------------- #

Track=BL2
RestrictedZones=-20,-160,20
ProhibitedTyres=Normal+Super
MaximumSpin=360

Car=XFG
AllowedSpeed=165
GoodTimesAbs=6900,6875,6850
Car=XRG
AllowedSpeed=170
GoodTimesAbs=7000,6950,6900

# -------------------------- UFB LEAGUE Options -------------------------- #

Track=SO6
# Values for this type of car on all tracks
Car=UFR
# Defines required intake air restriction
IntakeRestriction=45
# Defines required added mass
AddedMass=0
# Defines percents to add to default required time
TimeAdjustment=1830

Track=AS1
# Values for this type of car on all tracks
Car=UFR
# Defines required intake air restriction
IntakeRestriction=45
# Defines required added mass
AddedMass=0
# Defines percents to add to default required time
TimeAdjustment=1370

Track=AS2
# Values for this type of car on all tracks
Car=UFR
# Defines required intake air restriction
IntakeRestriction=45
# Defines required added mass
AddedMass=0
# Defines percents to add to default required time
TimeAdjustment=1900

Track=FE2
# Values for this type of car on all tracks
Car=UFR
# Defines required intake air restriction
IntakeRestriction=45
# Defines required added mass
AddedMass=0
# Defines percents to add to default required time
TimeAdjustment=1280


# ---------------------- Other Track Options ---------------------- #

Track=BL2R
ProhibitedTyres=Normal+Super

Track=FE5
ProhibitedTyres=Normal+Super

Track=FE5R
ProhibitedTyres=Normal+Super

Track=FE6
ProhibitedTyres=Normal+Super

Track=FE6R
ProhibitedTyres=Normal+Super

# ----------------------- Other Car Options ----------------------- #

Track=KY1

# Empty car means the values apply to all cars on this track
Car=
MaximumSpin=360

Track=KY1R
Car=
MaximumSpin=360

# Empty track means the following values are valid for all tracks

Track=
# Values for this type of car on all tracks
Car=UFR

# Defines required intake air restriction
IntakeRestriction=45

# Defines required added mass
AddedMass=0

# Defines percents to add to default required time
TimeAdjustment=1350

# Here are time adjustments for GT2 custom cars
Car=FX2
TimeAdjustment=475
Car=XR2
TimeAdjustment=475
Car=FZ2
TimeAdjustment=475

# ------------------ Values Supported / Explained ----------------- #
Quote from michele0676 :Hi EQ, i did this, it's just formatted ?

CustomCars=FX2|FXR,23,0 XR2|XRR,25,0 FZ2|FZR,20,0 UFB|UFR,45,0

DefaultCar=UFB

# -------------------------- UFB LEAGUE Options -------------------------- #

Track=SO6
Car=UFR
IntakeRestriction=45
AddedMass=0
TimeAdjustment=1830

Track=AS1
Car=UFR
IntakeRestriction=45
AddedMass=0
TimeAdjustment=1370

...


Good custom car definition, this approach has many advantages. (I think custom cars are one of the coolest Airio features, so I'm glad you're using it. )

DefaultCar definition is OK, UFB is perfectly valid entry. If you use one Airio on one server, it is no problem to define DefaultCar=UFB in TCD file. If one Airio is managing more servers, that definition should be only on one server (in appropriate Airio.srv.x.txt file), so that not all servers use UFB as default car (assigned to each new connection).

Then we have there the restrictions and time adjustments and I'm afraid that's completely wrong and it is my bad example, sorry! The correct definition should look like this:

Track=
Car=UFR
IntakeRestriction=45
AddedMass=0

Track=SO6
Car=UFB
TimeAdjustment=1830

Track=AS1
Car=UFB
TimeAdjustment=1370

Track=AS2
Car=UFB
TimeAdjustment=1900

Track=FE2
Car=UFB
TimeAdjustment=1280

First global UFR restriction is defined, so that everyone is forced to use UFB. Then it is sufficient to define time adjustments only, but for UFB and not UFR! And that's where I was wrong in the earlier example. So sorry...

Quote from michele0676 :I calculate the % for each ufb league track, it's strange that there are so many differences from track and track

Yes, there can be quite large differences, because UFB is much slower to accelerate than UFR, has lower max speed, but can take corners at the same speed as UFR. So, on short and twisty tracks, it can be about 10 percent slower, on longer tracks with straights the difference will raise to 20 percent. UFB is simply a different car.

You could settle for some average values, say 1500 (15 percent) or make it track specific, as you have it now. When you have some stats gathered, you can also define track/UFB-specific good/great times and such, but I would say that's possible only when using limited set of tracks.

Quote from JustForFunRacing :Updated at 6:00h this morning... lol

Thanks for info!
OK, for confirm now i've only this:

CustomCars=UFB|UFR,45,0

and

# ----------------------- Other Car Options ----------------------- #

Track=KY1

# Empty car means the values apply to all cars on this track
Car=
MaximumSpin=360

Track=KY1R
Car=
MaximumSpin=360

# Empty track means the following values are valid for all tracks

Track=
# Values for this type of car on all tracks
Car=UFR
IntakeRestriction=45
AddedMass=0

Track=SO6
Car=UFB
TimeAdjustment=1830

Track=AS1
Car=UFB
TimeAdjustment=1370

Track=AS2
Car=UFB
TimeAdjustment=1900

Track=FE2
Car=UFB
TimeAdjustment=1280


OK ?
Looks OK, but DefaultCar is also good to have defined (maybe on server level), because newly connected just type !sb and get track+UFB listing, which is correct.

One more note: To check the time adjustments are just about correct, type !good which shows good/great split/lap times. The values shown should be close to top UFB server split/lap times, not off by several seconds.
yes, i specify the default UFB car.

!good
Good/Great/Top/WR times (FE2+UFB) :
L1 : 24.49 46.66 1:19.52 (24.49 22.17 32.86)
L2 : 24.25 46.21 1:18.74 (24.25 21.95 32.53)
L3 : 24.13 45.98 1:18.35 (24.13 21.84 32.37)
WR : 24.01 45.75 1:17.96 (24.01 21.73 32.21)

!tb
Server best theoretical laps - FE2/UFB (23)
1. 1:18.54 PLZ-Sypher 23.71 22.72 32.11
2. 1:18.68 PLZ-Ulisse 23.70 22.67 32.31
3. 1:18.72 PLZ-Sklero83 23.74 22.73 32.25
4. 1:18.84 LIT mc0676 23.69 22.78 32.37
5. 1:19.17 Fasterkid 23.84 22.77 32.56
6. 1:19.43 PLZ-Bossforce 23.94 22.92 32.57
7. 1:19.61 PLZ-AleXio 24.01 22.91 32.69
8. 1:19.82 LIT DrifterK 24.37 22.88 32.57
9. 1:20.60 PLZ-Unitsas 24.88 23.00 32.72
10. 1:20.69 PLZ-FLASH 24.96 23.03 32.70

Are ok ?
Quote from michele0676 :
WR : 24.01 45.75 1:17.96 (24.01 21.73 32.21)
1. 1:18.54 PLZ-Sypher 23.71 22.72 32.11

The WR here is actualy Virtual Record, because there's no true UFB WR record available. It is time-adjusted UFR WR.

I believe the settings are OK, best UFB time on your server is a bit worse than virtual UFB WR, but not by much. If you have one day a beter time than WR, just lower a bit the TimeAdjustment value for that track.

Note in the sector times that UFB loses time in sector 2. The same as for tracks applies here: In twisty sectors UFB will lose only a bit, in straight sectors much more comparing to UFR.
I was wondering if it is possible to show your and the best reaction time at the start?
1) There's no exact indication when the green lights actualy appear.

2) Car positions including speeds (which would probably be used for the reaction time) are on server updated just 4 or 5 times per second at best, and especially at race start the lags are clearly visible.

=> On server it would be pure chance if your reaction is seen as 0.02 or 0.2 seconds.
hmm... but a list of the best acceleration 0-100kmh could be done...
Hmm... I like the idea of using custom cars!

But I did not get it right until now

If one Airio controls several servers how do I configure it to force the use of the custom car only on one server?

1.) I create the custom car like this: CustomCars=MyCar|OriginalCar,30,0
2.) I create a time Adjustment valid for all tracks:

Car=MyCar

TimeAdjustment=750

(of course there is some testing needed to get the correct value for the adjustment)

3.) force guests only to use "MyCar" on only one server... ??? HOW???

If I define it like this:
Track=
Car=OriginalCar
IntakeRestriction=30
AddedMass=0

I am not able to use the non restricted OriginalCar on the other servers, right?
You got it right, and even your deductions are very correct. A few notes:

1) "MyCar" must always have only 3 characters, just like all other LFS cars.

2) Indeed if you define a certain restriction in TCD file, it is applied to all servers. The option here is to apply the restriction only for certain tracks, if they are unique for the server where restrictions should be used.

3) The other option is not to restrict the original car, but make it a prohibited car on certain server. This is from default SRV file:

# Car types separated by space that cannot be used on server - string
# You may use this setting e.g. to allow only custom cars to join
# race - when you define UFB, you may restrict joins with UFR here.
ProhibitedCars=

4) You can also use the !/cars command, it is converting custom cars to standard ones and manipulating with the above config item. Say you have UFB defined as a restricted UFR. By typing !/cars UFB only UFR will be available in selection screen, but it will be restricted at the same time, alowing joins only with UFB. If both cars should be available, you type !/cars UFR+UFB.

5) Using restricted cars requires defining additional strong welcome text and similar measures, because people are usually confused, do not read any messages (saying why they were spectated), and generally do not like any restrictions.

6) Very useful is the !cars command (different from !/cars mentioned above), because it summarizes all defined custom cars and car categories.

Hope this helps.
On another note: Airio 2.3.1 is released.
  • The FREE version contains << Previous and Following >> buttons allowing easy listing through any multi-page output, such as the help system, !sb, !ptt and similar.

  • The FULL version gives limads/admins Kick/Ban/Act buttons in !players and !recent lists, making all the management actions much easier (no !ban typing is necessary now). All such actions require confirmation or some input (such as ban length or its reason). The Act button combines spectating and penalizing.

  • There is also a command allowing to cancel approaching race restart/end action, handy sometimes.
Enjoy!
CFG TCD and SRV files of 2.2.9 are 100% compatible with 2.3.1 ?
Can i use and is this works?

CustomCars=UF-BR|UFR,45,0
CarCategories=UF-BR|UFR
CarGroups=UF-BR|UFR

I like old CTRA servers car name
Hmm... I discovered a problem and I don´t know how to solve it:

I would like to setup 2 Demo servers - one with XFG/XRG, one with restricted FBM and normal FBM.

But you should be allowed to drive the XRG only if you gained enough points with the XFG, then you should be allowed to drive the restricted FBM if you gained enough points with the XRG and finally the full FBM if you gained enough points with the restricted FBM.

So far so good... But Setting this up does not work as suggested

It only is possible to allow a car if you have a special rank - no matter how you gained it...

And as Limad4 (isAdmin) you are able to drive every car - no matter which rank you have...

Would it be possible to change the Car by rank option that way that you can specify with which car the rank/points have do be gained?

Which option do I have to turn off to disallow Admins (Level4 AND 5 if possible) to drive cars above their gained points - I would also like to stay in my rules...

Next question I have concerns this setting in the CFG file:
Quote :# Days to cycle (clear) points/data gathered from races - integers
# Relevant point data are zeroed for all players on server midnight
# in the set intervals. 0 means never.
DaysChamp=7
DaysTotal=0

What does it exactly mean? What is a champ and Total here? If I set Total to 30 all points will be cleared once a month, right? But then all racers that gained enough points to race the faster cars will have to start again, or am I wrong?
Quote from JustForFunRacing :Hmm... I discovered a problem and I don´t know how to solve it:

I would like to setup 2 Demo servers - one with XFG/XRG, one with restricted FBM and normal FBM.

But you should be allowed to drive the XRG only if you gained enough points with the XFG, then you should be allowed to drive the restricted FBM if you gained enough points with the XRG and finally the full FBM if you gained enough points with the restricted FBM.

correct me if i'm wrong, but isn't that a feature in the full airio?
right - it is a FULL feature...

Quote :EQWorry:
About the restricted (spectating) and limited (ignoring that lap) zones: Certainly it is possible to define those for every track (or even specific track/car combinations). Drive to one end of such a zone, type !loca, read the X and Y numbers. Drive to opposite end, type it again. Calculate center and radius of the circular zone, enter it at the appropriate place in Airio.tcd.txt file.

It is just sort of manual work, but you need to make sure by experiments the zones are correctly places. By default they are included only for demo tracks because layouts (tyres, barriers) are not possible there. I have no zones for other tracks available, never needed those. But especially limited zones may be useful there, because you can cut in emergency without crashing and Airio will just ignore your lap time. They are good way to have stats free of cutting lap times...

And I have a question to the restricted / limited zones: If you enter a limited zone in a race the lap does not count. Does it mean you are one lap back then? I can´t imagine that! I think this means only the lap time will be ignored in the Airio stats. But what about LFSW then?? But gaining a position by cutting is bad too - and who cares if the laptime is ignored in the Airio stats for the case you gained some positions...

On the other hand specing for entering a restricted zone might be good on Demo servers... but at S2 servers I would suggest just to give a drive through penalty for that...

Would be nice to find an option to specify the penalty for entering a restricted zone - server separated in the SRV file
Quote from michele0676 :CFG TCD and SRV files of 2.2.9 are 100% compatible with 2.3.1 ?

Well, yes, only the 2.2.9 config files are missing some items added later. You'll find all such items mentioned in changelog, it is also good and fast to compare your present config files with the current default ones to see any differences.

Quote from Okram :Can i use and is this works?

CustomCars=UF-BR|UFR,45,0
CarCategories=UF-BR|UFR
CarGroups=UF-BR|UFR

I like old CTRA servers car name

No, that would not work. First, all custom cars must have only 3 characters, e.g. UFB, not 5 like you have. So these entries would be correct:


CustomCars=UFB|UFR,45,0
CarGroups=UFB+UFR

But groupinig UFB and UFR is strange, because this is used for approx. equal cars that may compete together, which is not the case of UFR and UFB. Same for CarCategories, they are used for grouping cars into categories usable in commands like !sb and similar, such as !sb gtr or !sb tbo.

Quote from JustForFunRacing :I would like to setup 2 Demo servers - one with XFG/XRG, one with restricted FBM and normal FBM. But you should be allowed to drive the XRG only if you gained enough points with the XFG, then you should be allowed to drive the restricted FBM if you gained enough points with the XRG and finally the full FBM if you gained enough points with the restricted FBM.

First, limiting cars per points/ranks is really a FULL version feature. Second, you're right under one Airio this scheme is not currently possible, because rank is derived from total points of any track/car combination. This is a known issue, I'm currently trying to come with some scheme to allow the limitation you suggest, allowing one kind of cars based on points gained in another group of cars. When it is implemented (say in one or two weeks), it will very probably still be a FULL version feature.

Quote from JustForFunRacing :And as Limad4 (isAdmin) you are able to drive every car - no matter which rank you have...

In CFG file find item AllowJoining and set it to 6. It would mean only limads of level 6 will be able to always join races, regardless of restrictions and other limits. And there are no limads level 6 in Airio, level 5 is currently maximum.

Quote from JustForFunRacing :What does it exactly mean? What is a champ and Total here? If I set Total to 30 all points will be cleared once a month, right? But then all racers that gained enough points to race the faster cars will have to start again, or am I wrong?

Points and other data (lap time, race time, drift score, podiums, later also starts/finishes, maybe also average time) for each driver and track/car combination is stored on two levels called total (which should be never erased) and champ (by default erased once a week).

Commands displaying the data always have two forms plus alternates, such as !ptt (points total, !total) and !ptc (points champ, !champ), !btl (best total lap or !laps), !bcl (best champ lap time or !lap), !btr (best total race time or !races), !bcr (best champ [last week] race time, !race), etc...

Yes, if you delete total stats, nobody will have any points, no ranks, so do not do it. If you want some time-limited competition, use the champ level, erased by !clrc command.

By setting DaysChamp=30 the champ data will be erased every 30th day, regular monthly erase is not supported this way, only scheduled commands may be used for that. But monthly erasure is best done manually, you'll also have a chance to capture the results e.g. as screen shots. Ability to export champ results before erasure is also planned, at least in some limited form.

Quote from JustForFunRacing :And I have a question to the restricted / limited zones: If you enter a limited zone in a race the lap does not count. Does it mean you are one lap back then? I can´t imagine that! I think this means only the lap time will be ignored in the Airio stats. But what about LFSW then?? But gaining a position by cutting is bad too - and who cares if the laptime is ignored in the Airio stats for the case you gained some positions...

Indeed you're not a lap back, that would not be (realistically) possible. Also Airio has no control over LFSW, I believe you'll see improvement there even if some penalty is applied for cutting. But LFSW data are not absolutely reliable anyway.

Prohibited zones are by default used only at places where cutting creates major troubles, such as on the inside of T1 on BL1, favorite crashers spot and place of many accidents. Restricted zones really only ignore that lap in Airio, they are created to have "clean" times in Airio stats, e.g. when qualifying for some event.

But you're right an option to define zones with penalties would be nice to have, maybe another independent item could be used for that in TCD file with penalties defined on SRV level...
Quote :In CFG file find item AllowJoining and set it to 6. It would mean only limads of level 6 will be able to always join races, regardless of restrictions and other limits. And there are no limads level 6 in Airio, level 5 is currently maximum.

Thanks for the answer. Well but this would mean that Admins cannot drive on a PB locked server too... I need to think about that...
Quote from JustForFunRacing :Thanks for the answer. Well but this would mean that Admins cannot drive on a PB locked server too... I need to think about that...

True it is hard to satisfy every need, but maybe the AllowJoining item is too general and should be split into two, one for applying required ranks-licences, one for other limits like time lock or limited joining. I guess car restrictions should be always applied, without questions.
Swearfilter
We discovered some minor problems with the swearfilter:

for example:

Curse=arsch (german word for ass, arse)

Quote :
driver xyz : ... war schön so ganz allein
driver xyz - KICK - Cursing : arsch
driver xyz : KICKED FOR BAD LANGUAGE

"war schön so ganz allein" means "driving alone was nice".

At the moment we bypass this with
Excep=war schön
Excep=war schon

Same problem with Curse=con (french insult)
Players will be kicked vor chatting "connection", "controls", concept" or similiar words.

Would be nice if AIRIO could be a tiny bit more sensitive...


Oh, and thx alot for the new features in 2.3.1.
Quote from EQ Worry :I guess car restrictions should be always applied, without questions.

i thought that was already done, i remember being spectated for bad setup while being a limad4.
Quote from VoiD :We discovered some minor problems with the swearfilter...

Yes, the filter is a touchy matter, but as always it depends on settings. On every text first character replacements are applied, by default all spaces and punctuations are removed, but you may change that. If you leave spaces in text, no one would be warned/kicked for unlucky combination of words, but also the filter would not capture e.g. "shi t". So it is a trade-off. Basically, too short and general words like "con" cannot be defined, it is a far too common combination of letters.
Ok, no problem...

Btw: is it possible to have a "!pi"-button next to the "!ban"-button (under !recent)...?

Would be pretty handy for (lazy) limads...
Quote from VoiD :Btw: is it possible to have a "!pi"-button next to the "!ban"-button (under !recent)...? Would be pretty handy for (lazy) limads...

Oh yes, the buttons there are pretty new, containing what just came to mind as useful. Your idea sounds good as well. There will also be unban (and maybe pi) buttons beside the ban list, which was already required by other lazy limads.

Have patience though, I have now many requests for smaller or more substantial updates from several sides and also I will be offline now for several days. When I'm back I'll see what can be done, update the buttons and maybe come with other small improvements, nothing major though, as I'd like to fully debug and clean this version (and give everyone a break with constant updates).

AIRIO - Advanced LFS Tracker
(2372 posts, started )
FGED GREDG RDFGDR GSFDG