Quip

So with this rather unusual configuration I have been able to force a new bug I think... The Bk90's I fire will hit the side of the hill, even though it's set to approach at 200m (TAKT 912000). It's like it does approach/terrain follows at the higher altitude, until it finally gets into the final approach stage when it descends to 60m (which is its default altitude) and thus hits the side of the hill... See this film:

Concur...

In real life - and I'm not saying this is working properly in the game, but it's worth remembering - pilots can pull high Gs as long as the onset is slow. It's far worse going from 1 to 5G in a blink of an eye than to pull 7G for several seconds.

You can do this using SRS radio for DCS. But it's not how Sweden used the radios in the Viggen (-era). You only spoke on one radio, and often the flights were done in complete radio silence... Just so you know why the Viggen only has one :) (The 2nd radio is a pure backup/emergency/guard radio and super weak as well)

No, it's like a cruise missile and it uses an INS nav system much like the one in the Viggen to fly towards its target. Only it's got no engine. But treat it like if it had an engine. For Bk90 uage, watch this demo:

I hadn't seen your reply when I wrote mine :)

I concur https://forums.eagle.ru/showthread.php?p=3494378

Yeah, most likely...

Use F10. You can cycle between the different modes using [L-ALT]+[Y] (you need to move the mouse to see the units shift). So set the map to MGRS and zone in on the correct area on the map, that shift to Lat/Lon with deg/min/sec and ta-da.

Cool. I do remember having that said to me though. But really not important :) And Thanks

Adding XT to an AC in flight doesn't give the added fuel. It shows on the 3D model, and weapons are loaded, but the XT is empty. This is in my initial tests flying in the Persian Gulf. Don't know if it is also true for Caucasus.:cry:

It'd still render the world an additional time, and that's not acceptable in Heatblur's view. And certainly not acceptable in 2018 IMHO.

1 hpa is 33.863886666667 inHg. So 29.55 x 33.9 gives you the value in SI (for the Viggen). Simply multiply by 3 and add 1/10th and 1/10th again after adding a zero: 30 x 3 = 90 90 + 9 = 99 990 + 9 = 999 The exact value above is 1000.68 The difference is 1 hpa, which is approximatively the equivalent of 10 m error at sea level (at standard pressure and sea level, the pressure decreases approximatively by 12 hpa per 100 m). Using this method you end up in the near 100 m.

^--- that. (I add 3)

In real life, that's what you have your meteorologists for. But in-game, here

"Not until the graphics engine makes it possible without rendering the screen separately for each mirror (with its attached overhead)" is the answer they've give, if I'm not misinformed.

Hey 1) You can, but there's no "Built in" function for this. You have to go about it in other ways. I do believe (can't quite remember) that ATC does give you QFE for the airport when you contact them - that would help... 2) See my reply here; it contains the info you're looking for. In short: you can, but the way TILS is implemented will give you errors. https://forums.eagle.ru/showthread.php?p=3449342#post3449342

Oh I can hear it alright. But it's part of the soul IMHO :)

So I didn't understand why my private missions didn't work. Several hours later I find this post of yours, and yes, that explains it. Quite amazing that a function that has worked flawlessly since 1.forever suddenly ceases to work after an update that doesn't concern that functionality (as per release notes).

TRK have been a problem since Flanker 1-0. Basically, if the TRK doesn't capture all the commands exactly during recording, or doesn't replay all the commands during playback exactly 100% right, the TRK is corrupt. Sometimes the difference is small enough to allow for the overall TRK to be OK, but many times it isn't. Back in the Flanker days this was most often coupled 1:1 with CPU performance.

See image. Settings on the left image generates fog. Settings on the right doesn't This is one of several checkboxes that aren't respected. Another that I know of on the top of my head is the VR setting "Cursor Confined to Game Window" that is reset to ON at game launch, every time, regardless of the actual state of the checkbox

You guys seen these ones?

RagnarDa, true story to follow: The sim F/A-18 Hornet 2 had a bug I discovered and reported. If you flew at negative AOA, drag was removed from the flight model. So if you ran out of fuel: just fly inverted at high negative AOA and you could get home without any problems, then dead stick land. The bug was never corrected, even in Hornet 3.0 Yeah... So you're in good sim-company ;)

Why it got SO wild? You did almost everything right, except you followed the FD on the ADI in a high crosswind. The ADI, unlike the steering dot + fpm on HUD, doesn't compensate for sidewind. Had you tried (not sure it'd even work in that type of crosswind) to place the fpm on the steering dot rather than crossing the FD on the ADI you'd had an approach along the centerline. :)

TOViper A few facts about the TILS - It only works to one side of each runway. This is a bug. In real life, there is one TILS-truck (or installation) where the TILS is supposed to work. The TILS then only emits in one direction. The games TILS is only placed at one end, but emits bi-directionally! - In LNAV the Viggen adds a virtual "B" point called "LB". This point is situated some 22km from the TILS emitter and the nav system guides you to this additional B point. This turn is shown on the CI as the "q". Your ADI and steering info on the HUD guides you there. The CI always points to the runway center. - Once you're at the LB point, The system switches over to LF (Final) and guides you in a shallow-ish turn towards the extended centerline to catch the TILS. The system switches over to LF (Final) - If you're already inside the TIL emitters range, the system omits LB and goes to LF directly. In practice in the game, this happens even if you're far from the TILS emitter as long as you're more or less aligned with the runway. - You set up the system in this way: First airport, then runway, then approach mode. So let's look at your approach. 1:05 you have activated TILS for runway 04. The system is in LNAV and gives you steering guidance to LB at the far end of the "q" with a right hand 180 deg turn to the runway centerline (the tail of the q). 1:15 By switching rnw to 22 the system (or game) notices you're on centerline to rnw 22 and so it switches to LF. 1:30 You have now switched the system back to rnw 04, but since you flip-flopped, the LNAV isn't reset to LB mode, so you're now in LF. Look at the last point I made above. But this isn't important in your approach as you 'll see... 4:30 Remeber what I said about the LB being some 22km from the TILS? Well see, now you're at 20 km and the TILS is captured. But you're way too high. at LB/20km you're supposed to be at 500m / 550km/h. If you follow the reference lines and steering cues on HUD/ADI this will be correct. 4:55 Perfect distance for gear down, but way too high 5:25 Here's the crucial point. The HUD has now added the dropped horizontal lione to show the glide angle at 2.8 deg. Now, if you had stayed in LNAV and rnw 22, the system in the game would have brought you to a perfect approach to the *far end* of the runway - THIS is the bug! But you didn't. Rather, you switched to LP/O. Now, for an LNAV you never go to LP/O. LP/O is the manual system and by switching to it you're telling the system "I want no TILS thank you very much!" LP/O is used for visual appoaches when a TILS isnät available or for go-arounds. So, again refering to the last item on the list above: decide before if you're doing a guided approach (LNAV) or visial (LP/O). The rest of your approach is pretty perfect. I love how you rode the AOA the last 15 s, really good. I'd add that irl if you do a full reversed landing you normally also setup the AOA to 15.5 deg by clicking on the small button below the autopilot, but that's minor. I hope this explains it all for you.