• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Registry Keys FSX, FSX-SE, P3Dv1, P3Dv2

I can confirm for P3Dv1.x at least, as that is what I've been using.
As for ESP, your guess is likely correct, but I've never even seen ESP so don't honestly know.
 
Thanks Bill :) That's a huge help. All I need now is to confirm ESP and figure out how to transcode my VB6 script to VB.net or C# :D

Right now I have tweaked the code on my original installer routines, but it only handles one sim at a time. If I can get this squared away I can release the program or maybe even make it open source as I'm really not a programmer. :D
 
Is ESP even used still?

I don't think it ever reached mainstream userbase, like P3D did by virtue of not having a general market alternative (like FSX was to ESP), and I'd expect professional solution to be long gone to P3D on account of available support.
 
Bill I read your post that you use "AppPath" with local user. I have been using "SetupPath" for years. I noticed that AppPath uses the LOCAL_USER and SetupPath uses the LOCAL_MACHINE. I have my installer selected to both user and machine but i am using AppPath. So far it seems to be ok but every once in while i get a customer who gets no directory. Is this because they installed their FSX or P3D to a specific user on their computer and there is no local machine registry for their sim? I am hoping to keep using these settings since all of my products would have to be updated even if i start making the setup like yours for new products.

Now i am thinking it made no sense selecting both user and machine if i use SetupPath since user only has AppPath. So why do they give you a mix option for both user and machine?
 
I have no idea why MS chose to use AppPath for the key name used in the HKLU registry entry, only that they did. I also know that if you ask for SetupPath instead of AppPath, you will get a NULL return (empty) instead of a valid drive:\path...:wizard:
 
Hi Bill, Delivery...
i think the logic behind HKLU is to allow a definitive per user settings; as appose to global approach,
 
So i am thinking using my settings if a customer installs FSX or P3D or Steam to a user on his computer rather than for everyone, then SetupPath will cause an issue? Still wondering why i get 1% of customers with no directory. Which means my installer does work but looks for SetupPath under local machine only!
 
the no directory is an easy one; here's the scenario i personally had,
i restored my OS from an image backup; in which didn't have FSX previously installed;
but i had FSX before i restored on a separate partition; i didn't want to go through setting everything up from scratch (no point; since FSX is a standalone)
i simply run a handful of supporting libraries installed (dx, msxml, vb lib); and fsx runs perfectly (without reinstalling everything),
P3D will not agree with the above procedure; but FSX does (i am guessing FSXSE wont either)
a similar path could have been taken if a user reinstall his OS again; while FSX is on another drive,
 
MyPC8MyBrain said:
Hi Bill, Delivery...
i think the logic behind HKLU is to allow a definitive per user settings; as appose to global approach,
Click to expand...
Well yes, of course. But, that wasn't the actual question being addressed, which is why MS uses AppPath versus SetupPath as key names.
 
Seems that my setup is different than what others are doing but it does work as it uses the local machine address. And for the few customers who move their FSX i have created instructions for them to update their registry. As a matter of fact a customer used my new instructions today and emailed back that it worked. So i guess i will keep using this setup as it will be harder for people to alter the registry and have a copy of the all the files to share with others. Although there is no solid way to prevent this but at least my aircraft folder will not work alone as it will cause errors if they try to share it.

Here is a great question! Can we make it so if someone moves or copies the files in the location it was installed it will delete. Or can we make ICP look for a file in FSX so it will only install if the game is actually there?
 
n4gix said:
Well yes, of course. But, that wasn't the actual question being addressed, which is why MS uses AppPath versus SetupPath as key names.
Click to expand...

yes i have missed that, ill try again :)
to my logic SetupPath HKLM is a global key; and AppPath is individual HKLU
some users could be restricted to certain HKLM areas; HKLU should have the entries permitted for the logged in user with no restrictions!

For licensing concerns; some users may need a HKLU area for individual addon installed later
 
Does anyone have the 'name' of the folder that FSX Steam Edition is called; exactly? I had renamed mine to FSX when installing it.

I see all of the Registry routes, but none have the actual folder name that the simulator is actually in.

I am guessing its Microsoft Flight Simulator X Steam Edition, but want to make sure.
 
if i remember correctly its conditional with SE
(be careful; they also seem to change their mind every other day)
if FSX is not installed previously; than it assumes the default FSX path;
if it is installed it is listed in the page before this
 
lionheart said:
Does anyone have the 'name' of the folder that FSX Steam Edition is called; exactly? I had renamed mine to FSX when installing it.

I see all of the Registry routes, but none have the actual folder name that the simulator is actually in.

I am guessing its Microsoft Flight Simulator X Steam Edition, but want to make sure.
Click to expand...

When installed side-by-side with the original boxed version of FSX, mine installed to Steam\SteamApps\common\FSX. I didn't rename the folder or otherwise make any adjustments. I'm not sure how a standalone install differs if at all.
 
ollyau said:
When installed side-by-side with the original boxed version of FSX, mine installed to Steam\SteamApps\common\FSX. I didn't rename the folder or otherwise make any adjustments. I'm not sure how a standalone install differs if at all.
Click to expand...

It doesn't.
 
ollyau said:
When installed side-by-side with the original boxed version of FSX, mine installed to Steam\SteamApps\common\FSX. I didn't rename the folder or otherwise make any adjustments. I'm not sure how a standalone install differs if at all.
Click to expand...

Many thanks Olly.
 
My FSX:SE is installed as "stand-alone" and the path/foldername is this:

N:\SteamLibrary\steamapps\common\FSX
 
And now Prepar3D v3 is out. I have it already. Installed it but somehow I get CTD when I launch it. Stand by for the installation paths.
 
You must log in or register to reply here.
Back
Top