@MarcAurel Thank You for this post. I am brand new to Falcon BMS and this will help a bunch!

@Micro_440th surely you don’t mean VR … is there a separate MP guide document? (there probably should be) edit: lol it is confusingly similar name as g_bVRNoPresent … here I am asking about the new MP server cfg added in 4.37.1 I’d expect to find these in sec 3.3.1 of the technical manual… although there are other things there like g_fAmbientMin which don’t seem to be purely MP specific.

@airtex2019 said in ILS at Pohang AB wrong runway: @Ironman53rd well at the time, this was my primary source of confusion also it was super low-viz and ATC was directing me to runway 28 … seemed legit [image: U51XE47.png] Good catch. Typo indeed. Fixed in U3 (both AIP + Kneeboards) As Ironman described, ILS 10 is valid for ILS.

These two blocks in Training.pdf contradict one another. Code bug or doc bug? I’m assuming doc-bug … if so, delete the phrase on pg. 182 that suggests setting the laser-start time of 40 seconds. (It appears N/I for laser mavs, and I believe that is by design, as explained below on pg. 183.) [image: ncuNvNv.png] [image: 5L13iMJ.png]

Lately I’ve noticed some odd behavior with TGP cursor… this repros with either analog thumbstick axes, or 8-way-hat button bindings. TR#12 HARM training – head for PPT stpt 57. As the port facility comes into view, around 30 miles or so, use TGP to scan down (southwest) from the stpt. Notice it seems to “hang” or jerk around, as it passes over the hilly terrain. If you have FCR/GM displayed on the other MFD, you can see the radar crosshairs / SPI oscillating. As a pure guess, I’d say it seems like the TGP crosshair is tracing up and the down the terrain slope? incl. back down the invisible back side of the hills. As you get closer (within ~20 miles) the effect seems to diminish or go away completely. I don’t know if this is a bubble issue… or just due to the angle looking down from 20k ft, 20 miles away. Strangely, if I do an area-track on stpt 57 and scan down from there, the effect also seems diminished. (but I’d almost expect area-track to have trouble scanning over mountain ridges, from 25 miles away…) [Edit: not a bubble issue, if I descend to 15k ft the effect is worse, and closer than 20 nm.]

Delete the BMS - Auto.key go in the axis in alternative launcher so it reinitiate the writting of the file… Make sure in BMS it is selected as well…

