MYSE1234

Did you wait 3 minutes after take off to let them warm up first?

Done

The RWR classified the Tin Shield (one of its beams) as a Tornado before this patch as the two radar's parameters were very close to each other, which is why it showed as one of the aircraft symbols (the one related to the Tornado's radar). This patch added a custom radar for the Tornados that is quite different from the auto generated one from before this patch. So now the RWR should see it as a Tin Shield without problems. Knock on wood. So it wasn't strictly a bug, the RWR did work the way it should. It was just a bit unlucky with its guess on what radar it was seeing. From the change log: Added custom Tornado radar.

No problem! You were lucky I happened to have a look here so soon after posting.

They are not. Only the bombs themselves are. This was corrected last update, together with finally allowing BK90's to be jettisoned.

I think adding this to the livery description file will fix that, looks like a custom livery so probably doesn't have it. {"AGM_65B", DIFFUSE, "RB75_Diff", true};

I'm talking DCS, not what it's actually supposed to be.

Pretty sure KURSKORR is not actually hooked up to anything, other than the backup compass () so it's not really doing much other than being a visual thing. Setting it to 0 instead of random should be easy enough though.

More than likely. The actual radio only held 69 channels + the ALLM, T1 and T2. This limit is what caused the bug. So for anything above that you need manually tune it to whatever frequency the kneeboard says the airfield has.

^ These should be all the codes that are applicable to Kola. CK37 REF codes.kmz

Squashed this bug yesterday. It was indeed stuck in a loop trying to rotate to a number that was impossible to reach (anything above 72). Thanks for the report!

They're created and handled by the Viggen code, so not something that can be made "externally", i don't think.

The pages with reference codes have them, yes. Maybe some other that I've forgotten about.

Then I'm not sure there is a bug I'm afraid. You need to use the "sub page keys" to change the subpages, the "normal" keys just change the "main" pages.

Are you sure your keybinds are setup correctly for changing page? Maybe you changed them to something else, the text there is not dynamic. It's working fine on all missions I've tried it on, warning or not. Not sure what's going on with the warning being shown as all bases that are added are shown there. Will have a look.

Well yeah, you don't have the fix for it yet. It's fixed internally.

I mean, it wasn't deleted; it just wasn't working correctly Should be fixed now though.

Can confirm, it's broken . Will investigate, thanks for the report!

There is a bind for it: SAS mode SPAK flight stabiliser

Hello! Yes it was an intentional change to make the logic of the buttons match them to how the IRL manual describe them to work. To turn on a mode you just click the mode button you want; Just like before: SPAK will turn on SPAK ATT will turn on ATT HÖJD will turn on HÖJD The changes are more with the disengage logic. Pressing SPAK will as above turn on SPAK (if not already on), but it will also turn ATT and HÖJD off. Pressing ATT will turn on ATT, but will also turn off HÖJD. SPAK will remain on. Pressing HÖJD turns HÖJD on. To turn it off you press either ATT or SPAK, or the below. Pressing the quick disengage button (SNURK) will turn ALL modes off: SPAK, ATT, HÖJD. It's an emergency button you press in case some part of the system fails and causes the aircraft to fly dangerously. That said there are two keybinds coming (didn't make it unfortunately) that will enable you to bind physical buttons you have to ATT and HÖJD that will function as they did previously. The in-game cockpit buttons though will remain as described above, only the "toggle" binds will work as before.

Try disabling "Easy Communication" in the gameplay settings.

I'm not sure why, but disabling "Easy Communication" in the GAMEPLAY options seem to fix it.

Found and fixed the cause for the crash.