Jump to content

Vpilot error new version


mattia cherubin
 Share

Recommended Posts

Hello,

 

I just update Vpilot and I have the following problem 

"The active simulator was not found when Vpilot scanned your hard drive for available aircraft model. you will need to repair your simulator installation before using Vpilot with this simulator"

I use FSX.SE and i try to restore the installation via the option offered via steam, but the problem doesn't go away. All the settings are the same as per previous version.

Any ideas?

 

Thank you

Immagine.jpg

Link to comment
Share on other sites

That's very odd ... somehow you have FSX:SE installed and running, but vPilot can only find FSX installed. That means you have the registry keys and config files for FSX only, and not for FSX:SE.

Are you familiar with the registry editor? I would like to know which registry keys are present on your system. The ones vPilot looks for are as follows:

The install folder for FSX should be in one (or more) of these two locations:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0

The key name will be one of these: "AppPath", "SetupPath", "install_path"

For FSX:SE, it should be in one (or more) of the following locations:

HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\DovetailGames\FSX
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0

The key name will also be one of these: "AppPath", "SetupPath", "install_path"

If you are able to use the registry editor, please have a look at those registry locations and let me know the value of the installation path that you find for each of FSX and FSX:SE.

Based on what you find, I should be able to modify vPilot to handle your situation and not throw that error.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Hi Ross,

Here what I could find via registry editor, I hope is what your looking for I never used it

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
The value AppPath is: D:\STEAM\steamapps\common\FSX\

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0  Not present
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0  not present

HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX Not present 
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0

(inside there are no REG files that you mentioned) Computer\HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition (there is no 10.0 folder)


HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX not present
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\DovetailGames\FSX 
The value Install_path is present: D:\STEAM\steamapps\common\FSX
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 not present

 

Thank you

Edited by mattia cherubin
Link to comment
Share on other sites

Ok, that all looks normal. The next thing to check is your vPilotConfig.xml file. I'm thinking there might be some residual configuration there. Could you open up your vPilotConfig.xml file (it's in the same folder as the vPilot.exe, by default that's "%localappdata%\vPilot") and post a screenshot of the last section of the file which contains the ModelMatchingConfig section for each simulator? It should look similar to this:

image.png.c977e941f412d85d976bb8d2181a7425.png

 

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Okay, looks like at some point in the past, vPilot had detected both FSX and FSX:SE, since there are entries for both in your config file. I'm going to make a code change that should prevent those old config file entries from causing problems. I'll have a new version ready shortly.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

That means it found zero models in that folder. Did you delete the CRJ, or did your installation never come with it? Please let me know, because if some versions of P3D are not coming with the CRJ, I'll need to choose a different default default model.

Either way, you'll need to select a different default model. Detailed instructions can be found here.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

  • 1 month later...

Good evening!

 

Since there is the new update (version 2.5.2.) I have several problems using vpilot.

Vpilot kicked me from the server because it says: DLH123 could not be displayed using default model C172. Then I checked my Modelmatching rule set etc. and everything was finde. I already know what the problem is:

 

Vpilot thinks I am using FSX. But I only have FSX SE installed.  in the older version there was a option to manually set the type of simulator under "Model Maching, Settings for simulator:". But now there isnt. In my case there just stands: Fsx. 

If I try to set a new Default Model, it says everytime: "The specified default model for Fsx was not found during the last scan of your installed models...". So I think Vpilot searches for FSX Models and not for FSX SE Models. I am unsing FLAI for AI Traffic and it worked well for me since this new version was installed. How can I fix that?

Screenshots attached :)

 

Thanks for any help!

vpilot1.PNG

vpilot2.PNG

Link to comment
Share on other sites

Change it to "Airbus A321" ... "A321" most likely doesn't exist as a valid model.

Note that vPilot will show you as using FSX if you have the registry keys for BOTH FSX and FSX:SE and both keys point to the same physical installation folder. That's a very common scenario. FSX:SE's installer sometimes creates both registry keys.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Yes, that folder is where vPilot finds the cfg file. By renaming it, vPilot no longer detects that you have both FSX and FSX:SE installed.

Renaming it might cause problems in the future if you try to install an older add-on that is expecting to find the FSX cfg file, but you can cross that bridge if you come to it.

Marvin, I would like to try to update vPilot so that it detects your particular situation and handles it properly without the user having to manual rename folders. Could I ask you to help me with that? I would need you to post some screenshots of folder contents. Let me know if you're willing. Shouldn't take long.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...