Zev

Thanks for the reply, Rudel_chw! When I mentioned “bugs,” I was mainly referring to the small issues you note inside a couple of your missions — for example: In the Landing (Short Direct Approach) mission, the destination indicator displaying LB1 instead of LF1, even though the actual guidance is correct. In the off-road takeoff mission, where FARP ATC only responds to helicopters. Nothing major, of course — just minor quirks that can be confusing for someone still learning the aircraft, especially when trying to understand approach procedures. Your missions actually helped me identify what was happening, so thank you for that. Already found them, and they are really great. Always a fan of your missions you’ve made for DCS! Keep up the good work.

Both TOViper and Rudel_chw — thank you for taking the time to help me out. TOViper, your pointer to the manual (and the work you’ve put into updating it) really helped me understand the procedure more clearly. I also joined your Viggen.training website, which you keep wonderfully up to date — really great resource, thanks for maintaining it! Rudel_chw, the YouTube video you made based on your training missions was exactly what I needed to see what should be happening during the maneuver. The combination of both resources has definitely given me a much better idea of what I’m supposed to do and what cues I should be looking for in the cockpit. It’s a bit unfortunate that some bugs related to this are still unresolved. I hope they can be addressed at some point, even though I’m aware the module is quite old now and some of these issues have been around for a very long time — so I’m not entirely sure how realistic that hope is. Regarding the overhead break landing, I still haven’t found definitive information on whether this procedure was ever used by the Viggen at all, unlike aircraft such as the F/A-18. If anyone has solid historical or procedural references on this, I’d definitely be interested. Once again, many thanks to both of you: – TOViper, for the manual updates and the Viggen.training site. – Rudel_chw, and I hope you’ll eventually find the time to port your NTTR missions over to the Kola map — would love to fly them there!

Hi all, I recently purchased the AJS-37 Viggen module and I’m absolutely blown away by it. It fully lives up to Heatblur’s incredibly high standards, and I’m genuinely impressed by what this aircraft can do and the capabilities it brings as a combat jet. I’m still very much at the beginning of the learning curve and working on getting more familiar with the aircraft, but I’m enjoying the process a lot so far. Right now I’m trying to get a clear understanding of two procedures: the overhead pass and the overhead break landing. I know these are two different things, but I’m having trouble finding solid information on how they should be performed in the Viggen. For the overhead break landing in particular, I’m not even sure whether this procedure was ever actually used by the Viggen in real life—if it wasn’t, I’d love to know that too. I did notice that Chuck’s Guide briefly mentions the overhead pass, but the actual execution isn’t fully explained. The AJS-37 Flight Manual (RC2.1) also touches on it, but not in a way that gives me enough confidence to perform it correctly in DCS. So my question is: Does anyone have a detailed explanation or tutorial for the Viggen’s overhead pass, and can anyone confirm whether an overhead break landing procedure exists (and if so, how it’s done)? Any guidance, references, or videos would be greatly appreciated. Thanks in advance, and fly safe!

I’m seeing exactly the same behavior you described. During the start sequence, the DC BUS caution light comes on when the right engine reaches idle and its generator comes online. It stays illuminated through the left engine start and doesn’t go out once the sequence is complete. Just like you mentioned, cycling both generators simultaneously (as per the -1 checklist) does clear the light, but I’m not sure why it’s happening in the first place — especially since everything else seems to be working normally. Did you ever find out what was causing this, or if it’s something that needs to be done manually every time? I’m wondering if this is just a quirk of the current module or if we’re missing a step in the startup flow. Thanks in advance for any insight!

Already bought it

Yesterday I finally graduated as a TOPGUN F-4E pilot — and I couldn’t be happier! This was actually the first campaign I’ve ever completed in DCS from start to finish, and what an incredible experience it was. There have already been many great comments about Reflected’s MiG Killers campaign, so I won’t repeat them all. What I do want to add, though, is that this campaign is surprisingly beginner-friendly. Of course, you need to have the basic handling of the F-4E under control — but if you want to learn air-to-air combat in the Phantom, this is the campaign to do it with. Big thanks to Reflected for another masterpiece. Flying through this campaign felt like stepping straight into a 1970s training film — immersive, challenging, and incredibly rewarding.

Hopefully it is a successful trip then. As for the trim, the needle is responding to my inputs, it just seems to me that it can’t hit the outer value of the-3. (It can be solved by using the joystick as mentioned.) I have the same problem and stuck @ 21 selecting (either Tacan or HSI). Selecting either one or both doesn’t continue the training mission.

Great job, running through all training missions right now - Training mission 1 (full cold start carrier). Stuck @12.a trim -3 and +8. Did the whole trim range but mission doesn’t continue. (Tried spacebar, tried with keystrokes as well)

Found it thx!

Just downloaded this mission, and tried to do some slingloading. Where are the "slingloads" located? There is no option in the F6, flew around Camp Hermon --> no joy! Rest of the missions, as far as I could see, do work. Great job Sirrah

Hi everyone, I currently have an Astro A50 headset, but when I wear it under my Pimax Crystal VR headset, the VR headset presses down on the ear cups and it’s uncomfortable for long sessions. I’m looking for a (wired) gaming headset that: - Has a good microphone - Provides high-quality sound - Has a slim or flattened top design so it sits comfortably under the Pimax Crystal - Price is not a limitation I’d love to hear from anyone who has experience using headsets under the Pimax Crystal. Which models have worked well for you in terms of comfort and audio quality? Any tips or suggestions would be greatly appreciated! Thanks in advance!

Hi all, I’ve got a question about handling radar contacts in the F-4E with AI Jester. Let’s say I already see a (IFF) contact on the radar. At this point I don’t want to hard lock it yet — I just want Jester to keep following that contact area so he doesn’t lose it when he resumes his wider search pattern. Sometimes it feels like if I don’t lock immediately, Jester just keeps scanning, contact is lost and it can take too long before he reacquires the same blip. So my question is: Is there a way to tell Jester to “track” or “focus” on a contact without going to a hard lock? Do you guys use specific Jester Wheel entries or context button tricks to make him hold a radar focus on a contact? Any tips or workflow that help reduce the chance of losing a contact before I’m ready to commit to a lock? Curious to hear how others handle this — thanks in advance! Cheers, Zev

Thanks again for the clarification — that really helps to put things into perspective. Makes sense that it depends so much on the bogey’s altitude and the terrain background. The example with a target at angels 25 vs. angels 10 with mountains really illustrates the difference well. Good to know that Jester already scans ±10,000 ft by default (Zabuzard) , so I don’t need to micromanage him there. That simplifies things a lot. I’ll definitely keep boresight mode in mind for closer visual-range situations. Appreciate you taking the time to explain this

Hey Zabuzard, Thanks a lot for clarifying how Jester currently handles the radar search — that makes things much clearer. Good to know that his default pattern already covers a big chunk of the sky, and that there are options in the Wheel to fine-tune it if needed. Do you happen to have any specific tips or tricks for getting Jester to pick up a radar contact faster in practice? For example, are there particular search settings or habits that make a noticeable difference? Appreciate the insight! Cheers, Zev

Hey OmasRachE, Thanks a lot for your detailed reply — that’s super helpful and definitely something I can use! One follow-up question: when you mention flying slightly below the bogey to help the radar against ground clutter, how much lower are we talking here? A few thousand feet, or just enough to keep some separation? And in that case, should I also be telling Jester to scan higher with the radar, or is he smart enough to compensate once I’m below the target? Appreciate the insights — this really helps me get a clearer picture of how to set up the intercept properly. Cheers, Zev That would be really great