EDDV has an exclusion poly for multiple categories. After upload it is constantly rejected with validation error. A re-download of that same scenery reveals that some vertices are moved close to the next full latitude degree and the poly is resolved to many polys with a single category each.
I'm facing similar (but not the exact same) problem with VTSY ... the scenery I've submitted has exclusion poly that doesn't match what ends up in Gateway.
I'm using "WorldEditor 2.6.0r2, compiled on Oct 30 2024 02:23:13" (on MacOS 15.3.1 on M1 Max in case that makes any difference).
I believe WED 2.6.0r2 should not be used for submitting sceneries with Exclusion Polys into Gateway, since there seems to be some problem with the data handling.
I confirm there is an issue here. I created a simple airport (identifier: TEST) with just a runway, boundary and four-node polygonal exclusion (Road Networks). After a round-trip from WED to Gateway to WED, the exclusion disappeared completely.
Markku Post-Uttula April 18, 2025 1:35 PM
I'm facing similar (but not the exact same) problem with VTSY ... the scenery I've submitted has exclusion poly that doesn't match what ends up in Gateway.
I'm using "WorldEditor 2.6.0r2, compiled on Oct 30 2024 02:23:13" (on MacOS 15.3.1 on M1 Max in case that makes any difference).
I believe WED 2.6.0r2 should not be used for submitting sceneries with Exclusion Polys into Gateway, since there seems to be some problem with the data handling.
Markku Post-Uttula April 18, 2025 1:36 PM
Hmm... my attachments seem to not have been included with my comment
Julian Lockwood April 18, 2025 6:52 PM
I confirm there is an issue here. I created a simple airport (identifier: TEST) with just a runway, boundary and four-node polygonal exclusion (Road Networks). After a round-trip from WED to Gateway to WED, the exclusion disappeared completely.
Julian Lockwood April 18, 2025 7:10 PM
I’ve attached what we are seeing at VTSY also.
Ben Supnik April 28, 2025 6:17 PM
Marco Auer @Julian the GOOD news is this is an IMPORTER problem - the data is CORRECTLY exported to the gateway.
Marco, the bug is buffer overruns. DSF2Text.cpp, line 419
char buf[512]; char prop_id[512]; char prop_value[512];This was written before polygon exclusions existed. 😞
For now a dumb band-aid would be to set these all to 4096 long buffer lengths…stack space is cheap in dsf2text.
Ben Supnik April 28, 2025 7:26 PM
(I can confirm the dumb band-aid does work.)
Julian Lockwood May 1, 2025 7:02 PM
@bsupnik Marco Auer Are you able to compile WED (with this fix) and create a new .exe release for distrubution to the community?
If so, I can subsequently enable the new version for Gateway uploads, and disable the existing WED version.