pilotjohn

Hi, Is there a definitive mapping between offsets, SimConnect events and the drop-down list of "controls" in the button configuration? The terminology between these 3 are inconsistent, and the drown-down is not searchable (so it's hard to tell where I fill find something). Alternatively, is there at least a searchable file of the "controls" in the drop-down list? Thanks, John

Which IPC facilities can I use to trigger something (execute external program) on FSUIPC connect/disconnect? Should I assume that ipcinit is called only once, on first connection, or if there's a disconnect will it be called again? Is there something that is called on disconnect?

I managed to completely clean up and reinstall vJoy. I'll report back when this error occurs again.

I'll stop posting to this thread. I'm not sure if this was a mis-test on my part. The last few flights with FSUIPC running before the sim, I haven't had the issue of it not functioning as expected.

I'm supposed to have 6 vJoy devices, which it seems like I have. I can complete uninstall and re-install vJoy, but not sure it will clean up the registry completely.

Unknown for some of these. I'll do some more testing.

Probably, but not sure where to delete these from. I did have an instance of vJoy have to be uninstalled "manually" which probably left these. They are not physical.

Any suggestion on what/where to delete these from? I think these were being added by vJoy during install/uninstalls.

The series of events that is probably related to the pause (and how I generally have to recover): 1. Flying with no issues (controls working) 2. Controls stop working (e.g. always at the wrong time - e.g. late landing phase, some maneuvers etc.) 3. I frantically pause (e.g. press ESC; pause with menu) 4. Start FSUIPC (since in this case it crashed) 5. Resume 6. Flying again, still about to crash etc. (no control effectiveness despite FSUIPC now running) 7. Pause again 8. Go to FSUIPC Axes/Ok 9. Unpause 10. Things have recovered

Do you mean try to find them in the registry and clean them up? I'll enabled SimConnect and will keep you posted when it happens again.

This happened with a restart of FSUIPC after a crash as a result of TransmitClientEvent failed. Logs for both session attached (also in other thread). Log 1 leading up to FSUIPC crash, log 2 FSUIPC restart but controls not working until Axes/Ok. logs.zip

I just had another one of these events with the latest build... TransmitClientEvent failed, and an eventual crash of FSUIPC; logs attached (1). Also, on restart input was not working until I visited Axes and clicked Ok; logs for this also attached (2). logs.zip

This issue (or maybe different) seems to have returned... On today's debugging session (since like with FSX I'm doing more of that than flying), FSUIPC was running, sim started, flight launched, no response in sim (went to axes) still nothing. FSUIPC exit//restart was required.

Feature request please: be able to do this without having to create 100+ Lua scripts (or one giant one). Maybe adding a param after the key as the delay, and they could be executed in the order listed in the INI.

Is there a way to insert delays between key presses? MSFS seems very finicky about it's configured keyboard shortcuts (and a kludge with what it does with them). For example Alt+0 "loads saved camera 0" so I would simply expect a second press to do nothing. Instead it return to the default camera (even if you pan-ed away). As I result I'd like to send two Alt+0 to center the view (one to return to default camera - which it shouldn't be doing but so it does, and the second to return to the saved camera). This seems unreliable with a sequence, I assume because of how fast it happens. I'd like to insert a delay between them.

So it looks I am now also having this issue, and my previous post about "random disconnect" my in fact have been this behavior. I was flying, all control input stopped. I started to troubleshooting and noticed FSUIPC was no longer running. I saved the log, and saw the crash entry Event Viewer. In the log (attached) you can see FSUIPC reconnecting, but then it seems like it just crashed and that's the end of the log entries. FSUIPC7 - Crash.log

I found a solution that works fairly well. Instead of having a Pan Up-Left keyboard assignment in MSFS, and then mapping the UL POV to it, I instead send the pan left and pen up keys together for the UL POV. This ended up working better. Sending keys with modifiers is unreliable unless the modifiers and keys are mutually exclusive (e.g. sending ctrl-up for pan up and ctrl-shift-up for pan up left created all sorts of havoc).

There are two projects that you can use: https://github.com/nguyenquyhy/Flight-Tracker-StreamDeck which doesn't need FSUIPC and is bidirectional (e.g. update state) https://github.com/ashupp/Streamdeck-vJoy for which you probably want FSUIPC, but can always directly map to MSFS as well

One of the setups I was hoping for is a combination button of POV press and POV left for "quick view", but this would require "held" feature (since quick view springs back unless held).

It also seems the compound solution I was looking for is not possible because there's no "held" option for compounds (e.g. while POV is pressed and left send key X).

It seems possible to use the keyboard presses to simulate this, MSFS is able to interpret multi-key presses (e.g. ctrl+up+left) which allows me to set up key presses for some camera views (e.g. 45 degree left). Is this possible in FSUIPC? It seems I can only send one key and the modifier.

The camera events don't seem to work in MSFS. I was hoping to remap the POV on my Yoko+ with a combo, but even a simple test doesn't seem to work. Neither View Left nor Pan Left has any effect. Is this a known limitation? 64844438 [Buttons] 4=PD,38,C65671,0 64844438 FS Control Sent: Ctrl=65671, Param=0 PAN_LEFT

I don't have any button assignment in FSUIPC, but will try these.

Yes, the axes were showing correctly in the assignment/calibration windows. I will keep logging on and will share when it happens again. No, this didn't even require MSFS restart. At one point the plane was just doing circles (controls disconnected during a ground turn), I let it do that, and as I was trying to recover it at some point the controls started working (but not during a step where I would have expected it to - e.g. restarting FSUIPC).

With everything setup and working correctly (axis to FSUIPC direct and calibrated), the sim will stop responding to control inputs during flight (so far it occurred on ground several times). FSUIPC still shows the inputs working correctly, but the sim is not responding to them. Reconnect (go Axes and click Ok) or restarting FSUIPC does not solve the problem. In one case control input recovered after a few minutes.