Volk.

Thanks. Yeaaah, I'm not crazy/imagining stuff!

I'm assuming it's some form of lag as it calculates the ground speed. Airspeed is indicated on the dashboard gauge.

@Kaktus maybe this helps. And no, just unbind trim reset - it's a convenience thing not on the IRL chopper - you don't need it and it will kill you if used in flight. https://www.youtube.com/watch?v=4mGpE9KFnk0

Right side wall right at the back near the back wall, lower row there's a NVG-compatible cockpit lighting. One right at the back is the normal (white) cockpit instrument lighting, while the one just left of that is a blue NVG-friendly light for the instruments. So just bottom right of the EEG switches. Probably means those. Think you need to have the white lighting off for the blue to show IIRC. NB the white cockpit lamp that illuminates everything, instead of instrument back lighting is off behind your left should as you mentioned.

Thanks. I strongly suspect it happens to all helos (which don't have auto dust protection/dust protection activated) - heard of Mi-8s and such also going down inexplicably. Though I've never tested that, since it would require much more piloting over time to do tests in it.

Cockpit textures were updated maybe 2(?) years ago when BS3 got postponed. Unfortunately I don't have any insider access/news on BS3, so my speculation on "when" is as good as yours

few different things at play here: AI helos take unnatural levels of punishment. as one example, both contact fusing only and proxy fusing hits. This from a missile that melted the opposite wing when hitting a Tu-16 in the one engine. I can't recall but they might have patched the Havoc specifically, but few months ago I still saw Mi-8's taking AIM-120s to the engine and keep trucking without smoke. Apache Hydra rockets and M230 rounds as well as S-8 rockets, no problem for them apparently. Tail hits seem to kill them one-shot often enough - I'm surrpised that Hind took even one of your Vikhrs in the tail and kept going @Go_dzilla - that's unlucky or exceptionally messed up damage model as you say. The can drop smoking, but sometimes the smoke goes out and they recover, so stick with them till they die - wait for the fireball. If they manage to land safely, they appear to get even more immortal, and you can separate pretty much all their components - they won't fly again, but still count as 'alive' and don't despawn. It's a general DCS AI helo (or maybe even AI aircraft) issue, not related to the Vikhr. As for the A/A mode. A/A H/O does make a difference: timestamped you can see when the missile triggers. However, in practice, vs. stuff that the fragmentation sleeve should kill (i.e. not an armoured tank), I've found you can shoot down e.g. SAMs midair with A/A or A/A H/O with about the same effect. One would figure H/O would be necessary for it to "catch" a supersonic missile headed straight at you, but possible the frag sleeve's detonation was enough to still catch it. Now. All those things happened before DCS 2.8. So it might have changed.

Sorry, can't do that right now - time is non-existent for me right now. Dust tests are never short - and heavily luck dependent. In these cases I had it happen fairly quickly (again following the same rules form my previous dust vid of not having exactly zero ground speed, but slight movement, and super-low), time sped up of course.

On the right - big red & white of the ejection toggles, to the right of that is weapons power, then the anti-collision beacon, then the 'gyro switch'. In the English cockpit it's labelled MH & MAN. You want to from the top position, down into the middle position. If you take it all the way down to manual, then rather flip it all the way up again before taking it to the middle.

The Shkval's been able to 'see' through trees for ages. Or rather put, visually and on the IT-23 you'll just see trees, but the contrast lock itself might get a lock on the target. Timestamped an example (which I could think off the top of my head): At that timestamp - you'll see it keeps lock. And you would have been able to lock it through the tree leaves. at the 13m43 mark I show how it looks when it goes into memory mode - which it would when the target is actually lost, and it's just retaining inertial tracking.

Oops, yeah, what you said. on the timestamp here couldn't see much shaking in the camera/HUD more than before when slowing down. Of course that's ground speed on the HUD not airspeed (unless that HUD was different in that way too). Unfortunately the other footage with speeds (the one with external views too), you can never really see a difference between the shakes as it were and it's usually slowing down doing a loop/wing over.

I've had the HUD heading tape seem to reverse & similar issues to what you described. This particular flight (with that toggle up), it seemed back to normal (pre 2.8). That said Most of it was straight on one course for an leg, one turn and then I stopped in a hover before I had a disconnect. So Can't fully say I've managed to test it definitely fixes the heading and ABRIS alignment, but seemed normal.

The low-speed shakes should go away after a few seconds of slowing down to 50kph. Should only happen again if you sped up into ETL and then slowed down again. A shaking slider would probably be good.

Just had a roughly 40 minute flight, with it set to Gyrocompass, and route mode was keeping my track very well to within 1 degree (no wind). Also the Shkval seemed to be aligned on the ABRIS although I didn't fully check it. Was a cold start, and the magnetic variation & lattitude appeared to be correctly set up as at mission start. So probably only needs the toggle flipped up like you describe.

Been working for me: Easier if you can see the speck out the canopy rather than trying to slew-lock looking purely down at the IT-23. Locking range is shorter than for static/slow moving targets, and more likely to lose the lock. Generally still further range than an Igla's max range. Of course if it's low light then it won't work. High ranges it might be easier to slew heads-down. Full disclosure: I can't recall if I've used slew-locking vs. an aerial target in 2.8 yet.