John Dowson

fsuipc 5.103 is no longer supported - we only support the latest version of each FSUIPC release. And the latest version of FSUIPC5 is only valid fromP3Dv4.3 and later. You can use earlier versions of FSUIPC5 that supported v4.0 (if you can find them!). but they are not supported, sorry. John

This has been corrected in the latest build, now available.

You could also add the following to the [General] section of your FSUIPC6.ini file (what there is of it!): Debug=Please LogExtras=x200000 That should show me more. Finishing now - I'll look into this further tomorrow.

Looks like its crashing on scanning your devices and registry. I'll take a closer look tomorrow, but could you tell me what joystick/usb style devices you have? I can see just a Saitek Pro Flight Yoke, but it looks like there is problems retrieving its details from the registry. Did you install Saitek software and/or drivers? If so, please uninstall them, disconnect your yoke and then reboot. Connect the yoke and try again. If you haven't got any additional drivers/software installed, it still worth disconnecting, rebooting and re-connecting, maybe in a different USB port. And if you are connected to a USB-3 port (blue), try a USB-2 one instead. I'll take a look in more detail tomorrow and see if we can add some extra logging to track down where.

Same place as your .log and .ini files.

Sorry, but could I also see your FSUIPC6.JoyScan.csv file please.

I can confirm this behavior: - FSUIPC offsets and the Fuel Pump control act as toggles between off/low - no parameter to the Fuel Pump control - this just acts as a toggle - FSUIPC correctly updates the fuel pump offsets when in off/low - manually setting the fuel pump(s) to high does not show any events/controls, and does not update the FSUIPC offsets - once the fuel pump(s) are set to high, the FSUIPC offsets and controls no longer have any affect I will raise this with Asobo. John

SimConnect is an API which allows communication between 3rd party programs and the flight simulator. FSUIPC is one such 3rd party program which makes use of the SimConnect API. SimConnect is an API. i.e. an application programming interface. You need to write a program to use it. FSUIPC is a utility program. If you are writing a program from scratch, you would be better of using the SimConnect API. SimConnect is provided and supported by the maker of the simulator, and as such is supported by them as is the simulator. FSUIPC is build on top of SimConnect and will survive as long as is needed. Try goggle. There is plenty of information out there on both SimConnect and FSUIPC. John

For requests, you will probably get more responses in the main support forum. This forum is to hold such scripts when contributed. For the FSL A3xxx series of aircraft, you need to look into the use of the ROTOR BRAKE control, which has been re-purposed for diffferent controls based upon the parameter. You may find what you need there (but I can't check as I don't have these aircraft). Please see 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/ John

@Mouseviator has kindly provided an updated java SDK for FSUIPC. This should be more efficient than the existing SDKs as requests are processed in batch, rather than individually. Please see . The new SDK with documentation and examples is available from @Mouseviator web site: https://mouseviator.com/fsuipc-java-sdk/ Also available from github: https://github.com/Mouseviator/FSUIPC-Java This package has been added to the SDK in the FSUIPC6 installer (after version 6.0.10). John

Can you please attach your FSUIPC6.log (from the crash when registered, but also when using it unregistered if possible) and .ini files please. Also check the windows event viewer to see if there is a crash log there, and if so show it to me. John P.S. I have deleted your 'status update' message to Pete. All support is via the forums, not PMs or 'Status Update' messages, whatever they are...

Strange...Are you using the "JoyLetters" facility (see User guide if you don't know what this is). If not, activate it as this will prevent issues if/when your joystick ids are re-assigned.

Can you please stop posting/complaining about the same issue in multiple threads. I have nothing more to add on this issue.

Please do not cross-post (i.e. post in a topic that is not relevant to your question). How have you assigned? Have you calibrated? Have you tried adding a 'slope'? i'f you require further help, please post a new topic (and attach your .ini). John

Of course FSUIPC uses SimConnect. It just doesn't need the SimConnect.dll any more as it is now compiled against the static SimConnect.lib file.

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