• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Please Report Issues With Version 1.6 in This Thread

Any sub-24hr flight plan must complete within the repeat period.

By setting the departure time of the return leg to 0200, you were forcing the total time required for the FP to 2 hrs plus the return time, which is a no-no. When you set the departure time of the return leg to 0100, you were "within the rules".

Don
 
gadgets said:
Any sub-24hr flight plan must complete within the repeat period.

By setting the departure time of the return leg to 0200, you were forcing the total time required for the FP to 2 hrs plus the return time, which is a no-no. When you set the departure time of the return leg to 0100, you were "within the rules".

Don
Click to expand...

Ahh, well that makes sense then. Knew i was being dumb
 
Confused....

Just downloaded and unzipped version 1.6.18 and I note the AI_Flight_Planner.exe (434 KB) is dated 4/30/2009 while the "older" version AI_Flight_Planner.exe (434 KB) is dated 5/15/2009. Further, when I run the "new" version it says "there is an update available, do I want to download now." This is becoming tedious.:confused:
 
Geezer, we're having trouble with the server. Please see the thread announcing version 18.

DOn
 
Cannot enter departure time

I am using the latest released version and when I get to the box where you enter the departure time - based on anything other than a 24 hour repeat - I get an error message saying the time format is incorrect for this repeat period.

Am I missing a step somewhere or ???????
 

Attachments

  • ScreenHunter_110.jpg
    ScreenHunter_110.jpg
    66.9 KB · Views: 515
I am using the latest released version and when I get to the box where you enter the departure time - based on anything other than a 24 hour repeat - I get an error message saying the time format is incorrect for this repeat period.
Click to expand...
0900 is not a valid time for a two-hour repreat. Please refer to the second last paragraph of section 7.21 of the user manual.

Don
 
gadgets said:
0900 is not a valid time for a two-hour repreat. Please refer to the second last paragraph of section 7.21 of the user manual.

Don
Click to expand...

As I read the documentation -

"When a sub-daily repeat period is selected, the hour value of the arrival and departure time entries must be less than the repeat period. For example, for a repeat period of 4 hours, the maximum acceptable arrival or departure time is 03:59."

It is saying that I cannot create a flight plan which repeats every two hours and select my own starting departure time. Is that correct?

If not, then how on earth do I create one - that starts at 09:00 (as an example) ?? I really do not want to have it start at 03:59 or some lesser value.

I hope I am not being to dense but a restriction like that makes no sense to me and I have not seen such in other flight plan creators.

I appreciate your patience.
 
then how on earth do I create one - that starts at 09:00 (as an example)
Click to expand...
You can't. A two-hour-repeat flight plan runs every 2 hours, i.e., 12 times a day. You can only specify deparure and arrival times within the two-hour period. (This is not a AFIP restriction; this is how flight-sim works. According to its documentaton, TTools also applied a similar constraint.)

If you want a flight plan that starts at 09:00 and repeats every two hours until, say, 2100, then you've got to create several 24-hr plans, one starting at 0900, another at 1100 and so on.

Don
 
gadgets said:
You can't. A two-hour-repeat flight plan runs every 2 hours, i.e., 12 times a day. You can only specify deparure and arrival times within the two-hour period. (This is not a AFIP restriction; this is how flight-sim works. According to its documentaton, TTools also applied a similar constraint.)

If you want a flight plan that starts at 09:00 and repeats every two hours until, say, 2100, then you've got to create several 24-hr plans, one starting at 0900, another at 1100 and so on.

Don
Click to expand...

Well Don - I have been doing it for several years with no issues having TT compile them.

Here is an example of a 1 hr repeat which I use often for testing new aircraft:

AC#1,OPAXXX,5%,1H,VFR,14:00:00,14:15:00,030,F,1013,KDAL,14:00:00,14:15:00,030,F,1013,KDAL

Note the second leg is an exact duplicate of the first - FS2004 will ignore the second leg in such cases - giving me a 1 hour repeat of the "out and back" flight starting at 14:00 GMT.

