3 hours ago, aeronauta said:

Sorry Oliver, that is not correct, I have OZx at Layer 999 and whatever I install (without using the xml ) will vbe undert it...I get the msg that the scenery.cfg is wrong and will be corrected.

Jorge

If you leave gaps in the scenery.cfg then you will get an error message, that is like it always was. I don't edit the scenery.cfg at all and do everything with XMLs files, so things look a bit different from my perspective. I have completed my scenery ordering tool today, and I will stop worrying about this now :o))

But just to be clear: the layer tags and the priority are reciprocal. On the scenery library dialog in P3D you are seeing the priority, not the layer. The priority is a completely virtual value on that dialog that does not exist as a parameter - and it is the opposite of the layers. Assuming your highest layer number is 130, then it will have priority 1 and appear on the top of the list in P3D. The base layer of the scenery.cfg has layer 1 - but priority on that dialog will be 130.

Best regards

13 hours ago, Lorby_SI said:

Sure, here you go. This will add Aerosoft LIEO, that I have in my FSX:SE installation, to P3D V4 right above the default scenery (126 is the last entry of the defaults - until something screws up the cfg...).

I will finish my scenery sorting app today, that should help.

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>LIEO</AddOn.Name>
<AddOn.Description>Aerosoft LIEO</AddOn.Description>
<AddOn.Component>
<Category>Scenery</Category>
<Path>C:\Program Files (x86)\Steam\SteamApps\common\FSX\Addon Scenery\LIEO</Path>
<Name>LIEO</Name>
<Layer>127</Layer>
</AddOn.Component>
</SimBase.Document>

Best regards

Does the layer element dictate where it goes in scenery.cfg?

I wouldn't mind seeing your utility as well.

2 hours ago, ahuimanu said:

Does the layer element dictate where it goes in scenery.cfg?

I wouldn't mind seeing your utility as well.

The layer dictates where it goes in the complete library - which is comprised of scenery.cfg and all the add-on.xml's. P3D will sort out layer number conflicts, but it is better to avoid them IMO.

The scenery organizer has a few teething problems, but it is getting there. Just send me a PM, you can try the beta if you want.

Best regards

Just read through this topic ; people now are modifying the xml files...What about straight forward installation without having to read the SDK ?

I have 100+ scenery addons and I now manually have to make xml entries ?

38 minutes ago, GSalden said:

Just read through this topic ; people now are modifying the xml files...What about straight forward installation without having to read the SDK ?

I have 100+ scenery addons and I now manually have to make xml entries ?

Actually, you would only need one xml file, if you install all your own scenery into the same external folder. If they are not installed that way, you can still use one single XML file where you drop in all your paths. I already made an app to support this, and it won't be long until others will appear - or LM integrates a management tool into the sim itself.

Why? Because the manufacturer of the platform recommends it. I suppose that they know why they do that. Imagine the next point release of P3D would reset your scenery.cfg back to default. Imagine the scenery.cfg is removed completely with some point release. Etc. The XML files will even survive a complete uninstall and cleanout of the base simulator platform.

This method of configuration through automatically discovered XML files is very common in the "real" software world.

Best regards

7 minutes ago, Lorby_SI said:

Actually, you would only need one xml file, if you install all your own scenery into the same external folder. If they are not installed that way, you can still use one single XML file where you drop in all your paths. I already made an app to support this, and it won't be long until others will appear - or LM integrates a management tool into the sim itself.

Why? Because the manufacturer of the platform recommends it. I suppose that they know why they do that. Imagine the next point release of P3D would reset your scenery.cfg back to default. Imagine the scenery.cfg is removed completely with some point release. Etc.

"Straight forward" as the automated installers do is IMHO a no-go for a professional platform. The method of configuration through automatically discovered XML files is very common in the "real" software world.

Best regards

At this moment my addon scenery is devided over 4 SSD's , so if 80% can work in v4 I manually have to copy , paste and modify xml files 80+ times....

I need a tool that I can use to read my v3 scenery.cfg file and xml files and then can add them to v4 ...

 

