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

Aifp 1.6.12

Messages
1,268
Country
us-hawaii
Don --

I installed 1.6.12. I loaded in the bad flightplan fileset that I had saved previously, did the edit to fix the bad leg time (same as previously) and then "update fp in list". I did NOT get an exception :) Then I saved the file set and looked at the flightplans, and the edited leg times were accepted and are correct. I then repeated that process for all flightplans and at the end, passed validation and saved correctly.

I still have to test and see if I can recreate the original problem, that messed up the leg times initially.

scott s.
.
 
No need to test further. I know what messed-up the times originally and have already fixed it. (See 4th to last post in previous series.)

While I still can't be sure what was the underlying cause of the exception, I know which line of code actually created the error. I have added a test to ensure it won't happen again.

So, enjoy the weekend.

Don
 
Back
Top