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

FSX SbuilderX and AB_ExcludeAutoGen Poly

rhumbaflappy said:
At this point, I would remove all addons and systematically reinstall them, to find the problem. Make some notes as you reinstall.

This is obviously a conflict with addons. I suspect it is caused by a GUID number duplicated by an addon. For example, a GUID for a windsock could be compromised by using the same GUID for another type of object. Just a guess, as I do not have that combination of addons.

Don't think GEX is not causing problems, as it may well be the source of the conflict, as could any of the addons you have.

It could also be caused by a bad airport bgl. In the past, I have had issues with bad airport bgls causing problems at scenery areas many kilometers away. So the problem may not be at EHAM at all, but at some other airport ( which might explains why such a large exclude rectangle is needed).

I don't think you'll get any more help than has already been offered. It's very hard to solve these types of problems, as no one else has your combination of addons.

Dick
Click to expand...

Dick, I thought my combination was rather standard. But I agree most tend to use rather UTX and much less SceneryTech. AmsterdamX and GEX Europe are very popular though. Anyhow I'm very much thankful for your time and thoughts that you, guys, shared in my thread on this rather technical forum. Besides, I've learnt something about tip of the fsx scenery iceberg. :banghead:



Thanks,
Sabre.
 
For what it matters the problem was fixed by removing SceneryTech land class and installing Open VFR's LC instead:

SceneryTech:
Sparce.jpg


Open VFR:
fsx2012-08-2410-03-43-59.jpg


Also the LC by Open VFR looks much better in Europe, and it's a newer product.

I think rhumbaflappy was right suggesting some numbers were mixed up or some bad bgl was causing the problem.

Thanks,
Sabre.
 
rhumbaflappy said:
Don't think GEX is not causing problems, as it may well be the source of the conflict
Click to expand...

rhumbaflappy, you were spot-on. GEXE was causing the conflict in this combination: AmsterdamX + STLCEu + GEXE. I had to remove either STLCEue or GEXE, so I ended up removing STLCEu.

The same buildings popped up right away in P3D with AmsterdamX+GEXE. The developer of GEXE do not support P3D at the moment, so this is no problem for them.

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