BJ55

It is! Thanks Aerges.

Overall runs good, some stutter here and there, mostly while pointing at some airport areas and big cities, but a lot depend on your hardware... Just flew a TTI mission and had less than 60FPS only at low level, while gunning some units with the CPU/GPU heavy F-4E... And lots of clouds!

The sources: https://forum.dcs.world/topic/349673-agm-45-shrike-quick-guide-by-klarsnow-updated-june-5th-2024/ From the manuals/guides I thought it was a manual operation, but now I see that the reticle is automatically depressed (at 34mil). Edit: it's even in the Weapons Delivery Manual, pag. 41, shame on me for not bookmarking that page! So, the 35 mil thing has a purpose or the WDM is using outdated procedures from a previous version? Thanks.

Screenshots: TGT/MSL REJ switch is in DF REJ position, shrike goes on target, but I suspect that range estimation is wrong.

T: time in seconds from when it started monitoring. Same horrible performance here, above Rota GPU load is 99%, without shadows and using medium textures goes to 80%, changing LOD, time or weather has little to no effect. P-51D takeoff pratice quick mission above Kagman is a little better, with high settings GPU is at 85%... TTI unplayable!

In order to use the WRCS AGM-65 mode the F-4E Aircrew Weapons Delivery Manual, Klarsnow and Chuck guides tell to set LCOSS to A/G with a 35 mil depression, while in the manual this step is missing. When I set the reticle depression the pipper stay still, is it as intended, pilot error or a bug?

Consider yourself lucky, most of employees around the world have no unauthorized access at all. Btw, better having enforced login than use Cloudflare's MiTM mass surveillance, since most of the time it's broken.

Probably not a settings related issue, did some checks and there are some small trees that appear/disappear (change shape and size) as you pass by, this with visib. range ultra and extreme, LOD 1, forest detail 1...

Are we talking about the same company that to solve performance issues now will add more performance issues? https://www.windowslatest.com/2025/11/22/microsoft-says-it-will-always-run-windows-11-file-explorer-in-the-background-to-load-it-faster/ . In my case disabling the power service does nothing except rising VR VCC current from 1.4A to 5.8A when idle, have yet to check for other issues or potential side effects, but I'm on Windblows 10. The 10+1 mess is having performance issues since 23H2, the power service is bugged and vulnerable, like many other services, add al the bloat they're forcing on users and results are pretty obvious... Blame Satya & Co.

Did some tests enabling/desabling v-sync and frame limits in both DCS and Adrenalin, with them disabled the stuttering goes away, but the card runs at 100% without reason (Caucasus free flight), don't remember if I had the same issue with the RTX 3070, maybe some NV owner can confirm/dismiss the issue, but I assume it's because of radar bad coding or some incompatibility of the unmaintained module with the latest DCS version.

It would be nice to include LIPH S. Angelo Mil, once home of the 2° Stormo (for the upcoming G.91) and then of the 3° RMV. https://www.alessandrozucchelli.it/treviso87.html

https://www.surfertoday.com/surfing/what-is-a-swell

My monitor is a 60Hz, turning off v-sync = tearing. Before with HMD PNVS+VID TADS I was forced to use medium textures, no shadows and 512 displays and still 40-50FPS (100% GPU usage) when over high density areas, now I run with high textures, flat shadows and 1024 displays without issues... Pointless? Don't think so, for sure I'm not going to wait 14H to download a previous release just to grab some screenshots with FPS limiter on/off and show the difference... I simply wanted to report to ED that now, on my system, both AH-64 and Ka-50 are stutter-free on high settings.

I'm having a CPU bound stuttering when radar is in DEC or VISU mode, this happens on every map and at all flight levels, anybody is having the same issue? dcs.log (moved from Razbam/M-2000 section)

Yes, 2560x1440 60Hz, V-sync enabled in Adrenalin, in DCS I've set max FPS 90.

Thanks. Here's what I see: I see the same on the F/A-18C and M-2000, but not on the AH-64, A-10C II and JF-17, so it's difficult for me to point at a driver issue. (Unfortunately TAA is a no-go because of blurred labels)

@grim_reaper68 : can you check if with the latest drivers the HUD has a good definition using MSAA 2x? Performance is the same as with 25.9.2?

I'm here just to report that after the last updates the AH-64 performance is great, video feed is not causing FPS drops, this using the same high graphical settings I've set for aircraft. Thanks ED!

You did nothing wrong, btw... ...So I assume they are working on it.

"Did some tests in Nevada with Mk-82, Mk-82SE HD and Mk-20" I've recreated your bombing profile, test at 6000ft / 0.98nm, 130mil: test at 1.3nm, 99mil: Reticle depression is accurate, screenshot took when pipper over target: When I had the RTX 3070 laydown never worked, now with the RX laydown is almost perfect... It's a mistery. f-4_nevada_laydown.miz

Can you check with the attached track/mission? (I'ts above Cairo) I can reproduce the OP issue: inverted flight no stutters, radalt stby no sutters, radalt on stutters. F-16_radalt_Cairo.zip

I have an opinion... ...Time to spend some income for a curved 49"!!!

Good catch. CPU-Z can do a stress test to diagnose issues, but first you must suspect that the CPU has issues!

Did some tests in Nevada with Mk-82, Mk-82SE HD and Mk-20, 50% fuel, 29.92, no wind, accuracy seems good: Since I've had the same results at 100ft MSL it's not a target high elevation issue... Have you tried with different speed/altitude parameters? Edit- be aware that "target range" must be bigger than "release range", look at the pic below: 1- TR > RR (ex. 120 mil), you hold the bombs release button when the pipper is above the targer, it takes the time to travel from TR to RR for the bombs to be released. 2- TR = RR (ex. 130 mil), you hold the release button, in this case the time to travel from TR to RR is zero, so bombs are released at button press. 3 TR < RR (ex. 150 mil), you hold the release button, in this case the time to travel from TR to RR is "negative" (impossible without flux capacitor mod), bombs are released at button press, but the impact has an offset = RR - TR. With Laydown I set the TR distance in order to obtain a 80-110 mil sight depression, otherwise I use Direct mode.