Make "Look Closer" momentary instead of latching
-
It’s a toggled reduced FOV from Falcon 4.0 days (L on the keyboard if I remember right). You press it once to set a reduced (fixed) small FOV and again to return to the previous FOV.
I believe it may be possible to invoke the look closer callback twice, once on down press of DX button and once on DX button release. This would give taotoo the momentary functionality requested.
-
I believe it may be possible to invoke the look closer callback twice, once on down press of DX button and once on DX button release. This would give taotoo the momentary functionality requested.
That’s what I was thinking - any idea how I might go about it? Searching/docs haven’t yielded anything.
-
Ah, he is referring to the FOVToggle callback… unfortunately, there doesn’t seem to be any way to make it momentary without having to go into a software profile. The only “momentary” switch that comes to mind is the MPO switch but I think it is hard-coded to be momentary.
I actually use the FOVDecrease callback to get a nice “zoom in” feel. I’ve scripted it so that it’ll execute the callback 5x… so kinda like looking through binoculars.
-
Use the Force Luke……Use your stick software, that what its there for. I did.
-
unfortunately, there doesn’t seem to be any way to make it momentary without having to go into a software profile.
I thought that might be the case, but thought I’d ask anyway… there does seem to be some sort of press/release functionality, but it doesn’t look like it will do what I want (I tried two lines in the key file - one with a press, and another with a release).
-
Use the Force Luke……Use your stick software, that what its there for. I did.
Just trying to avoid the '90s-feeling CH software thing, and also hours scripting and tweaking when I could instead be playing the game… maybe I’ll do it anway
-
Ah, he is referring to the FOVToggle callback… unfortunately, there doesn’t seem to be any way to make it momentary without having to go into a software profile. The only “momentary” switch that comes to mind is the MPO switch but I think it is hard-coded to be momentary.
I actually use the FOVDecrease callback to get a nice “zoom in” feel. I’ve scripted it so that it’ll execute the callback 5x… so kinda like looking through binoculars.
There is a special release condition in the key file format which can trigger a different behavior on release compared to press. If it’s possible to double bind the same callback to both press and release contexts it should toggle on press and toggle on release effectively momentary. I’m rewritting my key file to make use of this to utilize less DX buttons (I was over 32 before) and simplify the arrangement. Here is an example:
SimRFNorm 81 -2 -2 0 0x0 -1
SimRFQuiet 81 -2 -2 0x42 0x0 -1The difference is the 0x42 instead of 0. Both are triggered by actions on button “81.” I have yet to fully test this.
-
There is a special release condition in the key file format which can trigger a different behavior on release compared to press. If it’s possible to double bind the same callback to both press and release contexts it should toggle on press and toggle on release effectively momentary. I’m rewritting my key file to make use of this to utilize less DX buttons (I was over 32 before) and simplify the arrangement. Here is an example:
SimRFNorm 81 -2 -2 0 0x0 -1
SimRFQuiet 81 -2 -2 0x42 0x0 -1The difference is the 0x42 instead of 0. Both are triggered by actions on button “81.” I have yet to fully test this.
I think that’s exactly what I tried, but will try again later today and report back. Thanks for the tip!
edit: I must have done it wrong before, because that works perfectly - thanks so much!
-
I tried using a button on my CH pro throttle, set it to press L and on release press L again. This works sometimes because if you notice, if you are not at your maximum set FOV when you hit L the first time, it will zoom out to that FOV. The next press it will perform the zoom, so you see how that can cause issues if you try to script it.
I tend not to be at my max FOV when operating things in the cockpit, so it didn’t really work out for me.
-
I tried using a button on my CH pro throttle, set it to press L and on release press L again. This works sometimes because if you notice, if you are not at your maximum set FOV when you hit L the first time, it will zoom out to that FOV. The next press it will perform the zoom, so you see how that can cause issues if you try to script it.
I tend not to be at my max FOV when operating things in the cockpit, so it didn’t really work out for me.
I see what you mean - I don’t actually use variable FoV, so haven’t run in to that issue. Got me thinking about trying it though…