S. Low

These knobs I have circled on the right and left that change the map cursor position. I can't for the life of me find a keybind for them. I'd like to map them to my throttle just in case.

Both the default keyboard keybinding, and my controller binding were attempted. The rotary knob merely swaps back and forth from 863 to ARK1. It doesn't actually rotate through all the selections, clockwise or counter clockwise.

How is it correct behavior that rudder pedals get stuck when you don't have Yaw AP turned on? The video posted here of the guy in a hind cockpit shows how the dampened pedals work, and if you push on one side then the other returns. That isn't being stuck. What am I missing here?

If you have a flight where you get pitch oscillation that you think is a bug, when you quit out of the mission save the track file and upload it with a time stamp.

Here's some video evidence of low performance from a youtuber. Start at 11:45 if my link doesn't.

Not my video but it shows the pedals being "stuck". Start at 9:41 if my link doesn't start there.

If this isn't a FM bug (I can't say one way or the other), what would be the piloting cause? Also has anyone else experienced the GE pushing the Hind up and out of GE? It's almost like I'm constantly bouncing in and out of GE, especially with this near constant oscillation that I don't feel is PIO.

Don't descend straight down, instead descend down and forward.

This isn't a huge deal, just a bit of an irritation. I have two monitors. One for gaming and the other is for info or youtube or whatever. Before 2.7 if I paused DCS to go to my second monitor to do something then DCS would stay up. But now every time I click on my second monitor, DCS automatically minimizes. I don't know why this happens. Any ideas?

If that happens again remove your feet from your physical pedals and check the position of your virtual rudder pedals. Are they stuck to one side? If so, is your Yaw AP on? If not, save track file and report it here please. It keeps getting reported sporadically but we need proof.

I'm just teasing a bit, but even if the tracks are desynced its better to have some kind of physical evidence. Every single thread the testers/mods are like "Track? track file? Track file missing."

There's multiple reports of this in Controller bugs. I don't know that ED has enough solid evidence yet to consider it a bug.

https://youtube.com/c/HelicopterLessonsIn10MinutesorLess

Depends on the aircraft. Taking the Huey as an example with no autopilots or any assists, the rotor (I don’t remember off hand the direction it rotates) transfers a lot of torque force to the airframe, cause the frame to spin. Can’t remember if it’s counter spin to the spin of the rotor? Anyway, on the Huey it spins the airframe to the right/clockwise. So you need a bit of left pedal and left stick to counter it on take off and on hover. once you enter ETL / forward flight, you need less left pedal eventually because the rotor uses less power to create lift. Then once you get near top speed you may need right pedal to stay straight because the airframe is helping with lift and rotor isn’t doing as much work, so tail rotor is over doing it. “In combat” depends. Combat landing, take off, hover? Combat turns? Generally speaking the helo pilot is almost always working the control surfaces a bit. But when you enter a bank to turn, you’ll need to probably adjust collective, pitch, and pedals to keep the bank angle smooth. That’s the Huey. in the hind with autopilots and dampeners and a heavy frame designed for stability you can trim out to flight hands off for the most part thiugh I don’t trust yaw autopilot so I keep adjusting pedals manually

If default in all helo modules is for FFB then I’m sure I’ve been doing something wrong lol. I don’t have a FFB

Uh what? Lol. I think you’re in the wrong ... place

Post this in the controls bug section. I’m trying to investigate this with a tester

Yeah I didn’t realize it at first either. Double check trim types menu in special options. Default: more like ka50, press and hold until stable flight then release Center option: more like Huey, move stick to stable flight then press trim once and release your physical stick to return to center third option is for FFB sticks I think

I actually felt like my Pete crosshairs were low lol. They sometimes pop up way beneath the pilot sight.

If I remember I’ll make a quick video showing what it’s doing. Requires me getting out of a birthday party.. hmm. “honey I’ve got important work to do...”

Key assignments: im at work so I’ll try to remember. cyclic: trigger 2nd detent - weapons release brake lever - wheel brakes axis top center hat - trim up, down, left, right top center hat “click” - wheel parking brakes top right button - discord and ts ptt bottom right button - in game radio menu Bottom middle hat “click” - ......(will update) Hat on left side low of stick - “click” and hold, then release for Trim set. Back click (towards me) for Trim reset Throttle: Put landing gear on a switch somewhere. Mines on the bottom left base switch. Use a four way hat for AI Pete. Left, right, down, up for menu movements. “Click” of the hat for opening the menu. Then bind a nearby button for ai weapons setup.

Virpil mongoose stick and throttle, crosswind pedals Cyclic axes: +10 curve Collective: 0 no curve Pedals: -15 curve, 4 deadzone I use a -15 pedal curve on all of my dcs helos. They never have the sensitive authority that I think they’re supposed to have. Setting to -15 gives you a lot of authority upfront where you’re using most pedal corrections. The cyclic needs a +5 or 10 on the hind IMO. I can’t imagine it handling like a light helo on the ground in real life. Maybe it does.... but the +10 will make you a happier player

I’m analyzing controls as I enter the mission. Free flight Syria mission does not have stable flight at start. It has full left pedal which creates a left bank. Trim reset clears the pedal situation and I can go back to flying. Weapons range ground start is randomized. My pedals sometimes start full left, sometimes full right, sometimes neutral. Most times, being aware of this behavior, I have time to press trim reset to recenter before i spin around on the pad and crash if i spawn in pedals full right, I agree with you that simply touching controls returns everything to normal if I spawn in pedals full left, it requires trim reset. All of these behaviors can be corrected and make the game playable as far as I can tell. My issue is there’s an underlying bug/issue here that is randomizing your controls trim (and the controls helper) at start.

It’s exactly this, though I find that bleeding airspeed from 270 down to 50-70 is quick and easy, but managing the final bit of airspeed requires more pitch up than you initially are comfortable with because you’re blind. Gotta angle the nose away from where your landing pad is