SnorreSelmer

I have the same issue. Windows 11 Pro.

I was asked to post the server specs for the 132nd Server here: CPU: Intel i7 4790K RAM: 32GB Storage: All SATA SSDs (no NVMe) WAN: 500/500Mbit FTTH

The Viggen is mainly a ground-pounder, but can do A2A. Its main limitation in A2A is the high-AoA compressor stalling that can cause flameouts. It's a simple plane to fly, weapons are fairly easy to set up, but it's not a loiter-and-wait-for-a-call aircraft like the A-10 is. The Viggen is more of a pre-planned strike type aircraft. Sent from my SM-G950F using Tapatalk

My best tip for learning good takeoff habits: never use the parking brake once you start taxiing. Use the cyclic to accelerate and decelerate, trim once you're in position for takeoff. With the parking brake off you'll see what the helicopter us trying to do, instead of it taking you by surprise once it lifts and releases all that stored energy. Sent from my SM-G950F using Tapatalk

I think it's been broken since 2.5 released. It's also broken in Open Beta as of 2.5.2.18307. If you open a track, set the output to "Raw AVI" or "PNG+WAV" (haven't tested this with OGG) and start rendering, it will render ~3 minutes and then DCS just restarts. If the track is less than 3 minutes then it won't crash. In my experience, it usually happens at ~3m20s (1920x1080@30fps). Hopefully this can be fixed at some point. :)

I'll be one of the Soviet-fanboys to counter the NATO-fanboys, and say "We need more quality Red Air!” MiG-23/27 and Mi-26 are high on my list... Sent from my SM-G950F using Tapatalk

Maintain a 2-3m/s descent, watch out for the vibration (that's not VRS, it's just the transition from flight to hover) and start adding collective when it starts. Keep the descent above -3m/s when in the hover region. Also, don't yank on the collective, you'll only shoot upwards and possibly lower rotor RPM to the point where the generators disengage for a short while. Sent from my SM-G950F using Tapatalk

There is a mention in the 2.5.2 Beta patch notes about them fixing some drift issue in the Viggen. Maybe it's relevant to this? Sent from my SM-G950F using Tapatalk

Another possibility could be joystick calibration/deadzone issues. But then all aircraft would behave like this. Sent from my SM-G950F using Tapatalk

Any wind on the mission? (Stupid question, yes, but always good to ask.) Sent from my SM-G950F using Tapatalk

I can only think of reloading the cartridge or manually inputting the coordinates again. The first is a bad idea as it will screw up your position fix, the other probably isn't very easy unless the original coordinates are still on the kneeboard from mission load. Sent from my SM-G950F using Tapatalk

Copy that, thanks! Sent from my SM-G950F using Tapatalk

As STRIL 60 was a ground-based air intercept director system, it might have been useful for the AJ-37 until the JA-37 came along. Sent from my SM-G950F using Tapatalk

You will see the anticollision light reflected in both the Mi-8 and the Ka-50. It's a modeling issue, should be easily fixed. Sent from my SM-G950F using Tapatalk

With global illumination on, the cockpit can get a bit hard to read in places, but I don't really find it bothersome. Maybe I'm just so used to reading the instruments at a glance. The Ka-50 has a worse time there. The autopilot channels get *darker* then they light up! Go figure.. Sent from my SM-G950F using Tapatalk