Just create the message yourself, it is the best and simplest option you have now:
BadCarType=^7Restriction is required: ^3FZR+^120%^3, XRR+^125% ...
BadCarType=+^3For more info about required car restrictions type ^1!cars
I guess the best way to turn off track rotation is to use:
depending on what you use. To start the rotation again a simple !rld may be used, because it will read and apply what is in the CFG/TCD/SRV files.
It seems to me the car definitions are almost correct. Always, only !rld is required to update the definition, never Airio restart. I think the space after = in the 1st item may be a problem, try to remove it and use this form:
Also, you have FO8 in two categories, I'm not sure how this will work. FX2 has probably switched 0 and 55. And final note, you should use other car names than FZ2, XR2 and FX2 (and GT2), because they are used "officially" as a GT2 class car with very different restrictions (about +10% comparing to what you have).
As i so on GT3 Touring car cup they changed FXR GT3 spec from 32% to 31% so all results from wr's and tables are invalid or not show... is there any way we can add some percent on time so we can use 32% handicap records?
The AIRW database is capturing/storing all personal best lap times done with restricted cars. So, if someone is using FXR with 31 percent restriction under Airio PROS, the time is saved. (Well, at least I believe so, it is some time since I was checking this.) The problem is that for now FX3 is defined on AIRW as FXR plus 32% or higher intake air restriction. So FXR+31% is in fact seen as the immediate faster FXR category, FX2 in this case.
Overall, the custom cars matters are getting somehow confusing, because people are using GT2 to mean various restrictions. And because AIRW has its own "official" definitions ignoring local definitions, there can be unclear situations. The good news is that I could do a change at AIRW at any time and redefine FX3 as FXR+31%. No data will be lost, people will still have their FX3 best times, but they'll be able to improve those by using slightly lower restriction.
Problem is it will add to the overall confusion. Another question is whether it is a good change, because there are various GT2 and GT3 specifications and those are changing as well... Eh...
Don't worry Worry, the GT2/3 restrictions are fine. The whole point of AIRW is to keep a common set of restrictions across various servers, and not changing %ages that have been used for 3 years just because the drivers of the FXR in some league are too shit to be on the pace that they think 1% will suddenly make it all even.
I think the main idea about restricted GTR cars is pretty much the same everywhere. GT2s have restriction slightly above 20%, GT3 have slightly above 30%. (From this perspective a GT1 category seems to be one with something over 10%.) Another problem is making the restricted GTR cars approximately equal. I believe there is a way, and that is comparing online WRs of GT2 and GT3 cars. If for example FX2 WRs are consistently (and significantly) worse on all tracks, then we could reduce 1%. If on the other hand XR2 WRs are substantially better comparing to FZ2 and FX2, maybe adding 1% would be good...
If you limit cars to GT2s or GT3s, it is up to you to communicate the fact to the connecting people. You have many options how to do that – connect messages and buttons, customizable info screens, LFS connect screen, customizable bad car type messages. Everywhere you may instruct people to type !cars and see the restrictions, you may also create (at least in the FULL version) e.g. !info screen with detailed info not only about required restrictions but also how to set them.
However, it is a common fact that many many people simply do not read even the biggest info on screen, they just try once to join with GTR and then leave. This is happening on all servers with restricted cars and no messages, custom defined of default from Airio, will change it. If you're running a GT2 server, half the coming people will disconnect without ever bothering to find out why they can't join race, and Airio messages cannot help.
In R2R we have a GT2 server and this is happening all the time though we have perfectly clear instructions prepared, using custom server commands, and we're sending them whenever someone new is spectated for bad car type (full GTR). Still, the above applies – some people (well, quite many) are too dumb to read or follow simple instructions.
Another example is the hybrid tyres, which any serious rallyx server should require. Despite BIG messages with extremely simple instructions three quarters or even more demo people are kicked from AA rallycross server for bad tyres after 3rd attempt to join using normal tyres. And the instructions are in bright colors, just Shift+P > [rallycross] setup > Join. Same with renaming, because we do not allow unnamed people to race. Rarely someone is able to follow the 2-3 simple steps to rename.
All the above means one thing: There are many people that can't read, or at least behave so. Put in any unexpected limitations and you are in troubles. Airio cannot make such people read and understand. Pity there are no options to FORCE on joining cars the limits automatically, informing the driver of the adjustment. I would think such a feature would be great addition to LFS.
(Unfortunately it would require LFS developers to update LFS. Unfortunately, because they do not respond to anything, and if they do, they only close some threads, saying the discussion there leads nowhere and that everything was decided long time ago. And that, actually, is the problem... )
On an other note, new Airio is released. The biggest addition in this version is TeamSpeak3 support, but only for FULL and PROS versions. Airio may connect as a server query to a (team) TS3 server, announcing its presence. Using private chat people may display current server(s) state, and TS3 admins may connect to any server through TS3 and do everything a host can do, that is to send messages and use all LFS and Airio commands remotely. Very handy for quick checks and changes. If you have FULL or PROS licence and did not receive my mail announcement with download link, please contact me.
If we would limit the cars to GT2 there would be no problem for messages like "use FXR with x % restriction", but we change the cars often, it was just a short experiment with enabling GT2 and many left^^
Hi, sorry for delay, I was waiting for bug reports for a few days. I'll send the files today, as well as an answer to the question you asked some time ago already. Again, sorry for delay.
Well, adding THIS (Airio, I think) to a cruise server seems pretty weird to me, because Airio is purely racing system. There's no AllowCruise in Airio, I think the only thing you need to do is too make sure there is CheckDriving=false in Airio.srv.txt file. Also you'll need /cruise=yes in server config, but that is another matter.
Glad to hear that TS3 update solved the crash (connection lost) problem. To disconnect from current server in TS3 (or IRC) chat send !conn (or just !cn) without parameter/number.
This shows wrong setup for FO8 (or generally any type of cars) in the TCD (track/car data) file, see AllowedSpeed there. Quick fix would be to disable speed check altogether using CheckSpeed=false in the SRV file.
Dec 10 17:23:05 37 - Padovan : ^L!TOP
Dec 10 17:23:05 37 - Padovan : !top
Dec 10 17:23:13 37 - Padovan^L disconnected Dec 10 17:32:50 /pass=
Dec 10 17:32:50 host : ^L!ch on
Dec 10 17:32:50 LFS server settings have been reset...
Dec 10 17:32:50 Airio basic checks are now turned on...
Dec 10 17:32:50 Airio advanced checks are now turned on...
Dec 10 17:56:26 Spectate All command carried out... Dec 10 18:06:26 /pass=
Dec 10 18:06:26 host : ^L!ch on