Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

vPilot can't detect sim


Sherlock Lau 1461982
 Share

Recommended Posts

Sherlock Lau 1461982
Posted
Posted

i am using FSXSE and after installing, it can't detect the sim.

Message: No supported flight simulators were detected! Please ensure you have FSX or P3D installed correctly! vPilot will now exit.

Version: 2.3.1

I have used vPilot before, but i now have a new PC and i installed it again on my new PC. This has never happened to my old PC. Can anyone help me?

signature-dark.png
Link to comment
Share on other sites

Ross Carlson
Posted
Posted

I made some minor changes to the way sims are detected in version 2.3.0. I'd like to find out if those changes are causing this problem. Can you please install a previous version and let me know if it detects your sim? You can use this link to get the previous version:

 

http://vpilot.metacraft.com/[Mod - Happy Thoughts]ets/Files/Installers/vPilot-Setup-2.2.2.exe

 

Note that when you run this version, it will prompt you to upgrade to 2.3.1, but you will need to say No to that upgrade, then let vPilot run as normal, and then let me know if it detects your sim.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

Unhandled exception: Unable to obtain public key for StrongNameKeyPair

signature-dark.png
Link to comment
Share on other sites

Ross Carlson
Posted
Posted

You need to run it as an administrator.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

It also has the same problem.

The last version i installed on my old PC is 2.2.?, and it doesn't ask me to update the client and it connects fine.

signature-dark.png
Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

Maybe this is a problem with SimConnect, is there a link for the compatible version?

signature-dark.png
Link to comment
Share on other sites

Ross Carlson
Posted
Posted

SimConnect isn't required in order to detect the sim. Did you do a normal full install of FSX:SE on the new PC? (You didn't just copy the folder from the old PC, right?)

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

it's a full install. I also did a full install to the old pc and it works well

signature-dark.png
Link to comment
Share on other sites

Ross Carlson
Posted
Posted

In order to detect a valid sim, vPilot checks for several things. The first is the install path in the registry. For FSX:SE, the registry key it looks for is:

 

HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX

or

HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX

 

Within those keys, it looks for any of the following keys:

 

install_path

AppPath

SetupPath

 

If any of those keys are found, it checks to see if the value of the key points to a folder that actually exists and contains the FSX.exe file.

 

It also checks to be sure the fsx_se.CFG file exists. That file is in the application data folder, which you can open by entering the following string into a Windows Explorer address bar:

 

%appdata%\Microsoft\FSX-SE

 

If the cfg file is found, and the install path is found and contains the exe, then it considers it a valid installation.

 

Can you check for the above items and let me know what you find?

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

the fsx_se.cfg is in the AppData\Roaming\Microsoft\FSX-SE

signature-dark.png
Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

Where can you find the install path for FSX registry?

signature-dark.png
Link to comment
Share on other sites

Norman Blackburn
Posted
Posted

In the registry.

 

Note that messing with the registry can cause bad things to happen. LOOK, don't touch is the key.

 

Click start, run. Type regedit.

 

Start drilling down the paths as shown by Ross above.

Report back your findings.

Norman

sig_FSLBetaTester.jpg

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

The AppPath is in

Computer\HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0

Nothing is found in

HKEY_LOCAL_MACHINE\SOFTWARE

FSX_SE.cfg exists in the corresponding AppData folder

The FSX installation location is C\Microsoft Flight Simulator X Steam Edition (i know it's a weird path, but this is exactly the same path where I installed FSX in my old computer and vPilot connects fine)

signature-dark.png
Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted (edited)

Also this registry path worked for my old computer (I don't know if the apppath changed since this is the same installer I used in my old computer)

Edited by Guest
signature-dark.png
Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Okay, so that explains it ... the registry path is completely different. I'll need to update vPilot to look for that new registry key.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Sherlock Lau 1461982
Posted
Posted

It works now, thank you!

signature-dark.png
Link to comment
Share on other sites

 Share