Chibawang

I THINK he refers to the cross dropping down low as he pans right, and he has to go a bit further than the target and then up/left to correct. But again, this is totally irrelevant to the issue being reported.

All due respect, I think you're overcomplicating the subject and causing needless confusion. The point is there is an obvious problem with slew rate on the mavericks being much higher than the other sensors. Seeker instability is a separate issue, I don't even believe that is modelled. Hardware parity is also a separate issue, but concessions sometimes have to be made for home hardware use. ED does this all the time. But again, I don't think that's relevant to this whatsoever.

Ah, so I would need a shift for that...

I'll have to try that! How do you select an item once highlighted?

Do you mean like a shift state on the hat? I use that for view changes. I don't know, do they use head movement? Voice would be nice of course, but I think you still need a menu for those that don't want to go that way. Also, if you're not sure what you need to be saying you can look at the list.

@Wagsmentioned this during the Q&A and it got me thinking about what it might look like. I think a good solution would be a wheel menu or something similar, but the items are highlighted by moving your head. So for instance: Hold comm switch, look slightly up/left to highlight entry, release comm switch. The main problem with the current menu is reliance on keyboard/mouse, and scroll/selection buttons on the HOTAS would take up precious buttons. What do you guys think?

The question is then, does this negatively impact alignment with your head in a natural position, after the DED alignment process? I've always instinctively rolled my head to fix the error during alignment, but at times I've noticed some larger errors in the HMCS afterward.

nullThanks!

Luckily for me I guess, my package isn't so heavy as to feel claustrophobic! That is what I mean yes, I usually do it before taxi. Still, the sensitivity in DCS seems way too high even after curves and deadzone. Lowering saturation made it much more managable. Not ideal I realize, but I haven't noticed anything wrong in the air, even during BFM. Which leads me to believe NWS is just too tweaky. Supposedly, they patched a lower friction value in one of the gear tires that was supposed to fix the drift on takeoff, but it's still there. That only took them multiple years to realize one of the values was off, after countless complaints and bug reports. I wouldn't be surprised to learn there's another issue like that remaining.

LMAO, that's a perfect name for them. Yes, that's what I use. I really only fly the 16 these days, so basically just need them on the ground. Otherwise I would be more tempted to upgrade. But they work fine in O T H E R S I M

I'll look into that, thanks for the tip. Yes I can't really fly with feet on pedals, but that's a separate issue. Something about them goes wild whenever I first log in, have to remember to warm up the axis, and even then the steering is insane without bringing down the y axis by a lot. It's caused me a lot of embarrassment before I figured out a workaround.

Are they really? I didn’t know that. Well anyway, most people don’t seem to have my issues, so I think it has something to do with how DCS interfaces with my specific thrustmaster pedals. The cheap ones. I’ve heard of others having the same problems with those. But other sims don’t share the problems so it isn’t the hardware itself.

I am aware, I did this for NWS purposes. I will acknowledge that I need to fully deflect my pedals to the extremes every time I load in, otherwise the ranges of input are way off. A light pressure on the left rudder results in running off the taxiway. Even after doing so the problem exists without control mods

Yea I had this problem, thrust master pedals. Only solution I have is I use a slight curve and cranked the Y axis saturation way down. That fixed it, and after testing rudder authority doesn’t seem affected.

Testing?