1 hour ago, Lorby_SI said:

This gives me an idea about how one may be able to automatically rebuild a certain layering, even if ORBX Central is run. I need to think about that a bit more

I think a great many of us would appreciate that, thankyou!

6 hours ago, Lorby_SI said:

If you are using P4AO to sort out your layers, the groups and everything else work normally - until you run ORBX Central again. After that you will have to sort out your layers again. The groups themselves are independent of layering, they only care about scenery titles.

Thanks so much!

6 hours ago, Lorby_SI said:

IMHO, what ORBX should have done is, to load the whole scenery library config into a temporary structure, then find the insertion point, insert the ORBX assets, renumber the scenery library, and then save it again - across all add-on.xml files and the scenery.cfg. That is what P4AO does and it is not particularly hard to achieve. As long as the scenery layering remains the same, nobody will complain that all scenery config files have been updated.

This gives me an idea about how one may be able to automatically rebuild a certain layering, even if ORBX Central is run. I need to think about that a bit more.

Hope ORBX will take the advise of a proven expert onboard, and I'm looking forward to whatever you're considering here. Thanks.

On 10/18/2019 at 10:46 PM, QuaxTheSnoopie said:

My question: does Central 4 change this behaviour, means: does Central 4 respect all add-ons and renumber their layers in a correct non-duplicate way (as "it now integrates add-on.xml") ?

The version 4 does, but only if the sceneries are active. If everything is active, and "Advanced Layering" (I think that's what it's called) is activated, it doesn't rearrange anymore.

On 10/21/2019 at 1:20 PM, d.tsakiris said:

The version 4 does, but only if the sceneries are active. If everything is active, and "Advanced Layering" (I think that's what it's called) is activated, it doesn't rearrange anymore.

Yes I've seen the same. It is very annoying that it is like that and I'm not sure how come it's like that? How come it doesn't treat every entry the same way?

Because P4AO uses a (don't quote me on this) small hack to deactivate sceneries. ORBX Central doesn't recognize those entries...yet, FTX is aware of this and might change that.

23 hours ago, d.tsakiris said:

Because P4AO uses a (don't quote me on this) small hack to deactivate sceneries. ORBX Central doesn't recognize those entries...

That is correct, as stated in the user manual right at the beginning. Technically those disabled entries are broken, they invalidate the add-on.xml. But this only applies when you don't use the "strict package law". Make sure that when using ORBX Central the "strict package law" is active on the settings page in P4AO - no hacks in that mode.

I have been pestering Lockheed about adding an "<Active>" tag to the Addon.Components of the packages since V4 was released (with the default value being "true" to avoid compatibility issues with add-on.xml that don't have it). Or the opposite tag "<Disabled/>". That would allow us to disable single Components instead of having to shut down the whole package. But unfortunately that never happened, it must be a major problem for them.

Best regards

 

Edited October 27, 20196 yr by Lorby_SI