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

MSFS24 Debugging WASM

BattleMetalChris

BattleMetalChris

Messages
88
Country
unitedkingdom
I'm delving into WASM coding. I've got a little module working that doesn't really do anything more than write Hello World to the console, but the sim is loading it and it works - lovely.

I'm trying to enable debugging within Visual Studio 2022. I've installed the WASM debug extension, attached to the MSFS process and can get it to stop on a breakpoint in my code. Also lovely.

But I keep getting these, which I'm certain are unrelated to my module (they appear even if it's not loaded)

1787361106400.png

Over and over again, every few milliseconds according to the profiler. They're not from my code, is there any way to automatically skip them?
I've tried unticking the exception type in Exception Settings but they still appear.
 
Fixed it.

I'd read that in order to add the 'AllowDebugging' argument to the executable when running the MS Store version of the sim, you had to run the fsdevmodelauncher.exe in the SDK Tools folder.

Apparently not - instead I found the executable in 'Microsoft Flight Simulator 2024\Content' and created a shortcut to it with the argument in the normal way and it worked.
 
You must log in or register to reply here.
Back
Top