Jump to content

lddu red x insted of jetways


Recommended Posts

Thanks, however, it is doing this, according to the log.

 

[11:28:37.360] INFO  : SODE Version 1.6.4
[11:28:37.360] INFO  : Targetting Platform 'P3Dv3'

 

and then this

 

[11:28:37.445] INFO SODE.XML : Non-existing directory at \sdx\Turbulent\. [C:\ProgramData\12bPilot\SODE\sdx\Turbulent\*.sdx]

 

and this

 

[11:28:37.445] INFO SODE.XML : xml File Found: aerosoft_ENGM_SODE_Jetways.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: aerosoft_ENGM_SODE_Windsocks.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: DRS_LIMC_CTRL.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: Flightbeam_KSFOHD.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: JustSim_LFMN_Stands.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: LFMN.xml!
[11:28:37.445] INFO SODE.XML : xml File Found: ORBX_LDDU.xml!
[11:28:37.445] DEBUG  : Trying to build SimObject List out of XML definition files...
[11:28:37.445] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\aerosoft_ENGM_SODE_Jetways.xml'
[11:28:37.449] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\aerosoft_ENGM_SODE_Windsocks.xml'
[11:28:37.452] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\DRS_LIMC_CTRL.xml'
[11:28:37.453] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\Flightbeam_KSFOHD.xml'
[11:28:37.462] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\JustSim_LFMN_Stands.xml'
[11:28:37.467] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\LFMN.xml'
[11:28:37.467] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\ORBX_LDDU.xml'
[11:28:37.468] DEBUG SODE.XML : XML Data successfully read and List created.

 

but then it all goes wrong

 

[11:28:37.477] DEBUG SODE.FOLDERMANAGER : 'C:\ProgramData\Lockheed Martin\Prepar3d v3\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...
[11:28:37.477] DEBUG SODE.FOLDERMANAGER : 'C:\Users\eyals\AppData\Roaming\Lockheed Martin\Prepar3d v3\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...
[11:28:37.477] DEBUG SODE.FOLDERMANAGER : 'C:\ProgramData\Lockheed Martin\Prepar3d v3\add-ons.cfg' does not exist! Extraction of Add-On Package Paths not performed...
[11:28:37.477] DEBUG SODE.FOLDERMANAGER : 'C:\Users\eyals\AppData\Roaming\Lockheed Martin\Prepar3d v3\add-ons.cfg' does not exist! Extraction of Add-On Package Paths not performed...

 

because it is apparently looking for something that you say you do not have.

 

Can you delete the log and try again, to see what SODE is actually doing?

Link to comment
Share on other sites

Thanks,

It's doing the same, looking for your P3D v3 installation.

 

[12:14:32.159] DEBUG SODE.FOLDERMANAGER : 'C:\ProgramData\Lockheed Martin\Prepar3d v3\simobjects.cfg' does not exist! Extraction of SimObject Paths not performed...

 

I would guess that SODE only looks for installed simulators,

in my case I have a PLTMGR log for FSX, FSX-SE and P3D v4, all of which are actually installed

and therefore do have files to be found.

 

Yours seems to have found, presumably in the registry, P3D v2, P3D v3 and P3D v4.

Then it seems to start for P3D v3, which you don't have and it therefore finds no files.

 

I am assuming that you have used the SODE manager to make sure that it is NOT registered for

P3D v2 or P3D v3, did you?

 

If so, you could try cleaning up your registry, if indeed it does contain registry entries for all three P3D versions.

 

 

Link to comment
Share on other sites

Yes, because it is looking for P3D v3 and not working in V4.

 

The red X means that SODE is being told to place an object but that it cannot find that object,

as clearly written in the log.

Apparently it cannot find the object because it is looking in the wrong place:

 

From the log: 'C:\ProgramData\Lockheed Martin\Prepar3d v3\simobjects.cfg' does not exist!

Link to comment
Share on other sites

Just going through this thread and was thinking same as Nick: reinstall SODE.

In a few instances I have found that re-installing SODE solved the problem.

Just a comment,

Cheers,

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...