FlightSimBuilder WASM files now cause CTDs when trying to start FS2020 after update 9

After update 9 on 4/26/2022 my FlightSimBuilder GNS 530 and G1000 are not usable due to the update breaking the WASM files installed into the community folder from the FSB Launcher. If I remove the “flightsimbuilder-wasm” folder from the community folder the sim starts up with no CTD. I have sent this information to FlightSimBuilder. It appears that FS2020 can’t load this information correctly and causes the CTD.

Okay. For those of you who use the FlightSimBulder GNS 530 or G1000 units. You can set them up using spad.next. I just programed the GNS 530 and it is working nicely. I will work next on the G1000 creating a profile in spad.next. When it is completed I will publish both of them for anyone who would like to download them to use.

Same thing happens to me. I would like the fix download. bigd.blue@yahoo.com