BJ55

...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.

2025-09-18 10:55:17.970 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES Disable core parking. Edit: avoid latest NV drivers with the RTX 30 series, 552.44 and 566.36 run a lot better.

You don't need to turn off Defender, only to add E:\Program Files\Eagle Dynamics\DCS World folder to the exclusions. You could: perform a disk error check, make sure to have enough free space, manually delete the file/directory listed above and run another repair. Also take a look at the autoupdate_templog.txt in C:\Users\*your username*\AppData\Local\Temp\DCS .

Check if DCS installation folder is in the antivirus exclusions.

I've had the same, delete all files inside Saved Games\DCS fxo and metashaders2 folders, run "repair DCS world" and select "check all files (slow)" + "search for extra files", if you use the launcher https://www.digitalcombatsimulator.com/en/support/faq/repair/ . Restart the OS.

I'ts in the release notes: Known issues to be patched: Autopilot-induced oscillations, mostly visual on stick, no effect on flight path below 600 KpH

While waiting to complete today's update and see if something is changed: I've had the slow loading/saving issue before updating BIOS/chipset drivers (W10 Pro), other simulators/games/sw had no performance drops, so I think it's only the previous DCS patch that caused issues.

A big Thank You! Best regards.

+1. During dogfights I've had negative G blackouts even with small/short stick inputs. Edit: I'm only able to reproduce the issue with heavy scripted missions, track file is too big to be uploaded. Doing ACM in simple missions (2 units) I never exceed +6G -3G, doing the same manouvers in heavy scripted missions I reach +10G -5G, so I suspect a performance issue impacting the maximum stick displacement speed simulation.

What flanker0ne said, if not enough turn off ground shadows. The GPU has to render two (pilot view+VID) or three (pilot view+VID+IHADDS) different scenes at every frame, PNVS and TADS are also delayed, so it's a huge ammount of data to be processed. Don't know if it's possible to run video feeds at 1/2 or 1/3 FPS, it could be the best solution without lowering image quality.

Not on the F1 CE/EE/BE, don't know about other variants. (Magic 2, so after 1985)

From Mirage F1 Flight Manual page 96: "When the button is pressed, the sight changes to cannon air-to-air mode with radar guidance, the outer missiles are selected and a green light on the side of the sight mount turns on. Further short presses of the button release the current radar lock and command a radar search in front of the current target. A long press of the button commands the restart of the search pattern from the initial position." If you want to re-lock the same target you should long press C+M button.

Never had such issue, I can stop the download and resume it from the last byte everytime I need to. It's not possible to rewrite a multiple GB file (.surface5) while it's in use whithout exhausting system resources. Launch the download at night and don't play other games while doing software updates of any kind, CPU/RAM/MB have I/O limits, this user behaviour could lead to data corruption. Agree. Partially agree, they should make hyper-HQ AI units textures (skins) as an optional download, but cockpits textures need high resolution in order to see the labels clearly.

It does! Thank you.

With 2.6.3b, using the mission_settings_load_from = "savedgamesfolder", the airboss_enable = false is not applied, this often leads to a dcs crash (dcs LOG Through The Inferno (Georgian Coast) v2.6.3b.txt) , the only way to disable airboss script is set it to false in both TTI SP Mission Settings folder and ME settings. 263b_airboss.zip

I've encountered the same issue, the only way to undesignate the last AGM-65 target and use the active WP is select the Mav in SMS page, go to WPN page and short press TMS down, even when all Mavs are fired/jettisoned. (edit: there's a chance I've missed the "TMS down" step during the boresight procedure.)

The overall performance at Bagram has really improved, thanks ED!

It Depends on wich old version you're talking about, because after new terrain streaming, fog, volumetric lights and other things DCS has become more demanding. The last patch caused a performance regression, more noticeable in ME loading/saving times, and also more antifreeze warnings, from 2-3 to 8-12 on the same mission, but maybe it's only a scripting issue, because with simple missions there are no warnings. Edit: the core pegged at 100% is a long standing issue. Try with a 32/64GB pagefile and disable some eye-candy to see if the number of warnings decrease.

The bloated W11 on a I9-9900K with 32GB RAM, 16GB pagefile, 8GBVRAM: if you set resolution at 3840x1080, civ traffic, MSAA 4x, SSAO, SSLR, volumetric lights, flat shadows blur, etc., some "antifreeze" is expected.

QNH or QFE? There's a pressure units conversion aproximation error and a QFE calculation error in DCS, but the MB339 altimeter precision is within specifications. But there's a bug: the altimeter get stuck with negative values past -250.

Yep, auto start+accelerated alignment=asking for problems, manual start+normal alignment=no issues. (page 333 of the EN manual)

I was able to reproduce the "issue", on the overhead panel if the warning СЧИСЛЕНИЕ ГРУБОЕ / AC-POS. CAL. DATA is lit the auto hover can't work, solution: wait until the warning light goes off, after completing the startup procedure it can take 5 more minutes on the ground. (it could also be a bug https://forum.dcs.world/topic/372912-airfield-button-and-ac-pos-cal-data-indicator/#comment-5639656 , have yet to check a long mission) (Probably was the June 19 patch: https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.17.11733/ ABRIS. SNS accuracy low - improved) ka50_cau_test.trk

Unfortunately... VRAM is not!

Use a map with a big magvar, launch from distance (>40nm) and observe the difference from commanded magnetic bearing and missile flight path magnetic bearing, the difference is explained in my previous comment, this leads to the target being outside of missile radar search cone. CAU-F18_harpoon.miz CAU-F18_harpoon.trk