NightMan

Mine? Mine is 2.8.0.33006.

The sound of the engine is reduced when the canon is fired, almost to the point it is cut off and then resumes when firing ends. One should expect the sound of the canon to overlap the sound of the engine, but that is not what is happening.

This problem shows up in the Change Log as solved for the version DCS 2.8.0.32937 Open Beta: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.8.0.32937/ I was playing last friday, after the update, and the scores were indeed working.

It is at least amusing to watch the track. The chopper flies in circles and the heading tape on the HUD does funny things! Ka-50 - Auto-pilot in Route Mode, Heading data selector in Manual Heading.trk

Ka-50 - Auto-pilot in Route Mode, Heading data selector in Manual Heading.trk

Sure. By the way; is there any way of transferring the post?

Since version 2.8 that the cockpit of the Ka-50 no longer appears symmetrical. If we look at a screenshot taken from the interior, is looks like the left window bar is wider than the one on the right. However, if we look outside, they look exactly the same width. Compare it with a screenshot from version 2.7. I know the window on the left side is taller, but that doesn't seem to be the reason.

I verified what you said and you're right. However, I had all my controls set in version 2.7 and they were working properly, so something must have changed. I have an Excel spreadsheet where I keep all my settings. It allows me to standardize controls between models. I went to see and the "Camera transpose mode (press and hold)" already existed in FC3 models, with the control LShift-F1 associated, but it didn't prevent the one in General to work. I will reassign.

Since version 2.8 that the "Camera transpose mode (press and hold)" control stopped working on FC3 models and in the Su-25T. Maybe it is because this control for these models is on "General".

I've always noticed this problem, and now I finally have the time to report it. As the tittle say, when we replay a track, it rarely replays as it was recorded. For example, in the tracks I uploaded, I was firing at the trucks on the hill, but when I replay them I seem to be firing at the trees! Tracks don't Replay as they were recorded.zip

Since version 2.8, the blades stall all the time and the helicopter shakes almost uncontrollably with extreme ease. I doubt this is as in Real Life. We have several Ka-27s, mostly used in firefighting, and I don't remember seeing them shake this much. I know it's not the same machine, but they share the same kind of rotor. Maybe ED should have a very close look at this. Ka-50 - The Shark has the shakes.zip

And the Ka-50 got the "shakes". Now, the blades stall all the time and the helicopter shakes almost uncontrollably with extreme ease. I doubt this is as it is in Real Life. We have several Ka-27s, mostly used in firefighting, and I don't remember seeing them shake this much. I know it's not the same machine, but they share the same kind of rotor.

I didn't know that. Very interesting and useful. I will make some tests at higher altitudes; 5nm is WAY too close, especially when a Tor or an Osa are involved, so, if I want to be at let's say 7.4 nm I will need to be close to FL20. Thank you Sir.

I suppose you are correct. Attached are a couple of new tracks. The behaviour is the same with both planes, although disappointing. I think the problem occurs when we try to select a target "sideways". In the first tracks I uploaded, with the A-10C II, I used the HMCS to find the target, and so the TGP had the target to its left, therefore "sideways". With the A-10C, I had to point the nose towards the target in order to find it. This time I built a mission with one waypoint very close to where the vehicle would be and at ground level, so that I could just make that WP a SPI and slave the TGP to it, which allowed me to fly in the exact same conditions — straight line parallel to the target. What I found is that "sideways" both fail in locking and following the target. If this is the correct behaviour, then, please excuse me and archive the topic. But I ask you to please check into this, because it doesn't make sense in having to face the TGP head-on towards the target so that we can lock it — it renders the TGP useless. TGP has problems in locking and following targets.zip

You are right. I just reused the track from another topic. I will make new ones ASAP and provide them.

I'm not sure if this is really a bug as I don't know how it works in real life, but it surely appears to be. This happens in the A-10C II but not in the A-10C. In the A-10C II the TGP has enormous difficulties in locking and following targets, but in the A-10C it locks and follows very easily. The planes may be a little different, but aren't the TGPs the same?! That would mean the behaviour is wrong in one of them. A-10C - TGP has no problems in locking and following targets.zip A-10C II - TGP has problems locking and following targets.zip

That doesn't make much sense however, since it wasn't and stil isn't like that in the A-10C. Did Fairchild Republic change that in the A-10C II?! Previous Behavious - A-10C - Changing MFDs from MAV to TGP doesn't change WHOT to BHOT.zip

Here are a few tracks where the problem can be seen. The third one is where it is most obvious. Bug - Ka-50 - Shkval jumps after a target is destroyed.zip

Like I said; I'm not sure if it is a bug. Anyway; it is very annoying.

I'm not sure if this is really a bug as I don't know how it works in real life, but it surely appears to be. This hapens in the A-10C II but not in the A-10C. If we set the TGP to WHOT, switch to the MFD where the MAV is, change the crosshairs and symbols to "Maverick black hot" (according to the manual, page 94) and go back to the MFD where the TGP is, the TGP changes to BHOT. Apparently, changing the MAV to "black hot" causes the problem, but not changing it to "white hot". This is not new in version 2.8; I've noticed it before. Bug - A-10C II - Changing MFDs from MAV to TGP changes WHOT to BHOT.zip Previous Behavious - A-10C - Changing MFDs from MAV to TGP doesn't change WHOT to BHOT.zip

Like the tittle says, since version 2.8 that the scores are not being updated.

Indeed. But I think they launched it in a hurry only to show off with the Halloween easter eggs.

Since version 2.8 that the light changes between views. If we look to one side, let's say right view associated to one Snap View, the light dims progressively for almost a second. When we release right view the view returns to default and the light brightens up progressively for almost a second. So, the transition in light conditions is not immediate between views. Also, the default view is WAY too bright. Here is a link to 2 videos showing the effect: https://wetransfer.com/downloads/3abe212be7c3016aaab468d0b411864d20221103183618/a43bce614d25206b505f07ce157c122120221103183641/2c1a0c

Has anyone noticed that BS2 and BS3 could in fact be Bull 5h1t 2 and 3?! Beta testers usually ask for a track, but if you replay a track you will see that it NEVER replays the same way it happened.