Install scenery with XML method using Addon Organizer

[Seat* 53]

I will install a scenery with the XML method using Addon Organizer. I understand how I do with the usual bgl and texture files but do not know how to handle the files that are going to the main scenery folder into P3D and also how do I do with Airport elevation adjustment files that will be to scenery / world. I cannot find any instructions on how to do this.

From beginner with xml in Sweden

 

/Thomas

[Lorby_SI 2,038]

Hello Thomas,

 made a short photo documentation about how to add legacy scenery. The thread covers base layers and effects too:

 

Best regards

Edited June 29, 2019 by Lorby_SI

[Seat* 53]

Thanks for the reply. It works well. However, I have a question. When installing a scenery I got an error message. There was a problem with addons.cfg in appdata / rroaming / Lockhead Martin / P3D. It turned out that because I use the Swedish letters å, ä and ö, the name of the folder had been replaced by?. I changed to another spelling so the problem was solved. My question is whether you can use the letters å, ä and Ö.

/Thomas

[Lorby_SI 2,038]

35 minutes ago, Seat* said:

 

Thanks for the reply. It works well. However, I have a question. When installing a scenery I got an error message. There was a problem with addons.cfg in appdata / rroaming / Lockhead Martin / P3D. It turned out that because I use the Swedish letters å, ä and ö, the name of the folder had been replaced by?. I changed to another spelling so the problem was solved. My question is whether you can use the letters å, ä and Ö.

/Thomas

Hello Thomas,

Can you please be a little more specific about what went wrong where exactly? Where were those characters and what was the error?

P4AO shouldn't have a problem with localized characters. This sounds more like some other product changed the character encoding of the add-ons.cfg file. That happens a lot, because for whatever reason, many developers don't pay attention to text file encoding. Make sure that the add-ons.cfg is encoded in UTF-16 (UCS-2 LE BOM).

Edit: I just checked with German Umlaut characters (Ä, Ü, Ö). They work just fine in P4AO, as folder names, add-on names and add-on descriptions. 

Best regards

Edited July 3, 2019 by Lorby_SI

[Seat* 53]

Hello Oliver!

The message I received was "Error when reading config file" "Illegal characters in path" and the error occurred in app data roaming add-on.cfg. I tried to reproduce the error by registering another airport with the letter Ö in the name. The same error occurred again. I then used the Tools "Check encoding" tab and it turned out that there were errors on two files. Add-ons.cfg in both app data / roaming and application data. Both files appeared to be error-coded in UTF-8. I changed both files to UCS-2 LE-BOM.

Now everything works great and thank you for putting me on the track. Although you have written several times about this, it is important to pay attention to the correct encoding.

/Thomas