John Dowson

Did you manage to test this? I have tested here (of course) and it seems ok, so I will probably release a new version of FSUIPC6 this weekend. Thanks! John

You should be ok with all aircraft and scenery add-ons (although you can test with all these installed first to confirm) I would think, it is the other add-on types I would concentrate on, and add those back one at a time. It is interesting that MSFS console error of file-not-found is caused by Flow/SimFX - I wonder why this is, but I doubt very much that this is anything to worry about. Ok, that's good. Ok, sounds good - thanks. It would be very useful to know which add-on or combination of add-ons provoke this issue. I don't think its worth me continuing to try and reproduce this issue here at the moment. I am also going to post on the Asobo support forums about this issue. I will also release a new version of FSUIPC7 with the latest WASM updates in the next few days. Regards, John

Ah, ok. There is an ini parameter that you can set to increase the delay between re-running luas: But it is generally better to re-write such luas touse events... Ok, but rather than polling, you could assign your rotaries to LuaValue, with a different parameter for each position, and in your auto-ran lua wait for the position change using an event.param call and handling function. Regards, John

In your installation folder, along with your FSUIPC7.log and FSUIPC7.ini files (other files I ask for when you get issues). Please read the documentation - this explains such things. Which was?

Why would you do this? Nothing to do with microsoft... This normally happens if you have the document already open that you are trying to replace. Anyway, you should be able to continue with the installation. - this error should not stop installation. Also, if you have any installation issues, always a good idea to show me / attach your InstallFSUIPC7.log file. John

Ok... What add-ons are you actually using (apart from scenery and aircraft)? Maybe best to just start with FSUIPC installed, test that, and then add each add-on back one by one until you get the crash, Then go back and change the order to confirm its one add-on (could be a combination of add-ons....). You can also try the Simstaller program, which I think I mentioned earlier, to see if there are any conflicts. I have not used this yet myself although its been on my list to try for quite a while...

Those logs are interesting, and show that the WASM is most probably crashing when calling an MSFS Gauge API function get_name_of_named_variable. Although it could be crashing when I am logging the name returned by this function, but that was a recent addition so I doubt it. I have added additional code in the attached WASM to correct for this, so please switch to this version. Not sure what, if anything, I can do if its crashing in that function, except report to Asobo. I don't this error is actually anything to do with FSUIPC but something else causing a memory issue in MSFS that is causing the WASM to crash.... Anyway, last update doe today. I will continue investigating over the weekend, when I have time. John layout.json FSUIPC7_WASM.wasm

The WASM version mismatch message is nothing to worry about. As the WASM didn't crash, this is a completely different issue than previously reported. I will take a look at your files and see what they reveal, but over the weekend now. John

Are you using GSX by any chance? Or any other add-ons running with FSUIPC, apart from the aircraft (if thats an add-on)?

Ok, but this doesn't really help as the log shows the WASM crashing after the same line is logged. This is not relevant to this issue. It is a heap or stack corruption, which is (or should be) only available to the WASM. Ah, GSX....this has caused issues before. If you can first try with the latest WASM and show me the log (after a crash) from that, hopefully that will be more useful. Once you have done that, maybe try without GSX for a while to see if it still crashes without that... John

The WASM is used only for lvar/hvar controls and presets/calculator code. Standard controls are not affected. That is strange - I always have this open in an editor when running MSFS, and update when I need to, without issue. Yes, shouldn't be an issue - its the layout.json that matters. The manifest just contains text information associated with the build, although you can also use the attached, which just updates the version number and build date. John manifest.json

This is very confusing...are you also installing/replacing the layout.json file that I provide with each WASM update (in the folder one-up from the WASM itself)? The attached WASM has extra debugging, and will log each lvar found in the scan. The log file may get quite large, depending on how long t takes to crash... John layout.json FSUIPC7_WASM.wasm

Well, I can't even reproduce when NOT debugging! Yes, looks to be crashing on the same place. I will add extra logging in this area and provide you a new WASM shortly. This is very strange - I have not seen that error here. Could you let me know what add-ons you are using, and if using GSX maybe try without that, John

Ok, thanks. That is interesting and also very confusing, as it seems to be crashing in a block where there is no possibility of a memory issue, except if it is in the Gauge API function get_name_of_named_variable. Unless maybe there is a buffering issue with the log messages. Very strange... Ok, thanks, although I doubt the log files will reveal anything. Really I need to get this error here and trap it in a debugger, but after many hours of trying I still cannot reproduce....

Yes! My log file was > 64GB after an extended run. There is no way to open such large files - you need to split it into smaller files (when you get a crash) and send me the last 500mb or so. To split the files, see https://stackoverflow.com/questions/31786287/how-to-split-large-text-file-in-windows. It is definitely a memory issue, but I cannot find any memory issues, and I have ran MSFS.FSUIPC7 for over 24 hours with the WASM attached to a debugger, switching aircraft many times and sending many presets and lvar updates without issues. So this is very strange. It could be that another add-on is trashing an lvar name string that I am referencing, and when I try to reference this it causes the error. I have changed some code in the attached WASM version to correct for this if you could try it. I have removed the extra logging in this version, so the log files shouldn't be too large and it shouldn't effect the performance that much, so please switch to this version and let me know how you get on. Thanks for your assistance with this issue. John FSUIPC7_WASM.wasm layout.json

