John Dowson

That is quite a few and will certainly affect the start-up time of the FS. You should consider using the MSFS add-on linker program which can be used to limit the community folder to just the items you will be using for the flight -see https://flightsim.to/file/1572/msfs-addons-linker Yes - menu Log -> Buttons & Keys. This may have been because you had not activated the appropriate logging, but these statements are now present in your log files, e.g. 66703 HotKey entry at 3214, VK=48, Shifts=0, Flags=0, Result=0 Can you both try the attached version please. Add the following to the [General] section of your FSUIPC7.ini file: DetectToConnectDelayAuto=240 John FSUIPC7.exe

What do you mean by this? FSUIPC7 will give access to all lvars. Please show me this "snippet" - it should be relatively straightforward to turn that into a preset. Are you using the Asobo G58? If so, there are presets for de-icing: G58 PROP DEICE ON and G58 PROP DEICE OFF, and there are several de-ice lvars that you can look at. Alss, look at the Input Events - there are these: DEICE_Pitot_1<;FLOAT64> DEICE_Propeller_1<;FLOAT64> DEICE_Windshield_1<> DEICE_Airframe_1<;FLOAT64> DEICE_Engine_1<> Thee are also Input Events for the fuel pump you can try; FUEL_Pump_1<;FLOAT64> FUEL_Pump_2<;FLOAT64> But that lvar doesn't exist, at least not in the Asobo G58, so I don't know how this can possibly work. I think you should be looking to use the Input Events for both the Fuel pump switches and the de-ice switches. I will take a look later (or tomorrow) to check these and see what values/parameters you need to use.

This log shows that FSUIPC7 couldn't connect until more than 3.5 minutes after the sim was detected...very strange. Do you have a lot in your community folder? I will adjust to allow more time to be specified before the attempt to connect is made. No it doesn't. When you stop FSUIPC7, the log file is closed, and when you restart it a new log file is created and the old/previous one is renamed to FSUIPC7_prev.log. I therefore need to see the FSUIPC7_prev.log file if you do this, as that will be the log for when the hot keys were not working. The log also shows that you did not activate logging for Buttons & Keys, and also no hot keys were registered. John

Ok, great. Ok, interesting. That looks different from the available presets. Maybe you can share your assignments (presets?) so that other users can use these - i.e. post your assignments here. Regards, John

Ok, thanks for the update. There should be no problem when stopping a flight, going back to the main menu and starting a new one. Please show me a log file (no additional logging required) showing your issue, i.e. when starting a new flight, if FSUIPC7 isn't functioning as expected, close FSUIPC7 and attach the log file here. John

