John Dowson

I've been thinking about this a bit and it should actually be pretty simple to implement, so I'll add it to my 'to be implemented' list. However, with FSUIPC7 for MSFS being the priority at the moment, it will take some time before I can get around to looking at this in detail. I will implement as a plug-in dll, so I can add extra features not available in the SDK, such as a direct 'control/event' interface, not via offsets. Also, it should be reasonably straightforward to implement as a separate process, using one of the provided SDKs. All that is needed is to add an embedded http/websockets server, and then exposed the FSUIPC SDK functions as endpoints. The most developed/used SDK at the moment seems to be Paul Henty's .net client. Maybe @Paul Henty has already considered this? John

Yes, or at least it is in the Cessna Citation CJ4. I will report this. Later: reported.

Who knows! I could report this and it may get fixed, but if you check offset 060C first this should be valid for all flight sims, so it doesn't have to be specific for MSFS.

@zkiwi Ok, thanks for the update.

Hi Nick, yes, seems that way. However, you can check offset 060C (gear retractable flag), and if that's 0 then you can ignore 0x0BE8. John

The main window of FSUIPC7 is currently empty, and all panels are accessible from the menu bar. For the time being, the main window is just a menu bar really. I am planning to add 'button screen' functionality to the FSUIPC7 main window at some point, as provided by WideFS.

@bertranda I've checked the code and the request for the 'IS USER SIM' variable on AI traffic was commented out, as it didn't exist in earlier versions of the SDK. It looks like this is now available, so I've added it back. Could you try the attached exe to see if this solves your issue, thanks John FSUIPC7.exe

Actually, I'll put this on my list to investigate at some point. i.e add a http (or maybe websockets) interface to FSUIPC. However, I don't expect to have time to look into this for quite some time. Any such interface would only expose reading and writing to the offset data area, as is supported by the current SDK. John

Yes, I'm afraid so. That's the 'Active Pause' which still can't be detected. You should switch to using one of the other pause controls - either Pause On/Pause Off, or Pause Set. John

@StefanGA Thanks for reporting back. Glad its now working ok (and wasn't an FSUIPC issue!). Regards, John

I've connected my Track-IR now, and when using this I get the TranmitClientEvent failure. However, when this occurs the re-connect kicks in and seems to work for me:

I don't have any GF devices with displays, and have not used the lua GF library, sorry. I just tried the gfdDisplay.lua plugin though. It doesn't illuminate the leds on my RP48s. Not sure why.

I have released a new version that contains some changes to help me track down this problem Could you please update. Also note that one the TransmitClientEvent failures are received, disconnecting and re-initialising the SimConnect connection does not solve this problem. So unfortunately the only thing you can do at the moment is to restart FSUIPC7. I'm not sure why FSUIPC7 is crashing on the 3rd re-connect, but I don't think its worth investigating this issue at the moment. If/when you experience this issue with the new version, could you show me you FSUIPC7.log file please (full).

There is no web browser interface to FSUIPC as far as I'm aware. Please check the SDK for the available interfaces. I guess, for example, you could write a java plug-in that runs in the browser and communicates to FSUIPC via one of the Java SDKs. Or one of the other SDKs (e.g. python) if that is supported by the browser. There are no plans to add a HTTP or websockets interface directly to FSUIPC.

This is because you have Auto-connect to FS set in the Options menu. When this is set, the menu options to Connect/Disconnect (in the Start menu) are not needed. Sorry, I don't understand what you mean. Did you try the Assignments -> Axes.. menu option, which displays the Axes assignments panel.

@cessna117ab ou are also experiencing the same issue as reported in this thread: It is being investigated. Also, please update and try the latest version. I cannot tell what version you are using as you posted a 'continuation' log. I am closing this thread now as the problems reported here are already in other threads.

Hi Charles, sorry, I don't think I currently have any lua scripts I use with my RP48s. I have them connected to my development machine (not my flight rig) and use them for assigning controls during development/testing. However, what is you issue? The RP48 is just a switch box (no display, apart from the LEDs), and you can just assign in buttons & switches as any other device. Similarly, in lua, you can use as you would any other device (using the device number/letter and button number). For example, to detect a button press in lua, you would use the event.button function, giving the joystick number/letter and button number as arguments, as well as the function to be called when the button is pressed. I've not looked into controlling the LEDs, if thats what you are looking for. John

@mattia1513 Please note that the pause indicator and control offsets 0x0264 and 0x0262 are now working for various pause states (but not all!). Please download and try the latest update.

A new version has been released that contains some changes to how key presses are handled. Unfortunately the numpad 0-9 keys are still not recognised in FSUIPC7 when MSF has the focus - SimConnect is not passing these through to FSUIPC7 although they are requested. I will report this to Asobo.

This has now been released.

It will be available from SimMarket when ready.

This surprises me as it was only a fix to restart the SimConnect connection when the TransmitClientEvent failure is received. Has nothing else changed? Do you still get the TransmitClientEvent failures and it reconnects ok, or have the failures stopped? I am surprised at either! @flash In your case you get the failures and its trying to restart the connection, but is still getting the failures on restart. It then crashes on the 3rd reconnect. As Pete says, please check the Event Viewer to see if there is a crash report for this.

You could try this version to see if it prevents the crash and if it re-connects successfully. It wont fix the original problem, the TransmitClientEvent failures, which is still under investigation: FSUIPC7.exe It if still crashes, can you show me your log again please.

You have this problem: It is being investigated. FSUIPC7 is also crashing as there is a problem with the automatic re-connect on this failure (by default after 5 failure messages, but configurable) - this should (hopefully) be fixed in the next build.

I've added this at offset 0x0B46 (1 Byte). And its also writeable! This will be in the next build release, within the next few days.