AIFP and "stuff4FS"

[cj241101]

Have stuck with an older version of AIFP (3.3.2.3) which has always been adequate for my needs using FS2004. Began a new project a couple of weeks ago adding 1982 traffic to my local airport (Luton EGGW).  This involved adding the based carriers (Monarch and Britannia) first then the non-based/overseas operators.  Compiled the traffic file and found Monarch and Britannia appeared, except they didn't go anywhere.  Plus the aircraft present at any given time didn't match the timetable.  No sign of any of the other airlines - found their aircraft were stuck at their bases as well and didn't move at their scheduled times.  
So I thought maybe I should download a later version of AIFP, except it seems the "stuff4fs" site no longer exists.  Using the "check for updates" button produces an error message "unable to establish communication with AI Flight Planner server".  
I hope I have got around the problem having saved later downloads of AIFP and reloaded the 1982 flight plan file using version 3.4.1.6.  Touch wood this has worked.  Just a little concerned that this problem arose in tandem with the EVP problem I have already posted on.

[Erik]

As I found out not very long ago in the same way, Don Grovestine has sadly passed away in August 2022. That explains the end of Stuff4FS.

I run an even older AIFP version, 3.2.18(f). Same as for EVP: it works fine here but I haven't tried compiling traffic for quite a while. AFAIK the newer versions mainly contained adaptations for the newer sims. In some cases, such mods have been known to break older (i.e. FS9) features. Don would then repair those after they had been reported but that is not an option anymore. Perhaps, in this case, reverting to an older version might help, if you know that to have been OK?

Erik

[Jorge]

I changed by links to the site called "The Owl's Nest" for Don's stuff.

The Owl's Nest

Just go to the provided drop-down tab for his user applications and the latest one there is V.3.4.3.15 from what I can tell.

It appears the site has, thankfully, backed up many of the tools he made.  The only one I don't use is the newest AFLT since I'm not sure if it still allows you to just create a light library like the older version that I have.  The "ICAO-less" option is imperative for me to make light libraries for the Platinum Wings work I'm doing since it doesn't depend on a specific airport and they can be placed anywhere for any reason.

Well, now I'm off to work!

Regards,

Jorge
Miami, FL

[cj241101]

So now I'm using AIFP 3.4.1.6 and have just discovered the reason I went back to 3.3.2.3. Working in aviation for 45 years I learned an awful lot of airport IATA (3 letter) codes, so doing airline flight plans was much easier using them than the ICAO 4 letter variety. Type in a 3 letter airport code in AIFP changes it to the 4 letter version with the airport name as anyone familiar with AIFP will be aware of. AIFP 3.4.1.6 has a bug, though. Enter the airport 3 letter code and it changes the last letter of the ICAO code by one letter. So LTN/EGGW becomes EGGV, which is a microlight field 20 miles north of EGGW. Sometimes it doesn't, so BHX still translates as EGBB/Birmingham, other times it changes the last TWO letters. Palma - PMI/LEPA - became LEOX which isn't in FS9. So I guess I'll have to brush up on my ICAO codes. Or try another version of AIFP.