Hello all, as I prepared a fresh install of P3D v4.2, I went through the fun of the uninstall of the previous version. Program files, appdata/local, appdata/roaming, program data, my documents etc. Then I asked myself, why? Why do all these installs have to span these seemingly dozens of folders; why can't all this stuff install under one nice, clean folder?

I am no developer and this is nowhere near being a rant, just trying to understand the logic.

Well, that structure goes back decades of FSX versions so that's the simple answer.

There's no reason it couldn't actually be designed to be self-contained like XP11 is, but because it's a legacy program, it is what it is.

1 hour ago, tamsini said:

Program files, appdata/local, appdata/roaming, program data, my documents etc.

This structure is quite important and is created by Microsoft (LM didn't dream it up), and when followed allows for such things as a multiuser platform, multiple platforms for a user, and separates program data from user data.  XPlane on the other hand seems to want to do anything they can to not follow the Microsoft paradigm and have created something the most naive of IT professionals would hold their noses for (in my opinion).  The advantage to Laminar's approach is that allows every user to be a developer, but it's not a stable platform for professionally developed software.

Hello Mario,

why: because Prepar3D is a Windows program. Those folders are what the Microsoft Windows specification tells you to use for various purposes. All your Windows programs use them, and I suggest that you Google up what those folders are for to understand why P3D uses them and for what purpose. 

ProgramFiles: for the executable
ProgramData: for configuration data for this software that is valid regardless of what user is currently using it
Documents: for content (belonging to the current user)
AppData\... for configuration data that is specific for the current user

(If used exactly as per spec other users on the same computer could set up and use the same P3D installation in a different way, using completely different content (scenery, aircraft etc.) You could have a VFR, an IFR and a Flighter user if you wanted to, and they are all set up individually, have their own aircraft and scenery etc. Unfortunately this does not really work when addons are installed directly into the sim or alter the config files directly instead of using add-on.xmls in \Documents)

As XP has been mentioned: strictly speaking, XP is not a Windows application. It doesn't install correctly, it makes little use of the Windows folders, and it is using OpenGL instead of DirectX IIRC. The way that XP works is typical for Unix-oide operating systems (which is why it was easy for LR to make a native version for MAC-OS = Darwin = Linux).

Best regards

One advantage with the way XP is installed, means I can delete and permanently banish it from my SSD in one quick command.