admiki

You might want to check attitude. You constantly come here to ask questions that are, to be polite, on basic level of understanding Apache. You have already been told to WAS rockets (USE WEAPON ACTION SWITCH), not select them on weapons page.

This is the first I hear about this.

As long as you don't have stutters, 35 FPS is fine. Anything above 24 FPS brain sees as a smooth movie. Yes, it sucks that clouds have that much impact on FPS. Could ED make them better? I don't know, I'm not a programer.

You have 100k to throw at it? Good for you. You are correct, this is a SIM and it should be fun. But that does not mean you can just jump in and be an expert. That's what makes it a SIM. To get to the fun level, you have to put in some work. You said it yourself, it's frustrating. It is frustrating for you because you have no idea why it is doing whatever it is doing. If you don't want to put work in, it's fine, but then you can expect to get a snarky response from time to time. Believe it or not, you are not the first person that asks this exact kind of questions.

There is no other way. I know it sucks, but just keep practicing. First pull back on cyclic to start decelerating and keep that attitude (don't worry about balooning up) and then drop collective until you stop climbing. Keep practicing. With time, you will learn how much you need to pull back/drop collective. Muscle memory is a thing.

Wouldn't autopilot trim in more right pedal in OP case? And his collective wasn't high in the first place. My guess is that AP trimmed pedals to the left (comon situation at ground hot start) and then got disconnected somehow, leaving him with limited right pedal.

I have no idea, never been that high in whirly bird. I don't know if hypoxia is even modelled in DCS?

All of your points, except 3, are de-sync issues. As for your point 3, 18000 ft is not a hard line with on-off state. People can pass out from hypoxia at a lot lower altittudes and they can stay awake a lot higher.

Mark in yellow square is an indicator of how much you can move pedal to the right to avoid damaging tailboom. It's an automatic system. Was this a hot start helicopter? And did you turn off yaw channel autopilot?

I disagree on cloud being pointless. Cloud shadowing affect how good your observation of the ground is. Try flying in the mountains with low ceiling and see how much you pucker.

I'm not sure if that is implemented or not, but I was shown how infantry would bug off if you hit close to it. Close hits would supress for about 30 seconds or so. And supression radius was tied to type of weapon used.

#twoweeks

I'm not seeing any problems. Tested fully loaded and empty, level and descending deceleration.

Go to Apache/A10 tab and click on modifiers on the bottom. You probaby added those as switches, not buttons

I know that one, but Aeria refers to some bind other than AI Petro menu

Which bind is that?

I think you got confused here. Helicopter is spinning not because main rotor is producing too much torque, but because tail rotor is producing too much thrust. For fixed pedals position, as long as there is full RPM, tail rotor thrust has nothing to do with how much power you are pulling .

And once again, pedals being in the middle does not mean there is 0 thrust made by tailrotor and does not mean there is a balance between torque produced by main rotor and thrust made by tail rotor. So, if you don't have access to real life Apache documents that state that current implementation of tail rotor is wrong, ED should not change it just because you think it's wrong.

I thought that CMWS, at least older version, can just recognize missile launch, not where it is going to?

Sort of same bug with R-60. Regardless of whether safety cover is open or closed, if you press and hold trigger it will fire both missiles. If you just tap the trigger, it fires one per press.

Temp, alt, weight, wind? Any of those factors could influence the outcome. You have track file?

No, but you never do pull the same amount anyway. Mission weight, temp, altitude changes all the time, so you never were pulling "2.354 inches from bottom to get to hover". You fly and move controls as needed to get helicopter where you want it, there was never a formula with exact position of each control. Yes, there are changes in required power, but you saying that you need to relearn collective makes it sound like you now need to move collective sideways to get to hover.

It might have changed on where exactly you need collective for any particular phase of flight, but relearning the collective is a bit exagerated IMO.

Post a track file

I'm also on latest OB, simetrical load.