BJ55

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

F1: you must dim the HUD with the three rheostats below to notice the issue, Aerges dev's already found a fix. JF: yup, fonts are a bit bolder if compared to older screenshots, tested in both 1920 and 2560 resolutions, but I don't know if screenshots where made with a mod.

Thank you!

More images of the F1 here: https://forum.dcs.world/topic/376870-291812722-hud-is-unreadable/#comment-5675251 , it's a night/dimming issue. Add the JF-17 to the bold list. options.lua

It's the same result, only with bigger fonts: Tested also without auto fog.

Weird, daytime the HUD is OK: