Are you having problems with missing jetways all using Xbox ?
-
The scenery worked perfectly fine until SU5, which introduced bugs with jetways.
-
We made a workaround fix the DAY SU5 came out, which eased the problem on PC, but still some jetways randomly disappeared because it was an SU5 bug so, there wasn’t anything we could do to fix it entirely in SU5. Even default jetways at default airports sometimes disappeared, depending where you started your flight.
-
The bug HAS been fixed with SU6 so, right now, EACH and EVERY FSDT scenery has fully working custom jetways, confirming the bug has always been in the sim all along, and there wasn’t any problem with the sceneries to begin with.
However, all of this is ON PC and yes, I can see missing Jetways on Xbox now, on the same scenery that works fine on PC.
Maybe it’s not entirely clear how we are supposed to “test” a product on Xbox and, the reality is, we simply can’t.
We had a Beta period for SU6 on PC, in which we confirmed the Jetway bug WAS fixed on PC without any need to do any changes to the sceneries, but there was no Beta for Xbox so, we had to wait for SU6 public release first, then download our sceneries from the Marketplace like everybody else.
The general rule is that, if something works on PC, it should work on Xbox too but, apparently, this is not really the case. The Scenery Editor in the SDK has only ONE setting to “simulate” a specific Xbox behavior related to LOD and, of course, Jetways at LSZH (and other sceneries) shows perfectly fine both using the default LOD behavior AND the Xbox LOD behavior. So, using all the tools we have in the SDK, nothing indicates jetways shouldn’t work on Xbox or should be made any differently than on PC.
This leaves with the following explanations:
-
The jetway bug has been fixed in the PC version of SU6, but not in the Xbox version.
-
There’s something different related to jetways to take care of that is specific to Xbox and cannot be checked in advance with the PC SDK, even in Xbox mode, which hasn’t been documented. The release notes for the SDK promised to include a new Jetway sample and in fact, the default jetways has been updated, but the 3DS Max source file for the default Jetway disappeared from the SDK, we don’t know if this was an omission, and we surely reported it to Asobo. Other than that, nowhere in the SDK there’s any indication that something different should be made to have Jetways working on the Xbox, other than the general suggestions of using at least 3 LOD levels, which we obviously do.
-
Microsoft might have placed the wrong version on the Marketplace for Xbox. We don’t know if this is possible, since we only send a single file containing the package, which of course works perfecty fine on PC. However, since there’s no way to access files on Xbox (not even using Xbox Dev Mode, which I have but doesn’t work for commercial games), we don’t have any way to check if the files released on the Marketplace are the same we submitted. Yes, there’s the version number but, that alone won’t tell for sure if every file is correct.
So, the only solution I see is asking Asobo for help, sending them the sceneries to test so they might figure out what the problem is because, assuming the Marketplace version IS correct, it seems the general rule that “if a scenery works on PC, it will work on Xbox”, doesn’t seem to work here.
And, until the Public released of SU6 for Xbox, there was no way for us to even KNOW, since we don’t have any way to test antyhing on Xbox, there was no Xbox beta, and everything works perfectly fine on PC right now and all along during SU6 Beta.