DesertPilot85

Check this post: http://www.avsim.com/topic/476676-simstarter-version-27-out-now/?p=3313591

With FTX Central 2, the dialog can be immediately started for a specific simulator (FSX, P3Dv2, P3Dv3, etc) by using the /sim command-line parameter. On the ORBX tab of the Profile Settings, when "Use SIMStarter for ORBX settings" is enabled and the selected region is set to "Use 'FTX Central 2' dialog": When SIMStarter starts the FTX Central 2 dialog, the /sim parameter is apparently not passed to specify the simulator version. So FTX Central displays the "Select a simulator..." dialog. Can this be fixed such that SIMStarter will automatically start the FTX Central 2 dialog for the currently enabled simulator?

I am currently using multiple external scenery.cfg files, with names such as orbxscenery.cfg (dedicated to Orbx flying) and otherscenery.cfg (for non-Orbx flying). I have set up an Orbx profile in SimStarter, specifying the use of orbxscenery.cfg as the external scenery.cfg to use. I also enabled the FTX Central prompt, to allow me to run FTX Central when starting up my Orbx profile. It appears that SimStarter currently is not copying orbxscenery.cfg file to scenery.cfg, before running FTX Central. When I switch between FTX Global and regions using FTX Central, FTX Central will update the scenery.cfg file. But that scenery.cfg hadn't yet copied over from orbxscenery.cfg. When FTX Central is closed, SimStarter will then copy orbxscenery.cfg over to scenery.cfg, clobbering the scenery.cfg updates made by FTX Central. Can SimStarter be fixed to have the proper scenery.cfg file in place first based on the profile scenery specifications, before running FTX Central?

That solved my issue, thanks!

My P3D v2.4 has its default flight set to "Default Flight KSEA.fxml" for the Seattle area. I then go to SLX and create a new flight "Yosemite1.fxml" (departing from the Mariposa-Yosemite Airport) and save it. P3D is not currently running. I then click the "Fly Now!" button. P3D will first load to the KSEA default flight (with all the Seattle terrain loading), and then immediately after that loading completes, SLX causes P3D to then load the Yosemite flight/terrain/etc (with that SLX message appearing at the top left of the P3D window). This does result in a longer P3D startup process. Is it possible for SLX to detect that P3D is not running, and if so, then simply launch P3D with my selected flight? My current workaround is to just save my SLX-created flight, then go to "My Documents/Prepar3D v2 Files" folder, select the fxml file, and invoke a BAT file against it as follows: start "" "D:\Prepar3d v2\prepar3d.exe" "-fxml:%~1" Thanks, Andrew

Prepar3D v2.4 offers the "Clear skies" weather theme, to clear all weather. But SimLauncherX apparently doesn't offer this theme--"Fair weather" is the closest to clear I can get from the launcher. Can "Clear skies" be added to SimLauncherX? Thanks, Andrew

Jason, How did you determine the MSE2 BGL's that underline the area covered by Boston UltraRes? In other words, what's the best tool to determine locations of BGLs, etc.. Thanks