Drzewiecki Design

Stephen, Looking at our log, the platform manager was not able to add an simobject folder entry into your fsx.cfg and hence SODE is not able to load the SimObjects. One thing to try is to run the SODEPlatformManager.exe as administrator and unregister and then again register the module. This action...

1) Removing all mentioned files and folders 2) Removing old SODE DD files removed and SODE migrated as per their guide. 3) Installing new SODE together with activating its modules via the SODE Manager ! SODE v1.3.1 installed and activated via the manager ( indicates registered & active ) 4) Ins...

Uninstalled EETN & EPWA + SODE, cleared all folders. Installed SODE v1.3.1 Installed EETN & EPWA Same issue remains: [20:44:48.979] INFO : Targetting Platform 'FSX' [20:44:48.979] DEBUG : Initializing Text Menus... [20:44:48.979] DEBUG : Initializing Seasonal Object Handler... [20:44:48.979]...

Having issues with the SODEv1.3 objects at EPWA v1.5 not been generated. SODE has been migrated to v1.3 as advised. Here is the log: [13:45:27.740] INFO : Targetting Platform 'FSX' [13:45:27.740] WARN : VDGS Pack is not found/installed! [13:45:27.740] DEBUG : Trying to read Settings from SimObjectsD...

I am just wondering, what is your statement based on? The original exe.xml containing several other entries that are removed upon installing v1.3 UUEE. Having replaced with a backup I tested again, with the same result. BEFORE v1.3 : <?xml version="1.0" encoding="windows-1252"?>...

Hi,
Installing v1.3 the exe.xml file is not been appended but overwritten therefore deleting existing entries. Fortunately I have a backup.

Checked this twice.