Products Support > GSX Support FSX/P3D
Jetways Disoriented When Invoking Dock Sequence **SOLVED**
virtuali:
--- Quote from: Exodus20 on June 11, 2021, 10:26:52 pm ---I've tried restoring default jetways and that's not working.
--- End quote ---
Restoring default jetways from the GSX Control Panel will surely work.
--- Quote ---So, after I uninstall GSX/SODE; I have no jetways at all.
--- End quote ---
Of course but, you can reinstall SODE and GSX too. If you uninstalled GSX *before* you restored default jetways, you'll have to reinstall it, to get the GSX Control Panel back, which will restore default jetways.
Exodus20:
--- Quote --- you'll have to reinstall it, to get the GSX Control Panel back, which will restore default jetways.
--- End quote ---
Thanks for the advice. As stated in previous posts, I did uninstall and re-install both SODE and GSX and got the control panel back. Presently, when I choose the option to 'restore default jetways', the control panel re-activates the "disable default jetways" for a second, then reverts back to "restore default jetways". As if to say it cannot complete the action.
BTW, for some reason, it thinks that both the boxed version and FSXSE are installed, even though I have only the FSXSE version installed.
virtuali:
--- Quote from: Exodus20 on June 22, 2021, 12:21:09 am ---BTW, for some reason, it thinks that both the boxed version and FSXSE are installed, even though I have only the FSXSE version installed.
--- End quote ---
That's because your registry keys for FSX are wrong. This usually happens because one of the following:
- you installed FSX:Steam when you still had the original FSX, then you Uninstalled FSX. This leads to issues, because FSX:Steam would still be left configured in "side-by-side" mode, which use different registry keys and preference folders compared to the normal operation ( stand-alone )
The correct procedure to remove FSX and use only FSX:Steam is:
1) uninstall FSX
2) uninstall FSX:Steam
3) reinstall FSX:Steam
Step 3 will reconfigure FSX:Steam to properly behave like the only version of FSX installed, using the FSX registry keys and folders.
Another reason why your FSX and FSX:Steam registry is messed up, it's because somebody ( or some utility ), changed both registry keys to point to the FSX:Steam installation, which is also wrong, because it confuses PROPER products like ours, that supports BOTH as separate products with their own separate folders and registry keys. It's a trick that is only used to install legacy product that don't recognize FSX:Steam, but it will cause issues to newer products that supports both, even installed at the same time.
It's likely your messed up registry is causing your problem with the GSX Control Panel, so the correct solution is fix your registry, making FSX:Steam the one and only version installed, which is done by uninstalling/reinstalling FSX:Steam.
Since are likely not able to uninstall FSX anymore, you'll probably have to clear the FSX registry keys BEFORE uninstalling FSX:Steam, otherwise it will still think FSX is there, so it will still try to install itself in side-by-side mode, but with a missing FSX.
The key to make this work, is to have *every* registry key for the original FSX removed when installing FSX:Steam, so it will install itself in "FSX mode"
Exodus20:
Unfortunately, FSX has never been installed on this computer. It is a brand new build with Windows 10 (due to a hard drive crash). It must have been some "utility" (What other utilities are available that would modify GSX/SODE registry settings?) or the GSX installer itself since I only removed existing registry keys.
Update on troubleshooting:
- I engaged SODE and they have postings in their forum for this exact problem; only with GSX and SODE in P3D. However, SODE has not responded to the inquiries.
- I manually removed the C:\Program Files (x86)\12bpilot folder. Manually installed SODE v1.7.1 and that jacked up GSX. Therefore, I completely uninstalled GSX and SODE (which took away my jetways altogether). Re-installed GSX and GSX2; that brought everything back and maintained SODE v1.7.1.
- SODE control panel now only recognizes FSX-SE installation.
- The problem remains.
virtuali:
--- Quote from: Exodus20 on June 23, 2021, 03:37:32 pm ---Unfortunately, FSX has never been installed on this computer. It is a brand new build with Windows 10 (due to a hard drive crash). Since I have no idea of what registry settings are set/modified during the GSX/SODE installation, I wouldn't have modified them; thus it must have been some "utility" (What other utilities are available that would modify GSX/SODE registry settings?) or the GSX installer itself.
--- End quote ---
I wasn't referring to the GSX/SODE registry keys. Those are NOT the problem. The problem are you FSX registry keys. If you never installed FSX, and you only installed FSX:SE, the CORRECT situation should be that you should ONLY have the FSX registry keys, not the specific FSX:SE registry keys.
The FSX:SE specific registry keys are supposed to appear ONLY if you installed FSX:SE when the original FSX was still there.
OR, if some utility tried to "fix" something in the wrong way, and instead of swapping them out, it duplicated both keys to the same path. Again, not an utility that has any relationship with GSX or SODE, but likely some generic fixer or compatibility tool that was designed to trick old FSX-only installers to install into FSX:SE.
--- Quote ---- SODE control panel now only recognizes FSX-SE installation.
- The problem remains.
--- End 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 ?
Do you mean:
- Before you uninstalled/reinstalled SODE, you had BOTH the GSX Control Panel *and* the SODE Platform Manager indicating you had BOTH versions of FSX Installed ?
- After you installed uninstalled/reinstalled SODE, the SODE Platform Manager *now* identify the one version, the FSX:SE one, but the GSX Control Panel still finds two version ?
As I've said, the problem doesn't have anything to do with GSX or SODE, the problem is FSX *ITSELF* and, as long you keep the registry messed up, you are going to have problems with everything.
You said installing SODE "jacked up" GSX. This doesn't surely happen normally, they are designed to work together so, the only possible reason for this to be happening ( without having any idea what "jacked up" really means ), is still your wrong registry settings for FSX.
I'll repeat it again, a NORMAL installation of FSX:SE on a CLEAN system should result in:
- FSX registry keys present, pointing to the FSX:SE installation, preference folders in %APPDATA% and %LOCALAPPDATA% using the standard FSX locations.
- NO specific FSX-SE registry whatsoever, no FSX:SE preference folders present in %APPDATA% and %LOCALAPPDATA%
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version