fisadev

This might be useful for anyone having this issue:

Hi! I wanted to share a very useful discovery that at least in my setup, helps me fix the F10-map-related FPS drops when they happen. This doesn't prevent the FPS from dropping when using the map, but fixes it when that happens. Most of you are probably already aware that doing alt-tab can get your original FPS back, but it's unreliable at best, and sometimes it just won't fix it at all no matter how many times you do it. Well, I think I found out why: even if you alt-tab, if any screen (including the VR headset) is showing any pixels from DCS, there's a high chance the drop in FPS isn't fixed. So you have to make sure absolutely no screen is showing any part of the game at all, including the VR headset if you are using one, to get your FPS back reliably. In my case, that means doing two steps: 1) Alt-tabbing to another full screen app. Not just any app, but a full screen one. I just use a cmd.exe window in full screen mode with F11, which I always have opened anyway when flying because of some home made scripts I use for a button box. 2) Switching to the desktop mode of Virtual Desktop (which I use for the VR headset), getting out of VR mode, so DCS isn't rendered in the headset anymore. In the case of VD, you can do that with a VR controller or with the Shift+Windows+D keyboard shortcut (while DCS isn't in focus, otherwise DCS "eats" the key presses. But after step 1 DCS is already out of focus, yay). Those two steps guarantee that no screen, desktop or VR headset, is trying to show any pixels from DCS at all. And that seems to do the trick, I get my high FPSs back every time when doing this, 100% reliable in my case at least. Hope that's the case for others as well!

I found this bug today too. I was trying to record a tutorial video for the radar, but all targets were jamming me, even an I-16. It made no sense, until I realized it was the active pause that was causing the jamming.

FTR is good enough alternative to something 99% of the players can't simulate (a force feedback stick). Not even close to asking for something to be less realistic just because the realistic version is too slow for someone's taste, man.

Not useless, he's right. If everyone starts just posting stuff they "feel" could be different, the real bug reports will get lost in an ocean of noise. It's in the best interest of everyone to prevent that.

Happened to me too, can confirm that it was after hitting a wake.

A few people already posted that solution, but indicating that even with that they didn't gain fps. That was the case for me too :( Did you get more fps by doing that? How much?

If I set my shadows to "Medium", they are all over the place and really broken like it can be seen in this video. Please notice that they are also broken inside the cockpit (basically no shadows), not just outside in the world. If instead I set them to "Low" or "High", they work fine as far as I can tell. I'm with the MT open beta, in VR with native OpenXR (using the command line argument to force it), with an HP Reverb G2, a RTX 3080 and an i7 9700. Nvidia drivers version: 531.18 Track and mission attached. Also screenshots of the rest of my settings. area51_demos.miz shadows_problem.trk

Not even close. A heat issue wouldn't be instantly solved by alt-tabbing out and back into DCS, nor would it happen in the menus were the GPU load is super low.

Awesome! Didn't know that. And now I envy them for being able to do that too, hehe. Thanks

Hi! This is a well-intentioned question, not a rant or anything like that, I love the module and want to know more just out of curiosity How much realism and how much guesswork is there in the Ka50 module? Are stuff like the pages in the ABRIS known to be just like that in real life, or were they informed guesses? What about the functions of non obvios cockpit controls, like all the datalink and stargets storage stuff? Did ED have real life manuals or access to SMEs to get that info? I've seen posts over the years specially with discussions about the changes coming to BS3, but I'm talking about the current BS we have. Has ED published details on this before? I couldn't find anything aside form an old post from Wags highlighting that they only want to do aircraft that they have access to good info, etc, but not details on what's real and what had to be guessed in the BS module. After flying the Apache and seeing videos of real pilots commenting on how real it is, and also comparing what we see of the systems vs real life videos, I started to wonder if the stuff in the Ka50 is at that same level, given how obscure the real life thing is in that case. And I love realism, it's the single most important thing that makes me want to fly stuff in DCS: the possibility of interacting with these machines, which I would love to but won't ever fly in real life. I'm not looking to "validate" the module or anything like that, and I'll keep flying it anyway. But I would really love to know more about this

I would rule out the reprojection part, as I have your exact same symptoms and I always have it disabled. Even the weird stuff like the frame drop continuing in the menu and alt-tab fixing it. Also, today I tested enabling the hardware accelerated GPU scheduling, but I still got one occasion of frames dropping and continuing to be at 45 (instead of the normal 90) in the menu. So it didn't solve it

@muelchinteresting, I want to try that. Where does that setting live? Edit: found it, will test it today

I'm having exactly the same issues the initial post describes: the drop in fps persisting to the main menu, the alt+tab sometimes fixing it, etc. I'm using a RTX 3080 too, with a Reverb G2 and OpenXR, and disabled motion reprojection.

This isn't a direct response to the original question, people already answered the "how much can I control" part, but something related: I once asked on the Razbam discord F-15E channel how common it was to fly the bird alone (only one crew) in real life. There are a few real strike eagle pilots there, and their answer was something like: never in combat, sometimes to travel.