Solved Cannot change A-G GM FOV
-
Version
4.36.0 (x64)Build
26181Detailed Description
Quite often I cannot change FOV in GM A-G mode and lock ground target with TMS UP. This is not 100% reproducible but happens often around steps 6-9 described below. It does not depend on whether there are clouds in line of sight. Does EXP FOV have any gimbal or range restrictions? Or am I missing something?Cursor Up/Down/Left/Right are assigned to DX keys on joystick - I did it to remove any doubt about sticky SHIFT or axis drift.
Video:
Reproduction
- Load Training mission 10 - GP Bombs.
- ICP Next to change steerpoint to 6.
- Turn towards steerpoint 6. Aircraft is about 20 miles from steerpoint, height about 12000 feet above target, line of sight unobstructed (save for the clouds).
- Change master mode to A-G.
- Ensure CCRP submode is selected (I have set CCIP by default), so that A-G radar goes into GM mode.
- Click OSB 3 to change FOV from Norm to EXP. For a brief moment the radar scope changes its display but returns to Norm. Sometimes here FOV can be changed successfully. If it does, go to step 8.
- If FOV change didn’t succeed continue clicking OSB 3 enroute to steerpoint 6. Usually after a couple of attempts FOV change is successful.
- Go back to Norm FOV. Move radar cursor around and return to area of steerpoint 6.
- Try to change FOV now. Usually after moving radar cursor, FOV cannot be changed even though it could just couple moments ago.
Expected: I (think I) should be able to reliably change FOV in these conditions.
-
@Fox_15 Well, we’re all useing “pinky” on stick , which works as advertised, reliably , haven’t noticed ill operation.
Probably that’s why nobody haven’t even tried this.
Just stick to stick while this is repaired.
Good spot. -
@Fox_15 I’ve had this problem, since 4.35 at least.
Maybe I’m not as persistent as you – but when the bug repros for me, I’m not able to make it work by keep hitting pinky. I usually have to turn away from the target steerpoint and then back into it. (I’ve tried switching master mode, turning radar off and back on again, to no avail.)
But its only happened to my once I can remember in 4.36, and it did seem easier to unhork. Don’t remember what I did… I think I switched master mode to AA and back. So hopefully that’s the case…
-
@Fox_15 You could try flying level i.e. auto-pilot and at the steer point before adjusting A-G mode, you may have more success when your jet is level and the distance to steer point is within the range specified on the FCR. A couple things there I can see in the video. I have no problem setting mark points.
-
@airtex2019 said in Cannot change A-G GM FOV:
Don’t remember what I did… I think I switched master mode to AA and back. So hopefully that’s the case…
That is mother fix since begining of time… -if you notice anything strange with fcr , mode switch cures it
-
Thanks for hints. I too notice that when FOV is “locked” changing master mode to A-A and then back to A-G does not unlock it but making some turns and general flying around, as @airtex2019 suggested, does help. It seems that at the beginning of the mission if instead of turning 90 deg right at steerpoint 5 I make a 270 deg left turn the problem does not occur. Anyway, I will proceed to the next training missions and gather experience with it.
-
@Fox_15 I flew that TR mission at least 10 times over the past year, trying to nail down a repro steps. No joy. It would be awesome if you figure it out…
-
It has been reported in the BMS team.
-
-
@spooky Small nugget of additional info…
I saw the glitch happen, in a TE mission last night.
I was in AG mode (GM radar mode, with range set to MAN at 40 miles) and was attempting to use radar and TGP to scan around a SAM site for priority targets… I was still a bit too far away (over 20 nm range) so I was mostly staring at TGP waiting for something interesting to materialize on that view. I’d left the radar in DBS2 fov-zoom state…
I was cruising at FL20 toward the target, with AP on (hands off all controls). Just inside of 20nm range, right about the time when the radar might normally downshift range automatically from 40 to 20 (although, I had range set to MAN) the radar appeared to “kick out” of DBS2 mode and go back to normal fov scanning.
At that point, it refused to zoom in again… the MFD just flickered a little, when pressing the pinky-zoom button.
Switching master mode to AA and back, didn’t work. Turning radar to quiet/silent, didn’t work.
Pressing the OVRD button to turn radar off, then back on again, did seem to work. (Although sometimes this bug seems to fix itself, after a few seconds or minutes, so hard to say.)
The (maybe) interesting TL/DR here is that the glitch seemed to happen on its own – not in direct response to any input. And seemed to happen right around the time it would shift from 40 to 20 – but I had range set to MAN.
The bad news is that I tried to repro everything I did above … later in the same flight, and again repeating the same TE … and, no joy.
-
@airtex2019 Thanks for the inputs, i had the same weird stuff happening to me, at first is suspected something with my mapping on my HOTAS but eventually i figured out that it wasn’t that.