Registry Keys FSX, FSX-SE, P3Dv1, P3Dv2

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#61
That's correct, there is no space in the P3D v1 key, while the other have.

Isn't it nice when they change things to make it more complex :D
 
#63
One more silly question: Can I assume all flavors of FS (FS2002, 2004, X, STEAM Ed.) and P3Ds (1, 2, 3) have the "fonts" sub folder under their respective root?
 
#65
Hi guys,

I need to create an installer that will deposit a few FLT/FSSAVE/WX files into

C:\Users\<user>\Documents\Flight Simulator X - Steam Edition Files

and go in and add entries to dll.xml and fsx_se.cfg (and possibly a few others) in

C:\Users\<user>\AppData\Roaming\Microsoft\FSX-SE

I've looked through this thread and I don't see any registry entries for these two locations. Any idea where/how to get to them?

Also, any suggestions on what utility to get to add/modify .xml amd .cfg files on installation?

I've used InstallShield before, and it is quite powerful, but that was a while ago and I remember it was quite involving, and it needed a bit of script writing to get it done.
I'm just wondering if there is anything else out there that would accomplish what I need, namely appending/inserting text blocks at certain file locations.
 
#66
No registry entries, there are environment variables that you can use to get the values. Something like %APPDATA% for the second one, %USERPROFILE% for the first one and add downstream folders
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#68
Hi all,

32 & 64 Bit - Alternate

Platform: FSX, FSX XPack, FSX Gold (Verified)

RootKey: HKEY_CURRENT_USER
Key: \Software\Microsoft\Microsoft Games\Flight Simulator\10.0
SubKey: AppPath

Platform: FSX Steam Edition (Verified)

RootKey: HKEY_CURRENT_USER
Key: \Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
Subkey: AppPath

Platform: Prepar3d v2 (Verified)

RootKey: HKEY_CURRENT_USER
Key: \Software\Lockheed Martin\Prepar3D v2
SubKey: AppPath

Platform: Prepar3d v1 (Verified)

RootKey: HKEY_CURRENT USER
Key: \Software\LockheedMartin\Prepar3D
SubKey: AppPath
Can somebody confirm that for P3D v4 this CURRENT USER key is also present? Although not in this list I know that for v3 it is the case, but also for v4?
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#70
Thanks, so that's the same structure as before.

Later I realised that now with it being a 64 bit application there is only one key in LOCAL MACHINE as well, so maybe less need for the CURRENT USER one.
 
#71
Hi all
can you tell me what installer creators are you using for scenries or addons and i want it to read the registry key too
thnx in advance :)
 
#74
Does the list of keys in OP still hold true?
I use FSX Accel only, but I'd like to know installation paths to P3D in the windows registry for the app I'm working on. I'm particularly interested in Prepare 3D v2, v3, and v4.
SODE FAQ also mentions "HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4" ->> SetupPath (instead of AppPath when found under HKEY_CURRENT_USER) for P3D v4. So, what's the proper/absolute location for key search in this case? I'm a little bit confused...

Thanks!
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#75
I use the AppPath value for P3Dv4 in my tools and that seems to work fine.
 
#76
I use the AppPath value for P3Dv4 in my tools and that seems to work fine.
I use Clickteam's Install Creator (free version) and only the AppPath registry key seems to work, the other one (HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4\SetupPath) does not. I believe there is some security related reason for that...but I don't care as long as the AppPath based one does what is supposed to! :cool:
 
Top