FSDreamTeam forum
Products Support => Memphis KMEM Support FSX/P3D => Topic started by: tristar1011 on June 06, 2016, 03:27:03 am
-
Hello, I installed KMEM (register) and GSX (register too) and I tried to use SODE jetways but I have not jetway selection menu. The jetway doesn't move when I chose "boarding" in GSX jetway, only a green message "open L2 door"...
I Tried differents "JS" jetways, differents aircraft, I reinstalled KMEM, GSX and I download SODE 1.3.3 (activated) but nothing happens with jetways...
My FS is FSX SP2. Thanks for helping me.
-
If you don't have the jetway selection menu in GSX after selecting Boarding/Deboarding, it caused by one of these issues:
- The communication with SODE has been interrupted for some reason. You should see a warning message saying that. You might try to use the "Reload All" menu option from SODE, sometimes it helps.
- The SODE communication is working normally, but SODE cannot solve the animation needed to reach that airplane door. GSX will first ask SODE if that jetway can be solved, and if it can't, it will then display a message saying "No jetway can operate at this position"
The most likely reason for a jetway not being solvable, is that you are parking too close or too far away from it, or your plane door's are too high to be reachable.
-
I dont have any of those messages in my gsx. I select deboarding, and nothing happens after that. I get a message that says remember to operate jetway and open exit, but thats it. I have uninstalled and reinstalled gsx, which did not fix the issue. I wish you could just operate it though CTRL J.
-
I select deboarding, and nothing happens after that. I get a message that says remember to operate jetway and open exit, but thats it.
Are you sure you don't have ANY messages about SODE ? try to use the "Reload All" menu option from SODE to restart it and see if you get a message from it that has been loaded.
-
Yes, Im positive, is the Sode something I need to install separately?
-
If you don't have the jetway selection menu in GSX after selecting Boarding/Deboarding, it caused by one of these issues:
- The communication with SODE has been interrupted for some reason. You should see a warning message saying that. You might try to use the "Reload All" menu option from SODE, sometimes it helps.
- The SODE communication is working normally, but SODE cannot solve the animation needed to reach that airplane door. GSX will first ask SODE if that jetway can be solved, and if it can't, it will then display a message saying "No jetway can operate at this position"
The most likely reason for a jetway not being solvable, is that you are parking too close or too far away from it, or your plane door's are too high to be reachable.
Thanks.
I reinstalled again all my FSDT products. Now jetways only move with the default 737 (nothing happens with the A321 or others default airplanes). I can't try with my payware airplanes (gates too smalls for widebodies PMDG MD11 and 777).
-
Yes, Im positive, is the Sode something I need to install separately?
From your screenshot, it seems you were expecting the command for call the SODE jetways would be displayed together with the GSX menu. It's not like that!
Have you read the KMEM manual ? You are supposed to be asked about jetways AFTER you select either Boarding or Deboarding.
-
Yes, I have. I select the deboarding process, the vehicles start to move, then I am asked, "remember to operate jetway" but that is it. I dont get any other choice in gsx or anything.
-
Have you updated to the newest version of GSX also? As far as I understand, the SODE integration (of course) requires KMEM/KIAH scenery (newest version) along with the newest version of GSX. Also, download the newest Addon Manager and install that - just in case ;)
-
then I am asked, "remember to operate jetway" but that is it. I dont get any other choice in gsx or anything.
That message indicates the scenery has a standard FSX (CTRL+J) animated jetway, not a SODE one.
Which seems to be odd, since KMEM never had any jetways other than SODE, while with KIAH, you must download the latest version to get the SODE jetways.
-
The latest version of what? MEM?
-
The latest version of what? KMEM?
KMEM only has SODE jetways, while KIAH requires to be updated. But BOTH require the latest full GSX version to work with SODE.
-
I have uninstalled and reinstalled gsx version 1.9.9.
-
At KIAH some of the jetways ( Gate B I think ) are still made with the CTRL+J method, since they are a bit unusual. GSX will tell you if a jetway is standard adding "/J" to the parking name, or it's a SODE jetway, adding " /JS" to the name.
-
I got it to work. For whatever reason, during the install of mem an error occurred during the side portion and it didn't install all the way. Reinstalled and it works just fine now. I still don't see the reason behind why every jetway no longer moves, even for ai, I know it saves on performance, but flytampa have implemented side at every jetway even for ai I believe.
-
I still don't see the reason behind why every jetway no longer moves, even for ai, I know it saves on performance, but flytampa have implemented side at every jetway even for ai I believe.
We have been doing airports with jetways moving with AI at each and every parking of every airport we made for years, when nobody made animated jetways but, once we saw that many AI traffic packages all have added features to disable AI doors to save fps, we assumed this was a most requested and used feature so, the GSX implementation of SODE, purposely restrict the activated jetway to the parking selected in GSX, which is consistent with how GSX always worked: docking systems are too entirely static (and they don't turn on for AIs) unless you activate the parking with GSX, so is the marshaller and anything else related to a parking.
The cost in VAS and fps to be able to afford several jetways and docking systems working is simply something we cannot afford anymore, and we take optimization very seriously. Even in our airports using standard animated jetways, that in theory would be visible for AI too, we used LOD to restrict the visual range of the animated objects, so you couldn't see more than 3-4 jetways attached to AIs, but then the issue of in-out LOD-popping between animated/non-animated was a bit annoying, so we think the current solution to restrict jetways to your plane only and only if the parking is selected by GSSX, is the less visually distracting AND is the absolute most efficient in VAS and fps savings.