• 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.

Problem designing weekly flight plans

A

Adrien1004

Messages
3
Country
france
Hi everyone,

First I'd like to thank you all for the great work you're doing, and for sharing it for free with all FS-lovers. You rock !

I'm using AI Flight Planner with FSX, and I am getting trouble writing weekly long-haul flight plans. Let's take an example. I would like a boeing 747-400 to fly from Paris CDG to Taipei CKS several times in a week; I set the first leg as follows :

Departure on monday at 11:15 AM (LFPG) - Arrival at Taipei (calculated by the software) at 05:18+1

But when I move this leg into the flight plan building window (by clicking on "add leg"), it shows 05:18+7 as arrival time, as if it took a whole weeek to cover the distance... It's always the same, no matter which plane or asian destination I use.

Could anyone tell me why and how to fix it please ?

Thanks !!
 
Don will have a better answer but...I believe this is just the way AIFP deals with time periods, and not an error. Complete your FP and it should work. You might try working in GMT rather than local times, just to get a feel for how things work.

Bob
 
Glad to have you back, bobbyjack. Adrien,this shouldn't happen. Something's gone wrong in the converstion of local times.

I'm planning another release for later today. It will be fixed in that release (which may not happen now until tomorrow).

Don
 
Don

A couple of months ago I did a major overhaul on my FSX box and wiped out everything. I wanted a fresh start. I just this past week got an addon airport complete enough to have traffic go to it. I've been following the forum but stayed out of the way. I see you've changed a number of things. I haven't worked much with local times so I haven't seen much of Adrien's problem. I noticed that there is still a pop-up when I compile a FP that uses an addon airport that the airport may not exist, or that it requires scenery(or something like that). Is this really needed because if you enter an airport, while creating a plan, that is not in the airport.dat you are prompted to add it?

Bob
 
Adrien, I'm happy to say I've found the error causing your problem. It was something I missed when I did the redsign between versions 1.4 and 1.5. It only affects flights that are airborne at midnight. It will be fixed in this evening's release.

BobbyJack, it would seem to me that if someone attempts to compile a file with a missing airport after having been told on the problem, they need the reminder.;)

The real reason it's there is because if you're trying to compile after you've been told about the missing airport, you likely think you've fixed it, but haven't. Better (from my standpoint, at leaast) to have a potentially superfluous error message than numerous reports of "my file won't compile."

Don
 
I completely understand the popup if the airport does not exist, but these are airports that are already in the airport.dat list. They just happen to be addons. Not a big deal. Better to be safe than sorry. It just always makes me think I've done something wrong (again :D)

Looking forward to the next release.

Bob
 
BobbyJack, I'm not sure I know to which pop-up you are referring. You should get such a warning in three instances only:
  • the airport is not in AirportList.dat;
  • the airport is in AirportList.dat but no positional data is available for it; or
  • the airport is available but only for either FS9 or FSX and you are compiling for the other.
All these situations seem to be legitimate.

Is there another I've forgotten about?

Don
 
Don

KBOB, is my addon that is in FSX. there is scenery, positional data, and it is in the airports.dat file. Whenever I compile any of my addons,I get a screen like this. AIFP compiles successfuly. If this popup is your intention then thats fine, but it doesn't seem to be needed in this case.

Bob
 
Last edited:
Two things:
  1. Airports in AirportList.dat are designated as being available for FS9, FSX or both. This is set initially when the add-on airports are collected. If you compile for a version that is not designated in AirportList.dat, a warning is generated. It would seem your AirportList.dat designates the airport being available in FS9 only. If is is also available for FSX, you can so designate using the Airport Editor.
  2. At the bottom of the Airports menu is a item named "Identify Non-stock airports on Compile". If that item is checked (which it should be if you are getting that message), warning messages from (1) above are output. If not checked, these messages are not (should not be) output. Is your's checked?
Don
 
Oh man! Yes mine is checked. Is that a default setting? I just downloaded this version last week, and don't remember checking that.

No FS9.

I suppose your going to tell me that that setting has been in AIFP all along.

Bob
 
Last edited:
Bob, Don,

Thank you very much for your replies.

I'm downloading the new release today and will let you know soon if it could fix the problem on my computer.

Have a nice day !

Adrien
 
Hi everyone, and once again thank you for your help !

Unfortunately, the problem is occurring again...
I am now using AIFP 1.58c, and it is often impossible to design weekly flight plans, depending on the chosen departure time. For instance my flight EGLL-->RCTP works if the aircraft leaves at noon, but doesn't if I set the departure time at 23:00... The "+1" showed on the build-leg-line actually disappears when I save the changes to the flight plan. And things get even tougher when I try to design east->west FPs.

Is there any way to fix this ?

Have a nice day !

Adrien
 
Adrien, I acknowledge there are still problems in 1.58 converting to and from local time, particularly where midnight transitions are concerned (though I didn't think so after applying the fix in response to our last round of communications).

This is one area at which taken a very close look in 1.6 (now in beta trial). I've reworked that code a couple of times now, each time finding a way to simplify it and, at the same time, finding some problem in the eliminated complexity. It's now very simple and I think I've finally got it right.

But, with 1.6 only a week or so away from release, I'm reluctant to retrofit the changes back into 1.58. While he code is now much simpler, its effects are widespread.

So, I'd ask for your indulgenmce for another few days.

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