General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
Paddles:
--- Quote from: rsgunner on September 29, 2014, 09:22:16 pm ---Any suggestions concerning the FSChecker?
--- End quote ---
--- Quote from: rsgunner on September 26, 2014, 02:30:34 pm ---The AppPath for P3D is E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\
The above is a copy and paste from the registry. Read from HKEY_CURRENT_USER. My OS is Win 8.1.
HKEY_LOCAL_MACHINE P3D entry SetUpPath is E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\
--- End quote ---
Is this correct that there are two P3D keys in your registry?
The AppPath for HKEY_CURRENT_USER root and the SetupPath for HKEY_LOCAL_MACHINE root? And both pointing to the same location?
That's very strange, because the AppPath was used for P3D v1, then they changed the key to SetupPath for v2.
Could you show me a screenshot of the FSchecker's output (of the last version 2)?
Orion:
Is this helpful?
http://www.prepar3d.com/SDKv2/LearningCenter/getting_help/getting_help.html
--- Quote from: Prepar3d v2 SDK ---The following are the default installation directories for Prepar3D and the location of their registry key entries:
32 Bit Operating Systems:
* Install Location: C:\Program Files\Lockheed Martin\Prepar3D v2\
* Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v264 Bit Operating Systems:
* Install Location: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\
* Registry Location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2
--- End quote ---
http://www.prepar3d.com/sdk/sdk%20overview.html#Hints and Tips
--- Quote from: Prepar3d SDK ---Prepar3D Registry Key Information
Prepar3D's registry key information depends on whether or not you are running a x64 bit or x32 bit Windows machine.
Registry information for computers using a 32-bit architecture is here:
>HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
For computers using a 64-bit architecture the registry key information for the 32 bit Prepar3D application is here:
>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D
--- End quote ---
Note that v1 is within "LockheedMartin" (no space), whereas v2 is in "Lockheed Martin" (with space).
Paddles:
Yeah, I know that. The FSchecker v2 tries to find first P3D v2 64 bit, then (if not found) tries 32 bit, then (if not found) P3D v1 64 bit and finally 32 bit...
But what puzzled me most of all was the AppPath parameter found in the E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ key. Kinda mix of P3D v1 and v2... :o
rsgunner:
This is from FSChecker V2
"Roaming path: C:\ProgramData
------------------------------------------------------
Searching for FSX...
FSX installed in E:\Program Files (x86)\Lockheed Martin\Prepar3D v2\
Now reading FSX scenery config file in C:\ProgramData\Microsoft\FSX\...
154 scenery definitions read
------------------------------------------------------
Searching for P3D...
None of P3D versions were found"
Russ
Paddles:
Oh, my... :o
Russ, can you provide a couple of screenshots, just like thetford569 did?
What I'd like to see is part of your registry with HKEY_LOCAL_MACHINE and HKEY_LOCAL_USER roots, both containing ALL P3D and (possibly) FSX keys.
Thanks!
PS. Looks like W8 is something different than W7 or XP in regard to FS...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version