Products Support > GSX Support FSX/P3D
Jetways Disoriented When Invoking Dock Sequence **SOLVED**
Exodus20:
--- Quote ---Sorry, but now I'm having an hard time following you. In your previous post you said your problem was the GSX Control Panel indicated you had both FSX and FSX:SE, now you are saying the SODE Control Panel *now* only recognize the FSX:SE installation ?
--- End quote ---
I can see where the confusion is based on the terminology I used. It may be good to start from the beginning and perhaps more detail and better terminology:
- Windows 10 installed on new hard drive.
- Installed FSX-SE.
- Installed GSX/GSX2 (which of course installed SODE. See "note" below).
- SODE platform manager showed that I had both FSX and FSX-SE installed and only FSX-SE registered. GSX Level 2 control panel shows "FSX-SE standalone" & "FSX-SE +FSX" and gives me options to restore default jetways for both (which didn't work either).
- The problem surfaced the first time that I initiated the jetway docking process.
- I tried the original troubleshooting steps identified in my earlier posts to no avail (i.e. removed any registry settings that I could find along with any related folders I could find, re-installed GSX/SODE).
- Attempted to restore default jetways from the GSX level 2 control panel and it failed (i.e. it activated the 'disable default jetways' button for about a second then returned back to activating 'restore default jetways' only for each option and indicated that the status is "Default jetways disabled by GSX" for both).
- Uninstalled GSX/SODE again. This time I did not manually remove any registry settings and left whatever settings were there, uninstalled GSX and SODE, deleted both the Addon and 12bpilot folders, did not remove the "appdata" folder structure and re-installed GSX/GSX2 (and SODE of course).
- After the un-install completed, I launched FSX-SE again an had no jetways at all (I suspect because of the failure for GSX to restore the defaults prior to the uninstall).
- After re-installing GSX/GSX2 again, The GSX Level 2 control panel still showed "FSX-SE standalone" & "FSX-SE +FSX" and gives me options to restore default jetways for both. Status shows that "Default jetways disabled by GSX".
- The SODE platform manager still shows that I have only FSX-SE registered (see "note" below).
- Still no change to the jetway operations.
I tried some other operations:
- Initiated boarding process without first docking the jetway. The jetway problem persisted, however the baggage loading process successfully executed and no passengers were boarded (I'm guessing that is because the jetway docking process failed).
- Requested refueling. The jetway problem persisted and the refueling process successfully executed.
- Attempted to customize the gate and the jetway problem persisted and couldn't re-orient the jetway. All other customizations are accessible.
- Initiated pushback and departure and the jetway problem persists; but, the pushback sequence successfully executes.
So, the difference being that when starting with the jetway docking sequence, GSX waits for the docking process to complete; but, it never does, thus GSX is hung.
--- Quote ---The FSX:SE specific registry keys are supposed to appear ONLY if you installed FSX:SE when the original FSX was still there.
--- End quote ---
Note: I cannot speak to how the registry keys are supposed to align during the installation, since I'm not familiar with where they all reside. I had guessed earlier by doing a search for anything that I think to search by. Naturally, I was hoping that anything that I missed would've have been reset during re-installation.
However, I noticed that during the SODE installation (executed during the GSX installation process), it appears that the installer expects to see an fsx.cfg file in the %appdata%\roaming\microsoft\fsx folder, even when only FSX-SE is installed, or it will wait until one is found there. So, in both installation cases, I had to manually create the folder structure and manually drop an fsx.cfg file in to the folder (that I found from a back up of my old FSX installation, so as to not confuse it with the FSX-SE fsx.cfg tile). Once that is done, it's happy, and the SODE installation will successfully complete and the GSX installer will continue. After the GSX installation is complete, the SODE platform manager then shows that both FSX and FSX-SE are registered. I can later delete the "FSX' folder and the SODE platform manager will show only that FSX-SE is registered. With that being said, regardless of whether FSX-SE only or both are "registered", the problem still persists.
To your point, it may be that registry keys and folder structures are misaligned. If that is the case, then can you provide the correct alignment? Perhaps I can manually align them.
Still getting crickets from SODE. https://sode.12bpilot.ch/?topic=jetways-stick-up
virtuali:
--- Quote from: Exodus20 on June 29, 2021, 05:40:22 pm ---- Windows 10 installed on new hard drive.
- Installed FSX-SE.
- Installed GSX/GSX2 (which of course installed SODE. See "note" below).
- SODE platform manager showed that I had both FSX and FSX-SE installed and only FSX-SE registered. GSX Level 2 control panel shows "FSX-SE standalone" & "FSX-SE +FSX" and gives me options to restore default jetways for both (which didn't work either).
--- End quote ---
I'm sorry, but we can stop here. There's no way *both* GSX and SODE would be equally confused by a wrong registry key for FSX:SE. And, as I've said, a wrong registry key for FSX:SE CANNOT HAPPEN if you just installed Windows 10 afresh.
Have you possibly chose an option to install Windows 10, but keep your settings ? That would explain why you inherited the wrong registry settings from a previous install because that option keeps your old registry into the new Windows install.
I can only repeat and confirm the following: on a real, fresh install of Windows, on a system you NEVER installed the standard FSX before, if you install FSX:Steam, the result will be:
- You'll have NO registry keys for FSX:Steam
- You will only have registry keys for the Standard FSX, pointing to the FSX:Steam installation folder.
This will result both GSX and SODE detecting FSX:Steam installed in Stand-alone mode, and nothing else. This is the normal, correct, situation of a clean FSX:Steam installation.
This, of course, assumes you haven't installed ANOTHER software ( just after your "fresh" Windows reinstall ), one that set the keys in the wrong way, for some reason, usually trying to force-install itself or let you force-install older products that don't support FSX:SE or the side-by-side mode.
Exodus20:
--- Quote from: virtuali on July 01, 2021, 11:48:54 am ---There's no way *both* GSX and SODE would be equally confused by a wrong registry key for FSX:SE. And, as I've said, a wrong registry key for FSX:SE CANNOT HAPPEN if you just installed Windows 10 afresh.
--- End quote ---
Thank you again for the response and confirmation. So, we have concluded that the issue is not generated by a registry key setting.
What are other possibilities that GSX would tell SODE or FSX-SE (whomever handles the operation) to orient the jetway as shown in the original pic's? It appears that it must be a bug in the GSX and/or SODE code. Can FSDT provide some insights as to what can be done from a coding perspective. Is there anything that I can provide to FSDT that could help you troubleshoot this issue? I am seeing more and more posts for this issue.
I would like to at least get my default jetways back when I uninstall GSX. I've tried a fresh install of FSX-SE without GSX and something remains after uninstalling GSX that tells FSX-SE not show default jetways. And as mentioned before the GSX Level 2 control panel fails to restore them. This actually might be a clue to the problem at hand; but, I'll let FSDT explore that, of course.
Thanks again!
virtuali:
--- Quote from: Exodus20 on July 10, 2021, 06:28:02 pm ---Thank you again for the response and confirmation. So, we have concluded that the issue is not generated by a registry key setting.
--- End quote ---
I only confirmed your registry settings are messed up. Never said the issue with the jetway is not related to it.
--- Quote ---What are other possibilities that GSX would tell SODE or FSX-SE (whomever handles the operation) to orient the jetway as shown in the original pic's?
--- End quote ---
There are no other possibilities. All users reporting this problem, usually ended up fixing it by uninstalling/reinstalling SODE and THIS can go wrong if the registry settings are mixed up between FSX and FSX:SE, and yours surely are.
Jetways are created by GSX in their static version. When you operate them, they are replaced by the dynamic version that, in its "default" position is oriented exactly like the static one.
Then, GSX calls SODE and ask to animate the jetway and, since the animation can go in both ways, SODE can possibly put the jetway in the wrong position and/or not animate it.
GSX and SODE communicate through Simconnect so, other than the registry keys, another possible reason might be the communication between the two being interrupted or slowed down, possibly missing some commands. This CAN happen when using many other addons which might increase the traffic over the Simconnect communication channel, and overflow it with so many commands the sim cannot keep up with everybody, we noticed this sometimes happens with some 3rd party weather engines, or AI traffic products that control AI with Simconnect.
Another possible reason is a mix-up of Simconnect versions, which again can be a result of either confused registry keys, or having installed another add-on that has installed an older version of Simconnect ( multiple version of Simconnect can be installed at the same time ), which might have issues with the functions we need to have GSX and SODE communicate reliably.
A possible way to test this would be disabling ALL add-ons except GSX and SODE, and see if something changes.
But not before you fixed your registry keys, and reinstalled both GSX and SODE with the registry in the correct state. If you don't do this first, every other test would be useless.
Exodus20:
--- Quote ---GSX and SODE communicate through Simconnect so, other than the registry keys, another possible reason might be the communication between the two being interrupted or slowed down, possibly missing some commands. This CAN happen when using many other addons which might increase the traffic over the Simconnect communication channel, and overflow it with so many commands the sim cannot keep up with everybody, we noticed this sometimes happens with some 3rd party weather engines, or AI traffic products that control AI with Simconnect.
--- End quote ---
Unfortunately, I have not installed any other add ons. I'd like to install my Wx add on; but, I haven't done that since my Sim is effectively useless due to this issue (can't even do a pushback). I would at the least like to get my default jetways and ground vehicles back. Is there a way to resolve that issue?
--- Quote ---Another possible reason is a mix-up of Simconnect versions, which again can be a result of either confused registry keys, or having installed another add-on that has installed an older version of Simconnect ( multiple version of Simconnect can be installed at the same time ), which might have issues with the functions we need to have GSX and SODE communicate reliably.
--- End quote ---
Which version of SimConnect is required for GSX?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version