Sharkku

That markpoints get erased with WOW is just so utterly stupid. If it is correct-as-is, I can only shake my head in disbelief.

I noticed this as well. TDC depress produces no diamond anymore.

Disregard for now, I don't seem to be able reproduce at the moment.

Before I file a bug report, I'm asking here. Has anyone else experienced this? Since the 2.7 update: A/G mode, Gun selected, Rdr alt or AGR doesn't matter. The bullets land way beyond the target, the pipper seems to be placed too low.

Glad to hear it's being worked on as a priority. It completely ruins the VR experience. I was very disappointed when I loaded up some heavy cloud layers and noticed this.

Steps to reproduce: 1. Spawn in cold start Hornet on the Supercarrier in multiplayer server. 2. Take off, then die somehow. 3. Respawn without going to spectators in between. Hornet will spawn on the catapult, attached, with wheel chocks applied and non-removable. (This bug is especially annoying on the server I play, since it has persistent and limited fuel and weapons. If you spawn, you have to de-fuel and de-arm before going to spectators, otherwise the fuel and ammo will be lost, and you will become impopular amongst your fellow pilots for wasting resources. De-fueling a fully fueled Hornet takes quite a while.)

Well, you wouldn't call "Hornet ball" if you are in a, say, Tomcat. Then you say "Tomcat ball". etc.

I agree. The convention was: right mouse button to turn a selector clockwise, left to turn it anticlockwise. I would like it to be this way.

Great if you fix it, thanks Matvey!

I use a very similar setup, with main spring removed from the TM Warthog HOTAS stick. TM Pendular rudders are costly, but boy, what a difference compared to my old Logitech plastic pedals. I have the Index headset now, pretty similar to the CV1, just a little higher resolution. Used to fly with the CV1. One important thing: Do you have the collective axis reversed, so that you increase lift/collective by pulling backwards? It mimics real life more closely, and enabled me to fly a real helicopter competently on my first lesson. Really recommend it.

Is this perhaps the same bug as this: ?

In the bindings, there are two different entries for pilot and co-pilot control stick buttons. This means that every time you switch between pilot an co-pilot you have to go into settings and edit your bindings.

And hello to you, sir! I believe Draconus beat me to it here above!

Poor prioritization by devs. They have a list of fixes that they are working through in order, no matter what. This is literally a 5 minute job, that would make a lot of people happy. But it doesn't get done, because there are other things on the prioritization list, and noone cares to move it up the list. It is utterly ridiculous. I guess I'll keep editing the file after each update...

Cheers, thanks for the instructions! However, my opinion is just that, you shouldn't need those instructions. You shouldn't need to create channels or anything. Because there is always some people who don't do it. It should be on by default, talking locally to those in the same aircraft with you.

Multiplayer is awesome! One thing I found myself lacking though, was just being able to open my mouth and talk to the guy sitting next to me. No SRS, no Discord, no external plugin, no push-to-talk is what I want. DCS has voice communication, I know as much, but it doesn't seem to work? I'm sure I'm doing something wrong, but I shouldn't have to configure anything. It should be active by default if you're in the same space as someone else.

Woooohooooooooo!!!!!!!!!!!!!!!!!!!!

You know, it can be like this with old equipment sometimes. Oxide layers on the wires, rust, poor maintenance, can lead to faulty connections.

Yes, I have observed this behaviour also. I would definitely consider this a bug.

No, QFE setting causes your altimeter to read 0 when on the ground at the airport for which you have set QFE.

I have an Index, and I have the same problem...

This is the DCS equivalent to "did you put the plug in the wall socket?" Surprisingly often the root of the problem.

Yes, it must be the difference between the true altitude and the density altitude. Is it very warm in your mission?

Yes, it's possible. Use TOO mode, designate a target with TPOD, and the coordinates will transfer to the JSOW automatically.

Well, that would work if the field elevation was 600 ft, sure. But the trigger shouldn't check for radar altitude or QFE, it should check absolute altitude. And you shouldn't have to set the altimeter to field elevation anyway, if you set it to correct local atmospheric pressure, it should give you the correct altitude. The original post states the weather used was standard atmosphere, 29.92 inHg, which is also the QNH setting. Which is set by default in the Hornet. Something else is going on here. Please post your mission and a track.