question

Not much to add, but I can confirm that I had the same issue while trying to make water exclusion polys for a project yesterday. Behavior seemed a little more consistent for projects with only a few exclusion polys (though still a coinflip whether they'd appear correctly), and unaffected by other types of polygons (i.e. terraforming or vegetation).

There is a load order issue going on for water poly now, the same as what happened with the recently fixed photogrammetry and custom CGL bug in Feb '23
https://www.youtube.com/watch?v=6N-J1iwBHuo

I posted this in a hidden thread here with FlyingRaccoon, but I'm going to post it publicly as well so that you all can check on your end as well:

I went through my XML and saw that there are still water, vegetation, and terraforming entries bundled together into one polygon entry. This is all legacy polygon handling and as we know, each option should now have it's own dedicated polygon. So, I did an experiment..

I set a name for one of the polys that showed as being terraforming, but also had a water entry and found it in the scenery editor. Only terraforming was checked. Unchecked terraforming, checked water, unchecked water and checked terraforming again. Saved and the XML entry stayed the same.

Then I created a new polygon nearby and set it to terraforming and renamed it so I could easily find it in the XML. Only "FlattenMode" and "PreciseTerraforming" entries show up.

So, it appears that the scenery editor is not stripping legacy entries out of the XML when saving or even redoing settings. So, if you created any polygon features before this change was put in place many many updates ago, I would check your entries.

I have not yet attempted to strip all that out manually as I do not want to accidentally delete anything. I may isolate the different types of polys and then do it to see if it makes a difference.

Edit: I just noticed that I was viewing the wrong entry in the properties window, but I went back and checked and the story is exactly the same.

hi @FlyingRaccoon

Did you still need a package to repro this on ?

Here is another example of broken water exclude.

Prior to SU12 my Florida project worked with hundreds of water excludes of various types. The example I am showing here is part of the Key West harbor. Prior to SU12 water exclude was set to “water” (one would think it should be ocean, but only water worked) for all the polys shown. After SU12 none worked.

I have shown 4 photos of 4 polys where the water exclude has been changed to ocean 1 poly at a time. For the first 3 all goes well but add the 4^th and the first 3 all stop working. The same applies to other polys. You can get one to work but then others won’t. The permutations are endless and obviously not how it should work.

Why not have a setting which covers all water types for exclude instead of the different types? I can see the requirement for adding water of different types but not for exclude.

Here's an example near CYZV. Bad water data in the sim covers the islands with water, although the DEM rises the water. Water excludes have some effect on parts of the islands, but mostly they don't display.

Zip file of a project is included.

grandebasque.zip

A more descriptive example of this same area by Jean-Pierre Fillion is here:

https://www.fsdeveloper.com/forum/threads/exclude-water-to-unmask-island.457085/#post-914538

Hi! I also got this issue. But I was able to find a spot where the exclusion is partially shown? So I thought something was interfering with it. I started deleting stuff and all of a sudden it worked.....until I started to pan and move around. Then the water came back. Really annoying!

Hi @FlyingRaccoon Is anything happening on this problem? Please give us an update. Thanks

hi @Boris_

Are please able to get an update on this. There are a number of us with broken scenery that need to push updates out, the issues holding them from being released are now water polygons.

Even some information the fact it has been acknowledged and is being worked on would be handy.