UncleStains

All good advice here. When I was learning it helped to listen to music or a podcast. It occupied the part of my peanut-sized brain that was making me overshoot and allowed instinct to take over.

Yep, that's how mine is set up. If your stick is a little loose, a tiny deadzone can help it stay in autopilot.

Agreed. Also, there are keybinds for gunsight power and brightness but they don't appear to work. Would also be nice to have keybinds for each position of the fuel valve, supercharger, and mixture. Loving this module!

Your PERF page shows 85% torque is required for IGE hover, which agrees with your observation that you need around 85% to take off. It also shows that you need 107% for OGE hover, meaning that you are too heavy to hover OGE. There are performance limits that come into play long before you reach MTOW.

I don't know about this particular mission, but you can definitely embed kneeboard files in a MIZ file. Just rename the file from *.MIZ to *.ZIP file and then you can dig into the folder structure and find them.

Do you have any curves set on your axis controls setup? Curves are generally incompatible with FFB and this sounds like what happens when you try to use curves.

Holy cow! I took this advice and the F-16 suddenly became 10x easier to control. I fly with a VPForce Rhino FFB stick, but for the F-16 it is basically set up as a normal sprung stick. Turned on the X and Y gradients with zero deadzone (on the special settings tab). I have no curves on the axes in the controls setup page. Loaded into the Persian Gulf A-A refueling mission and had my first ever DCS A-A refuel with zero disconnects! Then I tried a few landings...it was like I was on rails. I'm convinced!

I'm not sure if this is related, but if you have the MARK page up on the DED you are not able to use TMS up on the HAD to lock targets. Just dobber left to get back to the CNI page and you can lock HAD targets again. No idea if is this is accurate to real life.

I've used them on helicopters but never a jet.

I'm pretty sure the boresight button on the collective is for older versions of the Apache and it does nothing in ours.

The gunfire FFB doesn't work if you have unlimited ammo set. As I understand it, the effect works by looking at the ammo count. So if the ammo count doesn't go down, no effect. This is for the VPForce Rhino implementation and I assume others.

The chevrons mean that your radar is detecting a jamming signal. In this case, the radar can't resolve a distance, so you get chevrons at the top of the screen on the detected azimuth. Sometimes you'll see the chevrons on top of a radar contact, indicating that your radar was able to burn through the jamming and resolve range to target. I hope that translates!

I'm just impressed that you managed to take down an F-15 with an Apache!

Ran M02, the Blackhawk down one, with 2 and half crews last night. That was a tough one! While none of our Apaches were damaged, the convoy got obliterated by a T-55 on the way out of town. I wish I could have told Blowfish to exfil south, the way they came in, instead of heading west through the city! Once we established that nobody was shooting at us, we hovered along the ridge southeast of town. In hindsight, we should have spread out more on the east side and chosen a higher altitude. Since we were bunched up and low, we didn't have great visibility around and between buildings. We also didn't coordinate fire well or split up the town between units. We had some delays setting up our squad datalink during startup, so maybe we arrived too late anyway? Does the convoy trigger at mission start or does it wait for you to fly over? The voiceovers made our failure a real punch in the gut. We were much more invested than the generic training missions I make. Overall a good learning experience, which is exactly what I wanted for weekly training. We are going to continue running the campaign and will revisit this mission when we're done.

I know how tricky the DCS mission editor can be!