Military AI Works

Gents,

This morning I upgraded AIFP to the latest version 3.3.1.1 and I believe I discovered an issue.

I have reported it Don who is investigating but for the moment I would advise not to upgrade from any 3.2 version.

The issue concerns some P3Dv5 compatibility he has added in the area of Find/Collect airports. After upgrading it states that the addon airports list is not in the correct format and to regenerate and when you do it seems to completely ignore a lot of afcad files including all waypoints, seemingly.

The effect would be that you can't then create a leg to a waypoint.

Will let you all know once Don comes up with something definitive.

Over in the AIG forum there is a AIFP thread and this issue was brought up by me and he is trying to help me.

https://www.alpha-india.net/forums/inde ... 340026#new

Don posted a new AIFP v3.3.1.2 and it seems to be working correctly. I compiled a plan that has waypoints in it and there was no errors.

An update after some investigation between Don and myself.

The issue appears to be that AIFP either terminates the search for new afcads early or terminates in an uncontrolled manner. We currently believe it to be the first one.
I have just sent him some more diags which I think points to where it is going wrong in the hope that it will help him found out why it is going wrong.

Version 3.3.1.2 does not fix this issue. It fixes Joseph's but Don didn't think it would solve this one.
For this one 3.2.22.3 found and added 26455 afcads whilst 3.3.1.2 found and added 688 afcads.

Will keep you updated.

Firebird wrote: ↑25 Jul 2020, 04:26 An update after some investigation between Don and myself.

The issue appears to be that AIFP either terminates the search for new afcads early or terminates in an uncontrolled manner. We currently believe it to be the first one.
I have just sent him some more diags which I think points to where it is going wrong in the hope that it will help him found out why it is going wrong.

Version 3.3.1.2 does not fix this issue. It fixes Joseph's but Don didn't think it would solve this one.
For this one 3.2.22.3 found and added 26455 afcads whilst 3.3.1.2 found and added 688 afcads.

Will keep you updated.

Sorry about that. I thought your problem was the same as my problem.

That's OK.

OK an update.
After various tests and information exchanges Don is convinced that his new code that he developed has a unforeseen logic hole.
He anticipates that it should be easy to find the fault and come up with a fixed version.

Good! I got rid of 3.2.22.3 just before I read your post, Steve! Doh...

Do you want the zip file to reinstall?

Just an update to the problem I reported.

Don has made progress to overcome the issue but there are one or two other things to fix with it. However, he has also discovered an issue that broke P3D v4/5 support so he is working on two issues at the moment.

Firebird wrote: ↑26 Jul 2020, 07:37 Do you want the zip file to reinstall?

Thanks Steve - got your PM.

An update.

It looks like Don has cracked it. I have tested the latest version and it all appears to be working fine.
Will have to check with Don to see if there is anything else outstanding and if he tells me when the new version is released I will update again.

Over the last week, each time I attempt to update an error pops up for server issues. This has been for each version listed.

Firebird wrote: ↑28 Jul 2020, 13:08 An update.

It looks like Don has cracked it. I have tested the latest version and it all appears to be working fine.
Will have to check with Don to see if there is anything else outstanding and if he tells me when the new version is released I will update again.

Not convinced! While it (3.3.1.2) might now be working for P3Dv5, it seems to have lost the ability to collect new airfield data for FS9 (important right now for my efforts to provide flight plans for John's GAF Eurofighters). Fortunately there's no such problem with 3.2.2.23 - very glad you gave me that, Steve!

No 3.3.1.2 is NOT the update we have been working towards. All it did was fix the problem that Joseph had.

The issue is resolved but Don wants to correct something at the core of the issue. Something that affects all versions from FS9 onwards up to and including P3Dv5.
To deal with that root cause he is writing some new routines that will eliminate it and future proof users that use a certain feature. At this moment in time he is not releasing a new version until that root cause is fixed. He anticipates that I would be able to test that later today - Wednesday p.m.

So at the moment it is best to remain on 3.2.22.3 if you haven't upgraded.

UPDATE.
The problem has been identified and code is being written by Don and tested by me.
It is an issue that AIFP never thought about trying to cope with from FS9 days. It never appeared as an issue until Don re-wrote some code for P3Dv5.

The fix is progressing but the issue is working out all the code changes for something that has been around a long time.

UPDATE

Pleased to say that Don is on the verge of releasing 3.3.1.3 which solves the issues that a lot of people had with version 3.3 onwards.

Feel free to enjoy it.

Gents,

Just to tidy this up. Don has worked hard to clear up a lot of issues that existed from the start of AIFP and issues with P3Dv5 compatibility.
These have been successfully dealt with and tested under development releases and a new general release is available for automatic download. This is good to go for all versions.

The version is 3.3.2.0

I just updated mine 3.3.2.3 and I just discovered this problem. I'm trying to update a flightplan, replacing some airports in the plan with another or waypoint. I save the plan, however the airport/waypoint that I changed reverts back to the old one. I even deleted the ones that I don't have/need and replaced them in the text lines. Saved that and reloaded it into the AI Flight Planner and they reappeared not taking the changes I made. Other changes I made such as changing from Registration to Flight # were ok. This if for FS9.

The only thing that I can suggest is that it might be linked to the fact that the airfields compilation had to be redone completely.

I would suggest deleting the following files :-
AirportList.dat
StockAirportList_FSX.dat
AirportList_AddOns.dat

From the main folder only, NOT the StockAirportList_FSX.dat in the Base Data folder.

Then start AIFP and rebuild the indices by using Find/Collect Airports for the Stock Airports and then do the same for the Addon Aiports. Using the Scenery Library option for both.

It maybe that something is not being found with your current data. See if that changes anything.

Now the other thing is that you say the plan is not being updated. Is that the txt version of the plans or the compiled traffic file?