Galinette

I can hear RWR spike (higher pitch) and overspeed (lower pitch, stays longer). You are going 850kts. Be careful, above 900kts the aircraft may become prone to instant self-disassembly as it can enter positive feedback pitch oscillation. I got destroyed like this recently in a BVR fight. While looking back happily at the sparrow left behind in the dust, I did not pay attention to the overspeed limit overlayed with RWR alerts... and kaboom.

I don't think files are shareable. I believe that all headsets have random factory disalignments. And that these are measured in quality control, and stored in the headset memory so that software can compensate. If ever the software doesn't compensate properly (such as swapping two values, or sign error...), it's possible to have various alignment issues across software. I have zero proof of this but this would be a plausible explanation.

1 - DCS yes - IRL to be confirmed 2 - It gives exactly the same control as USEL failure 3 - DCS and IRL - Yes, VRILLE Additional info : at low speed it gives a high risk of flipover, at high speed wing failure. You can be transparent, I know your questions are dogfight tournament rules related

Never. It's a testing switch for ground crew. The spin switch is here for the purpose you mention. It's unsure if the CDVE5 switch would even do something airborne, but we let it so that you can try flying the mode, waiting for implementation of USEL failures (see below) In real life the CDVE5 (also called USEL on the warning panel) automatically engages in cases all FBW channel redundancy is lost. It's very challenging to fly as the aircraft has a tendency to backflip, pilots train to landing on it on the sim.

It's enabling the emergency FBW channel which gives direct elevon control. No more AoA or G control.

There are lots of liveries available For instance this one is amazing: https://www.digitalcombatsimulator.com/fr/files/3318873/

Edit : there is a patch today, it's not included. But it's the last time you should need to replace it

Hi, this bug will be fixed in today's patch

Hi, this bug will be fixed in today's patch

Hi, this bug will be fixed in today's patch

Hi, this bug will be fixed in today's patch

No, it will be included now!

Try this one! HelmetIndicator_page.lua

Hmmm it seems it was fixed but not for VR. I need to find a tester with a pimax

No, unfortunately that's very likely a Core DCS render problem related to multithread. The harrier is impacted too, and possibly other planes

I don't think radio menu clickability is in any way module specific. Something might be wrong in one of your settings, I've always been clicking the radio menus.

Hi Did you try single threaded? It seems this issue is MT releated.

Issue confirmed, we will ask for a DCS hotfix as soon as possible. Here is a patch fixing the issue in the mean time clickabledata.lua

Yes. TACAN knobs, altimeter calibration knob, and IDN knob are broken as well. Most likely a core DCS issue, we'll keep you informed.

There are other missiles having the same capability in DCS. It is indeed a very good habit to turn off your jammer when engaged by a missile. Side note, the M2000C jammer does automatically perform standby cycles when the RWR detects an incoming missile and goes silent for a limited time afterwards, in order to try defeating HoJ (unless the jammer is forced on by the throttle button)

If the A-10 is jamming, the missile will home on jam. This is the most common explanation for this behavior. Side note, the M2000C can launch fox2 while keeping a lock (but here it's pretty obvious the target it outside radar gimbal limits anyway)

Items 22-23 state: 22. Press ignition switch and wait for engine to spool up 23. When engine RPM reaches 10 %, move throttle at IDLE position. Confirm RPM, Fuel Flow and T7 (Turbine Exit Temperature) increase. It tells you to set throttle to STOP before ignition switch, because otherwise you overheat and destroy the engine

It can be useful for people without detent on their throttle, finding the MIL position without going AB might be difficult. However, a bind that does move throttle from/to AB is a bad idea as it will fight against axis jitter. Adding a bind that would prevent/unlock the AB range is a better idea. I'll add one, it's not the first time someone asks for it.

This is a bug, introduced by the newly added PCA.lua. Here is a fix, it also fixes the empty tank error. It breaks Integrity Check as usual. PCA.lua

I do have a 3440x1440 and it definitely has no problem. You are using a non standard FOV, maybe from the head tracking settings.