FSDreamTeam forum
Products Support => Las Vegas FSX/P3D => Topic started by: Candler on August 18, 2019, 06:15:35 pm
-
Fresh install of FSX, GSX, FSDT KLAS, KLAX and KDFW on Windows 10.
KLAS Jetways not animating / operating.
LAX and DFW work perfectly.
I get a message at KLAS that the jetway is operating but it doesn't move and the de-boarding passengers are walking down an invisible jetway as if the jetway was there.
I reinstalled GSX and KLAS to no avail.
Please advise as to a solution.
Thank you.
-
Be sure you remove a GSX .INI customization file you made for KLAS in the past, before we added SODE jetways, because that would prevent for our own customization to work, so you won't see the new jetways.
Remove any file for KLAS in the %APPDATA%\Virtuali\GSX folder, if you have any.
-
The only file in there was a Folder named Texture and it was empty.
To be clear- The jetways are visible- they just will not move.
-
What key commands are you using to get the jetways to move?
-
I use the GSX menu and the various drop downs.
-
Also not seeing any American Airlines ground equipment available on the drop down at KLAS.
-
Hello? ???
-
What's your question ? The supposed lack of AA in the GSX customization option ? It's surely there, are you sure you checked ? Which simulator you use ?
-
See my first post in this thread.
FSX- New Install- No other scenery in the area- only KLAS.
Jetways not animating.
AA missing from menu.
KLAX and KDFW work perfectly.
Only KLAS has these issues.
-
First, in FSX it's normal the operator selection drop-down to be unavailable, since that's only possible with P3D4.
About jetwyas not moving, I tried a random parking ( A7 ) and it worked straight away, see the attached screenshot.
-
Southwest, Spirit, United etc are all available when GSX asks what equipment to use.
AA is not included in that selection.
It may work on your sim but it is not working on mine.
As I mentioned- LAX and DFW work perfectly, why not LAS?
-
GSX is telling Me " Jetway in Operation" and "Jetway Operation Completed" yet the Jetway has not moved and is still in its parked position.
What can cause this?
-
Southwest, Spirit, United etc are all available when GSX asks what equipment to use.
That's what you are supposed to have. Operators in GSX are assigned to an airport using a scoring rule, and AA apparently has a lower score at KLAS than the others.
AA is not included in that selection. It may work on your sim but it is not working on mine.
I never claimed to have AA at KLAS on my system. You said it wasn't there on the drop-down selection, but that's because you have FSX, so you cannot change it as easily as P3D4 users, but nowhere I said you are supposed to see AA on the operator choice menu, which is another thing than the drop-down customization, which would allow you to *change* an operator, but not in FSX.
As I mentioned- LAX and DFW work perfectly, why not LAS?
KLAS works too, that's why I posted a screenshot.
GSX is telling Me " Jetway in Operation" and "Jetway Operation Completed" yet the Jetway has not moved and is still in its parked position.
Have you seen the menu which asked which jetway should connect to which door ?
-
KLAS works too, that's why I posted a screenshot.
No it doesn't- that's why I'm asking for support. What could cause lax and dfw to work properly but not las?
Have you seen the menu which asked which jetway should connect to which door ?
Yes
-
No it doesn't- that's why I'm asking for support. What could cause lax and dfw to work properly but not las?
Yes it does, and please stop insisting it doesn't. At least try to say: why KLAS doesn't work ON MY SYSTEM ONLY ? Have you seen other users reporting jetways not moving at KLAS so far ? I haven't, so it must be something wrong on your system.
Yes
Then the problem might possibly be related to an issue with SODE, since the actual movement is handled by it, not GSX or the scenery. I asked if you saw that menu, to be sure the jetway was in fact handled by SODE and, if you see that menu, it means GSX has received confirmation from SODE the jetways is fine, and CAN connect to your airplane.
Check the SODE log in the SODE Platform Manager, maybe you'll find something there which might help.
Also, be sure you have the "Advanced Animations" setting enabled, but I doubt this is the problem, because if it was, you wouldn't see jetways moving anywhere.
-
Here is the contents of my SODE log.
What is interesting is that it is showing FlyTampa KLAS jetways instead of FSDT Jetways
I have FlyTampa KLAS installed in my P3DV4 and FSDT KLAS in FSX.
I have not run P3D today- Only FSX.
Is SODE somehow confusing the two different products of the same airport names?
I can't attach the sode log but here are some samples.
[11:34:23.427] INFO : SODE Version 1.6.4
[11:34:23.427] INFO : Targetting Platform 'FSX'
[11:34:23.427] DEBUG SODE.SETTINGS : All Settings successfully read.
[11:35:08.252] INFO SODE.FSLOOP : + SimObject FlyTampa_KLAS:Jetway 1 GATE_C 19 [jetway_A_STATIC_KLAS]. ID: 300
[11:35:08.252] INFO SODE.FSLOOP : + SimObject FlyTampa_KLAS:Jetway 1 GATE_C 16 [jetway_A_STATIC_KLAS]. ID: 301
[11:35:08.252] INFO SODE.FSLOOP : + SimObject FlyTampa_KLAS:Jetway 1 GATE_A 15 [jetway_A_STATIC_KLAS]. ID: 302
[11:35:08.332] INFO SODE.FSLOOP : + SimObject FlyTampa_KLAS:Jetway 1 GATE_D 39 [jetway_B_STATIC_KLAS]. ID: 303
[11:35:23.768] WARN SODE.FSLOOP : [AI DETECTION] (Static) Jetway Jetway 1 GATE_D 7 cannot be docked to AI=B752 N906NV [IKErrCode=4]
[11:35:23.768] WARN SODE.FSLOOP : [AI DETECTION] (Static) Jetway Jetway 1 GATE_D 6 cannot be docked to AI=B752 N902NV [IKErrCode=4]
[11:35:23.768] WARN SODE.FSLOOP : [AI DETECTION] (Static) Jetway Jetway 1 GATE_B 1 cannot be docked to AI=MD80 N401NV [IKErrCode=6]
-
I'm not sure how SODE can differentiate between two airports, because we never used SODE.XML files for our jetways, and I don't know if it's possible to have SODE installed in two simulators, one with a scenery that uses SODE XML jetways, and another one for the *same* airport that uses GSX/SODE jetways.
That's likely a question to make on SODE forum.