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

Missing autogen around airport after compile

Thank you Don,

with a 200m setting, compile is OK.

I have tried several values between 200m and 500m, but some trees are still missing.
 
I've found the problem with 100m and will have a fix available shortly.

Don
 
Hi,

If it is only a few trees missing, it's sometimes better just to plant a few library object trees in the bare spots.
 
tgibson said:
Hi,

If it is only a few trees missing, it's sometimes better just to plant a few library object trees in the bare spots.
Click to expand...

You're right, I will do that, but I can imagine that it's not satisfactory for Don.
 
Compile with the latest release (0.0.96(q)) doesn't prevent autogen from disappearing, even with 100m groups.
 
Compile with the latest release (0.0.96(q)) doesn't prevent autogen from disappearing, even with 100m groups.
Click to expand...
Compiling in groups doesn't prevent autogen suppression. Groups only minimize suppression.

There is no autogen anywhere near your round polys in the file you sent me, so I have no way of assessing autogen suppression at your airport. With 100m groups, autogen should not be suppressed (due to ground polys) more than 70m away from the edge of the group. If autogen is being suppressed beyond that point, then I'd suggest you look for other causes.

If you want me to pursue this further, I'm going to need whatever you are using to generate autogen in the vicinity of the runway/aprons.

Don
 
Don,

autogen is suppressed at 200m from the edge of a polygon, I don't know exactly where the edge of the group takes place. I will send you a screenshot in order to show you the position of the trees concerned.

When the ade-gp bgl is not active, the autogen is complete.
 
Jacques, a screenshot of your ADE display doesn't help me much. What I asked for, and what I need is
whatever you are using to generate autogen in the vicinity of the runway/aprons.
Click to expand...

There appears to be a large default flatten that is inhibiting all autogen over a wide area. Unless I have the file that you are using to replace that autogen, there's little more I can do but assure you that, if you compiled in 100m groups, autogen suppression due directly to the GP bounding boxes will not extend beyond about 70 me from the edge of any GP item.

While I'm not disbelieving you that autogen is being suppressed further away than that, I suspect that what you are experiencing is some indirect effect. For example, if you've used some utility to replace the autogen, perhaps a simple overlap of some portion of the bounding box and the area to be covered with autogen is sufficient to suppress autogen generation over the entire area.

Without the files to generate the same autogen that is being suppressed, there's nothing more I can do.

Don
 
gadgets said:
Jacques, a screenshot of your ADE display doesn't help me much. What I asked for, and what I need is

There appears to be a large default flatten that is inhibiting all autogen over a wide area. Unless I have the file that you are using to replace that autogen, there's little more I can do but assure you that, if you compiled in 100m groups, autogen suppression due directly to the GP bounding boxes will not extend beyond about 70 me from the edge of any GP item.

While I'm not disbelieving you that autogen is being suppressed further away than that, I suspect that what you are experiencing is some indirect effect. For example, if you've used some utility to replace the autogen, perhaps a simple overlap of some portion of the bounding box and the area to be covered with autogen is sufficient to suppress autogen generation over the entire area.

Without the files to generate the same autogen that is being suppressed, there's nothing more I can do.

Don
Click to expand...

You have an email
 
Jacques, I've now tested with your files and can find no difficulty. On my system other than the ground polys not being there, I can see no difference between the ground poly .bgl being present or not.

I am sending you some screenshots via e-mail.

Don
 
Don,

I can't understand what's happening but after installing the latest AMD driver I can't see any autogen suppression ! :banghead:
 
I'd say "3 cheers"!

FSX has no native ground poly processing. We're fortunate FS8-style ground polys still work (most of the time). But FSX (and it's companion processes) determine what actually gets displayed.

All ADE_GP can do is output ground polys in FS8 format - partitioned to meet FSX's 100m. requirement - and minimize other known issues, such as bounding box size.

Beyond that, it's "magic".

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