FG Tracker & Planner

I was informed by Google that "low level security" SMTP service will not be available to me on or after 2022.05.30. This will affect the callsign registration as I cannot send you the verification email to your email address. If you do not receive the verification email after callsign registration, please PM me (Hazuki) in the flightgear forum. I will activate your callsign manually.

Download Program (FGTracker-MiniSimconnect) here.

Points to note:

1. You must first register your callsign.
2. You shall read "README.txt" in the 7z file for usage instruction
3. All flights recorded by FGTracker-MiniSimconnect is having zero Effective flight time, i.e. time on FGTracker-MiniSimconnect will be excluded in ranking.
4. If you faced bugs, report here

As informed by building mamagement, power supply to FGTracker will be suspended on 06.01.2021. As such,  FGTracker service will suspend from 0200-1400UTC. As ususal, flights made during the suspension time will be loaded back to FGTracker by respective FGMS after FGTracker is resumed.

With the unhappy experience in PostgreSQL12 , I will arrange the DB clean up and upgrade sooner on 15.12.2020 from 0000-1200hrs. During the said time, as usual, while the FGTracker service is suspended, your flights will still be recorded by FGMS (MPSERVERXX) and the data during the suspension will tranfer to FGTracker after the tracker is resumed.

Fly safe. Stay safe.

========================================

Edit 15.12.2020 0830UTC: While the Database is upgraded to v13, The clean up job runs way longer than expected (I have no idea why Postgresql performs so badly on a simple deletion). While I have no exact resumption time, please expect FGTracker be resumed by 16.12.2020 0400hrs.

Recently (in December 2019) I have upgraded the FGTracker database from 11 to 12. Unforturnately it appears that there is memory leak in postgres instance:

I have tried to submit a bug report to pgsql-bugs but unforturnately I am not able to produce a replication steps simple enough for a decent bug report, and the bug report is closed.

In this connection, I have to make necessary arrangements to mitigate the memory leak by reducing the frequency on running the batch job. What the batch job does is to update the ranking, to update the start/end airport and to claculate effective flight time.

With immediate effect, the frequency is changed from 300 seconds to 1800 seconds.