Flappie

Yes, sir!

I was wrong. I've just tested a fix for the orange lines, and this also fixes the bug described in the OP. The fix should be part of the next update.

The range issue is reported internally.

I propose we wait for a fix for the naming bug before calling it a day, you never know.

The Kola issue was reported earlier. I've just reported the Afghanistan issue.

Yes, as long as the laser switch is set to ON, it's heating up. This means you can indeed burn the laser without even using the Shkval.

Syria was affected for a long period of time, and it got fixed some time ago. I'm pretty sure Kola and Afghanistan will get their missing zoom level too.

You're welcome. 2025-06-23 update : the M-2000 scan signal duration was incorrect (2 s -> 2.4 s)

Yes, all bugs don't get fixed in the next update unfortunately. It's on the devs todo-list.

The next time it happens to you, please record a DCS track (when exiting the mission, click "Save Track" in the Debriefing page) and attach it here.

The explanation is here:

Sorry, I read the OP too fast. Issue reported.

@cfrag It looks like the last update has fixed this issue.

This was reported many years ago. I bumped the report two months ago.

This is not an issue with the Mi-24P module. These maps lack one map zoom level.

@PawlaczGMD @Poor Yurik@BeerNfrites@Muskoka What is your VR gear model please?

There are four radio axis in the aircraft, and two of them can be locked: Left side: Receiver tuning knob (no lock) Audio volume knob (no lock) Aft right side: Wave control handle (can be locked) Antenna control handle (can be locked) If the lock writing is inclined, it is locked, as shown below:

I see two possibilities: The laser was powered On for too long and it burnt. Or you mistook Ka-50 (BS2) for Ka-50 III (BS3) - they have different bindings.

I'll ask for it in the report.

You are right. Issue reported.

I think the cause is different because these orange lines were reported a few months earlier. If you click on the latch, it will work as expected. A question remains: is the latch new behaviour a bug, or was its use made mandatory on purpose? I'll ask devs about it.

Issue reproduced and reported. It looks like two seats are Z-fighting. Thanks for the heads up.

Apparently, it happens only to some VR gear. Can affected users please name their VR gear? @Gumbers @Pizzicato @draconus

The presence of this rangefinder is now supposed to be conditioned by an argument. I guess the argument was not set properly for this video.

This should now be fixed.