MSFS20 SU9 DevMode polygon caution

[rhumbaflappy]

With SU9, all polygons are saved as XML code through the DevMode. But the DevMode also will convert any shapefiles in your project to XML code upon a save in the Scenery Editor... and delete your source shapefiles! There is no warning or option. Backups of shapefiles are highly recommended. I have a test project with 4 shapefiles. Each time I save throughScenery Editor, and reload the project, it converts and deletes one of these shapefiles... 4 -> 3 -> 2 -> 1 -> 0

The sim still will safely compile your shapefiles using packagetool or a direct compile.
For example:
D:\Programs\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe "-I" ; BuildAssetPackages "C:\Users\dickl\Desktop\MLE\Project_MLE.xml" "C:\Users\dickl\Desktop\MLE" "C:\Users\dickl\Desktop\MLE"
will safely compile my Project_MLE and preserve the shapefiles.

Most of us will not need to worry about losing the shapefiles, as the xml files are an improvement, but be aware you may lose your original source when visiting older projects in DevMode.

 

[GaryGB]

The sim still will safely compile your shapefiles using packagetool or a direct compile.

For example:

D:\Programs\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe "-I" ; BuildAssetPackages "C:\Users\dickl\Desktop\MLE\Project_MLE.xml" "C:\Users\dickl\Desktop\MLE" "C:\Users\dickl\Desktop\MLE"
will safely compile my Project_MLE and preserve the shapefiles.

Hi Dick:

I'm only in the very early phase of looking into scripted non-DevMode GUI versus DevMode GUI compilation for MSFS-2020.

I was intrigued by the topic under discussion in the OP above, and this linked thread (...from rather early after MSFS-2020 RTM):

https://www.fsdeveloper.com/forum/threads/package-tool-and-steam-version.448421/page-2


I am particularly intrigued by what distinction there may be between use of "FSPackageTool" and use of the command string example you used above: FlightSimulator.exe "-I" ; BuildAssetPackages in performing what, IIUC, is a "direct compile".


Whereas I can find "FSPackageTool" and its associated command switches in the MSFS SDK online Docs at:

https://docs.flightsimulator.com/ht...rhhlterm=FSPackageTool&rhsearch=FSPackageTool


...a executable command switch "BuildAssetPackages" is not found when used as a query string in MSFS SDK online Docs.


Where can info on non-Devmode compiles be found to explain what is referred to in the linked thread, and in your OP above ?

Also, does this non-Devmode compile option apply for those of us who use the MS Store version of MSFS-2020 versus Steam ?


Thanks in advance for sharing some more info with those of use who may wish to better understand our options, and whether there may be "non-destructive" command switches we might be able to use with compilation executables for MSFS-2020.

GaryGB

 

[rhumbaflappy]

You might just need to have the location of your FlightSimulator.exe for either Steam or Microsoft versions for this to work. To compile this way with the Steam version, you need to have Steam opened. I just have mine set to open on Windows startup. I'm not sure what the Microsoft version needs opened.

I delete my _PackageInt and Packagea folders before compiling to insure a complete compile. I can run this with an already open sim. In fact, I can run several instances of this at the same time.

 

[GaryGB]

Thanks, Dick.

On my MS Store installation, the path to my MSFS-2020 executable is:

C:\Users\Admin\AppData\Local\Microsoft\WindowsApps\Microsoft.FlightSimulator_8wekyb3d8bbwe\FlightSimulator.exe


In comparing this command string with the one used to "FastLaunch" MSFS-2020 as an App for access to the DevMode GUI via menus:

C:\Windows\System32\cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch


...I'm curious as to whether the above "Command Mode" launch of MSFS-2020 has a function entirely distinct from that of :

FlightSimulator.exe "-I" ; BuildAssetPackages.

Is the command switch parameter specifier "-I" in:

FlightSimulator.exe "-I" ; BuildAssetPackages

...a lower case letter "L" ...or an upper case Ietter "i" ?


Is there SDK (or other) documentation on this (and other) applicable command switch parameters for:

C:\Users\Admin\AppData\Local\Microsoft\WindowsApps\Microsoft.FlightSimulator_8wekyb3d8bbwe\FlightSimulator.exe


If so, where can one find this info ?

GaryGB

 

[rhumbaflappy]

capital i

 

[GaryGB]

Thanks again, Dick.

Just as a shot-in-the-dark test, I opened the Run dialog and pasted / ran this command:

C:\Users\Admin\AppData\Local\Microsoft\WindowsApps\Microsoft.FlightSimulator_8wekyb3d8bbwe\FlightSimulator.exe "-I"

Note that there were not yet any further characters or parameters etc, ...provided on the command line.


This was the prompt result on my MS Store installation of MSFS 2020:

Might this be due to MS Store App MSFS executable versions reportedly being "locked" ...compared to Steam Apps versions of MSFS ?

GaryGB