TOViper

Discussed separately here:

Hey AX47! According to RC2.1 page 331, this might not work the way you would expect, because the target has to be within 20km range. In fact, its not written what the missile does when no target is found initially. Did it work before the update?

Hey! I fly DCS mostly in VR since 4 years and I am interested in your statement, and have in fact two questions: .) What makes you confident that the newer DCS version has a different FOV? .) Did you play around with any configurations, like the SYSTEM settings page, or maybe some LUA files like the graphics.lua in the DCS/config directory, etc. to get rid of this (or make it appear like in the older versions)?

Yup, looking good. Curious to know why a bigger moon would be desirable? Moonstruck?

JA 37.

@KenaiPhoenix: Have you been in CCIP or CCRP while the TGP was your SOI? In CCIP I think AREA is not possible.

For the time until the next possible fix (?), you may play around a bit in the graphics.lua in the DCS\config directory ... Maybe changing the 0.5 to something bigger changes it. On the other hand, the value of 0.5 seems correct though ...

Of course, I can do that! Thank you for the heads up on! Here is a draft, you can use it temporarily, and provide feedback if you like. I will release a new manual somewhere around end of August I think ... let's see when the next DCS update comes into view. DCS_AJS37_Flight_Manual_EN_RC2.1_pages_86-87.pdf

I love you guys for making the Viggen better and better. Carry on guys please and: never stop!

100% YES, it has.

This trick is only for guys who use the Oculus Client (e.g. as the OpenXR provider) exclusively for DCS: Just use your Windows Firewall to block the relevant two Oculus .exe's. I'm not on my computer right now, but these are something called like oculusclient.exe and something like ovr64service.exe (or very similar); use your task manager to spot them, then you have the filenames and their paths. I do this since years, and the fagging auto-update function of the oculus client doesn't even know that Internet exists. For mandatory updates (because maybe DCS REALLY NEEDS a specific version, e.g. IIRC 2.7 needed one specific), you can disable the firewall rules, start oculus, do the update, and re-activate the rules again (and pray it works). Before: Make a backup copy of your Oculus installation directory. As said, I have this working eversince Oculus works in DCS (1.5.8 IIRC).

There is no reason for feeling silly about it. If that's the only way to get it work ... then let's do it

TOViper's sammelsurium of the last few months of flying DCS ...

Best idea one can have ... Return of invest rate: 100 %

Updatelog: 2024-07-20, 12:10 UTC ================== Dear Viggen drivers out there! Report: Due to a configuration problem in the ASSESSMENT CENTER, the Pre-Entry Checks for: A1.00 B1.00 B4.00 where not automatically re-newed in case you didn't pass it. This is fixed for now. All affected users have been informed by an e-mail with subject "Viggen.training - Course Information - Username" already. Background: Usually, Pre-Entry Checks should be removed from the list of available courses (your Assessment Center main page) 7 days after your first attempt. Unfortunately, they were not removed automatically, and there was no way for users to re-assign by themselves using the Shop function. Following this, I had to manually re-assign the Pre-Entry Checks (the ones users had initially assigned themselves) to the Assessment Center users. Luckily, I have figured out the problem quickly today, and I am already in contact with the Assessment Center distributor for a solution. Solution: Meanwhile, if any re-assignment is necessary, it will be done by hand by myself. This means, you can now attend the Pre-Entry Checks again in case you didn't pass them. Sorry for the inconvenience guys, this was out of my control. In case you still experience troubles or have any other question, please don't hesitate to ask. Kind regards, TOViper

Ah, ok, thank you for your quick answers!

Did this trick help you Noctrach?

Is LACQ the same as LHAQ? And when yes, why is it labelled differently?

Hey guys, where can I find a description of this mode in the manual?

Hm, not on that page; it is not even described on page 253, where it should IMHO. I'll add this for the next update, thanks for the heads-up guys. This is what I've prepared within the last 20 minutes: null

Hello Machalot! I think the information in the manual page 132 is in AND still correct: null

Hello Viggen drivers out there! Here are the manual updates that came with the DCS update July 11th, 2024: Manual update 2024-06-23: .) page 1: Changed to a background picture with higher resolution .) page 30: Changed section "The instrument shows ..." according to what is currently possible in DCS .) page 34: Changed wording slightly for the section "Engine nozzle indicator" .) pages 44 & 45: some warnings are now cautions; changed style and labels according to new cockpit design; Thanks Myse1234! .) page 46: Changed picture according to new cockpit design; Thanks Myse1234! .) page 46: Enabled OLJETEMP caution; light still has no function, but can be illuminated with the LAMPTABLA TEST; Thanks Myse1234! .) pages 47 & 48: changed style and labels according to new cockpit design; Thanks Myse1234! .) page 48: Changed picture according to new cockpit design; Thanks Myse1234! .) page 48: Removed note about wrong white boxes which became unnecessary with the new cockpit design .) page 50: Enabled the text about the white markers on the indicator and warning tables ("Some of the indicator ...") .) page 67: Changed picture according to new cockpit design; added note to Mode 3 about the orange light; Thanks Myse1234! .) page 72: Changed wording slightly for some indicator lights; Thanks Myse1234! .) page 84: Changed pictures according to new cockpit design; Thanks Myse1234! .) page 113: Changed captions vice-versa; they were mixed up; Thanks Snappy! .) page 121: Added schematic view of KB pod; Thanks Myse1234! .) pages 121 & 122 & 123: Changed data of KB pod programs 1 to 4. Observe new chaff & flares frequencies!; Thanks Myse1234! .) page 122 & 125: Deactivated section "Automatic release mode"; this is currently not working in DCS; Thanks Myse1234! .) page 164: Changed pictures according to new cockpit design; Thanks Myse1234! .) page 234: Replaced "Radar altimeter" with "Doppler system" .) page 257: Removed word "to" from sentence "The entered Mach number lasts until the next ingress waypoint or [[[[[to]]]]] the waypoint after the last target waypoint." .) page 264: Reworked whole page regarding chapter "Manual fixes"; Thanks Machalot & Myse1234! .) page 297: Changed wording for the chapter M71 Modes / Overview (for most of the text); Thanks Machalot & Myse1234! .) page 301: Changed header "M71 / CCIP (low drag bombs only)" to "M71 / CCIP (high drag bombs only)"; Thanks to Discord user SmugPappyToast! .) page 309: Changed wording for paragraph "The Navigation bombing mode (NAV bombing)..."; Thanks Machalot & Myse1234! .) pages 336 & 337: Reworked the section "RB15F, missile programming" slightly for better reading .) all pages: Consistently changed designation for the 120kg sprängbombs to "M71" throughout the whole document; Thanks Machalot! .) all pages: Consistently exchanged the word "warning" with "caution" in case a warning became a caution. .) all pages: Consistently exchanged the labels according to new cockpit design. Happy holidays & kind regards, TOViper

THIS 100% I love you all guys!

I do the trick by cycling (activating - deactivating) the quick release with my thumb on the right hand (Warthog). This gives flares every 0.3 seconds or so ...

De nada