pilotjohn

Hi Pete and John, I'm trying to make my button configuration more manageable and have been renumbering my configuration. I'm spacing the numbers by the 10s (since I have multiple assignment for many) to make it easier to locate related actions in the future. I am also using <1000 for real buttons and 1000+ for the virtual joysticks, where the thousands is the joystick number (e.g 1000 = first, 2000 = second), then the button number * 10. This would work greats, however it looks like the numbers are only supported up to 2099, at which point things are ignored, and new assignments wrap to 0. With the virtual joystick 9, for example, I would like the use the range 9000-9310. Is it possible to increase the allowed numbering? Thanks, PJ

Ugh, ok thanks for looking into it.

Hi Everyone, I'm looking to see if anyone managed to get the Caravan condition lever to work through FSUIPC? It seems to be using SET_FUEL_VALVE_ENG1, but something's off. It has 3 positions: cutoff, low and high. When moving the lever in the sim, I see the events but both high and low have a param of 1, and cutoff 0. Sending these form FSUIPC gets me cutoff at 0, and low at 1, but I can't seem to get into "high" from "low" or from "high" to "low" (sending 1 as param). I found an Lvar called Condition_Lever_CutOff_1, which is set to 2.0 when the level is high, but setting this via FSUIPC does nothing in the aircraft. PJ

Is this fully working for everyone? I configured it and it appears to do what it expected ... Logging A000 shows the correct axis positions (-1 to 1) Listing lvars and looking at THROTTLE<N>_SET shows the value written The message panel in the aircraft shows a T/O config warning when throttle is advanced But I have to move the throttle out of cut-off first, otherwise: Throttles don't move No indication changes in the thrust display Engines don't spool up Has anyone made the cut-off to idle work in the 0 to -16384 range?

Thanks... please let me know if you need me to test anything.

So I used the client library's FSUIPCExampleCode_CS project to test this out by modifying the BC004_WritingOffsets example. 0x3340 triggers and logs, 0x7f00 does not. This removes StreamDeck and my original setup/code from the equation at least.

Hi@John Dowson @Paul Henty, So I used the FSUIPCExampleCode_CS project to test this out by modifying the BC004_WritingOffsets example. I changed altimeterPressure to point to 0x3340 offset, and used a bool to toggle whether I was setting it to 1 or 0. This works and FSUIPC receives it. private Offset<ushort> altimeterPressure = new Offset<ushort>(0x3340); // 2-byte offset - Unsigned Short private bool b = false; ... private void btnSetStandardPressure_Click(object sender, EventArgs e) { b = !b; this.altimeterPressure.Value = (ushort)(b ? 1 : 0); It showed up in Buttons & Switch Assignments, and in the log for the offset: 643313 Monitor IPC:7F00 (U8) = 0 643313 Monitor IPC:3340 (U8) = 1 705719 Monitor IPC:3340 (U8) = 0 706032 Monitor IPC:3340 (U8) = 1 706219 Monitor IPC:3340 (U8) = 0 706719 Monitor IPC:3340 (U8) = 1 715594 Monitor IPC:3340 (U8) = 0 715782 Monitor IPC:3340 (U8) = 1 715969 Monitor IPC:3340 (U8) = 0 I then changed altimeterPressure to point to 0x7f00 offset, but nothing happens. It doesn't trigger in the Buttons & Switch Assignments and shows nothing in the log. private Offset<ushort> altimeterPressure = new Offset<ushort>(0x7f00); // 2-byte offset - Unsigned Short Thoughts? Thanks, John

Thanks, I'll test this and report back.

@John Dowson Thanks... I tried to use 7F00 with the client libraries, but FSUIPC doesn't seem to be reacting to them. Any thoughts on whether this is a client library or FSUIPC issue? Or me? I posted a thread here:

Hi @Paul Henty, I'm using your client libraries in a small plugin for StreamDeck to trigger virtual joystick buttons at offset 3340. This works fine. I'm updating my plugin to use offset 7F00, which provides more joysticks and buttons. I updated my usage, but this doesn't seem to trigger FSUIPC. I simply changed my offset declaration from: private readonly Offset<BitArray> Buttons = new Offset<BitArray>("Buttons", 0x3340, 36); to: private readonly Offset<BitArray> Buttons = new Offset<BitArray>("Buttons", 0x7f00, 256); and my bit calculation (example for clearing) from: Buttons.Value.Set((vj - 64) * 32 + bn, false); to: Buttons.Value.Set((vj - 64) * 128 + bn, false); All other logging I put in (which button being pressed etc.) work as expected, and there seem to be no other errors in any of the StreamDeck logs. I also put a watch on offset 7F00 as U32 in FSUIPC, but it seems to not be receiving anything. Any thoughts? What am I missing? Thanks, John

I've tried in the past, but the number of fuels selectors available doesn't seem to have been reliable. I'll have to try to again to see if there have been any improvements.

I'm specifically asking about the FSUPIC specific range that starts at joystick #64 (via offset 0x3340)? Based on the 36 bytes, it seems to be 9. Is there a way to use more somehow?

Hello, One of the things I'd like to be able to do is cycle through available fuel selector positions, except OFF (e.g. LEFT, RIGHT, BOTH, LEFT, RIGHT, BOTH) with a single button, ideally usable for all aircraft. Has anyone done something like this yet? I tried this in the past with an FSUIPC Lua, but there were challenges (e.g. setting a non-existing selector index would report it set even though the model wouldn't do anything with it). Does anyone have any suggestions? Thanks, J

Is it 16 (64-79)? I'm trying to space my panels out. Thanks!

Hello, Many times FSUIPC won't provide input when MSFS is first started and a flight is loaded. I have to quit and restart FSUIPC and then it starts working. The log in the former shows connected but never becomes ready (log attached). Have you seen this before? Thanks, John FSUIPC7 - No Input.zip

@Perk Did you find a solution for this? I tried a few things and none of them worked. Using Axis Mixture N Set Using Axis Condition Lever N Set Using Mixture N Set Using Condition Lever N Set CONDITION_LEVER_1_CUT_OFF and CONDITION_LEVER_1_HIGH_IDLE using range Toggle Fuel Valve using range

@nantelpDid you find a solution for this? I tried a few things and none of them worked. Using Axis Mixture N Set Using Axis Condition Lever N Set Using Mixture N Set Using Condition Lever N Set CONDITION_LEVER_1_CUT_OFF and CONDITION_LEVER_1_HIGH_IDLE using range Toggle Fuel Valve using range

No I didn't have the assignment window open. The reinstall of 7.0.9 from April 14th seems to have "fixed" it.

I'll try with the latest. No, the logs are before I quit FSUIPC to restart it, but was sitting on the ramp in the plane. I'll attach the full chain of events next time (if it still occurs).

Yes, I'm using the "old" release (where you added offsets for engine master). The log is complete, as in, that's all FSUIPC would show despite loading up a flight and being ready to go. Is there an official source for the latest greatest version (I'll search for these for now)?

I launch FSUPIC before the sim starts. With the latest update ipcReady never fires after loading into a flight and FSUIPC doesn't actually work (e.g. controls/events). I have to relaunch FSUIPC in order to regain functionality. Is this a known new bug? FSUIPC7.zip

It's the WASM module that was CTD on loading screen for me.

Thanks, it works using the new offsets as bytes.

I'll try this. I was testing on the TBM930 which does have off/on/auto and setting them to 0/1/2 does correctly set the switch and function.

Yes, the individual ignition switch state for each engine would be ideal as multiple offsets.