18 minutes ago, Lorby_SI said:

Hello Dave,

your add-ons.cfg still has UTF-8 BOM encoding. I am not sure why, it probably had it before too. I don't dare change the encoding automatically with P4AO. I could, but worst case that can also screw up the file completely. 

You must change it to UCS-2 LE BOM with Notepad++ or send it to me via email so I can change it. And I need it in the "non-broken" state too, just to make sure.

Are you using any other config addons that might do this?

Best regards 

 

I am not using anything else that might do this that I know of.  Can you send me your email in a DM?

 

Dave

Just now, tubbsds1 said:

I am not using anything else that might do this that I know of.  Can you send me your email in a DM?

 

Dave

Hello Dave,

address is on the last page of the manual.

Best regards

10 minutes ago, Lorby_SI said:

Hello Dave,

address is on the last page of the manual.

Best regards

Ok emails sent.

 

Hi Oliver,

I don't know whether it's relevant, but I notice that the SODE entry is now on its own in the ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg (*)

[Package.0]
Path=C:\Program Files (x86)\12bPilot\SODE\P3Dv4
Title=SODE
Active=FALSE
Required=FALSE

(As you can see SODE is currently disabled as I have yet to check whether it needs to be updated after moving recently to Prepar3D v4.5.12.30293)

(*) I believe this happened after updating and running P4AO v1.40.b06

In my case, Packages 0-15 are resident in the AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg

[Package.0]
Path=C:\Users\Cruachan\Documents\Prepar3D v4 Add-ons\A2A
Active=TRUE
Required=FALSE

Regards,

Mike

 

5 hours ago, Cruachan said:

I don't know whether it's relevant, but I notice that the SODE entry is now on its own in the ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg (*)

(*) I believe this happened after updating and running P4AO v1.40.b06

No, SODE itself has always been installing to the add-ons.cfg reference file in ProgramData. This is correct too, since SODE is a global, non user-specific addon.

Addons that you install with add-on.xmls in "Documents\Prepar3D V4 Addons" have their own add-ons.cfg reference file in AppData\Roaming, because they are local to your user account. Account name "harry" on your computer can't access "mikes"'s Documents folder, so the simulator itself puts them in the local, user-mike-specific config files. (this mechanism was broken in 4.4 but LM has fixed it again in 4.5)

Best regards

 

Edited June 2, 20197 yr by Lorby_SI

Hello @ll,

to avoid having this thread get ever more confusing, I am locking it. The problem that "tubbsds1" described above has been fixed, it was indeed the incorrect encoding as expected.

1. What is the problem:
   If the file "C:\ProgramData\Lockheed Martin\Prepar3D V4\add-ons.cfg" has ASCII character encoding, then P4AO 1.41 will make matters worse by changing the encoding to UTF-8 BOM
   This encoding cannot be read by SODE and causes some kind of internal error state. Why SODE wants to read that file and why the UTF-8 BOM encoding causes an error I don't know.
    
2. How to check if I have this problem:
   In P4AO go to "Tools" and click on "Check encoding" on the top left.
    
3. What is the solution:
   Download and install the latest version of P4AO (1.42+)
   Fix the encoding of the file "C:\ProgramData\Lockheed Martin\Prepar3D V4\add-ons.cfg". THIS IS A MUST, P4AO does not correct it for you.
   -> Open the add-ons.cfg in Notepad++ (As Administrator), go to the top menu "Encoding" and select "Encode in UCS-2 LE BOM". Save.

I didn't find out what is breaking the encoding in the first place. This can only happen when a user edits the add-ons.cfg or if an installer writes directly to the file. Both actions must be avoided at all cost! If you want to add packages to this file or remove them, use the P3D CLI "Learning Center -> Software Development Kit (SDK) -> Add-ons -> Add-on Configuration Files -> Configuration via Command Line" NEVER EDIT THIS FILE DIRECTLY!

Best regards

 

Edited June 2, 20197 yr by Lorby_SI