BJ55

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.

Probably nothing, I was never able to hit a target with L / DL mode, now I only use direct mode with my own bombing tables. Edit: the track doesn't display the bombing calculator parameters, so it's difficult to see if you're following the profile, also in your track the 82SE are hitting short, had the same issue while trying to report my findings... P.S.: for the first time I've had perfect results with 3 releases of Mk-20, 450TAS, tgt at 200ft, release alt. 750ft, distance 1 or 2 nm (don't remember), depression 100. Will try with 82's later...

OK, now I see, weird bug, 5 moths ago it was working as intended (YT screenshot):

A lot of modules are crashing since last update, logs attached (TTI Afghanistan, no tracks because I have them disabled). "2025-10-26 14:51:17.109 INFO EDCORE (Main): E:\sim\DCS World\Mods\aircraft\Mi-24P\bin\CockpitMi24.dll 2025-10-26 14:51:17.110 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff9835a45b5 00:00000000" dcs.log-20251026-145117.zip

It's something on your side, check procedures or remove mods.

Same here, also the INS alignment is having issues when using auto-startup, sometimes the counter stops, sometimes it goes backward.

Previously you wrote "This computer with the same hardware, used to work flawlessly a few months back", that's why I've never thought about a HW issue, btw, I've had a similar behaviour in the past with a borked (Asus) BIOS update, worth checking. Best of luck!

I see you're running 560.94, the latest decent driver for pre 50 series is 566.36, so if you want you can try it later. Just for curiosity, have you tried also previous chipset drivers? Do you have another SSD in order to install DCS outside of C:? Just for curiosity, can you upload the screenshots of cpu, memory and disk usage graphs from DCS start to ctd?

From the "I got like 4 frames of gameplay before it crashed again" and no WER other than DCS and Flightsimulator I can only suppose that it's not disk/AV/FW related, it's crashing while rendering terrain, so if a full repair with "check all files (slow)" + "search for extra files" + reboot don't solve the issue it could only be a Win11 conf/Win11 bug/driver issue... Or maybe a .Net bug introduced whith the last cumulative update? (how I miss Win7, it was so easy to solve problems) ( Damaged disk example: https://forum.dcs.world/topic/379011-what-the-latest-procedure-to-repair-an-installation/#findComment-5694880 , does't take much to check S.M.A.R.T. data for issues)

Have you disabled HAGS, Game Mode and Core Isolation? Maybe try with and older NV driver? (btw, latest W11 release is plenty of bugs, like every NV driver since 50 series release)

You own a 4090 but the DxDiag Notes say "There is a problem with AMD Radeon(TM) Graphics device. For more information, search for 'graphics device driver error code 43'", quite strange... edterrain4.dll crashing with memory access violation seems a driver related issue, try with disabling the iGPU (integrated graphics).

Thank you.

With the TACAN in REC mode the bearing needle doesn't move, like it was turned off. Below two screens with the plane in active pause, first TACAN switch in REC position, second in T/R. Best regards.

Forget previous pic, DCS had loaded the wrong 29 (FC). I've selected the empty loadout, then added the tank...

While I was trying to reduce the stutters in this map I've discovered that the scenery details factor setting is affecting also the details factor of some trees, is it as intended or a bug? Best regards.

Apologize, I was in the wrong section of the forum.

1944 MAGVAR -9°, 2025 MAGVAR +1°, that's the 10° difference.

It's on the stick.

...Ci sono rimasto malissimo, dai su, non chiamarlo così! Buon lavoro. (in trepidante attesa di Gina)

Uh, no no, only the folders listed with "ERROR: RMDIR", so "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/terrains/Falklands/Models" and "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\Falklands\Models", but I suspect that you're having disk issues... Edit: check if you have disk indexing enabled (right click on the disk letter), if so then disable it, can (will) cause issues when there is a huge number of files.