Marios Anastasiou 810284 Posted July 6, 2017 at 10:00 AM Posted July 6, 2017 at 10:00 AM Hi, I am trying with latest vPilot to identify P3Dv4 but I am quite unsucessful in whatever I do. It can identify v3 without a problem but v4 is not listed in the settings dialog of vPilot. I checked registry, prepar3d.cfg/simobjects.cfg etc etc all looking good, so my question is (directed to Ross mainly) what is really vPilot after in order to identify the sim so I am not trying to fix it blindly? Is it looking for registry, cfgs etc? Thanks in advance Marios Link to comment Share on other sites More sharing options...
Ross Carlson Posted July 6, 2017 at 11:57 AM Posted July 6, 2017 at 11:57 AM What version are you running? You must be running at least 2.1.5 to detect P3D v4. First, vPilot looks for the registry key that points to the installation directory. If it finds that, it checks that the directory actually exists. Then, it looks for the simobjects.cfg file. If that exists in the expected location, then it will consider it a valid installation. The registry keys it looks for are any of the following: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4\AppPath HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4\SetupPath HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4\install_path HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4\AppPath HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4\SetupPath HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4\install_path The location of the simobjects.cfg file is expected to be: %PROGRAMDATA%\Lockheed Martin\Prepar3D v4\simobjects.CFG Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Marios Anastasiou 810284 Posted July 6, 2017 at 12:48 PM Author Posted July 6, 2017 at 12:48 PM Thanks for the reply - I am using latest 2.1.6. Will check those items again individually to make sure there are no issues and report back. Thanks Marios Link to comment Share on other sites More sharing options...
Marios Anastasiou 810284 Posted July 7, 2017 at 10:36 AM Author Posted July 7, 2017 at 10:36 AM That was it Ross - AppPath was corrupted in registry. Initially I installed and then reinstalled P3D into a different path, but for some reason registry kept the old path. Updated the path and all worked perfectly! Many thanks once more Marios Link to comment Share on other sites More sharing options...
Recommended Posts