• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 FSPackageTool redirect output

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,485
Country
netherlands
Hi all,

Working on MSFS 2024 support in ModelConverterX and one thing I notice when trying to compile a MSFS 2024 package from inside my tool is that I no longer get the output from the FSPackageTool so that I can display it in the event log. Also for MSFS 2020 this seems to be broken. I am redirecting the output from the FSPackageTool application into my own application and I am quite sure it worked for MSFS 2020 when I implemented it a few years ago. Have others also encountered this and does somebody maybe have a workaround for this?

If I run the FSPackageTool from the command line, I see the output nicely in my console window.
 
Hi,

I have come to the conclusion that the FSPackageTool output is not written to standard output. When calling from the command prompt you can't redirect it to a text file either.

In earlier versions of MSFS 2020 this functioned ok, but now both MSFS 2020 and 2024 don't support it anymore. I have posted this on the official MSFS forum as well.
 
No, that opens another window, but when starting the tool from my application I still can't see that output if I redirect standard output (I also can't redirect that separate console to a text file from the command prompt).
 
There is a subroutine missing in the new FSPackagetool involving with commands, could be the problem.
 
The MSFS 2020 package tool has the same issues.
 
Oh, I see. It must have been changed around the time the -marketplace and -outputtoseparateconsole where added then before 2022. You can still download the old sdk's if you really need them though.
 
It worked when I first implemented package export in MCX about 2 years ago or so. But now with MSFS it doesn't, guess I'll just have to live with it.
 
Hi Arno:

I'm willing to bet Dick has a PowerShell routine that might be able to do some redirection. :scratchch


I wondered about the PowerShell "Tee" redirection option in regard to this scenario, although I have not yet tested it.

https://learn.microsoft.com/en-us/p...rshell.utility/tee-object?view=powershell-7.4


I'm not sure which info you are trying to capture, but I was able to capture certain DevMode load errors into a log file.

Apparently on my system, the MSFS24 SDK copy of FSPackageTool and FSDevmodeLauncher.exe from MS-Store are in:


[MSFS 2024 SDK_1_0_0 install path]\Tools\bin


I attempted a few CMD mode command switches with the above EXE's, and was able to capture errors to a file about not having given a Project name to load, by using the EXE's in that above MS-Store folder for my installation of MSFS24.


Another possible source of info on what Asobo is doing might perhaps be gleaned from a current FSUIPC installation process: :idea:

https://forum.simflight.com/topic/9...ller-now-available-for-msfs2020-and-msfs2024/


I hope this might prove useful, although I am confident you have quite an in depth knowledge of such things already. :)

GaryGB
 
Last edited:
Let me check if the Powershell approach helps.

All I'm trying to capture is the output if you run the FSPackageTool to compile a package.
 
Hi Arno:

While browsing MSFS20 SDK Online Docs, I happened to find this info regarding FSPackageTool in Release notes:

https://docs.flightsimulator.com/html/Introduction/#release_notes__

https://docs.flightsimulator.com/html/Introduction/Release_Notes.htm?rhhlterm=helipads helipad
"
  • Added: Two new commands for the fspackagetool.exe:
    • -outputtoseparateconsole : allow users to have Flight Simulator output to a separate console
    • -nopause : Prevent Flight Simulator from pausing at the end of the process"


I also searched the MSFS24 online SDK Docs and found these (2) hits:

https://docs.flightsimulator.com/ms...age_Tool.htm?rhhlterm=outputtoseparateconsole

https://docs.flightsimulator.com/ms...age_Tool.htm?rhhlterm=outputtoseparateconsole


I thought I should mention this in case it proves useful to your efforts above with redirecting console output to MCX.

Hopefully you may have found a workaround by now. :)

GaryGB
 
Hi Gary,

I tried these two options already and they don't give useful output in an external tool.
 
You must log in or register to reply here.
Back
Top