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

Huge planes sometimes visible in my sceneries ...

Sorry for the joke ;)

The XML code looks fine and compiles without trouble of course. I doubt it is only the taxisigns that cause this problem, as we would have seen it before in that case.

Are you sure you do not have conflicting XML-format BGL files that all define the same airport? I have seen strange things happening when you define the same airport twice. In general you need to be very careful with that.

Another thing (you might have already tried this, but I am too lazy to scan this entire thread). The sign BGL gives you the trouble, but does it also do so when you use only the sign BGL (without the rest of your scenery)?
 
No problem about the joke! :)

Yes, one tester analysed the situation in that way and only put there the sign bgl. He saw the default airport with some additional signs and got also the bug, so it MUST be the sign bgl.

Right now I'm doing the sign from a clean XML file in createSign with just the given aiports coordinates from the stock airport. This time, I used the minutes and feet in the coordinates ... lets cross the fingers ... :wave:


EDIT: Now the beginning of the file looks like that (and the airport data is from AFCAD):

Code: 
    <Airport
         lat="N48 41.4000"
         lon="E9 13.3167"
         alt="1267F"
         ident="EDDS">
    <TaxiwaySign
       lat="N48 41.1894"
       lon="E9 11.5578"
       heading="345.12"
       label="d[&lt;Z M&gt;]"
       size="SIZE3"
       justification="LEFT"/>
    <TaxiwaySign
       lat="N48 41.1653"
       lon="E9 11.5484"
       heading="340.31"
       label="d[&lt;Z M&gt;]"
       size="SIZE3"
       justification="LEFT"/>
    <TaxiwaySign
       lat="N48 41.0060"
       lon="E9 12.0495"
       heading="168.33"
       label="d[&lt;Y]l[Z]"
       size="SIZE3"
       justification="LEFT"/>
 
Last edited:
If it is only the sign BGL, can you sent that one to me? I would be interested to take a look at the file.
 
Hey Georg,

No idea why I missed that!

Before you break your back redoing the whole sign file, just try the old one with the simplified airport header. That *should* take care of it!
 
I released the scenery two days ago and the problem seems to be fixed - at least none of my testers reported it again. The solution seems to be the airport altitude which should be set in feet and not in meters (maybe also the header has its influences). FS seems to use feet internally and convert altitudes in meters and therefore the altitude has always some minor differences if given in meters.

PS: The word "seems" is used quite often in this post as I do not really know what the problem is an how it is solved ... but it "seems" to be working ... ;)

Thanks a lot for your affords, Dan an Arno :wave: :wave:
 
Hi,

I haven't reed all the replies, but I just had the same problem: a dark shadow over my scenery appears when I look around in outside view in the direction of the lightpoles I made. When I look in top view, I see it too.
This big shadow disappears when I delete the lightpoles and change them by another model less complicated. Or this lightpoles are somewhere corrupt.
Is there an explication for this ?

Greetz. José.
 
Georg Aubele said:
That problem in my scenery was related to the taxiway signs!
Click to expand...

Hi,

Sorry, this topic is so large.
My problem is solved. Using FSRegen for making API's (FS2002), I forgot to choose "library" in the rollout menue. And so I got a "light" file which causes the problem.

Happy Easter. José.
 
Just to give all interestet an update: It seems to be related to little typos, that the compiler lets through, like a wrong bracket or spaces. Why does the compiler not warn me?!?

I had the problem again in EDDK and by looking on every line of the taxiway sign XML, I found a bunch of typos. correcting them, the planes seem to disappear ... let's cross the fingers!
 
You must log in or register to reply here.
Back
Top