John Dowson

No, as this would mean that it is not possible to send the full axis range, which seems a strange thing to do... joystickcurves looks interesting though.Shame its an application rather than an API! Improving the response curves to something like that used by jjpystickcurves could be added at some point in the future. However, this would be a lot of work for only a small benefit. It is something I can look into in quieter times... Thanks for the suggestion. John

I'm not sure if uses Simconnect, but probably not as I can see no other 'Open' calls in your SimConnect.log. Maybe check for that in the full log to be sure.

Btw, are you using any other SimConnect clients, or any 3rd party add-ons that use FSUIPC?

I doubt it, it shouldn't matter where FSUIPC7 is installed. I recommend you follow the advice in that link, and uninstall and re-install the VC runtime.

Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.

Sorry, I didn't realise your issue was that the buttons are outside the usual 0-31 (32 buttons) limit. You will have to use virtual buttons to get these recognised, as given in the solution posted by @jaxx (thanks!). John

Activating this control locally, I can see it being logged when you click the ADF frequency swap button in the UI, but sending this event via SimConnect/from FSUIPC has no affect. I'll also report this. Thanks for the report.

Hmm. This has been reported twice before on other versions of FSUIPC, and in both cases we could not determine why this happens, as the slope display is using standard windows API calls. Its maybe be related to a driver issue, but can't be sure. I'm afraid I don't think there's much I can do about this. See .

Ok, thanks - thats what I was looking for! I'll take a look.

Ok, thanks. I'll report this. That control was removed as it is not listed in the MSFS documentation. I'll re-enable locally to see if it still works and, if so, I'll add it back. I'll report back on this.

Strange...thanks for the update.

Why "by hand"? Magneto Left is a valid control. Turning the magneto in the C172 I see it uses the MAGNETO1_SET control, with parameters 0,1,2 for the various positions. You could try that. I'm off now, I'll look into this in more detail tomorrow if you are still having issues.

There are various types of variables used in XML gauges. I'm sure something similar to lvars exists, but I don't know if they are called 'lvars'. Somebody else may be able to explain this better - I'm not a guage programmer. However, as far as FSUIPC is concerned, it doesn't matter. Previously, in P3D, LM provided access to such variables through the Panels.dll. In MSFS, we only have access to data through SimConnect at the moment, and SimConnect provides no way to access anything that is not exposed through that API. We are still waiting for information on what facilities, if any, will be provided to access such data.

I mean the VCRUNTIME library is not installed correctly. Please see the release note or the provided README.txt file. This is explained there, under Issues, with a link on how to resolve this.

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.