J20Stronk

I wish we could get tweakable default Level and Gain for FLIR WH/BH and CCD for all seekers. The default level/gain for WH and CCD is too dark and BH is too bright

Okay so I think I finally fixed it for real this time. I went into the Windows 10 settings and disabled Game Mode and Hardware-Accelerated GPU scheduling. I rebooted my PC and that seems to have fixed my issue for now. I loaded the same mission plus another one with heavy combat nearby, both 60-70fps, high GPU usage and no stutters. I quit the game 5 times and did not experience the bad performance from before. Hopefully it's fixed for real and isn't just placebo until it decides to crap on me again. EDIT: nvm, back to suffering...

RWR prioritization. OPEN will show the last 20 emissions regardless of how much of a threat they are. PRTY will limit the amount of threats displayed to only show what the RWR believes to be the biggest threats based on several factors. (Emitter class, type, strength, etc.)

Will do. Just re-formatted SSD and reinstalled DCS OB in a clean state again. Still getting bad fps. I will try de-bugging device_init.

Unfortunately it didn't fix it. Second run of DCS and after, 20-40fps instead of 60-80 in the same mission above, only in the JF-17. However it does appear to be only inside the cockpit now. I do get 60+ fps when in external views.

Today's patch didn't fix it. I think I'm done for now.

It's probably related to the F-16C wingtip missiles impacting the rail as it launches them. Apparently ED changed the way missiles behave. They seem to turn into separate objects a little too soon which causes them to collide with the launcher.

Will this also fix the weird fps drop me an Darkstar are experiencing, or is this unrelated? EDIT: I haven't had the chance to test it, but I hope that this was included in today's patch.

I have a similar problem. Normally I get 60+fps in most areas, even if there is heavy combat taking place nearby. However if I fly the JF-17 and only the JF-17, my fps is reduced by about 30fps. It usually goes as low as 20fps and sometimes reaches 40fps, but it generally stay around 30 with a lot of stutters. The crazy thing is, this only happens if I quit and run DCS a second time and afterwards after I boot up my computer and it only affects the JF-17; no other module has this issue, not even the F-14. I did almost everything short of reinstalling Windows 10 in an attempt to fix this, including formatting my SSD, reinstalling Display drivers, uninstalling KB5001330 among other things, none of which fixed this issue. I took a look at the dcs.log file, there's nothing erroneous there compared to one from a, "first boot" wherein the issue is absent. I also set every setting to the lowest and even then the JF experiences 20-40fps while others like the Tomcat get 90-100fps. I already reported this to Deka, but they can't reproduce this on their end. I'm at my wit's end at this point.

Yes, I even uninstalled it. What I did was simply turn on active pause when the mission started and looked around. In the JF looking straight down gave me 30 fps. Looking around give me anywhere from 15-40 fps with a lot of stutters. Meanwhile the other modules gave me 60+fps no stutters no matter where I'm looking. If I run this same mission in DCS 2.5.6, then the issue isn't there. The JF-17 runs perfectly fine.

So I went and also installed DCS 2.5.6 Stable and the issue isn't there. 60+fps with all modules including the JF-17 even after restarting DCS 2.5.6 several times. Reloaded the same mission in 2.7 and bad framerates and stutters in the JF-17 only. I copied over the 2.5.6 JF-17 files minus the JF17_ASM.dll and dcs_manifest.bin over to my OB install just to see if it would magically fix the issue but alas, it didn't. I also uninstalled Windows update KB5001330, nothing changed. I give up. I'm out of ideas. I've tried everything short of reinstalling Windows. I'll just fly something else and hope the next patch magically fixes this.

I tried changing the cockpit too, I'm still getting stutters and low fps. Thing is, it runs perfectly fine the first time I run DCS after booting my computer, then if I quit and restart DCS my fps drops in the JF only, regardless what cockpit I have selected. GPU and CPU usage drop as well, so it's not my system being incapable of running the quality pit.

That's odd, aircraft movement doesn't affect slewing on my end. I could be going 500kts, 90° to the right offset my target and my pod will slew left and right at the same rate as the other side. I'm at work right now, but I'll make a video later showing my WMD slew and settings.

Did you guys try tuning the WMD-7 sensitivity in the Specials menu? Mine slews perfectly fine with it at 2x in the Special menu and at 50 with a 20 curve in the controls menu.

