p3d v4 with sode 1.5.2 no target simulator

Home › Forums › Support › p3d v4 with sode 1.5.2 no target simulator

Topic Resolution: Resolved
Viewing 15 posts - 1 through 15 (of 23 total)
1 2
  • Author
    Posts
  • 10. June 2017 at 17:43 #1337
    deltabravo
    Participant

    Hi Jeffrey and Members,

    installed the lastest version of SODE today. Unfortunately it does not work. I installrd it in \ProgramData. The installation process runs without errors. I do not have SODE in the sim menu. Platform Manager .log tells me: No target simulator.

    Any help? Thanks!

    Cheers, Dieter

    10. June 2017 at 19:53 #1339
    12bPilot
    Keymaster

    Hey Dieter,

    Which sim is that? P3D v3.3, 3.4 or 4? If you open the SODEPlatformManager.exe, are there any problems when trying to register for the target sim?
    Can you then go to C:\ProgramData\12bPilot\SODE\log and post the files SODE.log, PLTMGR.log and PLTMGR_DETECTION.log here?

    Thanks.

    11. June 2017 at 05:37 #1344
    deltabravo
    Participant

    Ok Jeffrey, many thanks for your quick reply. It’s P3D V4. No SODE registration problems for P3D V4.

    PLTMGR.txt

    Ops: Registration, Install
    P3D Exe Path: H:\P3Dv4\Prepar3D.exe, Version: ‘4.0’
    Arguments Package: “-Configure: Category=Add-on Package, Operation=Add, Title=SODE, Path=C:\ProgramData\12bPilot\SODE\P3Dv4”
    Creating Process for Add-on Package…
    RESULT: 1
    SUCCESS!
    — END —

    PLTMGR_DETECTION.txt

    Trying 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
    ‘SetupPath’ key found in 64-Bit registry -> Install Path = ‘H:\FSX’
    Platform SimObjects file name: ‘fsx.cfg’
    Platform Roaming path: ‘C:\Users\Dieter\AppData\Roaming\Microsoft\FSX’
    —
    Trying to detect ‘FSX-SE’
    Hive: HKLM
    Registry Path 64: SOFTWARE\Wow6432Node\DovetailGames\FSX
    Registry Path 32: SOFTWARE\DovetailGames\FSX
    Key name: Install_Path
    Trying Path 32…
    >>> ERROR: Unable to find ‘Install_Path’ key in Registry!
    >>> ERROR: void Open
    —
    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
    Trying Path 32…
    >>> ERROR: Unable to find ‘SetupPath’ key in Registry!
    >>> ERROR: void Open
    —
    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
    ‘SetupPath’ key found in 64-Bit registry -> Install Path = ‘H:\P3D’
    Platform SimObjects file name: ‘simobjects.cfg’
    Platform Roaming path: ‘C:\Users\Dieter\AppData\Roaming\Lockheed Martin\Prepar3d v3’
    —
    Trying to detect ‘P3Dv4’
    Hive: HKLM
    Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
    Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
    Key name: SetupPath
    Trying Path 32…
    ‘SetupPath’ key found in 64-Bit registry -> Install Path = ‘H:\P3Dv4\’
    Platform SimObjects file name: ‘simobjects.cfg’
    Platform Roaming path: ‘C:\Users\Dieter\AppData\Roaming\Lockheed Martin\Prepar3d v4’
    —
    — END —

    SODE.txt

    17:21:19.765] INFO : SODE Version 1.5.2
    [17:21:19.765] FATAL : No Target Simulator Platform supplied! Shuting down…
    [17:21:19.765] INFO : Terminate SODE.

    Many thanks for the support.

    • This reply was modified 6 years, 10 months ago by deltabravo.
    • This reply was modified 6 years, 10 months ago by deltabravo.
    • This reply was modified 6 years, 10 months ago by deltabravo.
    11. June 2017 at 09:43 #1349
    12bPilot
    Keymaster

    Thanks for the files.

    The only missing link could be that Prepar3D has not correctly added SODE to the add-on list.
    Can you go to C:\ProgramData\Lockheed Martin\Prepar3D v4 and post the contents of the add-ons.cfg file? Also, C:\Program Files (x86)\12bPilot\SODE\P3Dv4\add-on.xml

    In P3Dv4, under Options -> Add-Ons. Is there an entry for SODE in the list?

    A certain indication if SODE is correctly loaded is the simconnect.log.
    You need to create a simconnect.INI file in your %USERPROFILE%\Documents\Prepar3D v4 Files.
    The contents of that file:

    [SimConnect]
