BJ55

With no HPTP It's intended as "relative to launch position" (BOL: Bearing Only Launch) , so it's the missile own heading once fired. In the case above the missile goes BRG169 mag - (HSI175 true - HSI168 mag) = BRG162 mag. For some reason the code is subtracting mag. dec. from mag. heading.

Harpoons are flying the wrong bearing, tested with HSI in both true and magnetic heading. Attached mission and tracks. FA-18C AGM-84D Harpoon.zip

@western_JPN : have you tried with a different cloud preset?

With the v2.6.1n I'm having a scripts load error when era is set to "cold_war", have yet to check if ww2 and korean have the same issue. Best regards. dcs TTI CW.zip

The one supervised by Mr. Deep Breath?

Unfortunately there's not much you can do, other than tweak axis settings.

No issues here, tested with IRMV sensor only at Caucasus in winter.

Maybe it's this W11 issue https://answers.microsoft.com/en-us/windows/forum/all/latest-update-of-windows-11-broke-my-legacy-alt/89a495fc-d160-45f4-8e6b-ab294160009a ? (no issues here with W10, alt-tabbing right now while using ME)

Have you tried with different Nv drivers? A lot of people are not happy with 560 series https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/553620/geforce-grd-56636-feedback-thread-released-12524/ .

Thank you for the info.

Delete fxo and metashaders, then try with this settings: You have only 32GB of ram, reduce preload radius to maximum 60000. Also try with a fixed pagefile of at least 32GB. I have no performance issues while landing in any region/weather/time (Nv 552.44).

Any news on this issue? On simple scenarios my FPS drop from 60 to 40, tested with 1024/512 displays, high/med textures, MSAA 2x/DLSS, default and flat shadows, on heavy scenarios it becomes a nigthmare. (Both Ka-50 and AH-64 are heavy on my system, GPU usage goes from 50% with AC to 90% with choppers, so it takes little to exaust resources)

NVG's, like in real life, have too much noise to see details. In pods and weapon feed you see only objects (LOD 1 and Visib Range ultra to spot targets at >25nm) .

Unfortunately I don't have PNG's of the screenshots anymore, in my case dots are black 2x pixel squares.

Almost nothing, because DCS render objects at the correct size and at that altitude/distance with that resolution it's impossible to spot a camo vehicle. In order to see something you need an "eye resolution", wich is magnitudes bigger than the ones of current video display devices.

2560x1440 MSAA 2x: Symbols are invisible and labels are unreadable.

I took control and everything was OK, check your axis assignments and also check if AP is engaged (it is when mission starts).

@uboats From the changelog: "Baro knob will adjust the value for selected source (QNH or QFE)" , QFE works as intended, but QNH is locked at standard 29.92 (baro setting knob does nothing), can you check? Best regards.

+1

Cancellalo manualmente e poi lancia il programma di aggiornamento di DCS, se continua a darti errori nella rimozione file obsoleti allora lancia DCS_updater come amministratore.

The hundreds rotary is correct. Buone Feste e Tanti Auguri a tutti gli sviluppatori di IFE!

You are in TV mode.

Glad to help you. I use different curves because I prefer a faster vertical slewing of the reticle with this module.

My settings: Ministick is not so precise, so you need a deadzone bigger than 2.

LastMissionTrack.trk dcs.log