Could you please try with the attached WASM module and let me know how it goes. Thanks, John layout.json FSUIPC7_WASM.wasm

Please show me/attach your FSUIPC7.log and FSUIPC7.ini files.

Try the presets PMDG B777 FUEL CONTROL LEVER R CUTOFF and PMDG B777 FUEL CONTROL LEVER R CUTOFF, or the presets PMDG 777 FUEL CUT OFF ENGINE 1 TOGGLE and PMDG 777 FUEL CUT OFF ENGINE 2 TOGGLE. If you check Select for Preset and then click the Find Preset... button, they will be listed under MobiFlight -> PMDG -> B777 300ER ->Engine. John

I spoke to soon...someone lese has now just reported an issue which also looks like a WASM crash. I will keep investigating. If you could provide me with the last few thousand lines of the log file generated by the last version I posted then that would be useful. However, you should only use that version until you can generate the log file for me, then switch back to the released or tagged-data version. The log file from my last session trying to reproduce this grew to more than 64GB!

Sounds like you are also experiencing a WASM crash. Yes, that is the thread where this was originally reported. Was the FSUIPC_WASM.log file you attached uploaded after MSFS was shut-down? If so, it was definitely a WASM crash. If not, the next time this occurs can you exit MSFS and take a look at the end of the FSUIPC_WASM.log file. If the log file ends with the WASM closing down like this: then there was no crash, but if it didn't log that message then it looks like the WASM crashed. You can also open the MSFS logging console (only available once devmode is activated) and search for 'messages with 'fsuipc' in them - if the FSUIPC WASM crashed there should be a message to this effect. I have been investigating this issue for over a week now and cannot reproduce this here. I will keep investigating this and get back to you.

Ok, glad its all now working again. I am not sure what fixed this though - re-installing really should not fix anything as there are only the two exe's that do anything, unless one of them got corrupted somehow...

You shouldn't need to restart the PC after installation, and yes - you open the FSUIPC6 main window from the P3D Add-ons menu, John

I am starting to think that this is not an issue in the WASM itself, but in your installation. However, I thought WASMs were self-contained (in a sand-box), so its rather strange. Anyway, I have added more logging in the attached if you could try this. The WASM log file will be very large - you may need to use a file transfer service to show it to me, if too large to attach when compressed. I will continue trying to reproduce here, but so far I cannot get the WASM to crash, and I am using he same aircraft (FBW A320, PMDG 777 and 737) and more. It maybe worth validating your MSFS installation. In Steam, you would do this from the game properties and selecting 'Verify intergity of game files', but I don't know how to do this in the MS Store version. John layout.json FSUIPC7_WASM.wasm Note: using this version will generate a huge log file, and the size will be dependent on how long the WASM runs before it crashes. It will probably also slow down MSFS quite a bit due to this excessive logging. I have been running this version for several hours now, switching planes and using plenty of presets and I still cannot provoke a WASM crash. Anyway, if you can try this version and can provoke a crash I will take a look. As the log file will be huge, even compressed, probably better to use a large file transfer service (with compressed file), such as https://filetransfer.io/. I have spent quite a lot of time on this issue now, and cannot reproduce here so I do think that this is peculiar to your system. And if there was a memory issue in the WASM I would have expected this to be reported by other users, which they haven't. So it may be worth checking your installation, as advised above, or maybe verifying your add-ons with Parallel 42's Simstaller (see https://parallel42.com/products/simstaller). Plenty of info on this product via google. Sorry, but I am running out of ideas on this one, and I need to get on to other issues....although I will check your log file from this latest update when provided.

Your logs show that WideServer/FSUIPC is not receiving the response from WideClient and the connection times-out: This error is usually caused by the connection being blocked by a firewall. Are you sure that you tested with ALL firewalls turned off? Especially check the firewall(s) on your server PC (i.e. the one running MSFS/FSUIPC7). Alternatively, something else could be running on the default ports (8002 and 9002). You could try changing these (for both WideServer and WideClient) - see the WidFS Technical guide for details on the Port and Port2 ini file oprions. Note that your FSUIPC7.log is large as you have event and axis controls activated, which aren't needed. Anyway, I just wanted to check that WideServer was running, which your logs show, so no need to attach that file again. There are quite a few reports with this same error/issue over the years (Flight Sim version not really important for this issue as WideServer and WideClient will be the same), and it is always the firewall configuration (maybe caused by a windows update) that causes this issue. For example, see the following: John

@JARS I know this post is now 6 years old now, but do you remember what exception and where this is located in P3D? Or do you mean that you ticket the box in a router config page to allow P3D to send/receive external traffic?