- This topic has 17 replies, 3 voices, and was last updated 7 months, 3 weeks ago by Gustavo Matias.
-
AuthorPosts
-
22. January 2017 at 09:38 #984damiendelilleParticipant
Hi,
I’ve installed SODE 1.4.2 for my FSX SE but it doesn’t appear in the menu. I don’t have any log.txt.
SODE 1.4.2 installed in C:\Program Files (x86)\12bpilot
SODE Platform Manager
Platform installation path : E:\Steam\steamapps\common\FSX
exe.xml and dll.xml path : C:\Users\damie\AppData\Roaming\Microsoft\FSX-SE
SOLDE REGISTERED
SOLDE ACTIVEAny idea ?
Thank you.
22. January 2017 at 09:57 #985damiendelilleParticipantWhen I try to install SODE 1.4.2, I get this error message during installation :
22. January 2017 at 11:55 #98612bPilotKeymasterHi,
It seems that your registry is messed up. Did you have the original FSX installed before on your system? Because FSX-Steam Edition would not create a “FSX-SE” folder if it is installed on a clean machine, but does exactly that when there are still traces of a FSX installation in your registry…
The SODE Platform Manager needs a properly set up system in the first place, so you need to clean up your system. There are several threads about this registry issue in the internet, e.g. here https://steamcommunity.com/app/314160/discussions/1/490123832541365433/Once everything is cleaned up, SODE Platform Manager should find the fsx.cfg file at C:\Users\damie\AppData\Roaming\Microsoft\FSX
22. January 2017 at 13:50 #989damiendelilleParticipantThank you !
No more registration error (I reinstalled SODE) but no SODE in FSX SE menu …22. January 2017 at 17:21 #99012bPilotKeymasterOk, can you post your SODE.log here? Platform Manager -> Tools -> Show Log
22. January 2017 at 18:15 #991damiendelilleParticipantTrying to detect ‘FSX’
Hive: HKLM
Registry Path 64: SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0
Registry Path 32: SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
Key name: SetupPath
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
—
Trying to detect ‘FSX-SE’
Hive: HKLM
Registry Path 64: SOFTWARE\Wow6432Node\DovetailGames\FSX
Registry Path 32: SOFTWARE\DovetailGames\FSX
Key name: Install_Path
‘Install_Path’ key found in 64-Bit registry -> Install Path = ‘E:\Steam\steamapps\common\FSX’
FSX:SE Co-Existence Key exists! Value = 0
Platform SimObjects file name: ‘fsx.cfg’
Platform Roaming path: ‘C:\Users\damie\AppData\Roaming\Microsoft\FSX’
—
Trying to detect ‘P3Dv2’
Hive: HKLM
Registry Path 64: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v2
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v2
Key name: SetupPath
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
—
Trying to detect ‘P3Dv3’
Hive: HKLM
Registry Path 64: SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v3
Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v3
Key name: SetupPath
>>> ERROR: Unable to find ‘SetupPath’ key in Registry!
—
— END —22. January 2017 at 18:26 #99212bPilotKeymasterThat’s the wrong one (PLTMGR_DETECTION). I need the SODE.log file contents
22. January 2017 at 19:34 #993damiendelilleParticipantOK but when I try to go to Platform Manager -> Tools -> Show Log, I get this error message :
22. January 2017 at 20:18 #99512bPilotKeymasterYou need to run a Simulator session first and then exit the sim. This will create a SODE.log file.
22. January 2017 at 20:27 #996damiendelilleParticipantI did it but no SODE.log !
22. January 2017 at 20:51 #99712bPilotKeymasterOk, then SODE is not being launched by P3D I guess. If you have a Anti-Virus program running, then you could add an exception for SimObjectDisplayEngine.exe.
22. January 2017 at 21:45 #998damiendelilleParticipantI tried, it does not work.
22. January 2017 at 21:50 #99912bPilotKeymasterDo you have TeamViewer? I can then check on your computer what’s wrong. I’m online for the next 10mins…
EDIT: I’m going offline…maybe tomorrow…
22. January 2017 at 22:06 #1000damiendelilleParticipantOK
24. January 2017 at 07:55 #100412bPilotKeymasterHey, I’m away from home until Saturday. So, the only advice I can give you for now is to completely uninstall SODE V1.4.2 and a re-install.
If that doesn’t help, then I suspect that the required SimConnect version is not installed on your system. This can be tested if you try to double-click the SimObjectDisplayEngine.exe in C:\Program Files (x86)\12bPilot\SODE. If the required SimConnect is not installed, you’ll be warned about this via a MessageBox saying something with WinSxS.Don’t forget to check the Task-Manager afterwards and kill the SimObjectDisplayEngine.exe if it is listed in the running processes list
If you get that MessageBox complaining about SimConnect.dll and WinSxS, you can install the required SimConnect version from your FSX-SE install path. There should be a folder X:\SteamLibrary\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces, install FSX-XPACK.
-
AuthorPosts
- You must be logged in to reply to this topic.