level=verbose
console=1
file=simconnect.log

    Start your sim and observe that a console window (simconnect server output) is launched together with the sim. When the Scenario screen is loaded, close the sim. Now, there should be a simconnect.log file in your P3Dv4 root directory. Post it here.

    Thanks

    11. June 2017 at 13:26 #1350
    deltabravo
    Participant

    Herre we go 🙂

    In the meantime I can see the SODE entry under Options >> Addons.

    add-onns.cfg under ProgrammData\Lockheed Martin\Prepar3D v4:

    [Package.0]
    PATH=C:\Program Files (x86)\12bPilot\SODE\P3Dv4
    TITLE=SODE
    ACTIVE=true
    REQUIRED=false
    [Package.1]
    PATH=C:\Users\Dieter\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
    TITLE=FsDreamTeam Addon Manager
    ACTIVE=true
    REQUIRED=false

    Program Files (x86)\12bPilot\SODE\P3Dv4\add-on.xml:

    <SimBase.Document Type=”AddOnXml” version=”3,3″ id=”add-on”>
    <AddOn.Name>SODE</AddOn.Name>
    <AddOn.Description>SimObject Display Engine P3Dv4 (c) 12bPilot</AddOn.Description>
    <AddOn.Component>
    <Category>EXE</Category>
    <Path>..\SimObjectDisplayEngine.exe</Path>
    <CommandLine>P3Dv4</CommandLine>
    </AddOn.Component>
    <AddOn.Component>
    <Category>DLL</Category>
    <Path>..\SimObjectAnimationModule64.dll</Path>
    </AddOn.Component>
    <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>..\data\SimObjects</Path>
    </AddOn.Component>
    <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>C:\ProgramData\12bPilot\SODE\SimObjects</Path>
    </AddOn.Component>
    </SimBase.Document>

    The simcinnect.log seems too big to post it here. It has hundreds of lines. I sent it via mail.

    Thanks for the help. Appreciated.

    12. June 2017 at 05:23 #1356
    deltabravo
    Participant

    Good morning Jeffrey,

    you’re correct. I uninstalled SODE and reinstalled in the folder wich SODE proposes during installation.
    What I don’t understand is how does the sim know there is an add-onn.xml (e.g. SODE)on drive C which the sim has to see/load.

    Last fall I purchased the migration tool when I switched from FSX to P3D V3. Didn’t use it however and uninstalled it.

    C:\ProgramData\Lockheed Martin\Prepar3D v4\ddl.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
	<Descr>AceXML Document</Descr>
	<Filename>dll.xml</Filename>
</SimBase.Document>

    C:\ProgramData\Lockheed Martin\Prepar3D v4\exe.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="exe">
    <Descr>AceXML Document</Descr>
    <Filename>exe.xml</Filename>
</SimBase.Document>
    C:\Users\<USER>\AppData\Roaming\Lockheed Martin\Prepar3D v4\dll.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
	<Descr>Launch</Descr>
	<Filename>dll.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Name>FSUIPC 5</Name>
		<Disabled>False</Disabled>
		<Path>Modules\FSUIPC5.dll</Path>
	</Launch.Addon>
	<Launch.Addon>
		<Name>as_connect</Name>
		<Disabled>False</Disabled>
		<Path>as_srv\as_connect_64.dll</Path>
	</Launch.Addon>
</SimBase.Document>
    
C:\Users\<USER>\AppData\Roaming\Lockheed Martin\Prepar3D v4\exe.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
	<Descr>Launch</Descr>
	<Filename>EXE.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Name>as_btstrp_config_manager</Name>
		<Disabled>False</Disabled>
		<Path>as_srv\as_btstrp_config_manager.exe</Path>
	</Launch.Addon>
