TheChafing

I've had that happen when I forgot to set the aircraft's skill to "Player" in the mission editor. This may be my new favorite plane, but I have a possibly stupid question: When I clip a pylon in the instant action racing mission, I immediately die, versus just getting dq'd or assessed a penalty. Is this the intended behavior? I was under the impression the pylons are big inflatable balloon things in real life, so they won't damage the planes. Regardless, this thing is awesome!

Something else I noticed yesterday, while screwing around in the Tomcat (different from the Hornet I talked about before), once again, in VR. The CPU frame time drops pretty significantly if I switch to a non-cockpit view, (ex: F2 key). I assume this is because it's no longer actually doing any of the work related to the cockpit instruments, and also not drawing the geometry of the cockpit, but while the GPU frame time dropped just a little, the CPU frame time dropped a lot - from 12-13ms down to like 8 or 9. It's enough to go from about fifty percent reprojection to near-zero. Also notably, the reported CPU load is generally never more 15-16%. On my 9900K, that (naively) suggests that what's going on is that the game is either only running two threads, or it's running many, but most of them are just waiting around for another one to finish some task they need. From one software developer to another, suffice it to say I'm glad it's not my problem to debug that. :D

Statics being... planes just sitting there on the ramp, being used as scenery? In my case, there were zero other planes in the mission. It was literally just me, in a clean-configured Hornet, going for a joyride. This was on the Nevada map, taking off and landing at Groom Lake.

Have you tried deleting the fxo/metashaders files in the saved games folders? I had a similar problem to you on almost identical hardware, where I'd get horrifically bad framerates when sitting on the ground at airports, and what seems to consistently fix the issue for me is to quit DCS and delete those files. Then, at least for the next session, the problem is mostly fixed, at least until I land. I haven't had time to try every one of the modules I own, but the hornet seems to be very consistent about this.

Something I noticed yesterday as I was installing the shader mod, and thus doing a little performance data gathering, is that performance on my system (I play in VR) is not actually GPU bound like most VR games seem to be. Instead, oddly, I'm CPU bound. The CPU is just barely fast enough to get around 90FPS while sitting still on the ground in a cold and dark Hornet. As soon as I start turning things on, the CPU frame time goes up to around 12ms, which is too long for 90FPS and I get reprojection. When I'm airborne, it's generally right around 12-13. I should note that I'm running the game on a system with a 2080 Ti and a 9900K clocked at 5GHz. This is the fastest setup it's practical to have (excluding the RTX Titan). What's really interesting to me, though, is that the game appears to be VERY CPU bound, even on the fastest CPU on the market. Edit: The way this appears to be happening is that the game is running only a couple of threads, and the single core performance of my CPU isn't high enough to get the frame time down below 11ms.

I bought the Hornet module over the weekend (Steam version, if it matters) and I'm seeing this behavior as well, in addition to some other odd quirks. Frankly, given how much the modules cost, it left a pretty nasty taste in my mouth - enough I almost returned it. Here's what I'm seeing: 1. It seems that I have to go delete the metashaders/fxo files EVERY time I want to play the game, or I get horribly low framerates whenever I look forward. Subjectively, it seems like maybe it's related to the HUD, or some other instrument in the cockpit, as it gets a little better if I look to the left or right. 2. The problem comes back, deleted metashaders/fxo or not, after I land the Hornet. Again, it's the worst looking forward through the HUD, and mostly goes away if I look away. Hardware in question: RTX 2080 Ti Core i9 9900K 16GB of memory @ 3000MHz HTC Vive Pro Settings in SteamVR are the defaults. Settings in DCS are basically just the VR preset, but with all the shadow settings turned down to the lowest option. Edit: I didn't have a ton of time to troubleshoot this, so I can't be 100% it's limited to the Hornet, but the only thing that changed over this weekend, as far as I know, is that I bought the Hornet module, and I've never seen it do this in any of the other airplanes.