Simstarter NG is a fantastic way to launch Prepar3D (P3D), giving you many options that would otherwise be a pain to do and all after the simulation loads in most cases. But I had to do a little trickery to get it to play nicely with things like TileProxy and for VR using FlyInsideFSX. I’ll show you a few of my techniques to get around these issues. There may be other ways of handling things, but this was the quickest and easiest route that I found.
We start off in the main screen for reference.. I typically use simstarter so i can break down scenery areas into various regions for profiles.. For instance, I use sceneryconfigeditor.. lots of groups, making it possible to create multiple “scenery.cfg” files which i rename and use the external option for scenery.. ie: North America, North and South America, Everywhere but North and South America, EasternUSA, etc.. This all might seem confusing at first, but once you do one of these, the rest fall into place.
SIMSTARTER + TILEPROXY (VR mode)
Out of the box Simstarter NG wont support launching fsx.exe (compatibility mode) for things like TileProxy when it comes to launching a saved flight at the same time. This requires a bit of trickery via a “file operation” in Run Manager to make it work.
Below are the screen shots of how i did this. Basically you have to:
- Choose an existing Run ConfigSet with the pull down under “Main ConfigSets” and click the Edit button next to “Run ConfigSet” or make a new one by clicking edit and create a new one. Below is how you would create a new one. Once you would create a new configset, you could click open in editor and import the contents of your custom cfg file into it and save (below I create the VRConfig, its the flyinside_fsx.cfg template).
We cant just copy the basic Prepar3D.cfg file that is the master file with Simstarter NG, we must take the already working prepar3d_flyinside.cfg file contents and somehow get them into SimStarter in its own cfg, which I call the VRconfig To do this i initially opened the master Config via Edit set and did a copy and gave it a new name.. “VrConfig” for instance..
Then if you do the open in editor.. you see the following:
Note the path.. all i did was open that config file with the path given and then paste the contents of my known working prepar3d_flyinside.cfg file.
- Once you either create or select and existing configset, you then Select a RunSet, in my case I have created a run set called FSX_TPBatchVR, where in this case this is where I would be using goggles with TileProxy.
- Add fileoperation at the bottom (we need to get the prepar3d.cfg settings into fsx.cfg)
Set source : %userprofile%\appdata\Roaming\Lockheed Martin\Prepar3D v3\prepar3d.cfg and
set destination: %userprofile%\appdata\Roaming\Lockheed Martin\Prepar3D v3\fsx.cfg
Be sure to set this operation to occur first in the order in the main Run Manager window. In order to use Simstarter NG with FlyInsideFSX, we have to do another file copy operation that basically copies the Prepar3D.cfg file into the prepar3d_flyinside.cfg file, but with a little extra step, hence we repeat this for prepar3d_flyinside.cfg.
Now we click Add Program and add your P3D install path to the proxyuser.exe in my case V:\program files (x86)\Prepar3D v3\TileProxy\proxyuser.exe
Note as shown below, I also have a batch file called flyinsidetoggleNormal.bat, this just changes the flyinside cfg entry from ForceVRModeDev = 0 to ForceVRModeDev = 1 for its ini file called settings_pro_FlyInside P3D_settings.ini as with this combination of picklists, it would be a VR run.
I opted to put the fsx.exe launch process in a batch file per below, this way I can call another batch file once fsx.exe closes to close proxyuser.exe and clean things up at the end. If you dont do it this way, you have to close proxyuser.exe window after you close P3D in tileproxy mode.
**The batch file for launching fsx.exe looks a bit like this in my case (Fsxwithtp.bat):
“V:\Program Files (x86)\Lockheed Martin\Prepar3D v3\fsx.exe”
Where taskkillfsx.bat kills many processes related to p3d at the end, once its closed. (I wont get into those specifics here, but it works)
FLYINSIDEFSX / VR only (no TileProxy)
Using the above techniques, I basically created another Run Set that I call “VR”, this is for VR only and doesnt do anything with tileproxy. It looks like the box below:
Summary of Config Sets and Run Sets to make this all work
Normal 2D mode without TileProxy:
Sim ConfigSet: 2DConfig
Run ConfigSet: Standard Set or FSX-TPBatch
VR Mode options:
Sim ConfigSet: VRConfig
Run ConfigSet: VR or FSX-TileProxyBatchVR
There are a ton of ways you could configure this, but basically now every time i launch a profile, i can basically either run it in “2D” mode with or without TileProxy, or I can run it in “VR” mode with or without TileProxy.