ruiner_

Disabling super carrier also made it much faster for me. Still very slow, but 10 second delays instead of 5 minutes.

To add to this, it seems my RAM isn't full but I have a cpu core that is completely maxed out while this is ongoing.

Same problem here, selecting a slot on the contention server takes forever.

You should probably watch a video on autorotation instead of telling everyone else they are wrong

Likely settling with power, ie you were too heavy and the engines could not provide the torque required to arrest your descent. Tell him to speed up to gain some translational lift to get out of it.

I'm sure this version got put into bypass at times, unless the datalink had the capability to send realtime rifle info and that was integrated into the cmws but based on what we know about the datalink that does not seem to be the case at all. I was thinking this was going to be a lost cause for you with no public information available but I think I have found something at least semi applicable. I'll pm nineline about it.

For all of the logic you cover in your post you base it on a 5km max range, ignoring the fact that there are a2a ir missiles with far longer range. You can't tell me you would still have enough flares in auto in a busy environment with friendlies firing off a lot of missiles just by making it run the program a bit shorter.

Curing the tads to the fcr target will also allow you to determine if it is alive or not. Firing off a salvo of missiles without iding your targets is a bad idea.

I've only seen them do that when the FCR doesn't have LOS on the targets that are still alive. I've seen this a few times and either raising up or repositioning solved it.

But that's not what you said.

I think saying it is caused by mods based off of one person's account of it working one time without a mod is a bit anecdotal.

There's a TGT button on the left side of the FCR page. You hit that, slew the cursor to a target and cursor depress. That will generate a new target point.

I'm not sure how we can say this in a different way so you get what we're saying, but it's because your collective is not in a position to hover when you switch back to the pilot seat. George has moved it on you. So when you touch yours it is set way too low for a hover and you lose control. As soon as you move any control it will resync with your hotas away from what George had set.

Not having watched the tracks, what is likely happening with your collective is when you jump back into the seat the controls will match what George had them set to. When you move your collective, it syncs back up with your collective and if your collective is far out of position from where George had it, it's going to cause a large adjustment.

I believe from the cpg seat you can slew the tads to the fcr target and switch over to the tads, allowing you to lase and rifle off multiple limas like you would have pre fcr.

Do the RWRs for any playable aircraft, at the time period they are modeled for, detect mm wave radar at 40 GHz or whatever the FCR uses?

I've come up behind a human operated hind and my first Lima came in from the top right and smacked into the rotors and engine. The engine smoked a little but kept running with no serious damage. So it's not just the AI damage model.

You need to use rudder to counteract the forces from the tail rotor. When you lock the tail wheel again, it won't actually lock until you roll forwards with it straight ahead. Try unlocking the tail wheel before you pull any collective, counter that and slowly increase collective to see how much rudder you need.

What shadow settings are you using?

The 737 max also begs to differ.

When in the central trimmer mode, the in game cyclic position lags only slightly behind the physical position of the stick. In either of the other two trimmer modes the in game cyclic moves extremely slowly, often up to a second or more behind the physical stick. You can see it by bringing up the control indicators with right ctrl enter.

I just wish the different trimmer modes didn't have such a large discrepancy in deflection rate compared to the centering stick option. Does no one else here using an unsprung stick have this problem?

There have been at least a couple of posts about this in the main Apache forum but I have not seen a bug report or any backing evidence of this yet. When in central position trimmer mode the cyclic reacts almost instantaneously, however, I fly with a dead stick configuration and when you use the joystick with no springs mode the cyclic is very sluggish and the in game control trails far behind the physical stick position. See youtube video where I am deflecting the stick at roughly the same speed in both: