Hi Jack,
Well, that’s very unusual to have two parallel FSX installs and the tool does not detect that.
The windows registry key holds only one FSX path at a time and the tool just reads out that one, in your case it is the C:\ drive location.
There is a workaround to be able to register SODE for the other location:
You have to manually edit the “SetupPath” key in your registry, then register SODE for the newly defined FSX install path. Then re-edit the “SetupPath” key to the original value (if you want).
For instructions on how to edit the path, see here: https://sode.12bpilot.ch/?topic=unable-to-get-sode-installed-properly/#post-2446
WARNING: Use at your own risk!
Armi scenery project: I only program the SODE module, I don’t have knowledge of all possible sceneries out there that have or have not used SODE for their jetways. Best is to contact the airport developer for support.
Please note that SODE can only do useful work when the airport developer has included specifically designed SODE-jetways in their sceneries!
If they are static or using other technology, SODE can’t do anything about it.
Hope this helps.