• 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.

Debugging WASM gauges How-To

Not very clearly though. The main WASM Debug page mentions that the two build types (WASM and DLL) need to match but it never says anything about HOW to switch the build type for the DLL. I had to search the forums to figure that out. And I gotta tell ya, "Fast WASM Compilation" doesn't exactly scream 'debug build' to me!
 
That I have to agree with! Also the recompile from WASM to dll can suck up stupid amounts of time depending on the size and number of WASM modules you have.
 
> From SU12 onwards you must also do the following:

If anyone can give me the Microsoft Store equivalent to add to the main post I'd be very grateful.
Hi guys, thanks for this post, it helped me greatly, also, my contribution: I have a MS Store version, so adding the -FastLaunch -AllowDebugger switches was giving me some grief. I managed to solve it by:

Finding MSFS executable, by following this YouTube video.
Creating a shortcut and moving it to my desktop
Editing shortcut's target to include the switches (note, they need to be OUTSIDE the quotes):
1713371267274.png



Done! Now you can use the this shortcut and have MSFS2020 launch without the intro anims, AND, attach the sim to the debugger without crashing.
 
Not very clearly though. The main WASM Debug page mentions that the two build types (WASM and DLL) need to match but it never says anything about HOW to switch the build type for the DLL. I had to search the forums to figure that out. And I gotta tell ya, "Fast WASM Compilation" doesn't exactly scream 'debug build' to me!
Not sure when, but that changed to "WASM Debug Mode":

1713371643348.png
 
Imo these huge grammar improvements are possibly even better than substantive content updates. Page/mode misidentification is enough to drive anyone mad, am I right? The Behaviors Debug has streamlined "quick refresh" into "quick reload" and that one simple change definitively ended the confusion between refreshment and rearming. That someone attends to these details suggests they'll remain relevant into the next version.
 
Back
Top