reported FCR Display, changing Azimuth on EXPend screen issue

[skywalker22]

On Fire Control Radar (FCR) Display when trying to change the Azimuth setting (between A1,A3 and A6) on EXPEND screen (not on NORMAL) the number for the angle does not change accordingly, I mean it actually does change, its just not displayed on the screen. All other settings work on expend screen (Range, Bars).

 

f16_azymuth_issue.trkno

Edited July 6, 2021 by skywalker22
So far its not correct 100%

[skywalker22]

How come is this "correct as it is"? It surely is a bug. Maybe I wasn`t clear enough.

On both left and right MFD in FCR screen when pressing: 

 

button for changing the azimuth between 10, 30 and 60 degrees, the symbology on the MFD is like "A1", "A3" and "A6".

When in "Normal" mode, those symbology change accordingly (correctly).

When in "Expended" mode, symbology does not change on the MFD when pressing Left/Right MFD OSH 18 button.

It always shows the last displayed from Normal mode. 

 

Azimuth actually does change, it is just not displayed on the MFD when in Expended mode. 

So for example, in normal mode I set to A6, then go to extended mode, clicking ones on OSB 18 button - symbology should change to A3, but it does not. When going back to Normal mode, symbology changes instantly to A3. 

 

This surely is a bug, I hope it can be fixed, check it out:

 

[skywalker22]

Just checking if admins read my last post up here?

[BIGNEWY]

Hi do you have any real world reference this should be different?

[Frederf]

Docs just say the azimuth can be cycled in a rotary by pressing OSB 18 next to the "A" label and never has wording that suggests there is a context where such action is not possible. The only vaguely related comment is that in expand the azimuth vertical blue lines are blanked.

[skywalker22]

On 7/7/2021 at 2:16 PM, BIGNEWY said:

Hi do you have any real world reference this should be different?

No I don`t. But why the number (1,3 and 6) wouldn`t change when you change the azimuth? It does in NORMAL mode, why it wouldn`t in EXPENDED? Its no big deal, its just cosmetics, and you actually don`t know in which Azimuth angle you are in when changing it - when being in Expended mode.

 

[NineLine]

This makes sense to me (not that that always means anything) I will see what I can find on the subject, and if you guys find anything let me know. Thanks.

[NineLine]

So I looked into to this, and indeed, the lines are removed with EXP along with other things. 

[Frederf]

The issue at hand is that pressing OSB 18 in expand display will not result in the digit associated with the "A" label number being visually updated until the radar exists the expand display.

 

There's no particular reason to believe that changing the azimuth setting or its visual display of label (e.g. A6, A3, A1) is ever inhibited by being in the expand display mode.

[skywalker22]

4 hours ago, NineLine said:

So I looked into to this, and indeed, the lines are removed with EXP along with other things. 

What do you mean by "the lines are removed"? Which lines?

Anyway, so this is how it should suppose to be? Ok, but it makes no sence. Personally I wouldn`t like to fly the RL aircraft with a glitch like that.

Edited July 9, 2021 by skywalker22

[Frederf]

The blue vertical reduced azimuth lines, right? But DCS already does this.

 

Right now in EXP OSB 18 changes the azimuth setting (inverted "T" motion shows this) but the label (e.g. A6 A3 A1) doesn't update to reflect the change until EXP is exited.

[NineLine]

12 hours ago, Frederf said:

The issue at hand is that pressing OSB 18 in expand display will not result in the digit associated with the "A" label number being visually updated until the radar exists the expand display.

 

There's no particular reason to believe that changing the azimuth setting or its visual display of label (e.g. A6, A3, A1) is ever inhibited by being in the expand display mode.

Ok, let me check. Maybe I misunderstood the report.

 

[NineLine]

Ok I have this reported now, I thought we were talking about the scan lines, so my bad. Thanks for the report.