John Dowson

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

It is the parameter/value that is sent with the control. Some controls take a parameter, others not. The parameter should be pretty obvious many/most controls, but if you do not if an FS control/event tales a parmeter, or what that is, then you will need to look up the event in the Asobo documentation (e.g. see https://docs.flightsimulator.com/flighting/html/Programming_Tools/Event_IDs/Aircraft_Autopilot_Flight_Assist_Events.htm). For presets, the parameter is used to substitute the parameter placeholder (the '@' symbol or $Param) before sending the preset calculator code and applying it in the FS, Some Input Events also take parameters (always 64bit floats at the moment) others not - you will need to use logging to determine if a parameter is needed and what the value range of the parameter is. You also posted in a topic that has nothing to do with your question. Please don't hijack unrelated topics/posts - create a new one, with an appropriate title, if you have a question unrelated to other posts. John (I also thought i had already responded to this question in a fresh post but can no longer find/see that...)

Or maybe try looking at the provided documentation....

All three components (Name, Address/email & key) must match. If they all match and the key still doesn't validate, this is usually because the VC++ reditributables need updating. Download and install the latest combined redistristributables (both x64 and x86) from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist and try again. If you still get the same issue, please let me know your order number (do NOT post your key details!). John

Sounds like you have checked the Control to repeat while held checkbox. Uncheck that and try again.

You need to use the lvars, not the standard FS controls. The easiest way to do this is to use the available presets. Check the Select for Preset box, click the Find Preset... button, and navigate to the Black Box->AnalogBaron presets, and under Electrical you will see the following presets: LEFT_ALTERNATOR_OFF LEFT_ALTERNATOR_ON RIGHT_ALTERNATOR_OFF RIGHT_ALTERNATOR_ON Try assigning to those. However, looking at the calculator code for those presets, it looks like the *_ON ones are toggles (but not the *_OFF ones) for some reason. You can either use those or define your own presets. Alternatively, you can add the lvars BKSQ_alternatorSwitch_R and BKSQ_alternatorSwitch_L to free/spare FSUIPC offsets and assign to the provided offset controls to set/clear the lvars via the offsets. John

First you have to be aware that the flight load/save/auto-save functionality provided by FSUIPC completely rely on the functions provided by the MSFS SDK, namely the SimConnect functions SimConnect_FlightLoad and SimConnect_FlightSave (as well as SimConnect_FlightPlanLoad). Although the SimConnect_FlightLoad function is documented as working, the SimConnect_FlightSave function (as well as the SimConnect_FlightPlanLoad function) is still documented as 'NOTE: The current status of this function is NO ERROR, NO RESPONSE.', which is Asobo's way of saying that this function is still not 100% working/reliable, It has been this way since release. Therefore the saving and loading of flights is still not 100% reliable, although some users have reported more success with this than others (maybe aircraft dependent). If it is not working, I cannot do much about this - you can try raising a bug request with Asobo, but they may reject this if the flight file is generated by the SimConnect_FlightSave function as they are already aware of issues with this. Flight files generated by MSFS2020 itself and those generated by external apps (using SimConnect_FlightSave) should be compatible/the same, but this may not actually be the case at the moment. You could try loading the flight file via FSUIPC7 (File -> Load Flight) to see if that makes a difference. You can do this either when in the World Map, or when you already have an aircraft loaded and ready-to-fly. John