Gents - noticed in the TO 1F-16CMAM-34-1-1 BMS.pdf#page=90/91, it states in 3 separate paragraphs the term SOI (Selected Option Item):
“The Bump Range feature is available but can only be used when the HSD cursors
are displayed, which happens when the HSD is the selected SOI (Selected Option Item).”

Is this acronym contradicting SOI which is defined in TO 1F-16CMAM-34-1-1 BMS.pdf#page=665:
“SOI = Sensor Of Interest”?

I fully realize it’s merely semantics, but could be confusing to ‘future new flyers’.

Dl’ed the smaller … no-joy. Went for the larger and extracted … works just fine!

Thx for the quick turn! Much appreciated…

@foxster and @oakdesign thanks to you both for an accurate, straight replies. Also, @foxster most certainly appreciate your tutorials and use of ‘FoxVox’ especially the content using Falcon BMS - exactly what I was looking for!

Thanks gents!

@oakdesign and @Micro_440th. Suggestion to move to documentation-bug-reports has been actioned.

Cheers!

@airtex2019 , with HAGS turned ‘Off’ and setting priority to ‘Above Normal’, the radar sweep is better (acceptable, not perfect) and the TGP cursor more responsive.

Thanks for the pointers!

SOLUTION: Thanks @oakdesign and @ka8yiu I incorporated the +5/-5 keybindings on the rotary dial and changed my ‘set g_nKnobAccelerationDelta 400’ you are both absolutely correct. If I rotate any of the dials click by click I get the +1/-1 movements. If I rotate the dial faster with intent, the movements (both CRS/HDG) move much more freely by +5/-5 - this is exactly what I envisioned. Thanks for the direction.

Cheers!

TO 1F-16CMAM-34-1-1 BMS
Page: 90 (two instances of misused acronym)
Page: 91 (one instance of misused acronym)

Original sentence: “The Bump Range feature is available but can only be used when the HSD cursors are displayed, which happens when the HSD is the selected SOI (Selected Option Item).”

Correct sentence: “The Bump Range feature is available but can only be used when the HSD cursores are displayed, which happens when the HSD is the selected SOI (Sensor Of Interest)”.

@Arty, this is exactly what I was searching for and it worked. Mind you, since this is RTTClient64.exe, even though I followed your directions using the numeric values (doesn’t matter if it’s hex or decimal value since they should translate to the same binary value), the value needed for “5: Above normal priority” needed to be changed to “6”. Confirmed in the Set Priority in Task Mgr/Processes which indicated “Above normal”.

This link (https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-set-priority-processes-using/df82bd40-ce52-4b84-af34-4d93da17d079) documents the values used in Win 11:

Thanks a bunch since it did eliminate the perpetual changing of the “Set Priority” in Task Mgr.

@oakdesign, if able I would consider this ‘bad-boy’ as “Solved” since the “Radar Cursors” now function better than before!

Vielen Dank!

@skippermike fair enough. The takeaway is ‘whatever works for one, may not work for everyone’. As long as it works. Thanks for taking the time to respond

Cheers

@oakdesign if you need help with the BMS plug-in, I can code in Java, Python and C++. If not let me know when the plug-in is included in joystick_diagrams.exe!

Vielen dank!

@oakdesign BTW - how did you get joystick_diagrams to capture BMS Auto-Key file when the application doesn’t recognize Falcon BMS to date? It recognizes DCS, Joystick Gremlin and Star Citizen but no method yet to ‘add’ Falcon BMS.

@skippermike fair enough. The takeaway is ‘whatever works for one, may not work for everyone’. As long as it works. Thanks for taking the time to respond

Cheers

@skippermike if you use the 'set g_nKnobAccelerationDelta (of note this needs to be placed in the BMS User.cfg file to prevent overwriting during supplemental updates of Falcon BMS) to a value greater than 300 (I am assuming the value is rated in millisecs), then you don’t need to use the button press as a shifted layer. The button will simply move by 1 value / per click for final fine tuning of the parameter you’re looking for.

@oakdesign I really appreciate the schematic of your layout. Can I assume the ‘blue’ highlighted colour indicates ‘Shifted’ layer? Your layout makes sense including some implementations I overlooked (CAT III / CAT I, PARK BRAKE ON, PARK BRAKE ANTI, PARK BRAKE OFF) - very nice indeed and easily understood! Many thanks!

SOLUTION: Thanks @oakdesign and @ka8yiu I incorporated the +5/-5 keybindings on the rotary dial and changed my ‘set g_nKnobAccelerationDelta 400’ you are both absolutely correct. If I rotate any of the dials click by click I get the +1/-1 movements. If I rotate the dial faster with intent, the movements (both CRS/HDG) move much more freely by +5/-5 - this is exactly what I envisioned. Thanks for the direction.

Cheers!

Indeed @Veg you are correct. Perhaps I will simply need to face the truth and get on with it!

Thanks to you both. I have assigned thru the “KEYMAPPING” as keys, however the choices were by “1” or by “5” increments/decrements. Logically, I selected the “1” but rotating the analog rotary wheels (physical clicks per each subtle rotation of the knob) is kinda exhausting until I reach the desired CRS/HDG. Is this the best I can achieve?

I tried to rotate the physical knobs quickly to capture the speed using:

set g_nKnobAccelerationDelta 300

which was appended to my Falcon BMS User.cfg file which did work using the keyboard. However, now it seems to be ignored no matter the speed the dial is rotated.

Hiya Fellow BMS’ers - I just picked up the Winwing Orion2 StrikeAce E/EX Throttle and am attempting to configure the HDG/CRS Rotary push-button knobs thru the Alt Launcher, specifically under the “AXISASSIGN” tab followed up with the “ICP, RADIOS, AUDIO & ALTIMETER” tab. Regrettably, the launcher doesn’t recognize either of them.

How would I go about getting the Alt Launcher to recognize these amazing rotaries?

Any and all options are open to have this feature available.

Cheers all!!

@foxster and @oakdesign thanks to you both for an accurate, straight replies. Also, @foxster most certainly appreciate your tutorials and use of ‘FoxVox’ especially the content using Falcon BMS - exactly what I was looking for!

Thanks gents!

Hiya fellow BMS’ers - I’ve recently purchased that awesome Orion Joystick Base 2 with the F-16 EX Grip and noted in the software itself, the option to create the “4 x 32 Button mode”. I strictly use the software for testing the stick/buttons - that’s all.

The question is: Do I need to enable to creation of the “4 x 32 Button mode” if on a Windows 11 Pro OS, on a 64-bit system and running Falcon BMS 4.37.6.0?

TIA for any feedback!