TobiasA

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.

To be fair, most of the stuff they do is pretty good. It is mainly the F-16 that suffers from long lasting bugs that don't get fixed for months and then something new comes and breaks stuff that worked. The A-10 for example is pretty fine, and the Hornet as well. And DCS as a sandbox is doing pretty well too, even if there are flaws.

This is really unrealistic as the maverick would run out of coolant before you are even close to the target, and it would do so on the A-10. On which boresight was never necessary. And it is about the same offset as not aligning because you usually have to lock targets very close. I understand that you see it this way though. But... These threads will continue to pop up as long as the system software quality is as low as on the F-16. They rework one thing that worked and screw up the hole SOI/SPI concept on the way in without anyone noticing before releasing. I can totally understand the frustration about that.

There is no way to help with boresighting mavs as of now. Best is to not boresight them at all, this way they will point to about the same direction. At least somewhere. This thread is more or less useless, the initial posting is far away from constructive feedback and there is no way to boresight mavs as of now. So there won't be any help either. There are many cool things in DCS, boresighting mavs is none of these. It never worked as it should, and even if it worked, the handoff never did, especially on movers. Let's just see if they fix it some day. As of now, I'd be totally happy with bugfixes. I don't need new functions when half of the stuff we have still has major flaws.

The manual is wrong here. MODE 1 will break the lock of an AI MiG-29 on your 12 o'clock outside of approximately 25nm. So either the manual is wrong or the implementation is wrong. Also, the selection of the band should determine whether your radar is jammed or not, while it currently doesn't really do this as it seems. All of it is wip, and I don't write this with a negative tone in mind.