It appears that the main reason the forum has been so sluggish recently is the huge number of attachments, posted mainly by me!
You may have noticed that some old forum threads have already been removed, but the old logos thread, now around 72 pages, was probably a big factor in the slowdown.
So I'm starting a new thread, and the previous one will soon be deleted. You can still download the logos from it from Allocator's website here
http://radarbox.gofreeserve.com/index.html. and I'll post a zip of the more recent logos very soon.
In the meantime, here's a copy of the explanation of how logos work from the now-deleted earlier thread.
Here's a summary in the order that the logic works:
1 - If the Flight ID is blank or just numeric, no logo.
2 - If the Flight ID is the same as the Registration (with spaces, dashes
etc removed), find a logo file to match. This means that if, for example,
the flight ID for G-WXYZ is GWXYZ, it will display GWXYZ.bmp. If there is no
matching logo file, show a blank.
3 - If the flight ID starts with three or more letters, find a logo file
that matches all those letters. This means that if the Flight ID is TARTAN2,
it will display TARTAN.bmp. If the Flight ID is TAR123, it will display
TAR.bmp. If there is no matching logo file, show a blank.
4 - If the Flight ID starts with two letters, or either of the first two
characters is a letter, look up the two characters in the IATA code (C2)
field of the Airlines table of NavData.db3. Find the corresponding ICAO code
(C3 in the Airlines table) and find the matching logo file. If there is no
match in the table, or no matching logo file, show a blank.
WHAT THIS MEANS FOR US.
Point 2 - we can create logos for individual aircraft that use their
Registrations as Flight IDs.
Point 3 - we can create logos for missions such as REACH, and we won't get
Aer Arann showing up instead!
Point 4 -we need to update the Airlines table in NavData.db3. A lot of the
data there is old, it doesn't have the latest airlines, and, because so many
aircraft use unofficial two-letter codes instead of their official IATA
two-letter codes, we can edit the table to suit ourselves.
For example Régional Airlines usually use their ICAO code of RAE, but also
regularly use RA as a Flight ID, but this is the IATA code for Mesa
Airlines. In Europe, therefore, it would be best to change the IATA code
from the official YV to RA. If Mesa Airlines do use YV, then local users may
prefer to leave it alone. I've already come across several other examples,
and have done some editing of my table to keep up with new airlines that use
a two-character code (official IATA or not). Remember IATA codes can be An,
nA, or AA, but not nn.
It will only be necessary to add new airlines to the table if they use their
IATA (or other two-character) codes in their Flight ID's. If they stick to
their ICAO codes, the Airlines table doesn't get involved.
I think this is a big improvement on how it worked before, but, because it
picks up so many more flight ID's and associated logos, it also means that
crew error inputting them can result in wrong logos appearing that we just
can't do much about.
Version 3.0 comes with many new and renamed logos that I created while I was
helping with the beta testing (and I pruned out some mouldy old logos as
well). I'm still very happy to take requests for new/updated airline and
mission logos, but please don't besiege me with requests for logos for
individual registrations unless they're for something very special!
Rod
