Lyon Saint Exupery

The 3D attribute on the Gateway is probably being triggered due to the presence of the windsock. I believe there is a need to revise the WED/Gateway API accordingly, such that only expected 3D objects trigger the '3D' attribute on the Gateway.

Nope,
windsocks are not supposed to trigger the 3D tag. Only Objects, facades and forests will currently set the 3D flag upon submission and this airport has none.

I looked at the current code and tested re-exporting scenery 45651 to the gateway in WED 1.6, which does set the type field to "2D" just prior to submission (which is where I killed the program).

There is some DSF content, though - 4 exclusion zones. WED doe not take this as a reason to trigger any 3D flags, the gateway itself might Former user ?

Hi, I noticed the gateway triggers a 3D flag as soon as there is a DSF, so even when there are only exclusion zones. D you think you could change that?

@meikelm, the Gateway has a policy of "not looking" at the ZIPs that WED sends it. That is, it only knows what WED tells it about the scenery packs. (In this case, it looks at for a "type" of "3D" in the JSON that WED sends.)

In WED_GatewayExport.cpp, there's this line:

scenery["type"] = has_3d(apt) ? "3D" : "2D";

It looks like has_3d(), in turn, is true whenever we have an OBJ, facade, or forest. I guess a windsock is an OBJ?

Yup, this is the very line I checked - it results in "2D" for this airport, as intended.
Objects are only the .obj assets that go into the DSF ...

Are you saying WED sends type=2D for this, but the Gateway marks it as 3D anyway?

I say right now WED puts 2D into the request with teh airport loaded back from the GW + I can see no changes to the relevant code in recent WED versions ...

Looking at the ZIP blob right now for more intel if anything was different/wrong at the time of the original submission.

Nope, the DSF and apt.dat in the zip block don't look like there was anything else in the scenery just prior to original submission that fatefull day ... any object, facade or forest would have left at least a few bytes of evidence in that DSF.

Huh. Well, I can't repro with either WED 1.6 or WED 1.5 (which the pack was uploaded with). I tried downloading and re-uploading both the pack in question and its WEDbot parent, but both were correctly marked as 2D.

It's possible (albeit unlikely) that the 3D property was changed by mistake by one of the moderators. We don't have a log to tell us exactly what the Gateway received at the time of the upload, nor when any changes to its attributes might have occurred. The most I can say is... I've fixed it by hand now. :/

I only see '2D' submissions on the Gateway currently. Was there originally a submission marked as '3D' but subsequently manually changed to '2D'?

Yep---I just fixed the offending, wrongly-3D pack by marking it as 2D.

Got it - I thought at first I was seeing things and I closed the bug report, but then re-opened it I do think this bug report has merit because I have seen this happen before and I doubt I changed it manually from 2D to 3D (but 'tis possible). Anyway, as it could not be replicated, I think I'll close this one. Any objections?

No, no objections.

For tracking this down in the future (under the assumption this is a real problem, not a one-off mistake), I have two ideas:

• I could remove the ability to change the 3D attribute for moderators from the Gateway. That would at least let us be confident that any scenery submitted in the future doesn't get mistakenly changed. (Aside from correcting bugs like this, I can't think of any reason a moderator would actually need to change that flag.)
• If we could get the original WED scenery pack from the submitter, that would help. We could try re-submitting it to see if the Gateway again erroneously marked it as 3D, and if so, debug further from there.

I think we had some discussion a while ago where airports had only s very few objects in them, like a windsock object or some ground markings object (grunges from the LR default library). None of that is the case at this airport.

IIRC the outcome was that the moderator may want to demote to 2D in some cases, as there is no future-proof way to hardcode a list in WED to "ignore" certain objects.

So yes, close this until we get new evidence or find its not an isolated mystery.

Right - will close this one and seek the original WED submission as a zip file from the artist (who may or may not still have this of course). As for the 2D/3D switch, I have demoted a couple of airports from 3D to 2D historically - literally probably only two or three .. and then I stopped doing it because I was worried it might cause this kind of confusion later. In hindsight I think it would be better to take away the capability to change the 2D/3D flag from within the Gateway UI.

@Julian, I've removed the ability to modify the 3D status of an airport from the front-end.

Thanks Tyler !

I followed up with the original artist for this scenery pack, but it seems he has further developed the airport and it now features a bunch of custom objects - so it's no longer suitable for submission tests to the Gateway.

Yup this is expected for now... It will come later on.
It shows 3D because there are a couple objects though...

Current version in XPlane incorporates this change.