</SimBase.Document>

    As always terrific support. Thank you!

    14. June 2017 at 16:10 #1370
    deltabravo
    Participant

    Problem is solved. Top notch developer. Thank you so much.

    13. July 2017 at 05:55 #1502
    mwcorder
    Participant

    Same issue – I Think I have checked all the files mentioned above and included them below.

    [22:31:26.682] INFO : SODE Version 1.5.3
    [22:31:26.682] DEBUG : CommandLineArgs [1]: NONE!
    [22:31:26.682] FATAL : No Target Simulator Platform supplied! Shuting down…
    [22:31:26.682] INFO : Terminate SODE.
    ***********************************
    Ops: Registration, Install
    P3D Exe Path: D:\P3Dv4\Prepar3D.exe, Version: ‘4.0’
    Arguments Package: “-Configure: Category=Add-on Package, Operation=Add, Title=SODE, Path=C:\Program Files (x86)\12bPilot\SODE\P3Dv4″
    Creating Process for Add-on Package…
    RESULT: 1
    SUCCESS!
    — END —
    **************************************
    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
    Trying Path 32…
    >>> ERROR: Unable to find ‘SetupPath’ key in Registry!
    >>> ERROR: void Open
    —
    Trying to detect ‘P3Dv4’
    Hive: HKLM
    Registry Path 64: SOFTWARE\Lockheed Martin\Prepar3D v4
    Registry Path 32: SOFTWARE\Lockheed Martin\Prepar3D v4
    Key name: SetupPath
    Trying Path 32…
    ‘SetupPath’ key found in 64-Bit registry -> Install Path = ‘D:\P3Dv4\’
    Platform SimObjects file name: ‘simobjects.cfg’
    Platform Roaming path: ‘C:\Users\mwcorder\AppData\Roaming\Lockheed Martin\Prepar3d v4’
    —
    — END —
    ***********************************
    <?xml version=”1.0″?>
    -<SimBase.Document id=”add-on” version=”3,3″ Type=”AddOnXml”>
    <AddOn.Name>SODE</AddOn.Name>
    <AddOn.Description>SimObject Display Engine P3Dv4 (c) 12bPilot</AddOn.Description>
    -<AddOn.Component>
    <Category>EXE</Category>
    <Path>..\SimObjectDisplayEngine.exe</Path>
    <CommandLine>P3Dv4</CommandLine>
    </AddOn.Component>
    -<AddOn.Component>
    <Category>DLL</Category>
    <Path>..\SimObjectAnimationModule64.dll</Path>
    </AddOn.Component>
    -<AddOn.Component>
    <Category>SimObjects</Category>
    <Path>..\data\SimObjects</Path>
    </AddOn.Component>
    <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>C:\ProgramData\12bPilot\SODE\SimObjects</Path>
    </AddOn.Component>
    </SimBase.Document>
    ******************************
    [Package.0]
    PATH=C:\Program Files (x86)\12bPilot\SODE\P3Dv4
    TITLE=SODE
    ACTIVE=true
    REQUIRED=false
    [Package.1]
    PATH=C:\Users\mwcorder\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
    TITLE=FsDreamTeam Addon Manager
    ACTIVE=true
    REQUIRED=false
    [Package.2]
    PATH=C:\Program Files\Imagine Simulation\KATL Atlanta 2016 P3Dv4\
    TITLE=Imagine Simulation KATL3_PD4
    ACTIVE=true
    REQUIRED=false
    ***********************************************

    13. July 2017 at 14:31 #1503
    12bPilot
    Keymaster

    Some questions:

    1. Did you launch SimObjectDisplayEngine.exe manually? (Double clicking it…)
    2. In your running sim, do you see a “Add-Ons” entry in the menu tab? Is there a “SODE V1.5.2 within that Add-ons menu?
    3. Also in the menu tab, go to Options -> Add-Ons. Is there a SODE entry in the list of add-ons?

    SODE requires to have the FSX-SP2/X-PACK SimConnect version installed.
    4. Start SODE Platform Manager, go to Tools -> Check SimConnect Version. Results?

    13. July 2017 at 18:37 #1504
    mwcorder
    Participant

    1. Did you launch SimObjectDisplayEngine.exe manually? (Double clicking it…) YES – Had to navigate to Windows/ProgramFiles86/12bPilot/SODE in order to find it. SODE.log then shows “No Target Simulator Platform supplied. Shutting down…”
    2. In your running sim, do you see a “Add-Ons” entry in the menu tab? YES Is there a “SODE V1.5.2 within that Add-ons menu? NO
    3. Also in the menu tab, go to Options -> Add-Ons. Is there a SODE entry in the list of add-ons? YES and it is enabled

    SODE requires to have the FSX-SP2/X-PACK SimConnect version installed.
    4. Start SODE Platform Manager, go to Tools -> Check SimConnect Version. Results? “10.0.61259.0 (SP2/X_PACK is installed)”

    13. July 2017 at 20:28 #1505
    12bPilot
    Keymaster

    Thanks for your answers.

    Double clicking the SODE executable does not help, because it needs to be supplied with the information which sim is launching it. “No Target Simulator Platform supplied. Shutting down…” is the response when the user has manually tried to launch SODE, so this is expected behaviour.

    In a nutshell, you have a correctly installed SODE and SimConnect, but it is not picked up by SimConnect. There is (was) a known bug within P3Dv4, where a corrupted exe.xml prevented other installed add-ons (using the add-on.xml method) from being launched.
    This was addressed and fixed in the P3Dv4 Hotfix 1.

    Is that Hotfix 1 installed on your machine?

    13. July 2017 at 21:00 #1512
    mwcorder
    Participant

    Is that Hotfix 1 installed on your machine? Yes, I installed it 6/27/17 (only the client)

    13. July 2017 at 21:10 #1513
    12bPilot
    Keymaster

    Hmm, what happens when you delete the SODE.log and then launch the simulator, load a scenario and then quit the sim. Will a new SODE.log be generated?

    13. July 2017 at 21:40 #1514
    mwcorder
    Participant

    No, a new log was not generated. Windows/ProgramData/12bPilot/Sode/log

    13. July 2017 at 21:57 #1515
    12bPilot
    Keymaster

    To check if Simconnect launches SODE at all, you need to create a simconnect.log.
    My post above #1349 outlines the steps on how to create such a log. The only thing to change is the word verbose to normal.

    The only other thing I can imagine is an anti virus program blocking SODE…

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 23 total)
1 2
  • You must be logged in to reply to this topic.