SimForums.com Homepage
Forum Home Forum Home > Flight One Software Forums > Ground Environment X Series
  New Posts New Posts RSS Feed - USE GEP3D WITH MORE THAN ONE PREPAR3D INSTALLATION
  FAQ FAQ  Forum Search   Register Register  Login Login

Topic ClosedUSE GEP3D WITH MORE THAN ONE PREPAR3D INSTALLATION

 Post Reply Post Reply
Author
Message
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 16595
Direct Link To This Post Topic: USE GEP3D WITH MORE THAN ONE PREPAR3D INSTALLATION
    Posted: September-30-2015 at 9:24am
This process will outline how to use GEP3D with 2 versions of Prepar3D installed.
 
 
Unlike FSX-SE whereby the developers are keeping the simulator installation with its updates in a common install location, Lockheed Martin has opted to allow multiple install versions of Prepar3D. This presents a real problem for developers in development and support time especially if they intend to make this a norm for all versions as time progresses.
 
The GEP3D interface has a smart failsafe for such changes and is designed to look for target registry keys as well as the target install folder. If one or both are not found GEP3D will launch a manual browse mode for the install location and then confirm it on selection. Once done the system is marked for the location of P3D and GEP3D runs normally from there.
 
GEP3D was designed to function with one installed version of Prepar3D however a workaround can be applied to use GEP3D with multiple install versions of Prepar3D.
 
 
 
The steps below outline the process. It is very simple to apply!
 
In this example let us assume GEP3D is already installed and is in use with Prepar3D (v1 or v2) and the user also installs P3D v3.0 for test purposes..
 

1. Browse to the original Prepar3D installation and locate the file: Prepar3D.exe
 
2. Right click Prepar3D.exe and rename it temporarily. You can rename it to anything you like in example: Prepar3D.exe.tmp   or   Prepar3D_temp.exe
 
IMPORTANT NOTE: There can NOT be a 'FSX.exe' file in the same install directory as Prepar3D.exe. If there is, remove it or this process will not work.
 
3. Once done, launch the GEP3D interface. The interface will request a browse to the location of Prepar3D. Browse it to the 2nd Prepar3D install be it v2, v3, v4, ect. Once located the interface will then run and open.
 
4. Since your original install was active the interface will read that and will display ENABLED IN P3D in the new location. This is of course wrong for the new location but easy to change...   simply select the green bullet next to Ground Environment Prepar3D World Edition and click DISABLE. After the interface runs through the process, select the red bullet and click ENABLE
 
GEP3D will then run the installation of the files.
 
5. If you have installed UTX products into the new version of P3D those will be detected and you can enable the GEP3D/UTX features in the 2nd P3D install using the same method as posted in #4 above. Simply recycle the UTX line items.

NOTE: Since a backup was already made with the original install, and, nothing changes with respect to the base ground tiles from P3D version to version, your original backup will work as the backup for any other P3D version.

That's it..  Once complete the files remain active in the new version of Prepar3D until you disable them in the interface using the same process above.
 
 
 
To switch back to the original P3D install simply rename the original Prepar3D.exe back and launch the GEP3D interface. It will then ignore the 2nd P3D location and work with the 1st. You can switch back and forth using the same outline above at any time.

 

 

DO NOTE: That after you have used the method above for the first time the 2nd sim location path will be written to the GEXInterface.ini file and therefore if you rename the original EXE again the interface will not request a browse and instead open to the 2nd location automatically based on the path that was established the first time this process was run.

Switching back and forth at that point is simply a matter of renaming the original install Prepar3D.exe
 

 
 
 
 
 
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 11.10
Copyright ©2001-2017 Web Wiz Ltd.

This page was generated in 0.109 seconds.