ridgeback68

Awesome. Thanks for the quick reply Taz. Really appreciate it.

Hey all, Unfortunately my Russian is limited to spaseeba and dosvedanya which doesn't help much with Russian voices in game. I'm flying mostly VR and miss most of the written text, so I have no idea what is being said. Is there any way to have all voices in English no matter what aircraft or airfield, etc.? A search only digs up old posts that refer to a 'sounds' folder that doesn't exist in the newer builds. TIA

Look on the bright side. As well as the Viggen being the most fun I've had with clothes on for a while, you'll get ED bonus points to use on another module. You don't get the points when you buy stuff on special.

Hey Hilmerby. Just going by the words you used, were you a Viggen pilot or ground crew?

Maybe they're "alternative facts" :music_whistling: Seems to work for Trump :D

Sorry if I'm being a nerd but it has to be the U22/A pod for ELINT as the basic U22 pod doesn't have the ELINT capability.

That's awesome grunf. Great explanation. :thumbup:

You have to press and keep holding the wheel brake while you engage the parking brake. I stumbled on this by accident but think I've read it since in the manual or somewhere else.

Can't say I've seen it happen. Might it be a stick/controller issue? I thought the altitude hold was broken as the plane kept losing altitude. Turns out my stick was slightly nose down in pitch even when centered. Put in a small dead zone around the pitch axis and it's now as steady as a rock. Worth a try if you haven't done it already.

Not your fault. Looks like the pop up waypoint is still a bit buggy after the latest update. Read from post #56 in this thread: https://forums.eagle.ru/showthread.php?t=180042&page=6

Well that's disappointing. I'll take learning the ECM stuff off my 'to do' list then! Thanks for letting me know.

Hey all, If I've read things right the U22/A pod has 15 possible active jamming combinations: Mode B + Bandwidth F or G or H or J or K Mode D + Bandwidth F or G or H or J or K Mode E + Bandwidth F or G or H or J or K There's no explanation I can find in the manual or elsewhere about how these work. What's the difference between the modes B, D and E? What bandwidth do I select? Is it the wavelength of the threat radar? Does the pod actively jam only on that bandwidth? If so how does it work against an SA-8 for example which uses both H and J band radars for tracking and fire control or against multiple different threats? Thanks in advance!

Problem solved. Definitely a hardware issue. The axis window showed a very slight nose down pitch when the stick was centered. Mapped a small deadzone in and now flying straight and level in Altitude Hold. Thanks to Corrigan and all for your time and help. Very much appreciated.

Yeah. I was going to re-calibrate but wasn't aware of the cntl + enter thing for control axis window. Will be the first thing I do when I get home. Thanks!

Many thanks to all who have replied. It doesn't seem to be a common issue so it must be something I'm doing wrong or something that's screwed up from my end. I've tried trimming her up before engaged the Altitude Hold and it doesn't seem to make a difference. I'll do some more testing tonight and will re-calibrate my controller in case it's doing something it shouldn't. That's what I thought. Manual says the autopilot should override the manual trim but I'm still getting this slow and gradual nose down effect every time I engage Alt Hold. Changes in the barometric pressure has no effect. Even I'm nose high when I engage Alt Hold she slowly and gracefully ends up in a nose down attitude until I fly into the dirt! Might also do a recording of it so you guys can actually see what's happening.

Having a small problem with the Altitude Hold auto pilot mode. Whenever I engage the Altitude Hold my altitude slowly decays. I can see the flight path vector slowly drop below the reference altitude poles and the altimeter unwinds. This is especially nasty at low level or if I'm heads down as I turn my jet into a glowing fireball. It's doesn't matter what altitude, it isn't airspeed related, and happens over flat or hilly terrain. I believe the autopilot uses barometric altitude and my QFE is correct as well. I've RTFM but am at a loss to figure out what I'm doing wrong. Any thoughts or help would be much appreciated. Thanks in advance.

That looks fantastic. This scheme really breaks up the Viggen's outline :thumbup:

FWIW - my thanks also For what it's worth I would also like to send a massive thank you to the LN team and all who made the DCS Viggen possible. I had owned the original DCS Black Shark but then life and kids got in the way and I dropped away from combat flight sims. Growing up as a kid in Australia somehow the Viggen (and the Draken) captured my imagination. I don't know why - I think it was unusual design and just how damn cool they looked. I remember my dad used to help me sketch/draw the Viggen and Draken with the blue & gold Swedish 'triple crown' national emblem. When I stumbled on some info that LN were doing the Viggen for DCS, I've jumped straight back into the flight sim world. Now got DCS, the Viggen, the A-10C and the Nevada range with more to come. So thanks guys for doing this aeroplane. It's brought back a lot of good memories and re-started my life in the combat flight sim world. Plus the Viggen is every bit as awesome as I thought it was when I was a kid. :thumbup:

Definitely longitude first in the Viggen. The name on switch - LO / LA - is the easiest way to remember it LO = LOngitude LA = LAtitude