First image shows what I have programmed as Pinky switch. Second how it shows up in BMS UI page. The text copied are my relevant 4.37.2 auto.key entries. Note that my button numbers will not work with your setup as device order will have different order and I also have about 300 entries programmed. [image: iomRFjz.png] [image: QyVX9B2.png] #======== F16 MFD 2 ======== SimCBEOSB_1R 640 -1 -2 0 0x0 0 SimCBEOSB_2R 641 -1 -2 0 0x0 0 SimCBEOSB_3R 642 -1 -2 0 0x0 0 SimCBEOSB_4R 643 -1 -2 0 0x0 0 SimCBEOSB_5R 644 -1 -2 0 0x0 0 SimCBEOSB_6R 645 -1 -2 0 0x0 0 SimCBEOSB_7R 646 -1 -2 0 0x0 0 SimCBEOSB_8R 647 -1 -2 0 0x0 126 SimCBEOSB_9R 648 -1 -2 0 0x0 126 SimCBEOSB_10R 649 -1 -2 0 0x0 0 SimCBEOSB_11R 650 -1 -2 0 0x0 0 SimCBEOSB_12R 651 -1 -2 0 0x0 0 SimCBEOSB_13R 652 -1 -2 0 0x0 0 SimCBEOSB_14R 653 -1 -2 0 0x0 0 SimCBEOSB_15R 654 -1 -2 0 0x0 0 SimCBEOSB_16R 655 -1 -2 0 0x0 0 SimCBEOSB_17R 656 -1 -2 0 0x0 0 SimCBEOSB_18R 657 -1 -2 0 0x0 0 SimCBEOSB_19R 658 -1 -2 0 0x0 0 SimCBEOSB_20R 659 -1 -2 0 0x0 0 SimCBEOSB_BRTUP_R 664 -1 -2 0 0x0 0 SimCBEOSB_BRTDOWN_R 665 -1 -2 0 0x0 0 #======== F16 MFD 1 ======== SimCBEOSB_1L 768 -1 -2 0 0x0 0 SimCBEOSB_2L 769 -1 -2 0 0x0 0 SimCBEOSB_3L 770 -1 -2 0 0x0 0 SimCBEOSB_4L 771 -1 -2 0 0x0 0 SimCBEOSB_5L 772 -1 -2 0 0x0 0 SimCBEOSB_6L 773 -1 -2 0 0x0 0 SimCBEOSB_7L 774 -1 -2 0 0x0 0 SimCBEOSB_8L 775 -1 -2 0 0x0 0 SimCBEOSB_9L 776 -1 -2 0 0x0 0 SimCBEOSB_10L 777 -1 -2 0 0x0 0 SimCBEOSB_11L 778 -1 -2 0 0x0 0 SimCBEOSB_12L 779 -1 -2 0 0x0 0 SimCBEOSB_13L 780 -1 -2 0 0x0 0 SimCBEOSB_14L 781 -1 -2 0 0x0 0 SimCBEOSB_15L 782 -1 -2 0 0x0 0 SimCBEOSB_16L 783 -1 -2 0 0x0 0 SimCBEOSB_17L 784 -1 -2 0 0x0 0 SimCBEOSB_18L 785 -1 -2 0 0x0 0 SimCBEOSB_19L 786 -1 -2 0 0x0 0 SimCBEOSB_20L 787 -1 -2 0 0x0 0 SimSymWheelUp 788 -1 -2 0 0x0 0 SimSymWheelDn 789 -1 -2 0 0x0 0 SimHmsSymWheelUp 790 -1 -2 0 0x0 0 SimHmsSymWheelDn 791 -1 -2 0 0x0 0 SimCBEOSB_BRTUP_L 792 -1 -2 0 0x0 0 SimCBEOSB_BRTDOWN_L 793 -1 -2 0 0x0 0 SimRadarGainUp 794 -1 -2 0 0x0 0 SimRadarGainDown 795 -1 -2 0 0x0 0 #======== TUSBA TQS R2 ======== SimTransmitCom2 1025 -1 -2 0 0x0 0 PrettyScreenShot 2561 -1 -2 0 0x0 0 SimTransmitCom1 1026 -1 -2 0 0x0 0 OTWSelectWeaponMode 2562 -1 -2 0 0x0 0 SimCommsSwitchRight 1027 -1 -2 0 0x0 0 OTWStepNextAC 2563 -1 -2 0 0x0 0 SimCommsSwitchLeft 1028 -1 -2 0 0x0 0 OTWSelectIncomingMode 2564 -1 -2 0 0x0 0 SimSelectSRMOverride 1030 -1 -2 0 0x0 0 SimSelectMRMOverride 1031 -1 -2 0 0x0 0 AFBrakesOut 1033 -1 -2 0 0x0 0 AFBrakesIn 1034 -1 -2 0 0x0 0 SimToggleMissileCage 1035 -1 -2 0 0x0 0 SimSlapSwitch 2571 -1 -2 0 0x0 0 SimCursorEnable 1036 -1 -2 0 0x0 0 SimEmergencyJettison 2572 -1 -2 0 0x0 0 #======== Thrustmaster HOTAS Cougar ======== SimTriggerFirstDetent 1152 -1 -2 0 0x0 0 SimPickle 1153 -1 -2 0 0x0 0 AFResetTrim 2689 -1 -2 0 0x0 0 SimHotasPinkyShift 1154 -1 -2 0 0x0 0 SimHotasPinkyShift 2690 -1 -2 0 0x0 0 SimAPOverride 1155 -1 -2 0 0x0 0 SimEject 2691 -1 -2 0 0x0 0 SimMissileStep 1156 -1 -2 0 0x0 0 SimPilotToggle 2692 -1 -2 0 0x0 0 SimTriggerSecondDetent 1157 -1 -2 0 0x0 0 SimTMSUp 1158 -1 -2 0 0x0 0 OTWSelect3DCockpitMode 2694 -1 -2 0 0x0 0 SimTMSRight 1159 -1 -2 0 0x0 0 OTWSelectF3PadlockModeAA 2695 -1 -2 0 0x0 0 SimTMSDown 1160 -1 -2 0 0x0 0 OTWStepNextPadlock 2696 -1 -2 0 0x0 0 SimTMSLeft 1161 -1 -2 0 0x0 0 OTWSelectF3PadlockModeAG 2697 -1 -2 0 0x0 0 SimDMSUp 1162 -1 -2 0 0x0 0 FOVToggle 2698 -1 -2 0 0x0 0 SimDMSRight 1163 -1 -2 0 0x0 0 SimVisorToggle 2699 -1 -2 0 0x0 0 SimDMSDown 1164 -1 -2 0 0x0 0 ToggleNVGMode 2700 -1 -2 0 0x0 0 SimDMSLeft 1165 -1 -2 0 0x0 0 RecenterTrackIR 2701 -1 -2 0 0x0 0 SimCMSUp 1166 -1 -2 0 0x0 0 SimCMSRight 1167 -1 -2 0 0x0 0 SimCMSDown 1168 -1 -2 0 0x0 0 SimCMSLeft 1169 -1 -2 0 0x0 0 #======== TUSBA TQS R2 : POV #1 ======== SimDoNothing 1 -1 -3 0 0x0 0 SimDoNothing 3 -1 -3 0 0x0 0 SimDoNothing 1 -1 -3 1 0x0 0 SimDoNothing 3 -1 -3 1 0x0 0 SimDoNothing 1 -1 -3 2 0x0 0 SimDoNothing 3 -1 -3 2 0x0 0 SimDoNothing 1 -1 -3 3 0x0 0 SimDoNothing 3 -1 -3 3 0x0 0 SimDoNothing 1 -1 -3 4 0x0 0 SimDoNothing 3 -1 -3 4 0x0 0 SimDoNothing 1 -1 -3 5 0x0 0 SimDoNothing 3 -1 -3 5 0x0 0 SimDoNothing 1 -1 -3 6 0x0 0 SimDoNothing 3 -1 -3 6 0x0 0 SimDoNothing 1 -1 -3 7 0x0 0 SimDoNothing 3 -1 -3 7 0x0 0 #======== Thrustmaster HOTAS Cougar : POV #0 ======== AFElevatorTrimUp 0 -1 -3 0 0x0 0 OTWViewUpRight 2 -1 -3 0 0x0 0 SimDoNothing 0 -1 -3 1 0x0 0 OTWViewUpRight 2 -1 -3 1 0x0 0 AFAileronTrimRight 0 -1 -3 2 0x0 0 OTWViewRight 2 -1 -3 2 0x0 0 SimDoNothing 0 -1 -3 3 0x0 0 OTWViewDownRight 2 -1 -3 3 0x0 0 AFElevatorTrimDown 0 -1 -3 4 0x0 0 OTWViewDownLeft 2 -1 -3 4 0x0 0 SimDoNothing 0 -1 -3 5 0x0 0 OTWViewDownLeft 2 -1 -3 5 0x0 0 AFAileronTrimLeft 0 -1 -3 6 0x0 0 OTWViewLeft 2 -1 -3 6 0x0 0 SimDoNothing 0 -1 -3 7 0x0 0 OTWViewUpLeft 2 -1 -3 7 0x0 0

