Well, when I was adding the command some 18 months ago, maybe I had some reason to hide it as too admin-specific. But I guess you're right and it is not necessary to hide other connected server statuses.
Go to www.lfsworld.net, sign in using your web credentials. Open Racers & hosts online, switch to Insim relay tab, enter IP, insim port, and admin pass of your server(s)... Indeed this has nothing to do with either Lapper or Airio.
Indeed, but it was done on a below-average notebook by today's standard, 4 years old 2GHz Pentium-M. But on the other hand not everything was exported, only about half of all the available data. Also SQLite is currently used only for export, not as the core stats engine (as LFS Lapper has it, if I remember correctly). But it is just a first step, in time the situation may be reversed and SQLite be used as the primary storage while STA files only as export. Using real database could (hopefully) substantially speed up internal searching and sorting algorithms and simplify the code.
One other note, the www.airio.eu pages are now using a different colors. Also they changed names and are part of ASP.NET now (ASPX instead of HTML file extensions). Old links will also work for some time, but later the HTML files will be completely removed. Links in my signature point to the new structure...
We could try, it is supposed to work, but it is at the same time a bit tricky matter, having two (or more) custom cars from one standard car... But I'll try to add these definitions and test everything.
One note concerning custom cars. In Airio the restrictions used to get into stats with some custom car are not stored. That means if you rename some custom car, you will lose all stats (unless you do manual car rename in STA.CR file with Airio turned off). If you use different restrictions for custom car of the same name, stats will be mixed.
Autio works differently, it always stores standard car and air/mass restrictions, reconstructing custom cars from these three data whenever necessary. It requires more space and processing, but the advantage is higher flexibility, easy car renaming and introduction or adjustments of car categories.
Well, it needs testing, but again, it is supposed to work. (Which of course means it will not work...) Give me a day to define and test GT3s.
GT3 car definitions have been added to the Airio World (AIRW) database. They have intake air defined as requested, that is FZ3 = FZR + 28 % + 0 kg, XR3 = XRR + 34 % + 0 kg, FX3 = FXR + 32 % + 0 kg. I did some testing using GT2 and GT3 cars and it seems all data are stored and recalled correctly and properly. You can check some data for example here.
Note 1: For GT3 data to be stored on AIRW you need Airio PROS 2.4.2 (or newer, when available). GT3 cars do not have to be configured locally in Airio and GT3 WRs and good laps will still be stored/shown using AIRW.
Note 2: However, local definitions of GT3s will make sure certain info is locally shown and stored correctly. If adding GT3 definitions to the TCD file make sure they are BEFORE GT2 definitions, or cars will not be recognized properly.
Below you have correct definition of all custom cars supported currently by AIRW. Check this all out, let me know if something fails miserably.
AIRW could require XR2 to add 10 kgs as well, I can change it at any time, but then all (well, most of them) the current XR2 WRs and hotlaps will fall out of XR2 category and new data will have to be gathered.