The creator I normally use (by Dave Westbury) is for FS2004 only and I was really hoping that I could use your Flight Planner to create similar traffic files for FSX - but unless I am comparing apples and oranges, it seems a flight plan such as the example above it not possible to create using Flight Planner.

Hope this helps you understand what I have been attempting to do.
 
Here is an example of a 1 hr repeat which I use often for testing new aircraft:

AC#1,OPAXXX,5%,1H,VFR,14:00:00,14:15:00,030,F,1013 ,KDAL,14:00:00,14:15:00,030,F,1013,KDAL

Note the second leg is an exact duplicate of the first - FS2004 will ignore the second leg in such cases - giving me a 1 hour repeat of the "out and back" flight starting at 14:00 GMT.
Click to expand...
I created a FP file using your flight plan, added an airports and aircraft files and compiled with TTools 2.21. You're right! It does compile and it does give you a flight plan that starts at 14:00. But, it also gives you a flight starting at 00:00, 01:00 ... 22:00 and 23:00. To be sure what was going on, I decompiled with TTools the traffic file I had just made. Sure enough, the 14:00 departure time had been replaced with 00:00, i.e., the AI engine had no "knowledge" of the original 14:00 departure time.

The only difference between AI Flight Planner and TTools in this case is that AI Flight Planner limits departure to a time within the repeat period (as noted in the documentation) and, if warnings are turned on, AIFP will complain that the departure time of the second leg is earlier than the arrival time of the first (which in thios case, it is).

To create an equivalent flight plan using AIFP, all you need do is set the departure time to 00:00, and suppress warnings is you don't want to be told about the second leg. Another way to avoid the warnings is to set up the FP as a TNG with an appropriate departure time for the second leg.

Don't know where I got the idea that TTools wouldn't compile yopur FP - but then, there's been "a lot of water under the bridge" since I started AIFP.

Hope this helps,
Don
 
Looks lika a Bug found in V. 1.6.21

After downloading the latest version yesterday, I tried to do an "arrivals/departures" function (in the fsx stock traffic file - airport BGSF).
After about 5 seconds I got an error message "out of memory". After several tries with the same result, I reverted to version 1.6.20 and voila...arrivals/departures works beautifully.

Hope this one won't be too difficult to fix.

thanks. You've got a great product

Geezer
 
Hi,

Have the same problem after loading a second flightplan and checking the departures/arrivals. Never noticed it until now.

Roby
 
In Version 21, I fixed arrivals/departures for sub-24 hour FPs but broke it for 24hr FP.

A new release will be posted shortly.

Don
 
AI Flight Planner doesn't handle boat traffic....
Click to expand...
Nor was it ever intended to.

Ok, it's not a problem with AI flight planner more of a request
Click to expand...
I'm extensively involved in another project right now, so it will be a while before I can look at this.

My expectation is that adding this capability would constitute "major surgery", with significant changes to both program logic and the compiler. Should that be the case, its not likely to be done unless it becomes a "hot issue" for an number of people.

Don
 
May I have some cheese with my whine?

Sorry, gadgets....just need to whine some more....

It appears that when you fixed the problem with version 1.6.21 with the release of 1.6.22, things, (arrivals/departures) went back to the way they were in 1.6.20, (i.e. does not show all iterations of a sub-24hr FP, only shows once)


Thanx

I.
 
I've just checked it on my system and all sems OK. Would you please send me a traffic file that exhibits the problem.

Don
 
gadgets said:
I've just checked it on my system and all sems OK. Would you please send me a traffic file that exhibits the problem.

Don
Click to expand...


Yessir...the small but questionable file set is (or should be) attached.

It's small because I've just started with it....most of the plans are 12Hr repeat, but they're only showing once.

Thanx again

I.
 

Attachments

Geezer, I'll get it right soon. What's happening is that the last cycle doesn't get shown. Since there's only two cycles in a 12 hr repeat, only one is shown. If you check a 4hr repeat, for example, you'll find only five cycles are shown rather than 6.

I'll get an update out shortly.

Don
 
You must log in or register to reply here.
Back
Top