Continuous Antenna Elevation Up/Down via Callbacks?
-
Bummer,
I recently picked up a Cougar throttle, which is awesome outside of the fact that I lost the slider axis that I had on my X52 Pro throttle. Had to assign FOV zoom to an axis, so the antenna tilt had to get moved to a shifter layer on a hat.
Holding the hat buttons does nothing after the single step, so I’d have to set it up in joystick gremlin to repeat keyboard presses. It would be nice if we had a smooth keyboard slew, similar to the way the cursor slew works.
Set the hat button to enact a repeating macro in SST. Then it’ll keep tapping down for you as long as it’s held.
-
Using a Warthog stick.
I get that the antenna elevation should be controlled by an axis, but so should FOV. I use it all the time. By far the most used control, outside of the joystick and throttle axes. Lots of visual spotting that needs to be done.
I’ll experiment and see what I can come up with.
-
Using a Warthog stick.
I get that the antenna elevation should be controlled by an axis, but so should FOV. I use it all the time. By far the most used control, outside of the joystick and throttle axes. Lots of visual spotting that needs to be done.
I’ll experiment and see what I can come up with.
There is a callback “look closer”, IIRC mapped to L by default. That toggles between the standard FOV and a zoomed view, around 10°. That does the job perfectly for me to spot things.
-
I have FOV set to an axis controlled by the Warthog MIC hat forward/aft buttons. I wouldn’t do it any other way.
-
Smart Scaling is already magnifying far distant planes x3 times. In Falcon there is no need to use zoom axis in case of spotting or looking closer. I don’t assign FOV axis for BMS.
Using Zoom Axis may increase visual information too much that is why I think @Sanpats’ new formula for Smart Scaling has to be applied in the future. https://www.benchmarksims.org/forum/showthread.php?28660-About-SmartScaling-and-future-high-res-monitors&p=463870&viewfull=1#post463870
So I prefer applying Antenna axis instead of FOV. However, I also wonder why Antenna elevation callback doesn’t work continuously while Range Knob callback does. This has been let so many users to go for TARGET scripting or so on and that made setup more complexed than just mapping DX directly.
-
While you may not think an FOV axis isn’t necessary, I obviously disagree. I’ve used it since day 1, and it helps immensely, with everything from enhanced SA in dogfights (max FOV is set to 100deg) to reading cockpit displays to getting VID on targets on the MFDs to getting VID on targets on the ground. It’s always useful. Always. So much so that I might consider adding some sort of slider axis to the cougar if I can figure out where to put it. It’s seriously that useful.
If the range knob works continuously as a callback, I may consider swapping that out instead. But I do agree with the point, why isn’t the antenna elevation continuously variable if the other axes like MAN RNG and throttle are?
-
While you may not think an FOV axis isn’t necessary, I obviously disagree. I’ve used it since day 1, and it helps immensely, with everything from enhanced SA in dogfights (max FOV is set to 100deg) to reading cockpit displays to getting VID on targets on the MFDs to getting VID on targets on the ground. It’s always useful. Always. So much so that I might consider adding some sort of slider axis to the cougar if I can figure out where to put it. It’s seriously that useful.
If the range knob works continuously as a callback, I may consider swapping that out instead. But I do agree with the point, why isn’t the antenna elevation continuously variable if the other axes like MAN RNG and throttle are?
Since day1 I am using mouse wheel for FOV (that I almost never change) and save an axis on my HOTAS for real fuction.
-
This post is deleted! -
Nobody should be ashamed to try to help a fellow user
Two question Mortesil if i may?
-1. what’s your screen resolution?
-2. should we stop answering the OP question because his realism setup doesn’t fit ours? yours?what you suggest indeed is what’s been told the OP in the first answer he got, he specifically said he needed them, so we keep helping them offering possible situations, what should we do rather? Ignore him?
each is free to use the sim as he sees fit, including the ones here so called realism freaks and who may need FOV for whatever Reason including maybe overcoming specific computer screen resolution issue or more simply, doing pictures for manuals or whatever -
Thank you Red Dog, for your kinder reply than the one I invisioned.
Smart scaling only gets you so far, particularly with limited monitor resolution and peripheral vision. Eyesight doesn’t have the same resolution limit, and anybody who flies can tell you how much easier it is to spot things on the ground or in the air IRL than it is in BMS. BMS handles it incredibly well, but there are still limits, particularly for people without monster screens running 1440p+. At any given FOV, you’re compromising something, be it display clarity or peripheral vision (and situational awareness), which aren’t compromises you have to make IRL, at least not to the same extent.
I use FOV zoom as an axis because it allows easier reading of things inside the pit, easier lineup of things in the HUD, better spotting of things on the ground (seriously, play some ITO80s and you’ll appreciate the necessity of visual spotting), and an all around better experience. Before I had functional MFD screens, I was using it to zoom in on the MFDs to ID ground targets.
It’s a feature that’s available, nobody forces anybody to use it, so either use it or don’t, but don’t gripe about other people using it or try to make other people ashamed for not sharing your specific values of the game mechanics, because it really doesn’t affect you, does it?
I do appreciate all of the other helpful input. I’m still set on using an axis for FOV zoom, although I’d happily take a mouse wheel if I had one on my cougar
-
This post is deleted! -
Honestly most callbacks for moving axis do not work as a continuous move anyway. HUD or HMS brightness, antenna elev, trim, sound levels, FOV : all of them works step by step.
The range knob is the exception - and that’s a good thing, considering its use in the TGP digital zoom.
For antenna elev, I dont know if you use TARGET with your Warthog, but if you do, you can use REXEC to do it :
MapKey(&Throttle, [color]MSU[/color], REXEC(0,[color]100[/color], "ActKey(KEYON+PULSE+[color]'a'[/color]);"); ```That's assuming you want to put an antenna elevation control in the throttle "Mike Switch" Up ( MSU ), and that one of the callback for antenna elevation is "a" in the keyfile. It will generate a keystroke every 100 ms.
-
I’m a bit surprised that axis adjustment callbacks aren’t self repeating. I actually suspect that they would. I guess callbacks aren’t durations but events so Falcon wouldn’t know when the callback ended.
-
TARGET becomes unstable when using it with TeamSpeak joystick hotkeys.
It doesn’t hide physical joystick from the PC.@starfuryth
How about assigning FOV to physical range knob, then assign in-game range knob to other buttons? -
That’s been a thought as well. I use the range knob less and could probably do without. Going to give that a shot the next time I go up.
Thanks:)
PS: I don’t use TARGET for anything. Joystick Gremlin or bust.