Currently I do not have any wasm files in my %APPDATA%\Microsoft Flight Simulator\Packages\fsdreamteam-gsx-pro which prevents the addon to work. I was under the impression that MSFS would create these files upon booting up.
Any suggestions, please keep in mind I am not a computer expert.
Thank you for your post! Your topic has been moved to the #gd-commsupport:tools-utilities of General Discussion & Community Support. The General Discussion category is meant for discussions that fall outside our other sub-categories.
Please check out these other categories for your future posts:
Aircraft
is where you discuss current or future planes coming to MSFS as well as assistance with liveries.
World
is where you discuss scenery, airports, and weather.
Tech Talk
is where you discuss installation, graphics, drivers, performance, CTDs, peripherals, and hardware.
Menus & Activities
is where you discuss activities (landing challenges, bush trips, etc), plus anything accessed by the menus including the Marketplace, settings, logbook, cameras, etc.
Yes, it was working perfectly prior to an issue I had with one of my programs on my computer causing it to crash during flight. It was suggested that I delete this program and GSX as these were the cause of my CTD’s. Come to find out, it was only my Alienware software causing the problem, not GSX, but I had already deleted it. I tried to reinstall but its not working. It normally opened right after the sim plane opened up on the tarmac. GSX doesn’t even show up in the tool bar on the top of the page while sitting in the cockpit.
I have been in touch with GSX support, however, they told me I had to delete the “%APPDATA%\Microsoft Flight Simulator\Packages\fsdreamteam-gsx-pro”, the problem is that this file does not exist. He keeps telling me its not a GSX problem, so that’s why I submitted this request on the MSFS forum.
Thanks for your reply and any help would be greatly appreciated.
.WASM files are included in a package that requires them, so these are in fact provided by the developer. However, before they can be used in the sim, .WASM files are compiled into a .DLL by the simulator automatically and the compiled .DLL is found in the following locations:
MS Store version:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages
Steam version
%APPDATA%\Microsoft Flight Simulator\Packages
These folders will contain compiled .DLL (which is the only thing the simulator will use; it won’t run the .WASM file directly) for each package which is both Installed and comes with a .WASM module.
Since GSX surely comes with a .WASM module, every user that has ran it at least once, should have this folder, unless:
The MSFS version in use is not the Steam version, so one should check the other folder for the MSFS Store
The folder has been removed manually, and GSX hasn’t been installed after the removal
The package might be installed but is not linked to the Community folder
Fact the users doesn’t see the GSX Menu in the Toolbar, which is just an html file, so it’s not affected by anything running like antivirus, wasm, dll, libraries, etc. seems to indicate that the user removed the folder manually, and never reinstalled GSX after doing this.
That seems the simplest explanation. The more complex explanation might be more serious issue in the MSFS install, which will prevent to compile ANY WASM module, that is assuming he already had other package with WASM modules installed (not clear) and he’s really using the Steam version