Leadnap

It isn't a bug - it is an operational issue: the Viggen was never exported, so the CK37 was never given changed programming that would allow for navigational parameters outside the Nordic area. The Prime Meridian runs through the Normandy map and the "01" can be 1 West or 1 East but the Viggen only ever was intended for Eastern Hemisphere operations. Navigational issues on Normandy and NTTR are known to HB but a work around hasn't yet been introduced. Essentially it would require creating a fictional operation of the CK37 because there is no way to input West or East (+ or -) in.

If you're willing to deal with a few backwards things, I found the Viggen to be very user friendly - while most would argue it lacks the refinement of say the A10 with the bells and whistles; the Viggen was built around being user friendly and ease of use. Where others argue the HUD is too simplified - the HUD doesn't flood you with information you don't understand. It has a very advanced avionics suite once you learn how to enter data and read data and features guided weapons that are easy to use. Best for learning pilots perhaps is the fact you have auto-pilot functions that you'll use the entire flight (in some cases) to stabilize the aircraft and even assist with landing - leaving you to figure out other flight basics like navigation. I learned on the Su27T then moved to the Viggen myself. I like the direct input and no MFDs to try and remember how to get to things. There are drawbacks of course - like no MFDs! It is also EA so there are bugs to work around (nothing major at this point). You also get accustomed to strange flight characteristics some times - I decided maybe to work on aerobatic maneuver practice (because in a Viggen you will eventually want strong skills in that area to fly fast, low and in tight spots) and took the Albatross out only to find it struggled through maneuvers I do with ease in the Viggen. Just my 2 cents, especially because you already own it. I started from having zero flight experience (was a ground pounder) and thanks to awesome sales have a good stable of aircraft to learn to fly - but decided to zero in on the Viggen to learn and then migrate. GLHF (that's the most important part)

I didn't high jack the thread - it was in OP from the get go as #4, and in general the whole discussion was of controls that don't work for the EP13. SGT Coyle's other post is about the controls being backwards which is NOT the issue I am reporting at all: the issue I have is the controls don't function at all. Given that other people have been able to get them to work (though backwards from documentation) and there are multiple bindings to those controls; the last question I had asked on the topic was what exactly had people bound for A0/1/2 so I could see why it wasn't working on my pc. My A0/1/2 do function the radar - so the keybindings work, but they don't change the EP13 for me at all. I stay in black on white no matter what. Now I am doing a clean install today so hopefully something changes in that regard but the HOTAS and Keyboard bindings I have for the modes don't change the mode which is both the original issue in this thread and an ongoing issue I have. Thank you.

I meant no disrespect - rather I'm envious of your opportunity to drop the real ones. The track simply only showed you coming down, and, unknowing of your background (and the propensity for people to try and deploy them in a DYK style) it seemed likely you were releasing them in a dive not a climb. Every example I have seen of a DCS release of them puts them in a vertical line rather than a horizontal string - which I thought was weird, but I've never dealt with aerial deployed flares IRL, just the kind deployed from cannon artillery or by hand. Thanks for sharing your wisdom with us.

5 & 6 I reported a while back, 7 - the RAT is definitely modeled, they've been working on making it not appear in the cowling (big thread in here on that) 8 - are you saying you cant adjust pitch at all? I can't - but others say they can which left me thinking I was just doing it wrong, but I have the same issue with the EP13 where my controls don't change the function but others report it works for them. 9) (adding again) I mentioned previously the Anti-Collision Lights come on when the player aircraft has NAV lights on - but AI aircraft don't have this issue. Anti-Collision light switch doesn't effect this.

Right - that contributed little to the discussion - as we already know it's backwards. The problem I am having is that A0, A1, A2 key bindings don't change the EP13 site, but they DO change the radar. I would be fine if they were backwards - but I am perpetually in black on white.

I would kill for a reload feature to work - Windows thinks the viewer is the most used application by me based on the number of times I open it vs other applications.

I totally agree, my only concern was that I had published a tutorial on it - which said to release ON the 4G pull up. The learning part is the part I love so much, it is what makes DCS what it is. I have no idea where to even begin thinking about what the HB and other developers have done to make this a reality.

Same here - was doing some flying earlier today and the system didn't even seem to notice the change between 15 and 120. Bravo!

"pull up at 4Gs" - they release on the throw principle - so if you are diving at 4Gs they will release but you are throwing them at the ground, vs throwing them up and out into the sky. At least I am concluding you dove based on the image here - if however the image just shows your diving after your pull up release, I would think you pulled up too soon. Do you have the track view from further back with the whole release?

Yes - when I've done all my testing for it the flash runs for 4 seconds, the long line on dist indicator for 1 second for a total of 5. As previously mentioned - there are certainly other (more clear/logical) ways to utilize HUD iconography to tell the pilot when to pull up complete with warning (hell there are for other weapons on the Viggen!) but this was produced by Saab engineers, so strange ingenuity is the name of the game. If you watch closely the 1 second indicator (long even line through whole distance indicator) drops and then the distance indicator works as it does on anything else as far as envelope dimension - with the distance line between the limits directly inside them and shrinking as you go. I suppose as the topic goes on and I continue to think about it - the best rationale for pressing the trigger at the 4 Second mark (5 seconds out) is that if suddenly enemy ground fire directed you to climb immediately the release parameters would be met and you would illuminate roughly near the target area - which follow on strike units could exploit.

In this you are absolutely correct, because as the manual states the munitions will release when the parameters are met - so it's basically a "any time now" button. The part that doesn't make sense is WHY you would trigger 5 seconds from the 4g pull if the 4g pull has to release them

Well I went ahead and did a lot of testing - and releasing the trigger at the 4 sec mark made no discernable difference, except 50% of the time even during the pull up there would be no release. For radar release the line flashes at 2 not 4 seconds so we're going to need someone who either speaks Swedish and can read the actual manuals, a dev, or a former SAF pilot to tell us what the difference would be because as far as the sim goes I can't differentiate between doing it wrong and waiting to pull the trigger until pop-up and pulling it a whopping 5 seconds before hand. I also just doing simple math in my head think an early release would be counter productive - they fall at 7.5m/s so 5 seconds early from the expected 150m AGL means a low opening - while if released in the 4g climb at M0.9 you're bringing them higher?

I didn't notice that until nhow… +1

:huh::book::doh::joystick::doh: Guess who is going to be redoing a tutorial.... this guy. I must have read that stupid section like 10 times and it just seemed to contradict a lot of other stuff. Excellent observation. Sorry to all who are following the tutorial (which still releases them - just not as effectively I suppose). That is strange though because behind the scenes I probably spend about a day reading and researching, another day flying around testing everything - then another actually flying it for the film - then I make the slides, script and record. Edit. Release. <- so in all of that process I was getting good effect with them not pulling at 4sec. Thanks for the observation!

Oh Saab....

Ahhh … yea I stick to military power, fly under 100m, and burn on ingress and egress.

Creating this thread to conversate with Sparhopper on the specs for a budget DCS build. Will post build specs here once I get them completed. For Sparhopper: What kind of money are you looking to budget on this?

A0: White on Black A1: White on Black A2: Black on White The radar mode selector (A0, A1, and A2) will select different contrast modes. (P319 of Manual)

How are you changing the A0/1/2? When I change them using the binds for the radar A0/1/2 they don't change the EP13. Is there a separate key bind specifically for the EP13 A0/1/2? That's the only issue I have with it, EP13 works (black on white) and I can deploy the RB75 with no issues (other than I am REALLY bad at aiming the aircraft AND the EP13).

I'll download the video later (at work, can't see vid now) to look at your release, as mentioned above - a lot of people confuse the selector switch or the release indications in the HUD. Since making the tutorial I consistently release them with no issue.

This is what you're doing wrong! The blinking line is a 4 second warning, not a release indication. This link will play the video from the part where I explain HUD indicators (specifically the blinking line) though I later at the end correct something from the next slide. The result is you are probably still holding on when the actual firing point has arrived, but the parameters are off.

Am I correct regarding the need to include the canopy ejection in the keyboard "full eject" bind which ignores the state of the canopy? You guys know about it, which is all I cared about. As previously mentioned, its very minor, especially since if you're seeing it everything else went backwards already.

You gave me hope! :helpsmilie: Thanks!

I am still impressed by the fact you are airborne long enough for it to be a problem! I only say that because in general I don't run into fuel constraints in the Viggen like I do other aircraft, though I've only made one mission where if you don't fly economically a glide will definitely be the landing used... I average about 35-45 minutes in the air per "flight", and stick to low level flights which should burn more fuel :joystick: