Jetways don't move **SOLVED**

[fipsi]

Hi guys

I've been using the FSDT LSZH scenery since GSX was released, I bought them in one pakacge, anyway, now to my problem that's occuring these days.


For a quite long time, my jetways don't automatically move to an AI and they aren't going to move when I call them, either. I use UT2 for the AI traffic. Actually, on any other airport, it works perfectly. Ok, LSZH is the only one airport that's a 3rd party scenery addon, but I think, as your jetway moving system is standard FSX source, there shouldn't be any problem. But the oddest thing is that it just suddenly happened a certain time ago, but I didn't change anything! 


I would be appreciated if I get a helpful answer.

Thanks!

[virtuali]

First, if jetways don't move with AI, it's possible you have enabled the feature that UT2 has to disable jetways, in order to save performances. And, our jetways are optimized to move only when seeing them fairly close so, you might not see them moving to AI, because the viewpoint distance.

But they surely move for your airplane provided, you are using an airplane that is native FSX with its Exits properly set in the FSX format in the aircraft.cfg

[fipsi]

As I've already said, I did not change anything in the past, it's really questionable why it's not working.

In the UT2 menu, I haven't disabled the jetway fuction so far. (It works with any UT2 aircraft and all my own customer aircrafts on every other airport, no matter what, so there has to be something specifically with your airport.


I mean, it was working once for a time.

[virtuali]

I'm sorry, but other than the viewing distance too high (or the zoom setting too wide, which is the same), which would force the lowest LOD setting to enter, which is optimized without bones and thus not animated, the jetways in Zurich scenery works normally, and nobody else reported this problem.

Unless, you are having a problem with a single jetway or two, and are assuming they don't work anymore. In this case, name exactly which parking position you are having problems with.

Note that, in order for jetways to move, the parking positions also matters. If you are a bit too ahead or a bit too behind the parking center as defined in the AFCAD, the jetway might not move.

[fipsi]

It's happening with every gate, but even the default loaders don't appear anymore.


AI as well as I parked at the right positions. It's not because of the LOD settings either, since I play FSX on highest possible settings.

[virtuali]

I'm sorry, but can't replicate this, jetways move and loaders appear just fine.

And no, LOD enters into play regardless of your settings, you can set them as high as you could, but it won't matter if a scenery object has defined its own LODs, they will always work without your control, and are depending on the zoom settings.

[fipsi]

I'm sorry, but can't replicate this, jetways move and loaders appear just fine.

Good for you, here it still does not at all!


Seriously, it doesn't work, what can I do now? I mean, just because you don't have the problem at your computer doesn't mean, that you could try to get a solution though. Perhaps on another way than just testing the product on a computer once and say, well, here isn't any similar issue, so it's not a known or common error and due to that, we won't help you.

Not the nice way!

[virtuali]

Seriously, it doesn't work, what can I do now? I mean, just because you don't have the problem at your computer doesn't mean, that you could try to get a solution though.

It's not that the problem doesn't happen "on my computer", it's the opposite: it's happening only on YOUR computer, since nobody else has reported it.

I believe to have suggested several solutions, yet you still don't like it so, what are you suggesting, since nobody else has reported it.

I can only list all the possible things that might result in jetways not moving:

- You are not parked in the correct position

- You have the "Advanced animations" flag not checked

- You have another scenery in conflict, like a duplicate AFCAD or just another scenery.

- You installed AES and there's a problem with its configuration

- You redefined the CTRL+J key to do something else

- You are seeing jetways from too far and/or with too wide zoom settings, so the low-complexity model of the jetway is displayed, and that one is not animated.

[fipsi]

You are not parked in the correct position

I definitely did. (As I already said).

You have the "Advanced animations" flag not checked

The option is enabled, since the jetways work on every other airport properly. (As I already said)

You have another scenery in conflict, like a duplicate AFCAD or just another scenery.

No, because I had an AFCAD file from Ray Smith before I changed to your scenery, and of course, I had removed the files before I installed your product.

You installed AES and there's a problem with its configuration

No, I neither had AES in the past nor will I ever own this crappy program.

You redefined the CTRL+J key to do something else

No, why should I do that? Even if there would be a reasonable reason, there's still the fact that it works on every other airport.

You are seeing jetways from too far and/or with too wide zoom settings, so the low-complexity model of the jetway is displayed, and that one is not animated

No, it's set all right. One centimeter away from the jetway, still nothing.

I cannot suggest anything about solving the problem, as you might know, I'm not the developer of it, so I could only suggest that you give some other tips to fix the problem.

[virtuali]

As I've said, I'm sorry, but can't replicate this, jetways move and loaders appear just fine.

And since nobody else has ever reported this before or, more precisely, whoever reported this, had ONE of the issues I've already listed as potentially problematic and after they fixed them, jetways started to move, then it means you still have overlooked something.

All are easy to check, but the "AFCAD in conflict" is not so easy so, enable logging in Couatl as follows:

open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case l and a capital F )

Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe. Then go in FSX, go to Zurich, start a deboarding, then exit and post here the content of the Couatl.LOG file that should have been created inside FSX\fsdreamteam\couatl

[fipsi]

Here's the content.


couatl v2.0 (build 2309)
log started on Sun May 20 00:28:00 2012

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 16 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon KLAS
Addon KLAS not installed or missing one or more files, skipping
Loading addon KFLL
Addon KFLL not installed or missing one or more files, skipping
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX not installed or missing one or more files, skipping
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (3- Logitech USB Speaker)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio)
Created OpenAL device: Generic Software on Speakers (3- Logitech USB Speaker)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World (layer 1)
  using Scenery/BASE (layer 2)
  using Scenery/0000 (layer 4)
  using Scenery/0001 (layer 5)
  using Scenery/0002 (layer 6)
  using Scenery/0003 (layer 7)
  using Scenery/0004 (layer
  using Scenery/0005 (layer 9)
  using Scenery/0006 (layer 10)
  using Scenery/0007 (layer 11)
  using Scenery/0100 (layer 12)
  using Scenery/0101 (layer 13)
  using Scenery/0102 (layer 14)
  using Scenery/0103 (layer 15)
  using Scenery/0104 (layer 16)
  using Scenery/0105 (layer 17)
  using Scenery/0106 (layer 18)
  using Scenery/0107 (layer 19)
  using Scenery/0200 (layer 20)
  using Scenery/0201 (layer 21)
  using Scenery/0202 (layer 22)
  using Scenery/0203 (layer 23)
  using Scenery/0204 (layer 24)
  using Scenery/0205 (layer 25)
  using Scenery/0206 (layer 26)
  using Scenery/0207 (layer 27)
  using Scenery/0300 (layer 28)
  using Scenery/0301 (layer 29)
  using Scenery/0302 (layer 30)
  using Scenery/0303 (layer 31)
  using Scenery/0304 (layer 32)
  using Scenery/0305 (layer 33)
  using Scenery/0306 (layer 34)
  using Scenery/0307 (layer 35)
  using Scenery/0400 (layer 36)
  using Scenery/0401 (layer 37)
  using Scenery/0402 (layer 38)
  using Scenery/0403 (layer 39)
  using Scenery/0404 (layer 40)
  using Scenery/0405 (layer 41)
  using Scenery/0406 (layer 42)
  using Scenery/0407 (layer 43)
  using Scenery/0500 (layer 44)
  using Scenery/0501 (layer 45)
  using Scenery/0502 (layer 46)
  using Scenery/0503 (layer 47)
  using Scenery/0504 (layer 48)
  using Scenery/0505 (layer 49)
  using Scenery/0506 (layer 50)
  using Scenery/0507 (layer 51)
  using Scenery/0600 (layer 52)
  using Scenery/0601 (layer 53)
  using Scenery/0602 (layer 54)
  using Scenery/0603 (layer 55)
  using Scenery/0604 (layer 56)
  using Scenery/0605 (layer 57)
  using Scenery/0606 (layer 58)
  using Scenery/0607 (layer 59)
  using Scenery/0700 (layer 60)
  using Scenery/0701 (layer 61)
  using Scenery/0702 (layer 62)
  using Scenery/0703 (layer 63)
  using Scenery/0704 (layer 64)
  using Scenery/0705 (layer 65)
  using Scenery/0706 (layer 66)
  using Scenery/0707 (layer 67)
  using Scenery/0800 (layer 68)
  using Scenery/0801 (layer 69)
  using Scenery/0802 (layer 70)
  using Scenery/0803 (layer 71)
  using Scenery/0804 (layer 72)
  using Scenery/0805 (layer 73)
  using Scenery/0806 (layer 74)
  using Scenery/0807 (layer 75)
  using Scenery/0900 (layer 76)
  using Scenery/0901 (layer 77)
  using Scenery/0902 (layer 78)
  using Scenery/0903 (layer 79)
  using Scenery/0904 (layer 80)
  using Scenery/0905 (layer 81)
  using Scenery/0906 (layer 82)
  using Scenery/0907 (layer 83)
  using Scenery/1000 (layer 84)
  using Scenery/1001 (layer 85)
  using Scenery/1002 (layer 86)
  using Scenery/1003 (layer 87)
  using Scenery/1004 (layer 88)
  using Scenery/1005 (layer 89)
  using Scenery/1006 (layer 90)
  using Scenery/1007 (layer 91)
  using Scenery/1100 (layer 92)
  using Scenery/1101 (layer 93)
  using Scenery/1102 (layer 94)
  using Scenery/1103 (layer 95)
  using Scenery/1104 (layer 96)
  using Scenery/1105 (layer 97)
  using Scenery/1106 (layer 98)
  using Scenery/1107 (layer 99)
  using Scenery/AFRI (layer 100)
  using Scenery/ASIA (layer 101)
  using Scenery/AUST (layer 102)
  using Scenery/EURE (layer 103)
  using Scenery/EURW (layer 104)
  using Scenery/NAMC (layer 105)
  using Scenery/NAME (layer 106)
  using Scenery/NAMW (layer 107)
  using Scenery/OCEN (layer 108)
  using Scenery/SAME (layer 109)
  using Scenery/Cities/Oshkosh (layer 110)
  using Scenery/Cities/Rio (layer 112)
  using Scenery/Cities/LasVegas (layer 112)
  using Scenery/Global (layer 113)
  using Scenery/Props (layer 114)
  using Addon Scenery (layer 115)
  using Scenery/Cities/Reno (layer 116)
  using Scenery/Cities/Istanbul (layer 117)
  using Scenery/Cities/Longleat (layer 118)
  using Scenery/Cities/Berlin (layer 119)
  using Scenery/Cities/Edwards_AFB (layer 120)
  using C:/fsgx2010/oce (layer 121)
  using C:/fsgx2010/eur (layer 122)
  using C:/fsgx2010/asi (layer 123)
  using C:/fsgx2010/csa (layer 124)
  using C:/fsgx2010/afr (layer 125)
  using C:/fsgx2010/ant (layer 126)
  using C:/fsgx2010/nam (layer 127)
  using C:/fsgx2010/LocalMeshes (layer 128)
  using Addon Scenery/Chprox/CHPROX_apts_d (layer 3)
  using Addon Scenery/Chprox/CHPROX_elev (layer 129)
  using Addon Scenery/Chprox/CHPROX_scen (layer 130)
  using Addon Scenery/Chprox/CHPROX_apts (layer 131)
  using Addon Scenery/Chprox/CHPROX_LANDMARKS (layer 132)
  using C:/Program Files (x86)/FS Real Time/TzFiles04 (layer 136)
  using TropicalSim/TSim_X (layer 133)
  using FsDreamTeam/ZurichX (layer 134)
  using Addon Scenery/tncm (layer 135)
Worker thread started
Addon GSX loaded
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Starting system monitors
SharedMemInterface connected
Loading aircraft data from Airplanes\CLS_A345
intelliscene.cfg provides aircraft data with priority 1
Using aircraft data from intelliscene.cfg
Loading airport LSZH from FsDreamTeam/ZurichX/scenery/APX_LSZH.BGL
Using airport customization from GSX.airports.lszh_fsdt
Loading user customizations from C:\Users\Philipp\AppData\Roaming\Virtuali\GSX\lszh.ini

[virtuali]

Apart for showing that everything in GSX is working fine, which of course doesn't have anything to do with jetways since GSX doesn't affect them at all, there's simply no reason why they wouldn't work.

Let's start it again, could you check the

[Exits]

section in your aircraft.cfg ? Post all the lines belonging to the [Exits] section only.

[fipsi]

They're working well, just checked them on a default airport.

[fipsi]

Apart for showing that everything in GSX is working fine, which of course doesn't have anything to do with jetways since GSX doesn't affect them at all, there's simply no reason why they wouldn't work.

Yes, GSX is off the hook, but that was clear since the beginning.





I take a look to the LSZH AFCAD, maybe it is corrupted

[virtuali]

Please indicate which gate you used, and try (PLEASE) with a DEFAULT airplane. Together with the Gate number, press Shift+Z when you are in the parking position where jetways don't move, and copy your coordinates here.