@Mav-jp - yeah, I saw that. but I also thought I saw some “from game” examples as well? If we should throw the TACView data out (which doesn’t bother me one way or another), then what are we actually talking about?

@Kavelenko said in Alt Launcher and DeviceSorting.txt question: No you read my post wrong, I choose to set my stick and throttle in the setup page initially purely out of habit. As I mentioned you could try to map them in the AL straight away but I dont, that’s not say it wouldn’t also work in the AL Thanks for clarifying – I understood you ok. I’m saying, I’m stepping through the AL code… it always writes its model of AxisMapping.dat and Joystick.cal, irrespective of whether any axes were already mapped within BMS. Presumably, the defaults it selects (at least for primary axes, not buttons) are all the same, so the question is moot.

@SemlerPDX @airtex2019 I dunno guys… back in the day, when I was playing SWKOTOR, I think it was, I remember hearing music and conversation distinctly behind me. I took of my earphones and there was silence, put my earphones back on and it was definitely behind me. The cantina environment was behind my character, or rather my character was facing one of the booths. As I turn the character around, the sound moved. Pretty cool! However, the game was obviously tracking where my character was facing, not where I was facing physically. Do these new headsets now track where the user is facing and adjust the sound accordingly? I wouldn’t be surprised if it did and HyperX’s are quite good headphones, so maybe a small accelerometer in the headset and some fancy software can do this? KOTOR was 2 decades ago, maybe more.

