Lost zoom on TGP
-
I used to press ctrl+F4 or F3 without any problems but somehow I lost this feature, is there any reason?
Also there an interesting feature on the coarse and heading mini dials. If mouse is placed on their right mouse wheel will be rotate them slowly, if placed on their left they will rotate fast.
-
Go to the SETUP screen in BMS. Choose CONTROLLERS. There should be a window on the right with all your key commands. What name is above that window? Is it your keyfile? Has it changed?
At that window you can push F3 or F4 and see what command is found. If it’s the proper command, there is some other issue.
Yes, one side of the heading knob changes in increments of 5* and the other in increments of 1* …. it’s in the manual … :wfish:
-
F3 was “radar gain decrease” and F4 was “radar gain increase”. That sounds like what it should be
-
F3 was “radar gain decrease” and F4 was “radar gain increase”. That sounds like what it should be
Yep, sorry. I meant to check the TGP function …. CTRL-F3 and CTRL-F4 ??? ( whatever they are for you; I don’t use the keyboard for those functions) … what does the SETUP screen say BMS recognizes for those?
-
I’ll give the answer as if you’re sitting in a real F-16 seat: The TGP “smooth zoom” is controlled by the range knob on the throttle, the same knob that controls the fine AG FCR gain. With that understood the next question is “since I’m not sitting in a real F-16 cockpit, what input controls the virtual range knob?” Glad you asked!
The callbacks are SimRangeKnobDown and SimRangeKnobUp. There’s also an axis assignment in setup. If that setting is not “Keyboard” then the callbacks will not function and you’ll have to use whatever axis is selected (or change it back to keyboard). It turns out in BMS.key at least these callbacks have default keybinds of Ctrl-F3 and Ctrl-F4. The steps to this discovery were:
1. Know the airplane. I would have to learn that it is the range knob that controls the TGP zoom.
2. Find the control. I would look in the BMS -1 to find what callback(s) are associated with that control.
3. Find the key. I look in BMS Keymap.pdf to find what keyboard key is bound to those callbacks. -
it seems that everything is setup right but somehow that functionality is lost. Perhaps one of the pc updates did something. The file I use is Dunc_DX and the ctrl-F3 is recognized as ‘hotas-range knob down’, the ctrl-F4 is recognized as ‘hotas-range knob up’.
-
- Check to see if any of your relevant keys on your keyboard might be sticking without you knowing it.
- Un-plug/wiggle/re-plug your keyboard cord.
-
Try using the actual keyboard first to verify the controls are working. It’s possible the profile is the issue. Also make sure The TGP is SOI as the range knob for that feature only works when that sensor is selected. You can test if the range knob works without a TGP by bringing up a mapping (GM or SEA) mode of the AG FCR and increasing the range knob to add and subtract gain from the AG FCR GM picture.
-
Try using the actual keyboard first to verify the controls are working. It’s possible the profile is the issue. Also make sure The TGP is SOI as the range knob for that feature only works when that sensor is selected. You can test if the range knob works without a TGP by bringing up a mapping (GM or SEA) mode of the AG FCR and increasing the range knob to add and subtract gain from the AG FCR GM picture.
do you mean Dunc_Dx by profile? the F3 and F4 keyboards are fine as they are. nothing is mechanically or electronically is wrong with them. In the game they don’t increase/decrease gain anymore for the TGP (with all the conditions met) although it did before. The range knob in GM or SEA mode don’t change a thing. I thought it was made to be this way since in the real F-16 pilots use the cursor only to gain range.
-
ok, I changed the profile and it worked this time. Changed it from Dunc_Dx to BMS.
-
<p>I encountered this problem recently and the cause was my axis mappings were reset and the radar range knob axis was bound to a nonexistent axis. I had to reset its binding to keyboard for my DX button bindings to work.</p>
