We should not need Addon Organiser to do the job that ORBx Central should be doing in the first place. It sounds like it needs to do a better job of keeping track of scenery layers on individual user systems.

Edited September 1, 20196 yr by Christopher Low

47 minutes ago, kevinfirth said:

I also had the same issue with objectflow as described by Pete Dowson.

I have not yet migrated any Orbx product to Add-on.xml

 

1. The objectflow folder in the documents folder should be deleted, it was for FTX Central and is redundant for Orbx Central.

2. If no Orbx files have been migrated, then there are no add-on xml scenery library entries and the Orbx Insertion Point

function works in exacly the same way as before, introducing three blocks of entries.

This method of adding to the scenery library is incapable of creating duplicate entries but of course if "AO" has been used to

set an xml entry and then Orbx Central is used aftterwards, the add-onxml entry may well conflict, if given the same scenery layer number.

The two work perfectly well together if the add-on xml entries are numbered around the pre-existing Orbx blocks, as has been the case since the release of FTX Central in November 2016.

Edited September 1, 20196 yr by Reader

3 minutes ago, Christopher Low said:

We should not need Addon Organiser to do the job that ORBx Central should be doing in the first place. It sounds like it needs to do a better job of keeping track of scenery layers on individual user systems.

 

I doubt if the software has yet been written that can look at an individual scenery library and without

customer input, determine how many and which of the hundreds of available addons have been added

using the xml method and where in the scenery library they should be, before reading the customer's mind

to find out which order the customer prefers and then editing the same add-on.xml files from myriad developers

which have been stored wherever the individual customer's whim has chosen.

Perhaps this would be a useful thing to do while you wait for TEGB Central.

That's why I still use the old method. I can switch the Scenery Library order, and enable or disable individual scenery packages at will from within the simulator.

59 minutes ago, Reader said:

 

I doubt if the software has yet been written that can look at an individual scenery library and without

customer input, determine how many and which of the hundreds of available addons have been added

using the xml method and where in the scenery library they should be, before reading the customer's mind

to find out which order the customer prefers and then editing the same add-on.xml files from myriad developers

which have been stored wherever the individual customer's whim has chosen.

Perhaps this would be a useful thing to do while you wait for TEGB Central.

It should be possible to read a customer's configuration and insert later numbers as they specify, orbx (not unreasonably) chose to only control their own insertions through OC, no others.  This works for default installations with orbx scenery, which will.probably be the majority of their users, but not for a minority with more complex requirements.

1 hour ago, Reader said:

 

1. The objectflow folder in the documents folder should be deleted, it was for FTX Central and is redundant for Orbx Central.

2. If no Orbx files have been migrated, then there are no add-on xml scenery library entries and the Orbx Insertion Point

function works in exacly the same way as before, introducing three blocks of entries.

This method of adding to the scenery library is incapable of creating duplicate entries but of course if "AO" has been used to

set an xml entry and then Orbx Central is used aftterwards, the add-onxml entry may well conflict, if given the same scenery layer number.

The two work perfectly well together if the add-on xml entries are numbered around the pre-existing Orbx blocks, as has been the case since the release of FTX Central in November 2016.

I think this is describing what I tried to  outline earlier..unless I'm mistaken?

I wonder how much these problems are affecting Orbyx sales

I am certainly not ready to expose a functioning set of sims,P3D,XPlane,FSX to this particular program at the moment

I would be buying a lot of Orbyx stuff normally because it is so good

xxd09

Luckily the new Belgrade can be installed using FTX C.

Not Orbx, but the customer decides which scenery order he wants ...

3 hours ago, Reader said:

1. The objectflow folder in the documents folder should be deleted, it was for FTX Central and is redundant for Orbx Central.

It was deleted. But there was still the reference to it in the Addons.cfg file, the one made by P3D when you enable addons placed in the Documents folder. That entry should also have been deleted.

So I restored the Addons folder in Documents, then used AO to remove that package, which did it properly. However, it was not clear what to do until I saw the newer ObjectFlow package listed in AO.

Pete

 

Hello Pete,

as I understand it, once the objectflow folder in the Documents folder has gone, the next time P3D is started,

that objectflow entry in the add-ons.cfg file is automatically removed.

I observe that each time P3D is started, among other things that it does is scan the documents folder

and only adds to the programdata add-ons.cfg file the add-on.xml details that it finds there.

Any entries that were there but are no longer are cleaned up.

Therefore, all that is needed is to delete the objectflow folder in the Documents folder and restart P3D.

I expect that it does the same for any add-on, wherever its add-on.xml file is.

On the other hand, if an add-on is only disabled in the add-ons menu and its add-on.xml file is still there,

it then leaves the entry in the add-ons.cfg file but marks it as Active=False.

This seems to persist between P3D sessions.

Edited September 1, 20196 yr by Reader

8 hours ago, Reader said:

as I understand it, once the objectflow folder in the Documents folder has gone, the next time P3D is started,

that objectflow entry in the add-ons.cfg file is automatically removed.

Good. I understand, thanks. But I always use AO first to check that my Orbx layers are where I want them. It is that which "seriously" warns about the missing Documents folder.

Pete

 

You guys are conversing so above my head! I own tons of ORBX scenery as well as a lot of others. Haven’t loaded the new ORBX central but don’t understand all the reasons I perhaps shouldn’t. Where can a basic operator like me go to learn in simple terms how scenery is supposed to be installed and prioritized? What the impact is having one scenery above/below another and how to change it? Does a document like that exist?

thanks

Don

41 minutes ago, wrap23 said:

You guys are conversing so above my head! I own tons of ORBX scenery as well as a lot of others. Haven’t loaded the new ORBX central but don’t understand all the reasons I perhaps shouldn’t. Where can a basic operator like me go to learn in simple terms how scenery is supposed to be installed and prioritized? What the impact is having one scenery above/below another and how to change it? Does a document like that exist?

thanks

Don

My advice in this case (which I am following as well) is if it isn't broke, don't fix (upgrade) it.

14 hours ago, Reader said:

I observe that each time P3D is started, among other things that it does is scan the documents folder

and only adds to the programdata add-ons.cfg file the add-on.xml details that it finds there

Only P3D 4.4 does that. All other versions use the \AppData\Roaming\...\add-ons.cfg for autodiscovery (or are supposed to). 

https://prepar3d.com/forum/viewtopic.php?f=6312&t=132273

The add-ons.cfg in \ProgramData\... is the reference file for addons that have been installed with the P3D command line interface.

Best regards

Edited September 2, 20196 yr by Lorby_SI

8 hours ago, exeodus said:

My advice in this case (which I am following as well) is if it isn't broke, don't fix (upgrade) it.

I couldn't agree more. For now at least I'd avoid ORBX Central like the plague. The whole business of add-on scenery management has become stupidly complex. As he said.....if it ain't broke don't fix it. Which is exactly what ORBX has done with ORBX Central......Doug

Have to agree-missing all those new Sceneries though!

Another Update of FTX Central 4 due soon

xxd09