why having those in files dll.xml and exe.xml are both in Programdata and roaming files ? and still are not the same ?

 

Stephane

If I understand correctly, P3D now uses \Programdata

Some (older) addons still use the roaming map.

At startup, P3D merges the 2 files so it does not matter in which file the entries are

Just make sure the same entry is not in both files - this can cause problems.

dll.xml and exe.xml placed in:

 

"C:\Users\[user]\AppData\Roaming\Lockheed Martin\Prepar3D v3"

 

are only utilised by P3D for that specific User logon,

 

 

whereas dll.xml and exe.xml placed in:

 

"C:\ProgramData\Lockheed Martin\Prepar3D v3"

 

are included for any User logon.

 

 

In other words you can set up a system that works in the same way for all users but has the possibility of setting up differences depending on which user logged in.

but still, I observed that when it is placed in Roaming/... it doesn't loadin

Seems you did something wrong there. Roaming location definitely works - on top of that if it did not work dozens of addons would not work too.

 

...items in ProgramData load first...

so if all in Programdata, no need for me to have them in Roaming, if I'm the only user

exactly, don't need \roaming - unless you want to have different set-ups for example log in as user 737 or A320

 

..remember that some older addons may still put their sections in \roaming, you can hand edit these into Programdata and remove from \roaming.

dll.xml and exe.xml placed in:

 

"C:\Users\[user]\AppData\Roaming\Lockheed Martin\Prepar3D v3"

 

are only utilised by P3D for that specific User logon,

 

 

whereas dll.xml and exe.xml placed in:

 

"C:\ProgramData\Lockheed Martin\Prepar3D v3"

 

are included for any User logon.

 

 

In other words you can set up a system that works in the same way for all users but has the possibility of setting up differences depending on which user logged in.

 

Interesting. I was asking this question myself, and now is clear.

Cheers, Ed

Cool, whenever I add any new addons, I'm checking for the change in the roaming files (exe.xml and dll.xml) and cut and paste into ProgramData, and I'm done!

Note that making a system multi-user means that Run as Admin can have issues when it is used to gain file permissions rather than system privileges. In any case it is recommended to add the Modify permission to the Users group on the folder where P3D is installed since it is owned by the installer User when made in a location outside of Program Files. Even so it is still recommended that the Modify permission is granted to the Users group on the default folder anyway if installed there. The reason is that some addons place read/write files in that folder and these must be writeable by any user logged in

 

Cool, whenever I add any new addons, I'm checking for the change in the roaming files (exe.xml and dll.xml) and cut and paste into ProgramData, and I'm done!

Good work Stephane, this is indeed what every user should do, at the very least these files should always be checked for problems after installing addons.