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

Georg Aubele said:
Dan - no success here :(

I even used JABBGL to view and change the altitudes inside the BGL's

Now the values are:

Stock airport: 386.181
SGX BGL: 386.181
Taxisign BGL: 386.181

And again the first tester reported the bug :mad:

The first value strikes me!

I decompiled the AP950140.BGL with BGLXML and there is clearly visible the value "386.18" and nothing more! But JABBGL shows the value "386.181" for the AP950140.BGL :confused: :confused: :confused: :confused:

Therefore I changed all values to that one, but the bug remains. It seems, it has it's origin very often in Runway-Signs (the red one with the yellow letters).

Question: Do you use spaces between the letters and digits? In the SDK-document nothing is written about, so it should be allowed. But the examples are all without spaces:

"m[11R-29L]"

I used "m[ 11R - 29L ]"

Again the question if that could be the source of the problem ... :confused:

I will rewrite the taxisigns without spaces and report back ...
Click to expand...

Georg,

Do the testers say that the problem goes away if they just remove the SGX bgl? I wouldn't want you to waste your time!
 
They say it goes away, when the don't use the Taxisign.bgl

Still Mesh and flatten areas are suspects ...

two testers reported that the bug is not there anymore, when they disable the mesh they installed ... they have different meshs
 
Last edited:
Georg Aubele said:
They say it goes away, when the don't use the Taxisign.bgl

Still Mesh and flatten areas are suspects ...

two testers reported that the bug is not there anymore, when they disable the mesh they installed ... they have different meshs
Click to expand...

Quite odd.

Ok, I would tell you testers to do this. Disable every bgl except the flatten. Then add the mesh, then the taxisigns, etc. until the problem comes up.

And by the way, I looked at some of the taxisigns I have created and I don't see any spaces.
 
Georg Aubele said:
As I use SGX, the flatten is inside the BGL with all the objects ...
Click to expand...

Never mind then! Might want to start splitting up that XML.

This is how I learned the hard way - now I always make multiple bgls. Much easirer for testing!
 
Georg Aubele said:
How do I recognize the flatten in the XML, can't find anything in the SDK doc! :confused:
Click to expand...

You can not create a flatten with a XML file. Some elements like aprons create an automatic flatten, but user defined flattens are usualy LWM polygons.
 
Georg Aubele said:
No, why should I?
And I don't use a LWM ... is this necessary? Never saw that before. :confused:
Click to expand...

You don't have to, it's just one of the methods used, so it could be why it wasn't in the XML.
 
I don't expect the flatten has anything to do with this bug (although it is a weird bug, so it could be almost anything). So if you haven't missed a flatten until now, I don't think creating one would really help.
 
Once again me with news:

All three beta testers havin the bug now reported that the bug is gone, when they deactivate their meshes. I'm just beginning to read the docs to Ground2K, but I hope, I can solve the bug with this little tool.

Any other recommendations?
 
Are they all three using the same mesh scenery?
 
Some new things that strike me:

I thought about flattens tonight (as you can see from the time of my last post :D ): Arno said, that taxiways, aprons and so on do their own flatten, but when I start FS2004 in Bird view, I get a much larger area that is flat - where does it come from? :confused:

EDDS_Bird.jpg




And another thing: I found a flatten feature in SGX (SCASM code). When I make one and compile the scenery, I get a new BGL - that's okay, but when I start the sim afterwards, the other BGLs are ignored! No other objects are shown then the ones in the SGX BGL. Could it be a naming problem?
 
Georg Aubele said:
Some new things that strike me:

I thought about flattens tonight (as you can see from the time of my last post :D ): Arno said, that taxiways, aprons and so on do their own flatten, but when I start FS2004 in Bird view, I get a much larger area that is flat - where does it come from? :confused:

EDDS_Bird.jpg




And another thing: I found a flatten feature in SGX (SCASM code). When I make one and compile the scenery, I get a new BGL - that's okay, but when I start the sim afterwards, the other BGLs are ignored! No other objects are shown then the ones in the SGX BGL. Could it be a naming problem?
Click to expand...

The large flat area is probably the default MS one. Also for the SCASM flattens I make in FSSC I get two bgls - do you only get one?
 
You must log in or register to reply here.
Back
Top