- This topic has 10 replies, 3 voices, and was last updated 5 years, 5 months ago by naoki.
-
AuthorPosts
-
2. November 2018 at 01:44 #2957naokiParticipant
Hello.
I downloaded SODE Ver.1.6.3. Then, I installed it. But, I can’t find register button like as attached screenshot.
Also, I read Troubleshoot Guide and FAQ, then I tried. But, I couldn’t solve.
Previously, the same situation happened when I downloaded and installed old version. So, I couldn’t use SODE.
Would you tell me how to solve the problem?
My simulator is FSX Gold edition (Japanese).
I attach screenshots(SODE Platform Manager and log) here.
Attachments:
You must be logged in to view attached files.2. November 2018 at 05:08 #2960jfmitch1716ParticipantThe only thing that I could recommend is giving up on SOSE and any products that use it. That is what I have done. It is completely useless and any product that continues to require it is less than what you are paying for. It goes against the grain of advancements in Flight Simulator. I use P3DV4 the most advanced flight sim program out there and have numerous airfields with working jetways. I ended up buying a product that required SODE (I wasn’t told that when I made my purchase) and spent 5 days trying to get the jetways to attach to my aircraft. That’s enough of my rant. When companies get that bad that they have to use SODE they are not worth the time to waste even if they were free.
5. November 2018 at 14:01 #296212bPilotKeymasterWould you tell me how to solve the problem?
Hi,
The platform manager reads out your Windows registry to get the installation path of FSX. If the entry is missing or incorrect, then SODE platform manager can’t display the register button.
Try to download this tool that should repair FSX registry settings: https://www.flight1.com/view.asp?page=library
Once the path is correctly set in the Windows registry, then platform manager will work.
6. November 2018 at 03:20 #2971naokiParticipantHello, 12bPilot. Thank you for your reply.
I downloded “FSX/FS9 Registry Repair Tool” from address which you described. Then, I tried as you said.
Consequently, the repair tool said that path was successfully added.(Please see screen shot)
Finally, I ran SODE again.
But, unfortunately, the same situation happened again.
Also, I restarted my computer, but it was the same.
Do you have another solution for this situation?
By the way, my computer operation system is Windows 7. I had forgotten to write here, I’m sorry.
Attachments:
You must be logged in to view attached files.6. November 2018 at 13:18 #297612bPilotKeymasterOk, can you attach the various log files concerning the platform detection?
C:\ProgramData\12bPilot\SODE\log ->
PLTMGR_FSX.log and PLTMGR_DETECTION.log
Thanks
6. November 2018 at 23:52 #2981naokiParticipantHello.
I can find PLTMGR_DETECTION.log file, but I can’t find PLTMGR_FSX.log file.
Also, I researched the file with research engine in my computer. Then, my computer found PLTMGR_DETECTION.log file, but not PLTMGR_FSX.log file.
Anyway, I attach PLTMGR_DETECTION.log file here.
—————————————————————————————-
Trying to detect ‘FSX’
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0
Registry Path 64: SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Key name: SetupPath
Trying Path 32…
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
>>> ERROR: void QueryValue
—
Trying to detect ‘FSX-SE’
Hive: HKLM
Registry Path 32: SOFTWARE\Wow6432Node\DovetailGames\FSX
Registry Path 64: SOFTWARE\DovetailGames\FSX
Key name: Install_Path
Trying Path 32…
>>> ERROR: Unable to find ‘Install_Path’ key in Registry!
>>> ERROR: void OpenKey
—
Trying to detect ‘P3Dv2’
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v2
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v2
Key name: SetupPath
Trying Path 32…
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
>>> ERROR: void OpenKey
—
Trying to detect ‘P3Dv3’
Hive: HKLM
Registry Path 32: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v3
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v3
Key name: SetupPath
Trying Path 32…
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
>>> ERROR: void OpenKey
—
Trying to detect ‘P3Dv4’
Hive: HKLM
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
Key name: SetupPath
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
>>> ERROR: void OpenKey
—
— END —
——————————————————————————————–
Thank you.
- This reply was modified 5 years, 5 months ago by naoki.
Attachments:
You must be logged in to view attached files.6. November 2018 at 23:59 #2986naokiParticipantSorry, I attached two same screenshot by mistake.
7. November 2018 at 19:32 #298912bPilotKeymasterLooks like the SetupPath entry still can’t be accessed by SODE Platform Manager.
I’m starting to believe it is a language setting issue.
Just to double-check, can you post a screenshot of the program “regedit” and the following path (see image below)
10. November 2018 at 10:32 #2999naokiParticipantHello. I’m sorry to be late.
I post a screenshot of regedit.
But, I can see only two files, “(Standard)” and “CurrentXPackProductCode.” So, I couldn’t take screenshot of SetupPath.
Also, my simulator is installed in my computer and have worked with no problem.
Thank you.
Attachments:
You must be logged in to view attached files.12. November 2018 at 15:00 #300912bPilotKeymasterThe entry is missing.
You can manually add a new String value -> right-click in the white area of regedit and create “New” -> “String Value”.
Then name it “SetupPath” and the value should be your path to FSX -> “D:\FSX”
13. November 2018 at 03:44 #3023 -
AuthorPosts
- You must be logged in to reply to this topic.