Then I can see what will likely be the first thing it does after the point where it crashes in the later version.Īlso I can then look to see if I can enable or add more logging. Don't run it too long as the log will get huge, just enough to get past where the failing one crashes (2-4 secs?). One other thing which might help is to run that same 777 Lua, with the 747 loaded, and the Lua logging on, using FSUIPC 5.103b, which you say doesn't crash. (This won't work if there are more than one of them, of course). That will be by taking half of it at a time, and keep halving till we find the culprit. could you try with that commented out (put - in front)?įailing these actions we might need to try narrowing down what in the Lua could be setting up for the crash. The ipc.display call, which should have done its job within the first second or two. Colud you test by loading the 747 then starting that plugin? Leave it running for a few sconds. There's an example Lua plug-in which monitors L:Vars by reading them all regularly. Many of them are L:Var events, which needs FSUIPC to continually read those L:Vars to see when they change. Maybe also worth to be mentioned: It seems, that there passes a second or two from the time of calling the script and the crash.ġ. Run till the crash then show me that log which will be named after your Lua file.īut the very first thing to do is make sure your 747 is up to date. In those logging options, opt for a different Lua log file.
Ipc.display("Preparing Cockpit Boeing 747\nFILE: a", 7)Īssuming that you cannot update 747 because it is already up to date then, though given what youve now said i think it wholly unlikely, maybe a Lua trace/debug log leading to the point of the crash will help - enable that in the FSUIPC Logging Tab before starting the 777 Lua (not the 747 one, so I'll know it isn't something specifically in the 747 values).
Does that display appear before the crash? In the Lua(s) there is this, executed early on before any of the Events can occur. And that result alone also points directly at the PMDG 747. I thought of comparing the two but as they both crash with the 747 but neithe with the 77 there's no value in that. I can't really do much with your Lua files.
Unfortunately the Windows crash data shows an error in "KernelBase.DLL", a part of Windows, so it doesn't help very much except showing it's rather more complicated than a simple code execution problem in FSUIPC. Your previous "working" version of FSUIPC, 5.103b, certainly qualifies as early enough. Is your 747 fully updated? There was a PMDG problem with that particular update which, in the early days of FSUIPC5, I worked around pending a proper PMDG fix by disabling a feature it was calling with the wrong call type (a 32-bit call only executed in the PMDG code if it detected the relevant FSUIPC facility present). Both scripts do NOT crash with the PMDG 777 (though the 747 script is obviously useless), both DO crash with the PMDG 747