@airtex2019 Thanks for this reply, had me infuriated after reading that 4.36 now supported throttle axis inversion. First world problems and all, but it was enough to stop me firing up BMS because I’d often leave my CM2 throttle with the inverted Falcon 4 axis profile loaded, it being the only sim I needed to reverse my throttle axis for… caused so many ‘accidents’ I quit playing it. So, Virpil users need to invert the left throttle axis, then explicitly set the IDLE at ‘0%’ then the AB where required. Happy Days

For years I’ve just been using the ‘K’ key for wheel brakes… Recently I expanded my hotas setup, and assigned an analog axis to the wheel brakes. I notice that differential braking, when applying yaw-axis input, seems backward… is it? With keyboard/dx-button braking (the ‘SimWheelBrakes’ callback) it works as expected – twisting rudder axis to the right causes my plane to turn slightly right (same direction as tail-rudder control surface). But with the brakes assigned to an analog-axis, it seems reversed – twisting right causes my plane to turn slightly left (opp. of tail rudder). Repro… Toe-brake axis: assigned to an analog axis Right toe-brake: unassigned (“keyboard” … even tho there is no keybd callback for right toe-brake afaik) On the taxiway… with NWS off: Taxi forward about 20 mph Apply right-rudder Apply brakes Expect: plane slows and drags to the right Observe: plane slows and drags to the left I tested both 4.36 and 4.35, they seem to behave the same in this regard, so it’s not a recent change. Maybe I’m doing something wrong or stupid. So far it’s only really noticeable upon landing … eg. decelerating, after nose down, applying a bit of rudder against the crosswind to keep straight. As airspeed decreases, the rudder has less effect, and the plane begins to turn the wrong way but once NWS is engaged the backward (?) diff braking isn’t so noticeable. Maybe trying to do tight pivot-turns on a carrier deck, would be problematic…

Note – as of BMS 4.36, this tool may now be redundant. I notice the new [shift+3] “SA Bar” overlay window shows the throttle position (and afterburner detent), on the indicator bar (mis-)labelled “RPM”. For actual engine RPM, you can add it to the HUD with the following cfg: set g_bNoRPMOnHud 0 Also new to 4.36, you can have an audible click when passing through the AB detent: set g_bAfterburnerDetentClick 1

Have fun with your new toy then All the best, Uwe

(cross-post of https://www.benchmarksims.org/forum/showthread.php?41786-A-mouse-as-throttle-(HOJAM)-experiment-for-Falcon-BMS&p=571903&viewfull=1#post571903 ) I recently added a small bonus-feature to my HOJAM prototype, to allow remapping mouse buttons 4-5 to arbitrary keyboard scancodes. This doesn’t really have anything to do with the original purpose of manipulating throttle… so I thought it might be of wider interest – cross-posting it here in case anyone is searching for a way do this. To use the fourth/fifth mouse button remapping, without the mousewheel-dragging, simply delete or comment-out all but the bottom 2 elements in the .config file: <add key="ScancodeForMouseXButton1" value="0xC7"><add key="ScancodeForMouseXButton2" value="0xCF"></add></add> Some ideas: PTT for UHF/VHS comms (this is the default) Look-ahead / Check-six Look-closer / Reset-FOV Speedbrake in/out Chaff/Flare programs (eg. slap switch / pgm #6) FCR antenna elevation up/down TGP zoom in/out (any other 2 functions which couldn’t find a place on your throttle or stick) Currently it only supports unshifted key presses (no ctrl/alt/shift modifiers) so you may have to alter your keyfile a bit to what you want. https://github.com/arithex/DragWheel/releases/tag/v1.1.2021.418

thanks:p