Sode would mot register for P3D V3 **SOLVED**

[walouigi]

Hi The sode platform manager does not register for P3D V3.
It does work for FSX and P3D V4, but not P3D V3. When I click to register
I get this error:
[P3DV3] Old Sode entries detected in exe.xml,dll.xml and simobjects.cfg at 'ProgramData' location!
Platform manager will now try to remove these entries.
I only have OK options. when I press OK nothing happened, and the sode is still not registered.
Please advise.
Thanks

[virtuali]

I'm not really sure of the issue is. As you might now, SODE it's a freeware product that is used by many sceneries, so you would probably had the same problem regardless.

It's just easier if you ZIP these files together:

C:\Programdata\Lockheed Martin\Prepar3d v3\DLLXML
C:\Programdata\Lockheed Martin\Prepar3d v3\EXE.XML
C:\Programdata\Lockheed Martin\Prepar3d v3\Simobjects.cfg

Attach them to a message, so I can fix them for you.

[walouigi]

Hi Umberto,
Ok I will do that when I get home tonight.
Thanks in advance.
Regards

[walouigi]

Hi Umberto,
As requested, please see attached my P3D V3 files that Sode is telling me it is already existed.
These files are from my program data folder
Thanks
Hani

[virtuali]

Try these files, and reinstall SODE.

And uninstall that Migration Tool, because I've think it might have caused the problem, since SODE was configured to be started in FSX mode, which seems to be a trick of the Migration tool, fooling P3D as being FSX, thus confusing every proper addon that must recognize the sim for what it is.

[walouigi]

Thank you Umberto, much appreciated.

[walouigi]

good morning Umberto,
The problem is still there, I cannot register the SODE for the P3D V3.
I have uninstalled the migration tool, and also GSX, and restarted the GSX new installation, and I have used the fixed files you have done, and same process, when I click on register, nothing is going on.
Please advise what should I do next.
Regards

[virtuali]

Try to uninstall sode and reinstall it. And be absolutely sure the Migration tool is entirely disabled.

[12bpilot]

Try to use the new SODE 1.5.2 installer -> http://sode.12bpilot.ch/?page_id=9

I just had a longer TeamViewer session yesterday with a user having a similar problem, only to find out that this Migration Tool has severely messed up the simobjects.cfg/prepar3d.cfg which confused the SODE Platform Manager totally.

Also, after clicking the "Register" button, can you navigate to C:\ProgramData\12bPilot\SODE\log and post the files PLTMGR.log and PLTMGR_DETECTION.log here? I want to have a look at those...

[walouigi]

Hi there,
Thanks for getting back to me, I am using the 15.1 SODE, as the new GSX install it automatically, with it installation process.
I have removed the migration tool as Umberto suggested with no luck
Here is the PLTMGR Log
Ops: Registration, Install
P3D Exe Path: F:\Prepar3D v3Prepar3D.exe
Arguments Package:  "-Configure: Category=Add-on Package, Operation=Add, Title=SODE, Path=C:\Program Files (x86)\12bPilot\SODE\P3Dv3"
Creating Process for Add-on Package...
 RESULT: 0
 >CODE: 2
--- END ---

and here is the PLTMGR detection log
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 = 'D:\FSX'
Platform SimObjects file name: 'fsx.cfg'
Platform Roaming path: 'C:\Users\User\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: kacke
---
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 = 'F:\Prepar3D v3'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\User\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 = 'F:\Prepar3D v4\'
Platform SimObjects file name: 'simobjects.cfg'
Platform Roaming path: 'C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3d v4'
---
--- END ---

Thanks for your help

[walouigi]

Hi There,
I don't know what I did, but I did remove everything, from the migration tool to all the FSDT product, and restarted, and now the SODE registered for all sims.
Thanks again for all your help guys, much appreciated.
Regards
Hani