• 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, Please, Please, When you Report an Issue ...

Status
Not open for further replies.

gadgets

Resource contributor
AIFP has often been referred to as the "Swiss Army Knife" of flight planning tools. As of today, AIFP incorporates over 45,000 lines of code in over 60 modules (I just counted them following today's general release) and a complement of features too numerous even to estimate - many of which I've forgotten about after >8 years of continual development and enhancement.

So, it should not be surprising that, when someone sends me a vague description of something they perceive as a problem, I have to ask for more detail. (Check almost any forum thread.) This is not only wasteful of my time but is frustrating to those reporting such issues.

I appreciate many of you have your own names for AIFPs functions. Such terms are often general in nature and, complicated by your native tongue, sometimes meaningless to me.

When you report issues, please be specific. Use the terminology AIFP uses - exact button, field, menu and dialog names and error messages. It is helpful - and often essential - for me to be aware of what you did several steps prior to the situation of concern manifesting itself in order to duplicate the problem. Check if the situation is repeatable. If it is, tell me the steps you took to duplicate the situation, so I can do the same without guessing. (If I can't duplicate an issue, it's unlikely I can fix it!) If the problem relates to a specific flight plan/aircraft/etc. attach the data or a link to it. Don't be concerned about too much information.

Finally, I also often get asked what will AIFP do in a particular circumstance. Why ask? Try it and see. You can't do any irrecoverable harm.

Best wishes to all for a very merry Christmas and a happy and prosperous New Year.

Don
 
Status
Not open for further replies.
Top