Machalot

I think this is difficult because the autopilot modes are progressive, SPAK-ATT-HÖJD. If you assign those Roman numerals, you're kind of asking for you switch positions to be: Aft II Middle I Front III Isn't it more natural to have aft as SPAK? This was intentional, because pressing the HÖJD button in the cockpit should only cancel HÖJD, leaving ATT active. This was previously wrong, where the HÖJD button would cancel ATT and HÖJD.

This is known and tracked. I can't reproduce this. Is there possibly an issue with your data cartridge files? There is some kind of issue with CTD when having too many cartridge files. Sorry that I can't reproduce this one since I have only a US keyboard. But I have reported it. Can you elaborate on what you mean by "have the cartridge selected"? There is always a cartridge selected. And what does "go a little bit funky" mean?

I'm unclear what you mean by "wipe the data cartridge", but does this symptom still happen if you also press T0 after TV for the fix? I think you can get what you want using these two keybinds: Autopilot HÖJD/ATT on the forward position, and Autopilot SPAK/ATT on the rear position. That would make the rear position activate SPAK only, the middle position activate ATT, and the forward position activate HÖJD. That is, if I understand correctly how the switch works, where the middle position is "no button" and the forward/rear positions are each a separate button that is held. This is known and tracked.

The beta testers have been discussing this with one of the SMEs while all the HB guys are out on holiday. We don't think it should work this way, and are unsure why it changed. This is known and tracked.

Wow, attention to detail! The warning lamp comes on during startup, but turns off near the end of startup. After that, the switch has no effect on the warning lamp. Unclear if the switch actually does anything. I have submitted a bug report to HB. Confirmed and reported. TID/UT shows current time when you depress LS/SKU. Otherwise it shows TID information for the currently selected waypoint. This is already known and tracked. Known and tracked. I haven't experienced this. Can you make a track file? AFAIK the only mode that shows radar elevation is IR-RB. Don't know if any other modes should have it. I'll ask. There's a known issue where now you have to press TV then T0 to complete a fix, whereas before it would complete on TV. If you don't press T0, it "drags" the current waypoint fix along with you as you fly until you press T0. Could this be what you're seeing? If not, can you make a track file? I haven't experienced any trouble like you're describing.

The datapanel 0 lack of animation is already reported. For the RENSA cover, try using the keybind called "Data panel RENSA cover OPEN/CLOSE" under the Navigation section. I have submitted a suggestion for the Fallsattamkpplare and Valb/Prep keybinds as you said.

Agreed, but the LK Flashpoint Levant server is an "80s setting" but the actual date of the mission is in the 90s, I presume to allow some anachronistic weapons that stand in for unavailable period weapons.

Yes, I was using the GPS switch in the F-16. Can you explain a bit? Before and after what? And is there a way to do a nav fix in the DCS Viper?

What I experienced was definitely more than 0.8 nm/hr (is that a 50% CEP?). I'll have to do more testing. After I realized my waypoint was miles from the target I relented on "realism" and turned on GPS. Within a few minutes it snapped back to the correct position.

Does anyone know the expected inertial drift rate of the Viper's nav system when GPS is disabled? The other day I flew a sortie from Incirlik to a target in Hama on the LK Flashpoint Levant server, which is an 80's historical setting. I used Stored Heading alignment and let it complete to 10.0. For realism I disabled GPS. After 20 minutes my target waypoint had drifted from Hama all the way to near the coast. That seems excessive, but I have no data to say one way or the other.

This is already reported and tracked by HB. Thanks!

Several things changed with the radios in the recent patch: 1. FR24 was locked to Guard frequency while in NORM+LARM setting. 2. FR22 and FR24 devices were swapped relative to previous SRS configuration, so you need to swap the push-to-talk keybinds until SRS is updated. 3. Special and Group (GRUPP) channels were reconfigured. Some multiplayer missions have probably not updated their special channels (1,2,3,EFGH), so they are all default 225.0 or something. To access the channels that used to be in these slots, turn the GRUPP selector to 10 and use the 0-9 channel buttons. The new frequency mapping is in the kneeboard. Hope this helps!

But I think the radar cursor is ground stabilized in certain conditions, isn't it? Maybe I'm misremembering.

I think in the real Hornet you have to depress the TDC switch in order to slew with it. But in DCS that is optional due to limitations of hotases. Maybe they could add an option to the Viper to have it ignore slew inputs unless a certain button is depressed.

Off center vertically or horizontally? In your track, the flight path marker is shifted to the right, which is likely the result of a crosswind. Try flying the opposite direction and see if it goes to the left side. If you are talking about the horizon line sitting above the horizon, that is a suspected bug that we have reported to HB.

This new requirement to press T0 to capture the fix actually breaks the visual fix behavior. When you pass over a point and hit TV, it continuously updates the fix position while you fly on, only capturing it when you again hit T0.

The slight movement of the cursor has caused multiple different problems for many people, including inability to boresight Mavericks, inability to get a point track and do a handoff, etc. I wonder if anything can be done about it besides requiring users to use a deadzone.

It's described at the end of the Viggen manual. There is also a good tutorial here: There was a test build that was supposed to fix that but I didn't get a chance to test it because of the holidays. One of the other testers reported that it worked for him. Hopefully it's in the hotfix.

My memory could be faulty about T0 before the update. After our discord discussion I'm convinced you have it right.

And fly at 150-300 meters altitude.

Other people I have asked say this has changed recently. I have always hit T0 at the end of the fix process anyway, assuming I had to "release the trigger", so I haven't noticed the change.

Bug report submitted. I haven't checked this myself though.

Confirmed and reported.

Do you know if this is a true intended design feature, or just a handy result of the rudder-aileron interconnect?

Confirmed and reported. Even on hot start, I can't get RB04 right angle jump [LCtrl+LShift+W] or Relocation [LAlt+LCtrl+R] to work. I filed a separate bug report for this