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

FS2004 Wrong units after reload (ft <-> M)

Thanks Don, I have to recreate the situation before my 4505 test first. (backup my results and soon..)
Sorry, if I am to slow...
 
I tested 4508 in a new 4505 installation with no luck.
An email is on the way (28MB) with scenery Folder, 2 screens and AFLT folder
 
Perhaps you should tell me what problems you experienced. 4508 definitely fixes the "input error" and I'm unable to reproduce the "wrong units" issue with it issue. It's helpful to know if something is fixed.

I note in one of the packages you sent you also report a compiler error, which I will investigate. But, my investigation would be a lot easier if you had sent me your project folder for EDMO (it contains info about the failed compile as well as the lighting data). Presumably, the airport .bgl is unchanged from a week or so ago., and that's why you didn't send it again. Also, in the absence of any further issue report, I'm curious as to why you sent airport scenery and your entire AFLT folder.

Please, please, please - as I asked only yesterday (repeating a similar, earlier request) when you report an issue with AFLT, include the Project folder and the airport .bgl. Making me ask for them often delays the diagnostic process.
 
In Project.ini in the Project folders, there's a line starting with "Make Library For=". If the appended value is -1, set it to 0.
 
gadgets said:
Please, please, please - as I asked only yesterday (repeating a similar, earlier request) when you report an issue with AFLT, include the Project folder and the airport .bgl. Making me ask for them often delays the diagnostic process.
Click to expand...
I did send you the project folder (AFLT4508A.zip), please check it
 
That may have been your intent. But AFLT4508A.zip contained the whole of your AFLT folder, strangely without the Projects sub-folder. Perhaps you inadvertently moved the Projects folder elsewhere. thinking you were copying it into AFLT4508A. That's why I noted above "I'm curious as to why you sent airport scenery and your entire AFLT folder.".

Just to be sure, when I ask for the Project folder, I am referring to the airport-of-concern's sub-folder in the Projects sub-folder. Also, when I ask for the airport .bgl, I am referring to the file compiled by ADE containing the airport elements (runways, taxiways, etc.)
 
Yes, you are right, I was lost in the "war of versions".
I found the project folder in another folder. I hope this one is useful.
 

Attachments

This one fixes the crash in the Make Library dialog. I have confirmed a successful compile with the data in the project folder you sent.
 

Attachments

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