P3Dv5 scenery.cfg issue: the Saga Continue

[scowms32 2]

After installing P3Dv5, along with Orbx and Flightbeam scenery files.....I started getting an error message stating there was an issue with my scenery file.  I viewed my scenery.cfg files and noticed that the sequential numbering was all out of order.  Also, I noticed that some of the files identified in the scenery library within the sim appeared to be out of order compared to my v4.4 files.  Is there a way I can do a reinstall of my original scenery file?  Also, I noticed at some airports add-on airports the scenery is totally wrong (black blotches, discoloration and missing tiles).

[Gumerson 73]

Did you open Orbx Central for some reason? Every time I do I make a backup of my scenery. 

[downscc 1,327]

Neither Orbx nor Flightbeam use scenery.cfg to install their products.  Something else corrupted your scenery.cfg; what might that have been?

Almost all developers are now using the SDK recommended method involving an add-on.xml file that is added to P3D in any one of several ways.

[scowms32 2]

10 minutes ago, downscc said:

Neither Orbx nor Flightbeam use scenery.cfg to install their products.  Something else corrupted your scenery.cfg; what might that have been?

Almost all developers are now using the SDK recommended method involving an add-on.xml file that is added to P3D in any one of several ways.

I installed the scenery via their programs (orbx central and flightbeam manager) as recommended and this is what I received.  I am not blaming it on their products, but this is what I ended up with.  Maybe I am using the wrong verbiage.  

Edited April 30, 2020 by scowms32

[Dick 47]

Can you share  the actual error message with us ?  Did you set the insertion point in ORBX Central ? 

[Jac_49 35]

Try FREE: Lorby Prepar3D Addon Organizer

this is a fantastic tool to fix problems with the scenery

[Christopher Low 5,332]

10 hours ago, downscc said:

Neither Orbx nor Flightbeam use scenery.cfg to install their products.  Something else corrupted your scenery.cfg; what might that have been?

That is not entirely true, Dan. I installed all of my ORBx software directly into my Prepar3D v4 folder (with ORBx Central), and this was done via the scenery.cfg method (the entries are not greyed out, and they can be enabled and disabled separately).

Edited April 30, 2020 by Christopher Low

[downscc 1,327]

3 hours ago, Christopher Low said:

That is not entirely true, Dan. I installed all of my ORBx software directly into my Prepar3D v4 folder (with ORBx Central), and this was done via the scenery.cfg method (the entries are not greyed out, and they can be enabled and disabled separately).

That is interesting... using FTX Central all of my Orbx are added with add-on.cfg entries per SDK.  Perhaps you have not migrated your products to a library?  That's it.... if one remains in the legacy method by not installing products via an Orbx Library then of course then you are still using the legacy method used by FSX.  Yeah, I've moved on from that a long time ago and incorrectly assumed others have as well.

Thanks.

[joby33y 152]

That is good info Dan!  I *just recently moved to the new Orbx Central (from the old FTX Central) so I want to ensure my understanding is correct.   So just to be clear :

- choosing 'install directly into Simulator" will use the legacy method ; 

- choosing 'install into main library" will use XML package method.  

 correct ? 

cheers, 

[scowms32 2]

19 hours ago, dick said:

Can you share  the actual error message with us ?  Did you set the insertion point in ORBX Central ? 

I am getting the following message after clicking "ok" to close the scenery library screen within P3dv5 "Prepar3D has detected non-sequential layer ordering within the scenery library list.  Would you like Prepar3D to attempt to repair this issue?"  Even after selecting yes, or going in to fix the ordering, I still get the same error message.

 

And yes, I did set the insertion point in ORBX Central.  

Edited April 30, 2020 by scowms32

[Bob Scott 7,715]

Are you running P3D as administrator?  Sounds to me like maybe you have a problem with not having write access to some config files.