Yes indeed, they are very incorrectly restored session data. Mannef1 disconnected shortly before track rotation and reconnected shortly after. The bug is corrected now, it concerns only FULL/PROS versions, update is available and it is a must for all admins with busy servers and track rotations.
Indeed !delete it is. The half move to SQLite (with the intention of full implementation) is intended exactly for these kinds of situations. Instead of having to implement all kinds of special commands admins could perform any query on the database with immediate impact. Also viewing current data in a SQLite tool would be much more user-friendly than the custom TXT files...
When I take standard FZR, it says FZR... When I take 23kgs on it, it says FZI, but when I taky 25kg it still says FZI. Basically it always says FZI if it's not GT2 or GT3 or standard, but it never confirms the car as a FZR_16H or FZ2_16H. XR2_16H works.
Such things always depend on configuration, usually items in the TCD file specifying track/car data and items in SRV file enabling specific checks. But the simplest solution: 1) If you're spectated/kicked because of impossible speed, set CheckSpeed in SRV file to false. 2) If you're kicked because of impossible split/lap time (which may happen on oval using draft), set CheckTime in SRV file to false.
Hello Airio users, I'm very sorry to announce this, but please DO NOT USE AIRIO version 2.4.3, FREE nor FULL/PROS. It contains a very serious bug that causes in certain not quite rare cases wrong stats to be saved, which are then hard to get rid of.
An update is ready, version 2.4.4, but unfortunately the airio.eu site is now out order for several hours, so I cannot upload the update and change links. I'll do this all as soon as possible. Updated version is already sent to 500servers, hopefully it will be available soon.
Sorry for this bug. It concerns stats "optimization" done when implementing initial SQLite support. Well, this optimization was not quite optimal. :doh::doh::doh::doh::doh::doh:
I was away later this evening, will install 2.4.4 tomorrow. Already downgraded to 2.4.2 when it became clear to me that it took longer than expected
I see great future for SQLite. For example it would be very easy to delete all times under WR from all top pages with one (but complicated) SQL instruction. So, some bugs are acceptable.
Yes, me too, and I'd like to extend SQLite support soon, making it primary data storage first and then replace all the in-memory hashtables by SQLite queries. In the meantime I'd appreciate if more people tried to install the SQLite support so that I'm sure the basic code is OK.