Belphe

Altitude and Attitude are HOLD modes but they are "passive" (as they don't "fly" the aircraft for you when enabled) and their narrow authority won't e.g. transition a travelling aircraft into a hover - you need to do that manually. Only when in a near-hover state (I believe it's speeds < 5kts) will enabling the Attitude Hold put the aircraft in a controlled hover. I strongly recommend you learn more about these systems as they behave differently depending on your speed and altitude.

The Apache does not have a true trim system known from other helicopters in DCS, e.g. Ka-50. Instead, it's using a stabilisation system that possesses some degree of authority over the controls when enabled. It can be temporarily overridden to allow manoeuvring and kicks back in when released. For more information I suggest reading through the Official Manual, Chuck's Guide for the Apache and/or watching videos on YouTube.

The largest Military Airshow in the World takes off in less than a month! I hope that at least some of You are going. Is ED/TFC going to be there in any shape or form? See you there! https://www.airtattoo.com/

Hi, Since there haven't been many replies to this post and the issue has not been officially addressed, could anyone tell me is this actually IS a problem and will be fixed in the future? Thanks!

Awkward, I actaully have to add right pedal now during takeoff...

Yes, same here and it makes sense (although just as Casmo says, it is wrong). We have to apply so much left cyclic to counter the right slide that we load the left wheel way past what should be reasonable. The only thing that holds us motionless is the friction of that left wheel against the surface and if we choose to lift off slowly the aircraft will tip over. Doing it faster will likely induce a left drift which needs an instant counter to the right. Wiggle wiggle wobble wobble

Hopefully, a few subtle but meaningful tweaks to the FM in the patch today (subject to change)

This is saddening. I'm spoiled by Virpil's configuration tool for my cyclic and collective, with curves, deadzones and analog-to-button functionality and in the meantime no one can manufacture a simple gaming pad with customisable axes and buttons..

I purchased the 8BitDo Pro2 controller but using their software so far, I have been unable to make P1 & P2 pads underneath the device to work. Also, the two buttons right next to the analog mini-sticks are not recognised by DCS, not to even mention splitting the triggers' axes into a stage one and two dual-purpose buttons. Is there a software out there that could unlock this device's full potential?

Precisely what I'm experiencing! All the money spent on extensions and precision oriented gear and we have to dumb down their sensitivity by flattening the curves to actually have control

Has anyone else noticed that moving the cyclic no longer affects the rotor blades animation when the rotor is spinning? As soon as the disc spin animation switches to "fast", blades show no or close to no movement. I don't mean blade pitching, rather lifting or lowering them at more agressive cyclic operation.

Even with us building more and more advanced and precise controllers for our pits we continue to struggle with flying the Apache as it is seen in real life videos. Yes, those guys are PROs who are practically living in those helicopters. It's their job to be good at flying them while for us it usually is just a hobby. Also, G-forces help them a lot. I don't need to mention that the current FM is WIP either... However, I believe we need to realise that even if ED models the Apache FM to represent the real aircraft 1:1 (which I suspect they strive to do!) we still won't be able to control it as well as the real pilots (courtesy of the above-mentioned inertia vs us stationary in our chairs, stereoscopic vison vs flat screens (if one is not using VR) and professional trimming systems vs springs, false dampers etc.). The question that arises is: should the FM be made to be as real as it can be from the technical point of view (and none of us will ever tame it as well as the real-life guys) or should it be "tweaked" to the realities of our home pits (so that we could easily get the aircraft to do what it would normally be able to do but wearing flip-flops ). Pardon me for expanding a bit around this subject.

Hi, What other gaming pads would you suggest using as TEDAC controllers apart from PS and XBox? Thanks!

For me, it feels much more wobbly in the hover and slow speeds. I can still hover fairly easily but getting there is like trying to stay still while being submerged in water. Before the patch cyclic movement would produce instant desired aircraft reaction. Now, I need to counter my cyclic deflection to stop the aircraft movement as going neutral would not suffice (just like in space!). I'm not saying it's incorrect! Just different and it'll take time to get used to. One other thing I found much more problematic is strafing sideways. The Apache develops awkward roll movements that quickly get out of control even at speeds of 30kts even though it was fairly easy to go sideways at 50kts before. Again, this could be true to the real thing... Oh and now I need to push the cyclic slightly forward from the centre to stay in hover after a vertical takeoff (that centre of mass shift?).

My native resolution is 5120x1440 (32:9). I need to zoom out to 66% of the total slider authority for the cockpit to assume the "correct" scale, comparable to the one on 16:9 monitors. The above mentioned symbology doesn't scale 1:1 with geometry and creates "fat"/thick letters and numbers when viewed on HUD (especially visible in the Viper, Hornet but less in e.g. Tomcat). There are threads about this issue on this forum that take it as far as editing .lua files for every aircraft separately so trust me: I haven't made this issue up :)

HUD/IHADSS/MFG symbology doesn't scale the same way as cockpit geometry when zooming out.

I don't need to zoom in at all because I have a big a** monitor. Are you totally blind on the thick font on both MFGs and HUD?

Zooming in or out will mess up your HUD/IHADSS

Hi, 3rd week into using my VPC MongoosT-50CM3 Base and I noticed an issue related to calibration. My in-cockpit LAT & LONG arrows on the cyclic base do not align with the actual logical values on the Control Indicators in DCS or the VPC Configuration Tool. When I set the cyclic in "perfect centre" according to the config tools mentioned above and enter the simulation, the arrows are off as seen in the screenshot below: When I actually align the cyclic to match the arrows in pit, the value readouts are incorrect in both DCS and VPC: I have recalibrated the CM3 Base using the up-to-date software. I have also reloaded the firmware, reset it to defaults under Windows and finally calibrated with VPC having it as the only plugged-in USB device at the time. Min and Max deflections as well as the centre points have been calculated and entered after the calibration to "clean up" any imperfections. Deadzones and Smoothing have been disabled. I am pretty confident that the cyclic is set up correctly. The misalignment is small (between 1 and 2%) and with 60k points both in X & Y axis it probably doesn't affect flying too much but it's one of those things that could keep me up at night... Has anybody encountered a similar issue? Any ideas on how to resolve it? I'd be grateful for your help. - Belphe

The missile battery operates for 45 seconds. You do the maths considering ambient temperature, air pressure, wind, actual flight path and target state. Easy peasy!

This!!! Next step is dampers + stick extension. With that on board you should be rocking "stick with no springs or FF" trimming method like a boss! Let them just fix the Trim Disengage and you're golden.

*for Super Ultrawide monitor setups (32:9++)

Experiencing the same bug

Worse for me. Pay attention to your idle torque. It is now 20% instead of 17-18 before the patch. To get the torque down you need to apply a little right rudder. Is this true to the real thing? Even if it is, try the following: - fly straight e.g. North at 35kts - yaw right 90 degrees but maintain North direction of flight (strafing left) - yaw back left 90 degrees maintaining the speed and direction I find it extremely difficult to yaw back left and sometimes even enter a spin to the right (rear rotor stall? Is it so easily done in real life? 35kts is not the maximum strafing speed). I believe that this is caused by an insufficient rudder force caused by shifting the center of authority in the FM.