TobiasA

I have locked up and shot down Kh-58 fired by a Frogfoot. So... Yes, it is possible.

Tbh there haven't been many bugfixes on the Viper recently, and annoying things as not remembering the last radar mode that was broken several updates ago remain open for quite a long time.

It seems the modeled blast damage to some amount now. Didn't have a single failed drop yet, they used to be more like 75% prior to the last few patches.

As far as I know, yes. And anyone can induce TDOA but it's best if the lead does it for the sake of avoiding chaos. The other members get the TDOA indication and everyone has PGM1 on that contact after some time if it worked.

You need to point at the same threat as the one who initiated TDOA, as the HTS pod doesn't have 360 degree coverage. Follow the arrow in the HUD next to the TDOA indication.

There are some threads about this, so I guess one doesn't need a track.

As of 2.9.6 it remembers some scan settings, but still not TWS / RWS.

It happens with any mode change.

What about selecting a threat on the HSD as a steerpoint, as those are stored as steerpoints? What about a DTC? And the option to draw lines and custom text and threats in that DTC that help you with keeping border, for example? Will these ever come then?

When you select TWS in MRM override, the radar defaults back to RWS when cycling the OVRD switch. After a mode change, it will always fall back to RWS, the current mode isn't stored. Each submode should remember its radar setting. Steps to reproduce: Select MRM with the override switch, select TWS with TMS right long, cancel override, enter MRM override again. Radar will default to RWS.

Do one in post-designate CCIP with a little crosswind. As for CCRP, it is similar. If you deviate from 1G after pickle, it will most probably miss. I am not anywhere near the computer unfortunately. But it actually happens very often.

Probably worth noting that it happened more frequently around the 20nm mark.

It is, but it should be visible in the tracks. Is the axis input recorded in the track?

This. Had one eating my complete AA loadout and continue flying.

To be honest, the best strategy to land a 9X hit against most planes is to wait until they are out of flares. The sidewinder refuses to track most targets with dual flare dispensers, especially helicopters and MiG-29 / Su-27. But, yes, you are right, even though my best kill with a 9X had 80° off-boresight. Guns are far from obsolete, but nowadays sensors and high off-boresight possibilities have made it difficult to actually enter a dogfight and survive initial contact.

I got it in the second try this time. MRM in TWS, cancel override, TMS down a few times and it got stuck. It never seems to happen in the first try. Then, it only seems to happen when you have the cursor over the target, and only after leaving a lock in RWS. As Yaga mentioned, it might also happen when losing a lock, which is hard to recreate (other than moving the target out of the gimbal area). RWS_no_altitude_control_short_3.trk

It also happens when you are in MRM / TWS, bug out with cancel override and press multiple RWS down, erasing the scope (last try in the attached track). It won't come back on its own then. RWS_no_altitude_control_short_2.trk

The 9X tracks like 90 degrees off the nose, so dogfights are probably very short these days.

Is there a way to display the axis position as raw value? I never touch the axis, just "bump" the scan width and it'll work again. Plus, the axis will do just fine in TWS.

Tested a bit more and there is no 100% sure way to create the issue, it just happens every now and then when you switch back to RWS, coming from TWS. In some cases, you are unable to move the altitude setting by axis. It seems to be unrelated to the override, but it is related to going back to RWS from TWS.

Until we get the sniper pod

Probably the Sniper pod. Edit: Denmark bought the LITENING G4 in 2013. In DCS, you can search for a buddies laser code by pressing uncage on the TGP. When you aquired his laser, press TMS up to lock on to that point or press uncage again. The laser code for LST (this function) is the second code in the DED page where you set the laser code. There is a danish group "Danica DCS" in case that you are looking for a danish group for DCS.

They can close this thread whenever they want, it belongs into the main section but not in bug reports.

He is a moderator on the Discord server iirc.

I did, and it ranged from "fixed" to "correct as is but fixed in a later release" to no statement at all despite having a track and a detailed description on how to replicate the issue. Like this one or the old bug with post-designate CCIP that has been there for years, especially on the CBU-97, reported many times from different people. I guess we are back on topic now? However, I agree on this being created as a rant and not a bug report. And to be fair, someone kidnapped my bug report and added a lot of chatter + a link to a totally different report. I should maybe create a new one.