Kenan

"Lift a finger"? That would imply an easy fix. And that is not the case here, if you are reading the same threads as I do, that is. So, majority of people here who are experiencing problems with the patch are yet to find a "lift a finger" type of solution you're referring to. For most of us it's far more workload than that. So, I hope you understand my frustration here. And where exactly in my post I implied that "nobody should try and play the game" because of these issues? Please do tell. I think it was quite clear I was speaking on my own behalf?

I find it amazing, reading the threads where players refer to post-update drop of performance (meaning, before the update, DCS ran fine) that there are people on this forum twisting themselves in knots, trying to treat this is as a "user-related" error and offering many "solutions". The only true solution is a new performance-fixing patch. Too many people are experiencing these issues for it to be treated as a coincidence. I am having these stutters as well. Why would I now have to "fix" something that was working pre-patch, and with a fairly good PC specs? Why did I invest money to buy better hardware if I'm going to have to "figure out" how to get back the previous performance because the patch messed it up in the first place? So yeah, I am going to wait and hope for the next patch..hoping QC is not gonna mess it up this time..

Since the other thread has been closed, just wanted to confirm I'm having massive framerate drops and stutters in VR (haven't really tested non-VR). Hope this gets fixed in the next update... EDIT: Before the update, my VR performance was very solid. Capped at and holding steady 80 fps.

Just wanted to report Super Hornet crashing to desktop every time FLIR screen is turned on (i.e. gets operational). (May have something to do with latest DCS update?)

^^I assume you are referring to the range of seeker head activation from the launch platform? So, if the target is say, 30 miles away, what seeker head activation distance should I enter? 20 miles? 25? I guess that also depends on the target's defense zone / parameters? Thank you. Will give it a look.

^^Neustrashimi / Moskva class. I guess "Large"?

From what distance should I be firing them from, please?

Here's the track file. LastMissionTrack.trk

With Thor Missiles. Even when set to "Average". The ship's air defences shoot down not only missiles but also free fall bombs. Bit overpowered, it seems?

I never had this problem before. Anyway, regardless of how I program my Harpoons flight profile (R B/L mode), they always go low and surface skimming. I even tried launching them from different altitudes but they always just drop low and that's pretty much it. I never had this problem before. I remember easily setting different flight profiles with Harpoons (combination of HIGH/LOW - SKIM/POP attacks) which is crucial for killing frigates and other heavily defended targets. But the way it is right now, they always switch to the same LOW/SKIM profile and get easily destroyed by enemy ships. Yes, I did correctly locked the targets via SEA radar, so I don't think that's the issue. I guess I must be doing something wrong afterall..but I'm yet to figure out what exactly..

I'm running DCS in Multithreading Mode (using Oculus Rift S) yet, OpenXR doesn't seem to work in DCS i.e. I can't see my virtual hands? In the VR tab I only have two options "Disable" and "Controllers", there is no "Trackers" option. This option does appear if I try to run OpenXR via Steam but even then, when selecting it, I do not see virtual hands inside the cockpit? Are there any additional steps I should follow to have the virtual hands enabled?

More than 2 months have passed since my September post and the bug is still there. I guess we will have to wait a little longer for this to be fixed...

I have a problem with 84E: Whether using GPS coordinates (Mission Editor) or TOO (Targeting Pod), the missile always misses the target by 100m or so. I also cannot control the missile via DataLink (holding TDS and trying to steer it) and I have "Realistic TDC" checked in my Options. Anyone experienced a similar problem?

Sorry for resurrecting this several months old thread, but it appears the pitch down bug is still present? When will this be fixed?

One way to avoid 3PTS and EGIW is to add full throttle AND slightly pull the stick backwards (i.e. raise your nose a little) just before touchdown.