Machalot

You said "or". It's trivial to target BK90s at two different waypoints. Stay in AKT POS/UT and hit the next waypoint button. But to do both, the step to change from long to wide mode requires TAKT/IN and typing. I would suggest pre-typing the 92x code but not pressing LS/SKU. Then release the first pair, hit LS/SKU, switch to AKT POS/UT, change waypoint, then release the second pair. Do you have a good keybind setup for the CK37 buttons that would let you do this quickly, or are you clicking with the mouse? I can provide my keybinds if you are interested. Another method could be to set up four waypoints and release the BK90s one by one in IMP mode. Keep the computer in AKT POS/UT, and between each release press the next waypoint button Addressing the "one shot and gone" nature of the Viggen, it would normally not fly solo. Multiple jets in the flight would attack these different targets without having to wrestle with the computer between shots.

This issue is known and tracked. I submitted report to HB for it a week or two ago.

I suppose I need to get in the game and test it, but based on the label that switch seems intended to control the range of the rocket sight (ARAK NORM/LA or NORM/LR in English), not the number of rockets fired.

Why would you want to use a smart weapon in dumb mode? The more waypoints the better I say!

Why does the label below the switch include the words ARAK and BOMB? I guess it's for ARAK sight range setting. But BOMB is under the SERIE/IMP side. (Just realized I have been typing EINKL when I should have typed IMP in all the previous posts.)

HB said they "swapped the devices" in the last patch. I know it affects SRS, which has the labels and keybinds mismatched now. I'm not sure why they did that, but I assume it will get fixed in the future.

What about with M/71 bombs and rockets? I haven't found an obvious difference between SERIE and EINKL.

Did you try looking at the other sub-pages by hitting RShift+Page Up?

This is reported and tracked. I'll put in a report for this one. I don't have the Nevada map. Could you provide a screenshot of the kneeboard?

We are trying to get HB to revert it so TV will complete the fix.

Yes. When you do that it uses different radar and target assumptions. It will hit the first thing it finds within a certain angular offset at any range along its path (maybe with a minimum range limit), rather than selecting a random target in the vicinity of Bx8.

@MYSE1234 I just noticed the quantity selector switch positions are labeled SNGL/PAIR in your English cockpit, while in the Swedish cockpit they are EINKL/SERIE. I assumed SERIE meant "launch them all in a series". Does it really mean pair?

Who is going around jettisoning all these canopies? We might have to start recovering and refurbishing them.

Sounds like you are getting the correct Bx8 circle and Bx7 cross. By default, Bx7 is off to the right so the missile doesn't fly directly toward the target at first and instead flies a "dogleg", I guess to conceal its intentions or something. I think this was a design choice by HB, but I'm not sure. If you don't like the dogleg, select Bx7 and do a new radar fix. Be aware that in the Dec 23, 2021 open beta, two bugs were introduced that affect fixes: the cursor starts on the right edge of the screen for a radar fix, and you have to hit T0 after TV to complete the fix. For the launch parameters, I would suggest selecting Bx7 as your destination (in ANF mode of course), not the M point. The range information on the HUD will be relative to the missile's full path through Bx7 to Bx8 (either that or it's for a direct path to Bx8 no matter which you have selected, I'm not 100% sure of this).

This is a known bug and is tracked.

Last night I took damage from AAA at low altitude, lost control and punched out. My jet survived impact with the ground, and sat there at full power slowly pushing its way through the grass. I walked up to it and stood on the wing. It ran for about 10 minutes before running out of fuel.

I made the same comment to the HB dev when they implemented this. Not sure if they plan to update it. This is known and tracked. I believe @MYSE1234 has a cockpit mod that fixes this.

Is this only in your Viggen, or all modules? Are you running with any third party mods?

I have deleted the original content of this post because it solved the wrong problem. The issue seems to be as you said, the flight is assigned to frequency 124.000 even though the briefing says 305. I have submitted a bug report to update the campaign radio channel assignments.

I had an issue on Hoggit's Syria at War server where the F10 map would take several seconds to load textures, and would just freeze while it was waiting. I didn't pinpoint a cause, and it was intermittent. I didn't notice if there was a correlation with marker placement.

Have you tried a DCS repair?

Go into the keybinds from the main menu instead of loading a mission. Set the seat height adjustment keybinds, and then load a mission and try to raise it.

Maybe we could request an F-14-like afterburner detent for the Viggen. That is, hold-to-push-through. Or do people prefer a toggle like the Viper and Hornet?

Why not try it and look at the lights? Near position is taxi light, middle is off, and far is taxi+landing light.

When using an F10 map cartridge, the LS and L1 waypoints are automatically set to your current airfield without any need to specify them on the F10 map. You can set them, but it's not necessary.