Machalot

And the radio group number indicators don't illuminate with the panel lighting. They still have some art issues to work out in that part of the cockpit.

Open beta 2.7. Just noticed it today, but it might be older.

Fixed in Open Beta 2.7.

This may not be new in 2.7, but I just noticed it for the first time. When the aircraft is pitched above or below a certain angle, the HUD goes blank. However, it doesn't resume displaying when the pitch angle is back within the limits. It seems to stay blank until the pitch angle gets close to zero. Track attached. AJS37_HUD_masked_by_pitch_angle.trk

In Open Beta 2.7, all the exterior lights seem to turn on properly. But if the LANTERN lights and LED-LJUS are both on, switching the LANTERN switch to the center position (off) does not turn off the LANTERN lights. They stay on until the LED-LJUS switch is also turned off. Track attached. AJS37_light_switches_bug.trk

I love the new afterburner effect, from the stage 1 warm glow up to stage 3 Godzilla's breath. DCS just crashed the second time I loaded a Create Fast Mission using the Viggen. It worked ok the first time. We'll see if this was just a fluke, hopefully.

Try setting the night filter and brightness when using PPI mode (A1), then switch to the B-scope (A2). It's much brighter and less red-filtered. Track is attached (forgive the fumbling around, I always play VR and didn't know the view keys without VR). AJS37_CI_filter_A1_vs_A2.trk Here's the filter and brightness tuned for A1 mode, then immediately switched to A2 mode. Note the darker red in A1 mode. And when the filter is tuned to a reasonable level for A2 mode, and you switch back to A1, it's now too red and dark.

Can't run the track at the moment, but just a quick check. Are you turning on the MIDS LVT knob (correct) or trying to use the D/L switch (non functional)?

Maybe there's something in the section about Terrain Avoidance mode?

It's the same symbol as on the HUD. I have a hard time believing it's not intended to move. A static 100m line is not a 100m line.

Sorry for the necro, but I was just researching this again and remembered reading this thread a while back. The manual on p. 117 says it's 0 deg relative to the horizon:

Or if the pilots do have control, it's something they plan and coordinate well in advance.

I'm referring to these symbols on the CI display. This figure is from page 109 of the Viggen manual. As far as I can tell, the 100 m line doesn't change length at all except when the Reference button is depressed.

By the way, I think the NAV SYST indication you got was from this:

So basically this note in the manual (p. 251) regarding "changing the take-ff airfield" has no effect? And this one on p. 263?

I really appreciate the effort you have put into this answer. However, I'm viewing it on a smart phone, so I don't know what I should be observing in the video. Can you explain?

In the specific example of 31L and 31R, I'm referring to Al Dhafra, which is surrounded by pretty flat terrain. Do you know of some DCS magic going on here?

Some of the navigation functions in the Viggen are based on the lat/lon of the selected runway. For example, when the aircraft lifts off, it initializes the navigation position to the known lat/lon of the runway you took off from based on the heading. You can check the runway heading used by the nav computer using BANA/GRANS mode. But how do you know if it's using 31L or 31R to initialize the position?

I use DYK/ANF the most, and I haven't seen that behavior of the steering cue. I think mine usually goes up. I wonder if this is pitch angle and speed dependent? I'll take a look later tonight. Edit: My memory was faulty. I do see the steering director move down instead of up.

New tech is coming to DCS F/A-18C or the 2022 real life version of the Super Bug?

Oh, if I could just take your idea and tweak it a little, maybe after you have just struggled through several minutes of frustrating overcorrection and maybe an unannounced turn by the tanker and you finally got the jet stabilized and on speed and then just the moment before you're about to connect, "Return precontact" and he retracts the boom!

Here's what I see:

Hm, for me it's not Comic Sans, it's a very stylized cursive. Maybe a smart phone font issue?

You asked a good question, but I would just like to give some constructive feedback -- that font is hard to read, especially in red.

What's bugged about NAV mode?