Jump to content
The simFlight Network Forums

CrazyKidJack

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by CrazyKidJack

  1. By the way... I am aware there is a beta version available that natively supports 128 buttons or something. I thought about trying to use that... but figured that if the only difference is the support of 128 buttons... using a beta could possibly make things more difficult for me to troubleshoot. I figured I'd get my stuff working in the stable version, and then try it out in the beta without the need for the HidDemo.lua script. With that said, if you think the beta will actually add functionality that will help me with my goal here, please let me know.
  2. Because I know that you always complain when people do not *thoroughly* read the documentation and forums... I spent *days* reading through every documentation file provided with the program, every FAQ forum topic, and tried probably a dozen different searches on the forum to look for my answer; I don't guarantee the answer is not somewhere... but I could not find it with diligent effort. I also know you prefer to help people that have a solid technical understanding, so I wanted to let you know I have over a decade in software development, a Bachelor's in Comp Sci, and am OSCP certified. My relevant hardware: Honeycomb Bravo Throttle Quadrant (henceforth called "HC") My relevant software: MSFS 2020v1.15.10.0 / FSUIPC7v7.0.9 / HidDemo.lua (set up properly to work and map controls to joystick 64 & 65) Notes: I am not using a debugger... just the in-built logging features of FSUIPC7 What I want to achieve overall: Using the "decr/incr" knob on the HC to interact with any knob in the simulator. My approach: Use key/button programming in FSUIPC to set "flags" telling FSUIPC which control the knob should alter in the sim What I have done so far: I have successfully used keyboard keys to set most flags. The "flags" I'm using are really the button flags for joystick 15. Joystick 15 has no actual device assigned to it. So far I have assigned flags for "selectors" 1, 2, 3, and 4, nav radio, comm radio, barometer, and transponder. What I'm trying to do now: The C172 that comes with MSFS 2020 has a G1000 autopilot (AP) system. When you set the "course" for the vor indicators on the G1000, you can't see what you are selected without also switching the active indicator (the one that is default is GPS indicator). What I want to do is have the "active indicator" switched to the one I am currently setting the course for. In other words, if the nav, and selector 2 flags are set, and I start turning the knob on the HC, I want it to switch the "active indicator" to VOR2 and start increasing the selected course. As an intermediate testing step, I tried to create a new flag (vor) such that when I set the vor flag and press the "1" or "2" key, it just switches the "active indicator" to vor 1 or 2 respectively. My first attempt was to use the same joystick 15 button flags as the others... but that posed a problem... To do this, I need to add a condition to a key bind but only offset conditions are available for [Keys]. According to the offsetStatus-v0.17.ods document 03C0 is where the button states are stored for joysticks 0-15. However, although it is not 100% clear from this post it seems that FSUIPC only updates those offsets if there is an actual device assigned to the joystick whose offset I'm trying to read. So even though I have the following line for my VOR flag: 113=86,8,1003,3849 ;set flag 9 (VOR) -{V: Press=: Joy 15 Button 9 }- the actual status that the button was pressed is not saved at offset x03FC+9bits. Therefore, my [Keys] condition: 14=D03FC&200 49,8,66502,1 ;vor flag&setting flag 1 -{1: Press=AP_NAV_SELECT_SET }- did not fire (x03FC&x200 == 0 --> FALSE) So I pivoted, the next thing I tried was to set the flag using a bit in one of the "free for general use" offsets... To be honest, I probably should have done this from the start. So I changed the line to the following because offsetStatus-v0.17.ods says A000 is free for general use and has a lot of bits available so I knew I wouldn't run out (not that I have *that many* flags to set): 113=86,8,x0700A000,x00000200 ; set flag 9 (VOR) -{V: Press=offset dword setbits, offset A000 }- I also changed my [Keys] condition to: 14=DA000&200 49,8,66502,1 ;vor flag&setting flag 1 -{1: Press=AP_NAV_SELECT_SET }- Unfortunately this didn't work either. So I switch to the other block of "free for general use" offsets. 113=86,8,x070066C0,x00000200 ; set flag 9 (VOR) -{V: Press=offset dword setbits, offset 66C0 }- and 14=D66C0 49,8,66502,1 ;vor flag&setting flag 1 -{1: Press=AP_NAV_SELECT_SET }- At least I am getting the offset logs to show changed in the offset 66C0 now... but that control doesn't seem to actually be changing anything in the simulator. Wrap-up/questions: #1 Is A000 working? If so, what did I do wrong? To be clear, when I was trying to use A000 nothing was showing up in the offset logs *and* the condition kept return a value of 0 leading to FALSE #2 Perhaps I am using the wrong control to set the "active indicator" on the G1000 so that I can see what I'm doing while selecting a course... and perhaps that is listed somewhere in the documentation... but from reading this forum I also know that there may or may be some issues when trying to interact with the G1000... so instead of going through the forums for another several days trying to decipher whether or not that is actually the case and figuring out which control I should be using if it isn't the case... can you please just tell me if there is a control or series of controls to do what I'm looking for? Thanks in advance, sorry for the long post. FSUIPC7.ini
×
×
  • 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.