John Dowson

If it can't be found, it's not installed correctly. You need to re-install. Please see the release note (in announcements) or the README.txt file provided. John

Maybe try cutting it down a bit - I am only interested in the logs around the disconnection (and just before), so you can remove anything before this if that helps. Otherwise you could post a dropbox link (or other file sharing service) if you use that. Thanks, John

Only in the drop-down menus at the moment. The ones provided by MSFS are documented in the SDK (under SimConnect: status of sim events). The controls list for FSX would be mostly applicable (available in the FSUIPC4 documentation pack - see the Download Links -> Documentation section for this).

Have you assigned a button/switch on your HoneyComb yoke to Magneto Off? If so, it looks like that button/switch is continually firing. Uoi can verify by activating logging for buttons & switches. The latest version is always included in the downloadable zip file.

Yes, sorry - I should have updated the build date in that version. Try zipping them first. They are text files and should compress pretty small. John

Sorry, no plans to add any special support for this device in FSUIPC. However, it seems that you can do quite a bit with this and FSUIPC with LINDA. See John

Well, that would be the ideal situation, but unfortunately many of the MSFS assignable controls are not exposed through the SimConnect API. At the moment that is, hopefully these will be added as the SDK is developed. For now, you could assign to a keypress in MSFS, and then assign your button/switch to the keypress.

Ah, ok - that makes sense!

The usual way to determine what events/controls are used is turn on Event logging in FSUIPC, then activate the button/switch in the UI and see what event/control is logged. However, the problem at the moment with the MSFS SDK is that many actions (in the UI) don't (yet?) have associated controls, and even some of the ones that do have no affect when you send the same control externally via SimConnect. The latter point has been acknowledged and should be fixed in up-coming SDK updates. I've asked about the former point (i.e. any assignable action in MSFS should be exposed via SimConnect) but have yet to receive a reply. I've checked VNV and FLC and these don't log any events, so I'm afraid that they are currently not assignable. I think they are the same, just alternative names. Just checked them in the C172 and both work. The AP button in the aircraft itself uses the AP ALT HOLD event. John

No, the livery doesn't matter. I've checked this and you are correct, the total weight is not updated after the initial value is set for the A320Neo. I'll report this to Asobo. John

No, I've never even heard of this before now! Seems to be something used for 'live streaming'. I'm not sure what support FSUIPC could provide for such a device.

But does the problem occur in FSUIPC7 without LINDA running? If not, then it sounds like a LINDA issue which I cannot help with. This sounds like a different issue then the TransmitClientEvent failures that is the problem for the majority of users in this thread. Maybe try logging axis and buttons & switches, and see if your axis movements and buttons are still recognized (i.e. logged) when this issue occurs.

Which version (build date) are you using? The profile name was added in a later build - the current released build date is 28th August - if you are not using that then please update (check you FSUIPC7.log file for the build date). It should be saved automatically when you close the panel by clicking the 'Ok' button. No, they are still saved on exit. I don't think it matters if you save the changes first or not, as they will be saved when you click 'Ok'.

There are currently quite a few known ussues with the SimConnect_Text functions and its is currently not possible to have an updating text window. Due to this, I have added the lua wnd library to FSUIPC7 (previously only available in WideClient). I have attached two scripts which show the fps (and other things), one using the non-working simconnect text funcytons (via lua of course) and the other using the newly added wnd library, which should give you an idea how it works. Note also that anything using lvars won't work, as these don't exist in MSFS. Most probably. But if you find an offset or control that isn't working as expected, please let me know. Thanks, John FPS_Monitor.luaFPS_MonitorW.lua

Its in the Options menu, Exit with FS checkbox. It should be checked by default. John

You can try FSUIPC4 for P3Dv2. I don't think you need the registered version (if you don't already have a license) to use with the PFC drivers, so you can try without first. For FSUIPC4, you will need to use the 32-bit version of the PFC driver, not the 64-but version. John

Maybe. Have you tried the default hot key to show fsuipc7 - alt +f?

Btw, there is no 'installation' for FSUIPC7. You just download, unzip and run it. There is currently no installer.

No. They are completely distinct. However, you cannot run FSX and FSUIPC7 at the same time (due to the clash in windows class names), but why would you want to....!

Ok, thanks. I'll check that one tomorrow.

Yes, all offsets are maintained between versions and don't change, although maybe some new ones are added and others may not work. It means the status is unknown/untested. Many (most hopefully) will work, I just haven't gotten around to verifying them yet.

Ok. Could you keep it like this for a while, and send me the logs (the SimConnect ones + the FSUIPC7.log) once you get the disconnect. You may want to clear the SimConnect log files each time before you start, so you know which ones to send (or just leave them and send the latest if/when you get the issue again. Thanks!

Yes, seems that way, can't think of another explanation!

Ah, sorry, was getting confused - I was in MSFS/FSUIPC7 mode for some reason.....!

You can get it here: I would think that you have the 32-bit one, GFdev.dll, which is the one used with FSUIPC4. Cheers, John