FGTracker issues

[Hazuki]

Hi buddy,

Recently I found out that FGTracker (mpserver15 fgtracker.ml) is being blocked by avast for no reason. If you wish to visit the FGTracker, please either remove avast or disable the Web Shield of avast.

In case you found any bugs on FGTracker (mpserver15 fgtracker.ml), please report here and I will read it when I have time. Thanks for supporting FGTracker (mpserver15 fgtracker.ml).
P.S. No feature request unless you will take the initiative to program it.

Added on 03.06.2015
- If you reports problems on a specific flight (or use a flight as an example to report a general issue), please provide me the

Code (): Select all

flight id

.

=========================================================================
FAQ on FGTracker
https://fgtracker.ml/modules/content/index.php?id=1

Rules and Obligations when using FGTracker (mpserver15 fgtracker.ml)
https://fgtracker.ml/modules/fgtracker/ ... itions.pdf
==========================================================================
Currently known issues: (Update on 2017.08.17)
1. FGTracker (mpserver15) is inaccessible if avast anti-virus software is installed. [2015.01.04]
- Won't fix. Either remove avast or disable the Web Shield of avast. (Removed on 2015.03.04)
2. Flight track is not guaranteed if you are using a mpserver with FGMS v0.11.X installed due to bugs. (Removed on 2017.05.07 as FGTracker does not accept connections from FGMS version <0.12 anymore)
3. Map in show flight won't get update after first time access (As at 17.08.2017 issue is fixed)
4. Local time of an airport will mess up if the county has more than one official timezone (e.g. 4 timezones in US continent). Up to now no idea how to obtain timezone data of a specific airport. Assistance is appreciated.

[Johan G]

Currently known issues: (Update on 2015.01.04)
1. FGTracker (mpserver15) is inaccessible if avast anti-virus software is installed. [2015.01.04]
- Won't fix. Either remove avast or disable the Web Shield of avast.

That is not nice.

[Johan G]

That is not nice.

Indeed, but nothing I can do with it. I reported the false alarm to avast but they just don't listen.

[elgaton]

I have reported the false positive as well. Maybe you could try replacing the Chinese comments in your code with English ones? That's the only unusual thing I've noticed in the code, might be worth a shot.

[Hazuki]

I have reported the false positive as well. Maybe you could try replacing the Chinese comments in your code with English ones? That's the only unusual thing I've noticed in the code, might be worth a shot.

Well I don't think I shall modify the script just to entertain the stupidity of the anti-virus.
Those are Japanese BTW.

[elgaton]

Agree (sorry for the Chinese vs. Japanese mistake - I don't know the languages and took a guess). Let's hope the Avast team solves the issue (from what I've seen they take approximately 10 days to analyze the site and correct any mistakes, due to the high number of false positives).

[elgaton]

It took a bit but I have received a response about an hour ago, the false positive will be removed in the next virus definition update. I'm going to check the site again this evening or tomorrow morning and report.

[Jabberwocky]

Well, if it comforty you, my website was reported for some time by Avast as well. The reason was, there were some unconnected pages (links without a direct link to a php or html with the same filename). Those were actually downloads. Seems Avast is getting heat from many website users all over the world for reporting many websites as wrong positives and that is what makes them so slow to sort it out website by website.

[Johan G]

Effective flight time bug

I have noted that since the beginning of April the effective flight time is incorrectly calculated. This is very apparent when looking at the flights by for example thuko48 or D-07007.

The effective flight time seem to be nearly exactly three times to high, though with one notable exception. When the flight duration is less than a fraction of a minute the effective flight time seem to always be 1:30. The break point seem to be a flight duration of somewhere between 25 and 40 seconds (my gut feeling says 30 seconds).

[Hazuki]

Thanks Johan G for reporting the issue.

The bug has been identified (wrong interface between objects) and effective flight time since Feb 2015 will be refreshed. This may take a while though.

[Jabberwocky]

I wondered already about having 9 days flight time in a week ...

[Johan G]

@ Hazuki: Thanks for the quick fix.

[Jabberwocky]

Seems, Server 15, the tracker is down or can anybody reach it?

[Jabberwocky]

Hi,

it appears, that since beginning of April, all the effective flight times in the tracker are not calculated any more. Means, no flight times are added and thus all the ranks stay the same forever. What's the story on that?

J.

[Johan G]

Hmm, seems the tracker is currently (21:45 UTC) down.