Hi Ladies and Gentlemens,

The Scenery profiler team is happy to announce the official release of version 1.2.3.
This version correct a few bugs about the scenery-add-on system for Prepar3d v3 and v4.

Mainly because some of our user are using manuals definitions of their add-on.cfg files.
As they are Xml files, they don’t support any un-xml characters such as &, ‘, <, > and all extra things xml don’t like.
They are still causing managed bugs in Scenery Profiler software, but the main thing is not in here.
Scenery profiler is now capable of reading an add-on.xml file even if this add-on doesn’t fullfill the prepar3d requirements.

As some of you may know, the start of the process is going throught the differents add-ons.cfg you may have on your computer.

Some of you are filling entries in this (or theses files) manually, not according to Prepar3d fullfillments.
Just as an example: look at this file:

[Package.0]
PATH=C:\Users\Philippe\Documents\Prepar3D v4 Add-ons
ACTIVE=true
REQUIRED=false

[Package.1]
PATH=C:\Users\Philippe\Documents\Prepar3D v4 Add-ons\FsDreamTeam Addon Manager
ACTIVE=true
REQUIRED=false

[Package.2]
PATH=C:\Users\Philippe\Documents\Prepar3D v4 Add-ons\FsDreamTeam KLAS
ACTIVE=false
REQUIRED=false

[Package.3]
PATH=C:\Users\Philippe\Documents\Prepar3D v4 Add-ons\FsDreamTeam\PHNL
ACTIVE=false
REQUIRED=false

[Package.4]
Path=C:\Users\Philippe\Documents\Prepar3D v4 Add-ons\Midden Amerika
Active=true
Required=false

Everything here, seems to be fine.
However, most .ini file parser will not agree while searching for Path instead of PATH.
That’s the case in Scenery Profiler, because I use a IniFileParser who can make a difference between PATH and Path. So this leads to errors in interpreting this file.

Ok, gratefully with some customers help, I’ve been able to discover this probem and solved it.

Now, going ahead, the Path key lead us (normally) to a {Path}\add-on.xml file.

Here again, some people, fill the information without taking care of what should be the content of an .xml file.
Please remember that some characters are not allowed in xml, and as an example I can inform you that ‘, <, >, &, are not allowed in xml files.

So what should happen if your software (in that case Scenery Profiler) find an entry like this one:

<AddOn.SceneryComponent>
<Path>M:\Midden amerika\Mexico\Ponciano Arriaga Int’l San Louis Potosi MMSP</Path>
<SceneryCRC>1836090399</SceneryCRC>
</AddOn.SceneryComponent>

Well, i would say that just an exception will occur…
And this is just because the correct entry would be:

<AddOn.SceneryComponent>
<Path>M:\Midden amerika\Mexico\Ponciano Arriaga Int&apos;l San Louis Potosi MMSP</Path>
<SceneryCRC>1836090399</SceneryCRC>
</AddOn.SceneryComponent>

So, Version 1.2.3 is taking care of that and (normally) shouln’d cause you any problem.

However, I don’t say that some of you may not encounter problem of this kind.
But, if you have any problem, you are now knowing on where to search and correct this problem.

Appart this disgression, version 1.2.3 is available here for those having a licence key:

https://drive.google.com/open?id=0B47_IgTrbC23TEsyeENBQnF3aVU

Happy flying to everybody !!!