This is a very old post - I have no idea, sorry. I probably didn't even raise this with them following Roman's post, But things have changed a lot since this post. To control the fuel pump in the G58 (and G36) you can use the available presets and maybe there are also some Input Events for this (I haven't checked). You can also use both presets and Input Events via offsets. John

Can you show me/attach a log file please. This parameter didn't exist before 7.4.9. Try the minimum value of 30 (seconds), John

I will take a look anyway and either update to allow calls that go to the FS when the thread is terminating, if possible, or I will update the documentation to specify what is allowed in a terminate function. It is interesting that a dying thread cannot send/post messages to another thread (or so it seems) and I would like to understand why and if this can be changed. I can also maybe look into changing the order of things, and process the terminate event before starting the thread termination, but that may not be possible, for various reasons. I may also update to post some messages (asynchronous) rather than send (synchronous) as this will allow subsequent calls to be processed, although the messages still won't be delivered/received/processed, for the same reason as already mentioned, but will allow any other calls to be executed Cheers, John.

Ok. This problem is that key presses are not being received and seems to be related to the state if MSFS when FSUIPC obtains the connection and starts requesting data and the key presses. It seems that sometimes the requests are accepted (i.e. no errors) but the request to receive keys is not processed and no key input is received. This seems to be a timing issue related to when the connection to the sim is obtained. I have been adjusting this in recent releases to fix this issue when reported, but this then breaks it for other users. Very annoying... What your users who are experiencing this issue can try is to manually set the delay between detection and connection. This is controlled by the ini parameter (in the [General] section of the FSUIPC7.ini file) DetectToConnectDelayAuto, which uses a default of 60 (seconds). They can try both increasing and decreasing this to see if that helps, e.g. add the following to the [General] section of the FSUIPC7.ini file: DetectToConnectDelayAuto=75 or maybe DetectToConnectDelayAuto=30 (note this ini parameter has a max of 90 and a min of 30). There is also a related ini parameter DetectToConnectDelay which is used when FSUIPC7 is manually started, which has a default value of 5, a max of 10 and a min of 1, Anyone experiencing this issue should play around with those parameters. I would be interested to know if this fixed the issue, and if so what values are used. Also, any log files from people experiencing this would be of use. Cheers, John

I can see this issue. Please try the attached version where this should be corrected. This was due to an error on my part - I removed (commented-out) some code that determined the Input Event control number from the name when the number was not available as I had added additional code to reload assignments once Input Events are loaded which would also set the correct control number. However, I then removed this additional code as it was creating further issues and forgot to re-active/uncomment the original code. Sorry about that. John FSUIPC7.exe

Are you starting FSUIPC7 manually or are you using the auto-start feature? Can you show me a log file showing this issue please. Once FSUIPC7 is running, activate logging for Buttons & Keys, load an aircraft and then press a button and key that has an assignment, and then exit FSUIPC7 before attaching your FSUIPC7.log file. I will perform some tests here to check this, but you should really only be using Input Event assignments in aircraft profiles as they are always aircraft specific. I will also need to see a log file showing this issue, but let me check here first and lets deal with the other issue first. John

No idea, sorry. I haven't looked at this since our last discussions, but I don't think there is much I can do about this. I will take another look when time permits. John

I can't see any changes between 7.4.8 and 7.4.9 that could cause this... I will need to see a log file with logging for Buttons & Keys activated. Some users reported key presses not being received in 7.4.8, and this seemed to be related to the timing of acquiring the connection to MSFS. This was changed slightly (i.e. a delay added between the detection of MSFS and attempting to connect) and seemed to fix the issue for those that reported it. Its rather annoying that this has now broken the same thing for some other users. I have no idea why MSFS is just not sending keys to FSUIPC7 in some cases, and no errors are reported. The users having this issue can maybe change the timings using some new ini parameters (undocumented). How are these users starting FSUIPC7 - is it auto-started (recommended) or are they starting it manually, and if so when (i.e. before or after MSFS is started). Are these users using a registered/licensed version of FSUIPC7 or an unregistered/freeware version? John

FSUIPC7 is the only version of FSUIPC that is an exe and that you can run standalone, all other versions are dlls that are embedded in the FS, so they only start with the FS that they are embedded in, so this makes no sense.

No, as I said... Why would you ever want to run both MSFS and P3D at the same time, let alone have them auto-started? I don't think there is any external FS app (i.e. one that connects to the FS) that can handle this scenario, or would even want to... John

Lua threads have no access to the FS, and they can only communicate by sending (windows) messages to the main thread that communicates with the FS. The problem is that these messages are not being sent once the lua thread is closing, so this applies to all lua calls that would interact with the FS. The terminate function should be used to close things down on the client side really, i.e. no interaction with the FS. I am not sure what or if anything can be done about this at the moment, but I will take a look after the SU15 release. You may have to set up something manual to achieve what you want, such has having an event.flag function to set/write the lvar value and then overload the LuaKill assignment to first set the flag (LuaSet) , to trigger the lvar update, and then kill the script (or call the LuaSet on press and the LuaKill on release).. John

I can see the problem (windows messages sent from terminating lua processes are not being processed) but am not sure what can be done about this at the moment. I will look into this further after the SU15 release. John

Event setting this ini parameter to the maximum of 20 seconds still doesn't allow lvars to be updated in the terminate function, so it looks like such calls are blocked when terminating. I am not sure why or if there is anything that can be done about it at the moment - I will look into this and get back to you. John

By the way, how are you exiting the lua script - are you killing it manually (i.e. LuaKill), or is it being killed automatically as the flight has ended? In case of the latter, it may be that the connection to the FS has been terminated before the request to update the lvar can be sent. Maybe try adding an ipc.log call after the request to set the lvar - does this message get logged?

FSUIPC7 is for MSFS2020 only. FSUIPC6 is for P3Dv4, P3Dv5 and P3Dv6 only. FSUIPC5 (now discontinued) is for P3Fv4 and P3Dv5 only/ FSUIPC4 is for FSX and P3Dv1-v3. They are not interchangeable, except for FSUIPC5 and 6 with P3Dv4 & 5. Well, as all versions of FSUIPC except FSUIPC7 are dlls (i.e. embedded in the sim), you cannot use these for any sim that they are not designed to work with. FSUIPC7 will not see ot connect to any other FS than MSFS2020. If it is running when you start P3D or FSX, it will prevent any other version of FSUIPC running, so just don't run FSUIPC7 with any other sim than MSFS2020. No, it will have no affect whatsoever on P3D.

Please try increasing the TimeForLuaClosing ini parameter - see the Advanced User guide for details. However, I would have thought that the default of 2 seconds would be enough to set an lvar value - I will take a look later... John

No problem!

Also anti-virus software (especially McAfree but also with other anti-virus software) can prevent the key validation program from running, so please check any anti-virus software that you are using. All of this is described in the FSUIPC7 Installation and Registration guide, under Invalid Key Problems. Please always consult the documentation before posting with issues. John

I have checked this order and the key details are valid. Are you sure that you are entering the details correctly? I have PM'ed you a key file - please try this. You are also using FSUIPC7 - please use the specific sub-forum for FSUIPC7 for all future issues with this product. John

Can you please show me/attach your FSUIPC4.log file generated after a crash. Also, please check the windows event viewer for the crash report and save and attach that. John