I'm still a bit confused. I wasn't at a gate, this happened after pushback at FSDT JFK. The airport position customization says it is using the FSDT.bgl, but it doesn't say there is a SODE jetway.
First, you are supposed to see "SODE jetway" only if the jetway was created externally by SODE with a SODE XML file. This is the case for all 3rd party sceneries that use SODE, but not for FSDT ones. The indication will say "Parking has an XML SODE jetway", and the jetway tab won't be editable.
On FSDT JFK, you will just see the "Parking has xx jetways" indication, with the Jetway tab editable. IF you have the latest Live Update, the parking will be flagged with a "/JS" (opposed to just "/J" ), to show it's a SODE jetway, just like the normal GSX menu.
If you have issues at FSDT JFK, the most likely problem is that you already customized the airport before GSX Level 2 so, your old .INI file is taking precedence over the one that comes with the scenery, and it has been updated with SODE jetways. To fix this:
- run the FSDT Live Update and ALLOW to replace the ACAD when asked.
- remove any customization you might have made for JFK in the %APPDATA%\Virtuali\GSX folder