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

Boolean function a bit buggy

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,536
Country
netherlands
While testing the new simplify feature I was adding, I noticed that the boolean function in scenProc is a bit buggy at the moment. For my test area the feature detection sometimes gives polygons that are intersecting with themselves. A few builds ago this problem was not there, so I'm going to see when this bug was introduced.

This bug might also affect other steps that use the boolean function, for example split grid or replace polygon by building rectangles.
 
I have found part of the problem and reverted some code back to the older version. Now the detect features step should work again as before (although I will run a test on more data overnight to double check).

However the step to place rectangles for building footprints might produce a few more quirks now. I'll try to find a fix for that (without breaking the detection like I did last time :))
 
The test last night ran successful, so I think the feature detect functionality should be working as before again. I'll continue to check if the other steps still work OK.
 
You must log in or register to reply here.
Back
Top