Quip

That's when the Quick mode comes in handy, it's exactly why it's there :) From the manual

BX6 isn't a point. It's a distance. BX 7, 8 and 9 are points. It's done this way so you can launch your 15's from whatever angle you approach from, almost: 1. If the line from your actual position and BX7 places the BX6 distance over land, the 15's a probably going to crash into ground. 2. if the total turns that the 15's are required to make is more than 135 deg you can't fire. The reason BX7 is a fixed point is seen from the image and the video (beolow): it's so that the 15 can use/avoid terrain features You may want to watch this closely :)

I don't know if it's been said before, but the error shown in the last digit of the CK37 is an estimate only. And that estimate is purely time based. What you must realize is that if the system knew how large the error was, then it would be able to correct for the error and thus never have a drift error. So with an estimated 5 km error, the true error can be anything from 5 to a gazillion. I've had cases where my error was 20 km with a low digit showing. Also, there is no need for a manual fix if you have TERRNAV working (a 5 in the second last digit). The TERRNAV is a separate system that was plugged in to the AJS update, and what it does is it sends fixes ever second or so to the CK37 (which remained largely unchanged). But if you haven't had a TERRNAV for a while, then a manual fix can come in handy

It's your go to instrument for precision, it's much more precise than the HUD. And it's you back up instrument if the HUD fails, or when you're in an ANF-mode, or the HUD is in the sun. Very very useful.

AJS37 in DCS has 221 as default.

I missread

You don't use the NWS when taking off or landing, you use the toe brakes. (But at the moment this isn't working)

I theorize it's got to do with ED changing the ground model (now that they realized it was bonkers, and couldn't get the FA18 working properly on carriers), so HB had to add a fix for the ground handling model And a fix is a fix. So hopefully they can get on top of this. Meanwhile, only brake using your reversor (no wheel brakes) until you're really slow.

What's the status on this? This is a show stopper for me as far as I'm concerned for the Viggen in MP. As it stands, the Viggen can't be fully utilized in MP since the road bases aren't functional with regards to rearming. What baffles me is that the AV8B was rather quickly fully implemented and fully functional. But the Viggen not so. And I don't understand why ED would be blocking this. How can we help in conveying the message?

Excellent, thanks! Odd, but thanks :)

I can enter BANA, but not LOLA for the new T/O location...

So I have a question. When you first start and you get near the runway you switch from BER to NAV. This sets the navigation system in "update" mode, so when you start your takeoff run (within 2 minutes), the INS is updated as you roll down the runway. This does a fix to the Lat/lon of the runway to setup the INS and also adds the magnetic variation. If your heading as you start rolling is off by more than 15 degrees the system will assume you're on the opposing runway and try to do a navigational initiation for that heading. Or you can press the Reference button. But the limitations are the same. Also, once you land, if you want to takeoff again, you switch to BER and LS and back to NAV to reset the HUD to its Takeoff mode (with the VRot speed and climbout symbology) (you can also set a different runway heading before rolling in BANA/IN, but that's not the point here) So far so good. But now the question. If you now land on a roadbase (or a different airbase), and want to takeoff, again, the heading will no longer be correct, and even more importantly, the Lat/Lon for that runways center point. So you end up with a NavSyst error. I would have imagined that the way around this would have been to enter the new starting point as LS. For an airfield this is pretty simple, just enter the airport code as REF and you should be fine. And for a road base, I thought you should be able to enter the correct Lat/lon to LOLA and the road's heading to BANA. But I can't seem to do this. I'm not able to enter a LOLA for LS. So anytime I want to takeoff from a road my navigational system ends up with an error NavSyst. Have I missunderstood something or is this something that hasn't been implemented correctly? And I know I can takeoff without doing the BER-LS-NAV-ballet which eliminiates the NavSyst error (since no Nav update is attempted), but I do like to takeoff in takeoff mode... :)

Please don't call it "W", but let it remain "B". You could very well say "break point" in English, and M for "Marked" and U for "up". So please let the LS, B, U, M, L remain untouched. It's so confusing when half the flight has the "English" cockpit and say "W" and half have the Swedish and say "B".

OK, so the way I see it, there's a limitation to the system(s) (old as well as new) that work against what I'm trying to achieve, and I'm not asking for a fix, but for confirmation that I've understood the fnctionality right: I can have 5 cartridges, full stop. I can't have 5 cartridges per .miz (mission) or somehow reditribute cartridges with the mission. I can't make sure all players in my mission have the exact same 5 cartridges. Right? Trying to understand.

So maybe I'm daft, but there is something about them cartridges I don't get. And yes I have been searching. The way I understand how they work, you add a ini-files to the Saved Games AJS37 folder. You can have up to 5 different cartridges. So my questions are: Is this a single ini-file or 5 different files? What happens if I add more than 5 files? How can I have multiple cartridges that go with different missions? 2 is really what this post is about: I'd like to be able to have "Green" flight to load Cartridge X (number, name?) and flight "Blue" to load Y. And I'd need different cartridges for different missions. So: How do I manage cartridges?

TILS weren't used outside fixed airports. I bet that they would have been moved had we ever really needed it. But afaik they weren't ever used for road bases (one of the reasons the Gripen had to come up with a different solution)

I propose a different analogy. Skip what what done in the Viggen and think "US", namely A-10 and F-16 etc... Use the TMS hat, and use T0 Aft T1 Fwd TV Right This approximates the way that the TMS is used in many US planes with aft being "unlock", fwd being "Hook" or "Lock" and right being"send to sensor" or such Just a tip

Many many thanks!

Waking up a dead thread. I did participate in the live interview, but I can't find the saved audio file. And the FTP link is dead. Does anyone have a copy that I could grab? Pretty please :D

So the 601 rel 9 is now "stable". Is this including the haxxor hack for the reversors or is this the one that breaks it? :D https://forums.eagle.ru/showpost.php?p=3603492&postcount=5

You need to understand the difference between a B and an M point. There are three differences only that matter. 1. Fixes: If you fix a B point, the entire flight plan is moved. This is because if you have a navigation error on a B point, then all points in the flight plan will be off. So fixing a B point "adjusts" all points (including M and BX) If you fix an M point, only that point is moved. Say you have a plan with a target on an intersection. But when you get near, they've moved a bit. So you fix the M point to where they are now. This will move the M point but nothing else (except U points, see below) 2. Pup-up points: You can create a pop-up point U (up), and it will always set itself in relation to the M point. You can only create a Pop-up point if there's an M (target) point. 3. Speeds and Time-on-target: If you play with leg speeds or ToT, you set these in relation to an M point, but not to others (B, U, BX). This is all black magic, but suffice to say that ToT use M points. Last point I'll make: You can set multiple M points, but you're not meant to. Rather, if you have many target areas, you're supposed to use BX points.

I disagree. That the Viggen as the sole system has the ability to detect any enemy unit like that isn't cheating any more than the Sidearm AIM 122 of the Harrier or anything else which is present in other AC.

But another observation from the same tests: Do the Bk90 terrain follow in MP at all, or are their behavior more like a simple glide bomb? Asking because during our flights lately, it seems that they're simply gliding in MP...

Ah, ok. So in that case, @putin: to defend yourself from Bk90, place troops on hill tops Good to know. And again: add that as info in the manual :)

That's good enough for me tbh. I suggest you add that as an info box into the manual.