Spent a few frustrating hours last night trying to solve a problem where all of the SODE jetways in a new install of ImagineSim's KLGA/New York LaGuardia were missing.

As part of a complete system rebuild, I downloaded a fresh installer using their Operations Center, configured it for SODE jetways, and there was nothing but a bunch of black holes in the terminals where the jetways should attach.

Turns out the xml placement file ImagineSim included in the scenery was borked...all the jetways were set with a base altitude of 0.0m, so they were there, but buried underground.  A global replace of Alt="0.0" with Alt="22.00" in the xml file (located in C:\ProgramData\12bPilot\SODE\xml) fixed the problem.  It was also necessary to make the same corrections in the xml file located in the SODE subdirectory of the KLGA scenery folder, as it appears any time you use the configurator to select SODE jetways, it copies that file over to the 12bPilot SODE xml folder.

I've made ImagineSim aware, but posted this just in case anyone else is pulling their hair out with this one.

Regards

Thanks for the update.  Whats up with these developers not testing properly

Edited November 12, 20187 yr by Skywolf

Hi Bob,

I am experiencing the same problem when using SODE at ImagineSim's KLGA. I followed your instructions and modified the entries and can see the the jetways but when I do, the jetways no longer work with GSX. Have you experienced the same situation?.

This is driving me mad and ImagineSim's reply is that another scenery is messing with KLGA's elevation... Except that the jetways show correctly when they are static.

Please let me know. Regards,

Christian Conesa

Just a thought, are you guys using their most recent installer? The one that lets you activate the SODE jetways in their own "Operations Center" configuration utility?

On 11/30/2018 at 9:33 PM, jalbino59 said:

Just a thought, are you guys using their most recent installer? The one that lets you activate the SODE jetways in their own "Operations Center" configuration utility?

Yes, I am.

A further thought, other than the correct altitude of the SODE jetways, I found that the jetways will work fine within SODE but not with GSX. I wonder if GSX is creating a conflict somewhere...

I updated my Imaginesim sceneries yesterday, I had several according to their operations center, and I found that the updated installers were adding a second set of xml and simobjects for KLGA in the SODE folders.  The old stuff has to be manually deleted.  Not sure if this is causing a problem for anyone but it is related.

When I was done all SODE jetways looked and worked as expected.  Didn't even thing to try to see if GSX would operate them.  Give the choice I'd rather operate directly without GSX anyway.

I later found I was also having problems with no runway edge lights at KLGA.  I did a LOT more troubleshooting, and the problem turned out to be the way ImagineSim had added their elevation correction file--using an xml entry rather than placing the elevation bgl into the scenery\world\scenery folder.  At least for me, that elevation correction has no effect as it is placed by the installer.  I moved it to the scenery\world\scenery folder, removed the entry from the relevant add-ons.cfg file, and went back to their original SODE xml file, and now everything seems to be lined up.  If, while sitting on the ground at KLGA, you are seeing an elevation of ~21 ft instead of zero, you probably also have this problem.  With the problem, the field was up on a short plateau with water textures along the sides.

Perhaps ImagineSim is using a different version of P3D...maybe they're still on 4.2 or even on the LM beta team and were testing it with a v4.4 beta, I dunno...but the elevation file via xml did not work in P3D v4.3 here.  In any event, I sent several e-mails to ImagineSIm throughout this evolution, and got no response except for the taxiway light issue suggesting I had a conflicting scenery.

Regards

17 hours ago, w6kd said:

using an xml entry rather than placing the elevation bgl into the scenery\world\scenery folder.  At least for me, that elevation correction has no effect as it is placed by the installer. 

I went back to revisit this based on your observation and what I found is that they put the elevation stub last in the xml sequence of objects rather than first as it needs to be.  I moved that object and now the odd water effects i used to see below scenery objects is gone as well.  Here is how it should be installed:

  	<AddOn.Component>
    	<Category>Scenery</Category>
    	<Path>D:\Addon\Imaginesim\KLGA LaGuardia P3Dv4\P3DSceneryWorldScenery\scenery</Path>
    	<Name>KLGA LaGuardia V3.1 Elevation</Name>
    	<Layer>2</Layer>
  	</AddOn.Component>
  	<AddOn.Component>
    	<Category>Scenery</Category>
    	<Path>D:\Addon\Imaginesim\KLGA LaGuardia P3Dv4</Path>
    	<Name>KLGA LaGuardia New York</Name>
  	</AddOn.Component>
  	<AddOn.Component>
    	<Category>Effects</Category>
    	<Path>D:\Addon\Imaginesim\KLGA LaGuardia P3Dv4\effects</Path>
  	</AddOn.Component>
	

In an xml file, last read item is on top layer or level.