[UPDATED][FSPACKAGETOOL] Workaround to display debug console

Here's a zip file with a patched fspackagetool.exe to allow you to get the debug messages back: fspackagetool.zip

- Replace your fspackagetool.exe by the one in the archive and copy the ConsoleDLL.dll in that same directory

MSXVC version users:

Use the fspackagetool.exe just you usually do, a console showing the debug messages should show up after a few seconds.

Steam version users:
(Note: Make sure there are no spaces in your project file path)

In order to have the console on steam version (using -forcesteam command with fspackagetool.exe):

- Download steamcmd.exe from https://steamcdn-a.akamaihd.net/client/installer/steamcmd.zip

- Extract and move steamcmd.exe into your steam install folder next to steam.exe, C:\Program Files (x86)\Steam\

- Launch Steam and connect to your account (the console will not open if Steam is not already running)

- When launching fspackagetool.exe in addition to your usual command line argument you will have to add: -usesteamcmd -steamuser <YOUR STEAM USERNAME>

- launch fspackagetool.exe with these argument and you should see steamcmd.exe executing

Sorry for the inconvenience.
Let us know if some of you are encountering problems with this workaround.

Regards,
Asobo

Thalixte commented · Oct 22, 2021 at 06:55 PM

Thks a lot ! Work perfectly for me (Steam version). The only problem is that Windows Defender consider your fspackagetools version as a false positive, with the Program:Win32/Uwamsom.A!ml signature. Are you a hacker, Sylvain ? ;-)

2 ·

FlyingRaccoon ♦♦ commented · Oct 25, 2021 at 02:41 PM

We've updated the archive once again to handle the case you mentioned with the command returning before the package build is done.

FlyingRaccoon ♦♦ commented · Oct 23, 2021 at 11:31 AM

Ok it appears there's a difference with the dev environment we used to test the MS Store version workaround. We haven't figured it out yet but we are still looking for a solution.
We're very sorry and know how frustrating it can be, it is frustrating for us as well.
We'll come back to you if we find another solution.

1 ·

FlyingRaccoon ♦♦ commented · Oct 23, 2021 at 01:05 PM

A new archive has been uploaded containing a new exe and a dll, fixing the behavior for MS Store version.
Extract it at your usual fspackagetool.exe location.
Waiting for your feedback.
Thank you for your patience.

NorthernSkyStudio FlyingRaccoon ♦♦ commented · Oct 23, 2021 at 02:12 PM

Well done! Thanks!

0 ·

explorer-jfi1z9u4cc.png (151.8 KiB)

1634998348666.png (135.3 KiB)

mamudesign FlyingRaccoon ♦♦ commented · Oct 23, 2021 at 02:24 PM

ms store version, win10, and it eventually works!

Thanks sooo much Sylvain, this is what I call a GREAT dedication and customer support!

screenshot-208.png (212.7 KiB)

FlyingRaccoon ♦♦ commented · Oct 25, 2021 at 09:10 AM

Hello.
We just added a new version of the fspackagetool with a console that closes automatically after a few seconds to prevent your program from hanging.
Regards,
Asobo.

Thalixte FlyingRaccoon ♦♦ commented · Oct 25, 2021 at 10:35 AM

Great ;-) It works now without having to type manually exit in the steamcmd shell.

But one issue still remains: as soon as i use the new fspackagetool version, and the steamcmd, my steam account is automatically disconnected from the main steam process. So, when i launch MSFS, i cannot access any server.

I have to reconnect my account to steam with the steam client app to be able to run MSFS again without any server connection error.

best regards,

virtuali FlyingRaccoon ♦♦ commented · Oct 25, 2021 at 11:40 AM

This version finally produce an output so, thank you for fixing this.

However, it's still a bit clunky to use, because it spawns a new proccess in another console, which make it difficult to use from a batch file.

My batch file is quite simple: I used to to start fspackage tool and the next line I do a "robocopy" to mirror the package folder in the Community folder for testing. Before SU6, this worked as expected, with the fspackagetool running in the same console as the batch file, that did't continue until the flightsimulator.exe process ended. Now, since the process starts in a separate console, the batch file continues without waiting for the scenery to be compiled, and the other process is waiting a key to close.