Faulting application name: SimObjectDisplayEngine.exe, version: 1.6.4.0

Home Forums Support Faulting application name: SimObjectDisplayEngine.exe, version: 1.6.4.0

Topic Resolution: Resolved
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #3487
    viperxbr
    Participant

    Greetings,

    I’ve seem to have a problem with SODE upon P3Dv4.5 startup.  The SimObjectDisplayEngine.exe keep crashing when starting P3D.  This started happening after I had a crash after a flight with the FSL Airbus.  While shutting down P3D, it crashed before gracefully finishing shutting down.  Very common occurrence with only this aircraft.

    Anyways,  after that incident, SODE will not run.  I’ve tried completely uninstalling and re-install SODE but no luck.  I’ve wiped the Prepar3d.cfg file and recreated a new one but still no go.

    Short of re-installing P3D completely, anyone have any ideas?

    Thanks,

    Todd.

    The Windows error below and see attached:

    ————————

    Faulting application name: SimObjectDisplayEngine.exe, version: 1.6.4.0, time stamp: 0x5c100d47

    Faulting module name: SimObjectDisplayEngine.exe, version: 1.6.4.0, time stamp: 0x5c100d47

    Exception code: 0xc0000409

    Fault offset: 0x000b3c45

    Faulting process id: 0x4fc

    Faulting application start time: 0x01d55e1d056d9ce5

    Faulting application path: E:\Apps\12bPilot\SODE\SimObjectDisplayEngine.exe

    Faulting module path: E:\Apps\12bPilot\SODE\SimObjectDisplayEngine.exe

    Report Id: 91459110-e281-4626-8445-f2ccfab6b268

    Faulting package full name:

    Faulting package-relative application ID:

    ——————

     

    • This topic was modified 4 years, 7 months ago by viperxbr.
    Attachments:
    You must be logged in to view attached files.
    #3490
    viperxbr
    Participant

    Update: Resolved.

    So there seems to be a parameter in the “add-on.xml” that P3D accepts but SODE completely yaks when used.

    What I also did just before this started happening was rearranging some of my scenery using the “DiscoveryPath” option in the add-ons.cfg file.  In a couple of the scenery directories, used the following config in the add-on.cfg file:

     

    <AddOn.Component>

    <Category>Scenery</Category>

    <Path>.</Path>          <——– Note the “.” aka “current directory”.

    <Name>Big scenery</Name>

    </AddOn.Component>

     

    Using the period “.” as the current directory caused SODE to to crash completely.  P3D has no problem with that parameter.

    So what I did to resolve the issue was added “Scenery” as the path and then added the Texture entry as well.

    Hopefully the Dev(s) at SODE will have a look at this and maybe support this option down the road.

    Thanks!  Todd.

    • This reply was modified 4 years, 7 months ago by viperxbr.
    #3492
    viperxbr
    Participant

    Correction, this issue is in the “add-on.xml” file, not “.cfg”.

    Can’t edit my previous post anymore.

    #3501
    12bPilot
    Keymaster

    Hi Todd,

    Thanks for your report and the solution.

    You are right, SODE was not able to handle that single “.” relative folder. I have fixed it and SODE will internally generate the full path now also for the relative base folder “.”, including subfolders of that.

    The only strange thing was that SODE does not process “Scenery” categories, only “SimObject” types.

    • This reply was modified 4 years, 6 months ago by 12bPilot.
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.