Toad McFrog

PM sent.

I find that it really helps using the VR recenter headset command (in the UI layer) every time I get into the cockpit...so much so that I have it bound to a button on my HOTAS. Once you recenter, it seems to "fix" your position in the seat and keeps you from having to contort to boresight.

The switch you are looking for is "NVS mode", and it's in front of the lighting panel on the left side of the CPG station. Switching it to Norm or Fixed will change the function of the rocker switches on the TEDAC to affect the HMD.

Ah, apologies - I completely misread what you wrote as not understanding the implication.

Posting a link to Dunning-Kruger would imply he believes that @NeedzWD40 over-estimates his knowledge of the topic (i.e., he is impugning his knowledge / ability to speak authoritatively regarding the technical aspects of the Apache or its weapons systems).

I agree that this seems to be a multiplayer bug of some kind involving desync or tickrate. I typically fly with a human CPG and it is nigh impossible to hit a moving target in multiplayer with Hellfires unless shooting from directly head on or tail on, but even then odds are less than 50/50 of a direct hit. When this happens, the missile always hits behind the moving target. In my experience, it seems like the missile tracks directly to where the TADS was looking when the missile was fired rather than tracking the moving target. I have even seen 2 missiles hit in the same spot behind a moving target when the target was being tracked by IAT. Of note, we haven't tried LOAL to see if that changes the behavior, but we'll give a whirl and report back.

Same behavior for me, but I'm running a Ryzen 5 so I don't think it's processor specific. I saw a very small increase in VR (3 FPS or so). Showing CPU bottlenecked at 25ish percent utilization.

Yes, same here. In our case it seems to mostly happen as we are descending to land.

I can confirm that not having F-14s in our Liberation missions seems to prevent the freezes. When they are present, limiting the amount of F2'ing around we do also seems to help. That said, the number of data points I have to confirm this is small, so I'm not wholly willing to call it the F-14s fault yet.

Oddly enough, I just had it happen while playing in single player. I was about 100mi from the carrier at 25,000ft (so not about to land), but I was F2ing around looking what was going on. When it locked up, I just so happened to be looking at an F14 that was getting ready to land. All of the talk of the carrier made me realize that this didn't happen to me while I was running a campaign that didn't have a carrier. Very strange. I've attached the logs just in case anyone might see something there. dcs.log

A friend and I are having the exact same issue. Oddly enough, it only appears to happen for us while playing Liberation missions. It's almost always while on approach to landing whether it's carrier or land, and it's happened while playing a mission single player and while playing multiplayer on a dedicated server. The end of the log seems to be different every time and doesn't seem to point to a cause that I can find. It has also happened to me outside of the aircraft - last night, after dying, my client froze after the view switched to the carrier. Very strange, and very frustrating. I'll start collecting the logs after the freezes and post them here to see if anyone can see something I'm not seeing.

Great info, @Leg2ion. I was kind of iffy about the use of DC since it seems kind of sketchy, but you can't argue with the results. I'm guessing that I could play around with using DC to put it back to "balanced" (and uninstalling it) and then using the W10 power settings as you have. Thanks again!

I think you might have just become my new personal hero, Leg2ion. I had tried everything under the sun to fix my annoying stutters, and this did it for me as well. I created an account just to reply and say "Thank you!"