Jump to content
Sign in to follow this  
stepmart

dll.xml and exe.xml

Recommended Posts

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

 

Stephane

Share this post


Link to post

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.


i7-7700K @ 4.9 GHz, 32GB DDR4, GTX1080, 2 x Samsung 1TB NVMe, 1 x 3TB HDD, Windows 10 Prof

Share this post


Link to post

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.

  • Upvote 1

Steve Waite: Engineer at codelegend.com

Share this post


Link to post

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

Share this post


Link to post

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...


Steve Waite: Engineer at codelegend.com

Share this post


Link to post

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

Share this post


Link to post

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.


Steve Waite: Engineer at codelegend.com

Share this post


Link to post

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


Cheers, Ed

MSFS Steam - Win10 Home x64 // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x - VR Oculus Rift // MSFS Steam - Win 10 Home x64 - Gaming Laptop CUK ASUS Strix - CPU Intel i7-8750H - 32GB RAM - RTX2070 8GB - SSD 2TB + HDD 2TB // Thrustmaster FCS & MS XBOX Controllers

Share this post


Link to post

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!

Share this post


Link to post

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.


Steve Waite: Engineer at codelegend.com

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...