John Dowson

and also please try this one (same ini settings): FSUIPC6.dll I would like to see the logs for both dlls please....

Could you temporarily re-enable your event.terminate and try the attached dll please (with TimeForLuaClosing=5 set), and show me the log file after closing: FSUIPC6.dll

Yes, thats the new warning I added in 6.1. I would use this for now (i.e. no event.terminate), and I'll look into why that lua delay isn't working and get back to you.

Yes, looking at this now... Did you try this?

Interestingly, I checked my INI and the parameter was already there... set to 2. Yes, interesting... Ok. After you have done that, could you re-enable and change that parameter to something quite large, say 5 (seconds) to see if that makes a difference, and show me your log file afterwards (or the closing extract) so I can see if that has any affect. If not, I will look into it....

👍

You could also try increasing this parameter (with your event.terminate active): You can try increasing that....looks like this is maybe set to 1 in your ini (?), as from your log: Only a 1s difference between those messages....

Possibly. But please try first without closing down first - just comment out your event.terminate call.

Not sure that will do much as its the com.close thats the issue. As I said, first try commenting out the event.terminate (which will prevent the event.cancel and com.close being called).

Hi Luke, I'm not sure its failing - I think the com.close call is taking to long to finish and the script is being killed from the closing thread... Yes, there were some changes, but these were to increase some waits to give more time for the com threads to close down correctly. Was it working in the previous FSUIPC6 release before these changes? If you don't know, could you try (I can give you the previous dll if needed). Was that the complete log you posted? If so, then it does look like FSUIPC didn't shut-down correctly, which would prevent P3D from closing. It could be killing the thread when its in com.close that is causing the issue. Try commenting-out the event.terminate call, and see if terminating the thread without this is more reliable.

I can confirm that using the lvar for this works. I can't get the MF events NO_SMOKING_ON, NO_SMOKING_OFF & NO_SMOKING_AUTO to work though. Has anyone got these working via FSUIPC7, and if so, how?

You can can continue to use FSUIPC5 if you wish. Just download and install the latest version - 5.157.

Just use the latest version available then - 6.1.0 You shouldn't do that really. As I said, to uninstall, run the uninstaller. Deleting the dll will stop FSUIPC6 being loaded, but P3D will still try to load it, but will fail. And there is no need to uninstall if re-installing. As I said, just use the latest, v6.1.0

Which version of FSUIPC are you using - FSUIPC5 or FSUIPC6? If using an unregistered/unlicensed version, I suggest that you use the latest version, FSUIPC6. However, if you have an FSUIPC5 license, continue to use that (or you can get an FSUIPC6 license at a discounted price if you prefer). To uninstall, if using FSUIPC6, you can run the uninstaller that will be in your FSUIPC6 installation folder. If using FSUIPC5. simply remove or rename the FSUIPC5.dll to prevent it being loaded. However, there is no need to uninstall. Just download the latest installer and run that - that will automatically uninstall your current version and replace with the latest (and if you switch from FSUIPC5 to FSUIPC6, FSUIPC6 will replace your FSUIPC5 installation). For the latest versions of each product, see www.fsuipc.com, or the Updated Modules -> Download Links section of this forum.

There is an lvar for this: XMLVAR_SWITCH_OVHD_INTLT_NOSMOKING_Position This accepts the values: 0 = On 1 = Auto 2 = Off The MobiFlight events listed previously use this lvar.

I am not sure this is possible yet. The switch is working (in the FBW mod at least) but does not emit any events, and the Cabin No Smoking Alert Switch Toggle event has no affect. I also can't see any lvars/hvars for this switch either. However, looking at the MobiFlight WASM events document (see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454), I can see these events: NO_SMOKING_ON NO_SMOKING_OFF NO_SMOKING_AUTO so that looks promising! However, these events don't appear in my MobiFlight event file, but I haven't updated this in quite a while. So I would suggest trying these fist - or maybe asking over on the MF forum to see if they are actually implemented. To use with FSUIPC, you would also need to add them to an event file to make them accessible from the assignments drop-down. There i another post in this forum on how to do this if not familiar with MobiFlight events. I'll update my MobiFlight WASM today or tomorrow and take another look once done. John P.S. Are you using the vanilla A320 or an FBW mod? If the former, I suggest you update to use the FBW stable mod instead.

Yes, sorry - of course it should be '=Set' - updated.

So john, any progress on turning on leds on goflight modules ? I haven't and wasn't planning on looking into this. But, as Pete says, please look at the GoFlight library.

Create a macro file in your FSUIPC7 installation folder, called (say) PA28Arrow.mcro, and then add the following: You should then see the entries in the assignments drop-downs.

That should be ok... did you create the macro file when FSUIPC was running? If so, you need to 'Reload all buttons' or restart FSUIPC7 to pick up the macro. Presumably you are using a registered version of FSUIPC7, no? Can you see the macro file in the [MacroFiles] section of your FSUIPC7.ini? Btw, better to call your macro file something like TBM930.mcro. Its then more obvious and you can use the same file to add other macros to the TBM930 later if needed.

Ok, then that makes sense. But, always better to close down FSUIPC before attaching logs. Did you have an FSUIPC assignments window open when the plane was loading by any chance? It looks like FSUIPC7 didn't even receive your aircraft name. so it never got to the 'ready-to-fly' state, which is strange...

Great, thanks for letting me know. And thanks for the hvar file, I will include that in the next release. Which also reminds me, I need to add something about hvars and hvars files to the documentation.... Cheers, John

But the log does not show FSUIPC closing down - did you attach it before exiting FSUIPC7? Usual places - on www.fsuipc.com or in the Updated Modules -> Download links section of this forum. v7.0.9 is basically the same as v7.0.9a, but best to try with the supported version before I investigate, if needed. If the log you attached was the complete log, then FSUIPC7 crashed and I need to see the event log. Anyway, download the latest version and try again. If you still get the same problem with v7.0.9, please also try with v7.1.0f. Any issues, attach your log + ini + any info from the windows event viewer, if FSUIPC7 is indeed crashing.

I have just tried this and it seems to still be working fine: The log you attached was cut short, and shows that FSUIPC7 did not reach the 'Starting everything now' stage. Did FSUIPC7 crash or did you manually kill it? Is there anything in the event log? Can you try again please, and if you still experience this issue attach your FSUIPC7.ini as well as the full log, and if FSUIPC7 did not close down correctly, please check the event log. Also, you are using an old release, v7.0.9a - please update to the official release, v7.0.9 (or the v7.1.0f beta).

To use it how? The FSUIPC lvar module provides access to lvars/hvars for FSUIPC7, and also for any other that wishes to use its facilities (vie the WAPI library). If using FSUIPC7, then you can use lvars/hvars only via macro files and lua scripts at the moment. There is also a section on configuration of the WASM in the latest Advanced User guide in the 7.1.0f release - see