John Dowson

No, as its an issue with SimConnect, not FSUIPC. We're awaiting a patch to the sim/SDK from Asobo/MSFS to resolve this issue. They are releasing information tomorrow about upcoming patches - hopefully this will be addressed and we'll know more then.

No.

Ah yes, forgot to enable that, sorry. Will do that shortly (probably tomorrow now). John

For the FSlabs A3xx, they do indeed use the ROTOR BRAKE event/control as a custom control, with the parameter specifying the action. There is a tutorial on how to use these with FSUIPC over on the FSLabs forums: https://forums.flightsimlabs.com/index.php?/topic/22402-v440-update-in-depth-tutorial-to-bind-switches-and-push-buttons-to-keyboard-or-hardware-for-the-a3xx/ There was also a recent support question on these that may be of interest: John

Ah, ok. I could add this. Currently the 'show' state is determined by the auto-connection flag. If you have auto-connect set, it will always start iconised, if not set then it is shown on start-up.

By "Show window", do you mean the main FSUIPC7 window? What do you mean by "persistent"? Do you mean to keep it on top of other windows (when open), as we do with the console window when you check 'Force Console to Top'? John

@jmig I have added back the Aileron and Rudder Trim set controls. Although these are undocumented, they seem to be working. Can you please download and try the latest release. John

Its not comparable. LittleNavMap uses an older 32-bit SimConnect implementation.

Just delete it. Or just don't run it There is currently nothing installed, you just download and run the exe. You will need to stop FSUIPC7 running first. There is a known issue with the SimConnect API in the released version of MSFS, we are expecting a patch soon., Please see John

Please see Also, please do not post in an unrelated topic. And check this sub-forum first to see if your issue has already been reported. John

This is a known issue with the released SimConnect API. Please see John

As Pete says, you should really try Paul Henty's .net dll client first. Its more modern and kept up-to-date by Paul, and has already been updated to work with MSFS. Please see https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ You can try the fsuipc.cs method if you prefer. However, I've never used/looked at this and don't know if it will be working with FSUIPC7/MSFS. John

This is what I assumed and answered for! As Pete says, this is the FSUIPC7 support forum, not for general MSFS support. Just seemed a strange question... John

There is both an 'on release' and a 'repeat' for button/switch assignments. Why do you ask - have you not seen this in the UI? John

I should hope they would provide such facilities. I have posted in the 3rd party forums to ask about this. I also noticed this: It has been brought to my attention that time does tick on regardless of what kind of pause you use! If you use the REAL pause you will see the clock stop… but if you unpause you will see it jump forward in time! The same goes for the ESC pause…! Just so you know. Nothing you can do about it, unfortunately. Doesn’t change the fact that the real pause and ESC should be used instead of Active pause. So even the pause we can use doesn't work as it should! John

This has now been released. John

Also, there is extensive documentation on FSUIPC's Lua interface. You can download this (for FSUIPC4) here: I will be adding the FSUIPC5/6 documentation to that page shortly (next few days), which is more up-to-date, although some facilities (e.g. mouse related functions) won't be working in FSUIPC7. John

You can use Lua as plugins to FSUIPC7, but not for stand-alone applications. For external/stand-alone applications, we provide the 64-bit external user kit for C/C++. There are a variety of other SDKs built on this, for .net, java, C, Delphi, Python, Visual Basic, etc. They should all work with FSUIPC7. See The SDK there is a bit old and needs updating, but should still be valid. I'll add the latest FSUIPC6 SDK at some point. There is also a new java SDK (32-bit and 64-bit) which was kindly provided a week or so ago, that is more efficient than the current version. I'll add that to the SDK shortly. John

There will be a discount for FSUIPC5/6 license holders, but not for FSUIPC4 I'm afraid. John

It has been reported to Asobo that many events for the G1000 are missing, and many of those currently documented (as 'Responded') don't actually work (also for the GNS430/GNS530). Asobo are aware of the issue and have said that this is work in progress. John

Please read the release note/announcement - under 'Missing Functionality' you will see: 1. Mouse Macros (and other mouse functionality, e.g “mouse look”, etc): pending facilities to be provided John

Hi Dave, sorry, but this is not a general forum for MSFS issues, only for those relating to FSUIPC. You should try the MSFS forums. Having said that, it sounds like you haven't specified the correct path to the SimConnect.lib in your build properties. It has to be the folder that contains the SimConnect.lib, not the SDK top-level folder or other folders. Note also, that there are now two SimConnect.lib files. I recommend you link against the one under the 'static' folder, as when using this you do not require the SimConnect.dll at runtime. John

You could try adding a mouse release code to your macro, e.g. [Macros]1=Landing1.1=RX4000001a,3 1.2=RX4000001a,131.3=RX4000001b,3 1.4=RX4000001b,13 (try with and without the 1.4 entry) Alternatively, you could try two mouse macro assignments to the switch instead of using a compound macro. You will need to set up the first mouse macro call. Then comment that out in the ini (or remove and save it). Then set up the second assignment. Then add back in the initial assignment, by editing the ini again, remembering to update the number. John

Also your FSUIPC4.log file, as well as your install log.

I don't see how that could help. Asobo posted on this issue today: John