JuiceIsLoose

Yea, I have only noticed it with player F-15E's. And will do. I'll try to get a group together this week and include a short track.

The TEWS does not indicate that a friendly F-15E is locking you in STT. I have reproduced this in BVR training missions with others. Upon launching AIM-7M, which require an STT track, there is no lock warning, or launch warning from the other F-15E. This makes air to air engagements with friendly F-15E's very difficult as there is no way to detect a buddy lock ,as no TEWS lock warning is indicated when you are locked by a friendly F-15E. In many cases we have also noted that the TEWS does not even show a friendly F-15E on the display detecting its radar emmisions.

OP, I'm running into the same issue you are describing. Its almost like the jet doesn't recognize the input from the castle switch sometimes and you have to do multiple presses for it to register. You aren't crazy....or at least aren't the only crazy one.

You are correct!! The audio book is read by John Pruden. My bad. Great Book! Definitely got me out of the hornet and into the viper for a few weeks.

No additional solution. But is the book "Viper Pilot" by John Pruden? Currently reading/listening to it and just got past that chapter where he did that.

So to update this. I tried forcing DCS to p-cores using Process Lasso like some others have suggested. No changes. I even went into my BIOS and disabled E-cores. DCS MT will not launch when I have the E-cores disabled....which was very interesting. Using Reverb G2 with the force XR runtime added into the DCS MT executable.

Same issue here using an i7-12700K. Its putting all the load on the E-cores. Noticed almost no change in FPS when switching from ST to MT. In MT it says I am still CPU bound. I have a GTX 3080TI and a i7-12700K. Noticed my CPU clock speed was low for it being CPU bound and then noticed DCS was only using the E-cores.