26 minutes ago, GSalden said:

At this moment my addon scenery is devided over 4 SSD's , so if 80% can work in v4 I manually have to copy , paste and modify xml files 80+ times....

I need a tool that I can use to read my v3 scenery.cfg file and xml files and then can add them to v4 ...

 

Or you use my Scenery Organizer to do that (once it is tried and tested - unless you want to try the beta). No manual editing of anything is necessary, you just point it at the "old" scenery folders. You would be no better off than adding everything to the scenery.cfg through the P3D dialogs other that it automatically creates the proper XML file for you.

About the automatic conversion of an old scenery.cfg - I have thought about this, but I am not sure that it would be a good way to go. It is not hard to do, maybe an hour of programming at most, but I am worried that it enables people to really screw up their setup. I will think about it, maybe include it into my app.

Best regards

AA at some airports addons like flytampa still some jaggies and shimmering using 4k and 4msaa

Ssaa cripples performance on titans sc in sli 

Anyone else see this?

51 minutes ago, Lorby_SI said:

Or you use my Scenery Organizer to do that (once it is tried and tested - unless you want to try the beta). No manual editing of anything is necessary, you just point it at the "old" scenery folders. You would be no better off than adding everything to the scenery.cfg through the P3D dialogs other that it automatically creates the proper XML file for you.

About the automatic conversion of an old scenery.cfg - I have thought about this, but I am not sure that it would be a good way to go. It is not hard to do, maybe an hour of programming at most, but I am worried that it enables people to really screw up their setup. I will think about it, maybe include it into my app.

Best regards

I have to wait as I use Prosim and it will be compatible at the end if august.

 

Hello Everyone,

Very useful thread.

Is "Scripts" also supported in the xml method?

I don't see it listed here: http://www.prepar3d.com/SDKv4/sdk/add-ons/add-ons_overview.html

Thanks!

Today I installed V4 and did a "quick and dirty" test by just replacing the V4 scenery.cfg with the one of V3. I also copied and partly renamed the relevant autogen files from the autogen folder for photo scenery. All backuped. Most sceneries and autogen seem to work, although it is not recommended this way. Has anybody else tested this this way? I will check the official method if I have more time.

12 hours ago, nidaren said:

Hello Everyone,

Very useful thread.

Is "Scripts" also supported in the xml method?

I don't see it listed here: http://www.prepar3d.com/SDKv4/sdk/add-ons/add-ons_overview.html

Thanks!

One can use the P3d command line interface  to install add-ons. Check the SDK.

On 13/06/2017 at 11:46 PM, Cargostorm said:

Today I installed V4 and did a "quick and dirty" test by just replacing the V4 scenery.cfg with the one of V3. I also copied and partly renamed the relevant autogen files from the autogen folder for photo scenery. All backuped. Most sceneries and autogen seem to work, although it is not recommended this way. Has anybody else tested this this way? I will check the official method if I have more time.

Doing it that way, you would miss any custom effects and sounds that may have been installed by the add-ons into the P3D v3 folders, which would be absent in your P3D v4 installation and not referenced by scenery.cfg.

1 hour ago, steve40 said:

Doing it that way, you would miss any custom effects and sounds that may have been installed by the add-ons into the P3D v3 folders, which would be absent in your P3D v4 installation and not referenced by scenery.cfg.

Of course I have also copied the files in the effects, sound and scenery/world folder. Alternatively, you can also make custom entries in the effects.cfg/sound.cfg in the Program Data folder and hinting them to the V3 installation..

 

1 hour ago, Cargostorm said:

Of course I have also copied the files in the effects, sound and scenery/world folder. Alternatively, you can also make custom entries in the effects.cfg/sound.cfg in the Program Data folder and hinting them to the V3 installation..

 

How do you know in advance if a scenery has effect / sound files / world folder files using the XML methode ?

Here I still use the scenery.cfg methode and I have saved my effect / sound / world folder files files from V3 and copied them into v4.