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

TaxiSigns in the Midwest

L

Lupo

Messages
35
Country
unitedstates
Hi Jon,
First this is a great tool, thank you for all your work!

I've been working on a small airport in the Midwest: KMLI. When I load the bgl (APX23170) into SDE (Version 00.90.2624) and open KMLI the ref TaxiSign displays its latitude out to only five decimals. This seems to throw off the rest of the signs as all the coordinates are off. So I can exclude the ref sign and place it a little outside the exclude without a problem. But now I have to place all the other signs by hand, not just the ones I need to move because if I paste them into my file they end up out in the corn field.:(

This could all be me of course but the short latitude seems suspect. The only sign that seems to be in the right place is the first sign in the list. This same behavior has been in the two previous versions as well.

In glancing through the APX23170.bgl the reference sign at KUIN displays only five decimals in its Longitude. I did not look further at that so I’m not sure if it causes the same trouble or not.

For that matter I don’t know conclusively if the missing decimal place is the problem at KMLI.

But something seems amiss.

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