Just like the WMD-7. It used to match the point you were looking at but some patch last year everything broke on it and it now looks in different directions.

Pretty much every mission, including MP. In the mission above for example I get 20-30fps with the JF, 60fps or more with other aircraft with Active Pause enabled upon spawning and just looking around the scene. If I do pause the entire simulation with the Pause key or Esc key, then I do get 60fps. I have another generated mission with me just sitting at the runway and a battle happening near the airfield. In the JF-17 I get 10-25fps. If I switch it out for the F-18 for example, I get 45-60fps. Same thing as before; pausing using Pause or Esc gives me 60. I don't know what else I can tell you except I do mod the aircraft a lot, but in this case everything is stock; no mods are loaded in either the main install or saved games folder. Even with a clean installation of the game, all mods wiped from my SSD, new Saved Games folder with default settings and at least one instance afterr booting my computer the JF, and only the JF has bad FPS and stutters.

It came back... I did all of the things I did last time including formating the SSD and installing the drivers again, but this time it did not fix the issue. Once again only the JF-17 suffers the performance dip, and only the second or later instances after a full system boot/restart. The first DCS launch runs fine. I have absolutely no mods installed, everything is as factory as I could get them.

Ok so it seems that this problem only occurs on the 2nd instance of DCS onwards after I boot or restart my PC. The first instance of DCS is fine, JF-17 runs well and I get 60fps+, no stutters like other modules. If I quit DCS and load it up again, flying the JF-17 and only it reduces my framerate to a stuttery mess. UPDATE 2: I *FINALLY* managed to fix this issue. I completely formated my SSD and moved the pagefile it had over to another SSD, reinstalled DCS and the newest Nvidia driver again and recreated the Saved Games folder. I also disabled an option in the SSD properties that let Windows compress the files in it to save space. One of those things managed to finally fix my issue. (I have a feeling it was the file compression setting, but it only seemed to affect the JF-17 and not other modules.)

It's later on, after giving the sim a couple minutes to load in all assets, I still get 20-40 fps constantly fluctuating with a <30fps average. I'm just gonna nuke my entire install and start from scratch, seeing as it's not reproducible. UPDATE: completely reinstalled DCS with no mods and only downloaded the JF, F-14 and F-18, and I also made a new Saved Games folder but to no avail. Only in the JF-17, I'm getting terrible fps and stutters, but both other modules I'm getting 60fps. I'm getting frustrated because this wasn't happening before.

I've been having awful framerates in the JF-17 with the recent patch. In missions where there is heavy combat taking place nearby, I've been getting no more than 25fps, sometimes dipping as low as 10fps, but only if I am flying the JF-17. If I jump in any other module such as the A-10C, F-18 or F-14, my fps is a stable 55-60fps in the same mission. I have reinstalled the module multiple times, cleaned out my shader folders in my save game directory, ran multiple repairs and even reinstalled various NVidia display drivers. Nothing fixed this issue, which only seems to affect the JF-17. The low performance is still present if I use F2 to jump to other far away units or F11 to jump to a far away airfield AO, but only with the JF. Switching away with other modules will maintain 60fps. I will attach the mission I used to test this fps issue, as well as a .trk, dcs.log file and my graphical settings. I will also attach some screenshot of the framerates and CPU/GPU usage in the scene with various modules. (F-18 and F-14 modules must be installed to view .trk and play mission.) Specs: i7-4790K - 4.0 Ghz 16GB RAM DDR3 - 1600Mhz ASUS GTX 1070 Strix OC to 2048Mhz 32GB Page file on SSD DCS installed on SSD Settings F-18 F-14B JF-17 (All screens from the same mission, cockpits and assets fully loaded.) fps.trk FPS test.miz dcs.log

Did you enable it in the settings?

You don't have the mask connected, just the suit.

Not a bug. The real plane keeps the power on if the canopy is sealed for emergency reasons.

OH MY GOD IT'S (probably) HAPPENING, EVERYBODY STAY CALM!

Scuttlebutt is Deka may rewrite their entire Gun Sight code from scratch since the solution provided by ED isn't working for them, as you can see. Apparently the real JF-17 has been upgraded with EEGS similar to the F-16, so we may get that as well if DIS fixes its code and gets documentation.