Jump to content
The simFlight Network Forums

pilotjohn

Members
  • Content Count

    316
  • Joined

  • Last visited

  • Days Won

    3

pilotjohn last won the day on December 24 2020

pilotjohn had the most liked content!

Community Reputation

5 Neutral

About pilotjohn

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    US

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sounds good, thanks. No hurry, just thought it would be cleaner to not mix topics. 🙂
  2. The "repeat while held" rate seems to be different between physical (those coming from the OS) and virtual (device IDs 64-72) joystick buttons. As I switched to triggering FSUIPC through virtual buttons from Stream Deck (instead of using vJoy), the rate at which events are sent to MSFS (for example, MHz increment on COM1) appears much higher for virtual buttons. This makes it hard to do step increments. I have the repeat set to 25,10 (40ms with 400ms initial delay), but the "initial delay" also seems to be ignored.
  3. If you'd like to use Stream Deck buttons to trigger FSUIPC functionality, you can use FSUIPC's native "virtual joystick", without the need for vJoy (which can create issues for certain games and devices), from this plugin: https://github.com/IslandJohn/StreamDeckFSUIPC. If there's interest, I can add triggering of offsets and controls directly, but I didn't see a need to move the UI for those things from FSUIPC.
  4. Everything seem to be working, except for one thing... the "repeat while held" for the FSUIPC virtual button seems to be a lot faster than for physical/device buttons. Is this by design? Can this by adjusted? Because it takes about 0.06 seconds for a press-release cycle, it's hard to stop at the right spot or do one step increments (like frequency). I'll just start a new topic on this.
  5. Ack, thanks. I'll post this Stream Deck plugin to User Contributions if it ends up working out (and I'll probably add actions for direct offset and controls as well). This will provide Stream Deck integration for FSUIPC (which Spad.Next is adding). Maybe it can be evolved by others to provide bi-directional updates (e.g. change the button image based on offset changes - I have no need for that but other probably do).
  6. Thanks, yeah connecting may be the issue... I'll have to test on my sim rig. I did think about this and may do it. The immediate issue I'm trying to solve right now is to get rid of vJoy. If I start sending offsets directly, I loose the "UI" in FSUIPC so I was planning to just start with buttons. I also use some custom Lua for very non-standard things (like fuel selector, and ignition/magnetos), so I prefer to keep "config" for functionality in one place. If this works out, I'll add a generic "offset" plugin action, where you can just set the offset, size and value. I think Spad.Next i
  7. Is the "Button Assignment" window supposed to react to these externally triggered offset changes? I assume yes, but want to make sure. And does it matter whether FSUIPC is connected to MSFS or not in this case (I know for physical devices it works without MSFS connection)?
  8. Ok, so I have the plugin working, and FSUIPC connection succeeding (and failing when appropriate), but FSUIPC Button Assignment window doesn't seem to respond to button changes. 1. Are "Offset" instances registered globally by the client library during construction? How does Process() know to deal with them? 2. Is BitArray appropriate for offset 3340 (as I use it here)? I have a Process() set/clear bit Process() as implemented here, but FSUIPC does not show a button press (even when I hard code 0 for the bit). Logs show things as expected (and so far experimentation reveals only
  9. Thank you both. I'll see how this works out. Hopefully I can just get rid of vJoy.
  10. Brief questions... 1. I'm not sure if StreamDeck creates a separate instance for every panel or button (and how it actually instantiates the plugins). Is there are a large overhead for (potentially) creating lots of connections to FSUIPC? I assume Open() is at some global/singleton level per whatever process it's running in. So I can do IsOpen checks for each event, and just reconnect as needed. 2. Since I have to read 3340, is Process() synchronous? That is, can I do this in the StaremDeck events: Process() (to read), flip bits, Process() (to write)? While 29F0 seems useful, I
  11. Since they're not visible when FSUIPC starts up, will they be auto-assigned letters when they are first received?
  12. I think that will work. So these virtual buttons will be assignable in the Buttons tab (what device letter do they show)?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.