John Dowson

I don't know - you should ask FSX Flight. However, only FSUIPC7 is compatible with MSFS. You should download and try it.

Do your button/switch assignments also stop working? What about any controls assigned in MSFS? If you don't have any axis assigned in MSFS, maybe try assigning one so you can test this when the problem occurs.

Ok, I thought it would, but unfortunately no idea why! Rather worrying.... John

Unfortunately not. I have reported many things, in the beta/third-party developers forums as well as via zendesk tickets, but am not getting much response to anything at the moment. I believe Asobo are aware of many issues with SimConnect and have various updates planned, so hopefully many of these will be addressed in these updates, but any concrete information is sorely lacking. The current SDK is still at version 0.5.1. Yes, that is/was are hope, but not sure if that's the case. Unfortunately I think they are currently more interested in xbox or "game" users rather than simmers, and the development of the SDK is a much lower priority.

So, of I understand you issue correctly, you are not seeing any errors in the FSUIPC log. When you say do you mean in the assignments/calibration window, or are you logging axis movements and seeing them there? I would be interested in seeing a log file produced when this occurs and you restart FSUIPC and get the same problem. And when you say: does this imply that, in other cases, the isue was only resolved by restarting MSFS? Other than that, I'm not sure what else I can advise at the moment. It may be worth activating SimConnect logs (as shown in the other thread) to see if SimConnect is still receiving/sending when this issue occurs.

Yes - do not load any flights using FSUIPC7 until Asobo have fixed this issue. And yes, Asobo is aware of this issue, and there isn't much that can be done about this at the moment. I am thinking of disabling the 'load' options for the time being, just to prevent people using this and then suffering the consequences....

You are using LINDA, so you need to contact LINDA support. I cannot help you with LINDA.

No idea. Why don't you ask them? They just said that they would report back once updated (as far as I can remember). Again, no idea. Such questions need to be addressed to Microsoft/Asobo. They have public forums for these type of queries now MSFS is released. Please see

Don't send a control on the button release. You can overload the button press to send both the Avionics set on and Avionics set off event/control when the button is pressed. You will need to manually edit the ini to achieve this. You then need to add an offset conditional check on offset 0x2E80, so that only the 'off' control (with parameter 0) is sent when the avionics are on, and the 'on' control (with parameter 1) is sent when the avionics are off. Offset conditions are explained in the Advanced user manual (for FSUIPC4/5/6).

If you read the initial post in the 'FSUIPC7 control problem' you will (hopefully) see that this is completely distinct from your issue, although you did also post your issue there (again, thread hijacking). The issue in that thread is that his controllers are no longer working, it is NOT a random disconnect issue. Its really not difficult. Search for an issue that is the same or very similar to yours. If one exists, use that thread. If not, create a new one. For your issue, please check your USB power management settings. If they are correct and you still have your issue, please start a new thread.

@pilotjohn Could you please try the attached version and let me know if that helps/solves your issue, thanks. FSUIPC7.exe

That seems strange to me. I don't have any PFC devices so cannot advise. I'll leave Pete (or Thomas) to respond to this. However, it seems to me that your throttle is detected as a standard USB hid device, so I don't think you need them (if you don't have any other PFC devices). Maybe at least try without those, to be sure.

There looks to be a problem with the request for keyboard input which I am currently investigating. The problem seems to be with the mapping from the MSFS defined key input strings and the MS VK codes. Looks like I misunderstood this when I implemented, so I'm checking now and will provide an update once done.

With TransmitClientEvent failures reported in the FSUIPC7.log file?

Ok. Seems strange as I've never encountered this issue, and stop and start MSFS with FSUIPC7 continually running all the time. However, I'll add an additional axes scanning request once MSFS starts, to see if this solves that issue. I'll post an update shortly.

@pilotjohn ok. But you have reported your issue in a different thread. Your issue is distinct from this issue, which has been identified as a SimConnect error that is causing the disconnect, known by having TransmitClientEvent failures noted in the log. There are currently lots of issues with SimConnect (and many in FSUIPC7, i'm sure), but it does not help me in the investigation when cross-posting your issues to different topics/posts. Could you please refrain from doing this, and post in the topic relevant to your problem. So, if you do not see any 'TransmitClientEvent' failures in your log, please do not add or follow the advice in this thread. It just causes confusion. Thanks. I will update the title of this thread to make this thread more specific to this issue. John

What update? If you edit a previous post, you need to check the 'show the message has been updated' checkbox and specify the reason in the provided text entry field, otherwise it is not noticed.

I'm checking this and will get back to you at some point, but it may take a while.

Ah, ok. Thanks for letting us know.

Ok, thanks.

I'm not sure, which is why I am asking for you to check. is that the config you have when you experience this issue? If so, then no. But if your assignments were previously different, then please check again with those assignments (presuming each of those axes is also calibrated in FSUIPC7 - if not, do that first).

@ark1320 I've just tested the numeric keypad input and it looks like FSUIPC is not receiving the input events for these keys. Not sure yet if this is an MSFS or FSUIPC problem, I'll take a look. In the mean time, I suggest you assign to other keys. John

That log file shows nothing, not even any key presses, although you have Button & key logging activated. Are you sure that either MSFS or FSUIPC7 has got the focus during your tests? Can you also update to the latest FSUIPC7 build, with date 08/09/2020. Thanks.

Ok, this is normal when using the PFC dlls and is nothing to worry about.

This is not the case anymore. ou can assign in both MSFS or FSUIPC7. Just make sure that you don't assign the same axis (or button/switch/keypress) both in MSFS and FSUIPC7. Its probably a good idea to create a 'FSUIPC profile'. But this can have assignments and doesn't necessarily have to be empty. John