Since PMDG 737, MD-80 and Fenix A320 are out in the market some weird behaviour is occurring on user PCs.
When they install or update any of these products, the compilation time of WASM takes very long time (20 minutes is the average), during the time the user cannot do anything.. however what is happening is after such time, the airplane will behave erratically unless MSFS is restarted.
This seems an odd behaviour, and I am not sure if these developers have reported it to the asobo team, my aircraft about to be released is using WASM, however it compiles faster since the modules must be much smaller, and my beta testers have no issues or have to restart MSFS after installing the product or after me pushing an update.
So it seems the behavior occurs after very long compilation times, so the question is:
1) Why such long compilation times? anything that could be done in the future to avoid this? users are not very happy with this behaviour on many forums, so if we could find a way to avoid this issue I think it would be good for the overall experience.
2) Why MSFS needs to be restarted so the modules work? is this the expected behaviour from your point of view? PMDG and Leonardo (MD-80) are instructing users to reboot MSFS after a compile in order to ensure all modules are loaded. It seems to be by design, everything should work despite of a long compilation time.
People are starting to become worry when an airplane is WASM enabled due to the issues explained above, so I am looking for ways to improve the process, etc. since I will be using WASM again for future projects.
Thanks in advance,