- This topic has 8 replies, 2 voices, and was last updated 6 years, 1 month ago by afonso_am.
-
AuthorPosts
-
3. February 2018 at 18:20 #2130afonso_amParticipant
Recently my SODE stopped working, so I went to check the Platform manager and it says that SODE is registered but the module is not active. However I am unable to activate it the module and to unregister SODE. I have tried uninstalling and reinstalling but the issue persists. I’m using version 1.5.3 with P3D v4.1
- This topic was modified 6 years, 1 month ago by afonso_am.
8. February 2018 at 15:43 #214512bPilotKeymasterThis is strange, since I am using Prepar3D.exe itself to activate/deactivate SODE.
Were you trying to do the actions while P3D was running?10. February 2018 at 13:25 #2146afonso_amParticipantNo, P3D was shutdown, I tried restarting and reinstalling SODE and the issue persisted.
This is what I see:Attachments:
You must be logged in to view attached files.11. February 2018 at 18:09 #215212bPilotKeymasterCan you upload/post your add-ons.cfg from here C:\ProgramData\Lockheed Martin\Prepar3D v4 ?
11. February 2018 at 22:54 #2156afonso_amParticipantHere it is:
[Package.01]
PATH=C:\Users\Afonso\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
TITLE=FsDreamTeam Addon Manager
ACTIVE=true
REQUIRED=false
[Package.02]
PATH=C:\Users\Afonso\Documents\Prepar3d v4 Add-ons\FSLabs
TITLE=FSLabs Aircraft Family
ACTIVE=true
REQUIRED=false
[Package.03]
PATH=C:\Users\Afonso\Documents\Prepar3d v4 Add-ons\Spotlights
TITLE=FSLabs Spotlights
ACTIVE=true
REQUIRED=false
[Package.04]
PATH=C:\Program Files (x86)\12bPilot\SODE\P3Dv4
TITLE=SODE
ACTIVE=true
REQUIRED=false
[Package.0]
PATH=D:\Flight Simulators\Prepar3D v4\Ecosystem\aerosoft\Anchorage Professional
TITLE=Aerosoft Sim-wings Anchorage Professional
ACTIVE=false
REQUIRED=false12. February 2018 at 08:23 #215712bPilotKeymasterOk, that cfg file got corrupted. Did you edit it yourself or did you install an add-on lately? SODE can’t be the root cause, since it uses native P3D routines to make the entry into that file.
As per P3D SDK, the [Package.N] entries must be continous with no gaps in between, starting with 0.
- [Package.0]
- [Package.1]
- [Package.2]
- [Package.3]
[Package.01] for example is clearly not valid. All those add-ons in your cfg with 01, 02, 03, 04 won’t load. I’ve just tested it here on my PC.
If it was an installer that corrupted that file, please report that to the add-on developer.
You can clean it up manually by correcting the numbers and put them in a nice sequence as defined above.
12. February 2018 at 17:28 #2158afonso_amParticipantJust did, SODE now works, however, the indications on the Platform manager are still the same.
12. February 2018 at 18:34 #215912bPilotKeymasterThen the cfg is still somewhat corrupted.
I’d just delete it alltogether and re-install the add-ons in question freshly. P3D will generate a new one for you.
14. February 2018 at 15:24 #2160afonso_amParticipantThat appears to have done the trick, thanks!
-
AuthorPosts
- You must be logged in to reply to this topic.