BJ55

I've set my monitor with low brightness because of eyestrain, that could explain why my values are so high. BTW: I change the fonts color because they're always hard to read with the map in background. (manual, page 405)

@Rissala "Check your aircraft weight (checklist page) before landing" As I wrote previously " I was exceeding MLW by 500lbs", probably I was decieved from the discrepancy in weight between mission resources and checklist page.

@Estamel_Ter @71st_Mastiff Did you tried a DCS repair? Maybe the problem is not the AV-8B module, because if I fly your .miz everything works as espected, but if I take control of your .trk the reticle locks on points without IR signature and I can no longer fire the Mav's, I suspect that the mission gets corrupted when loaded and the track keeps the corruption. +1

Ok, I was exceeding MLW by 500lbs, so my fault. I'm unable to replicate the LG failure at cat launch, time permitting I will test with different loadouts, cat misalignment and cross winds.

+1

To me it seems that the IRMV is only locking IR signatures, not terrain... I really can't understand where's your issue, are you using any mods? Do you run below 60FPS while slewing the IRMV?

Your Mav seeker reticle wasn't on target, so no lock. (Don't rely on "Good, you have a lock" message, only the reticle counts) I've took control, slewed the reticle on target and the Mav went away.

Open the mission in the editor and save it without modifications, then it will work, a lot of missions need to be resaved.

Windows bug confirmed! Yes, with the actual DCS memory usage 32GB is the minimum required, you can set a bigger pagefile size to prevent memory exaustion (with 32GB you can set "impostazione personalizzata" 32768-32768) and lower your DCS setting until it runs smooth.

Your laptop can handle 64GB of RAM, so it's not a hardware limit. ASC shows 4GB usage, TM processes shows 14GB usage or 73%... Could it simply be another Win11 bug? Task manager (and sensor monitor) had plenty of them in the past. https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/task-manager-display-incorrect-memory-info You could try the memory diagnostic tool, just to exclude the chance of a faulty RAM, then run resmon, start DCS, change some settings in order to use more memory and see wat that happens.

Is it a MSI laptop? The memory sticks are of the same manufacturer and model and both RAM sticks are visible in BIOS? Maybe you can find a solution here: https://www.elevenforum.com/t/usable-memory-same-after-ram-upgrade.11578/

Can you upload a screenshot of your TaskMan when it reaches 80% mem usage? P.S.: Resource monitor (Win+R resmon) is more reliable. BTW, I've also noticed that RAM usage was the same after upgrading to 64GB, well, until it required more RAM and there was no need to use the pagefile.

Flaps Full are a landing checklist item. Use the replay function to load your track file, wait until you're at 1200ft 250kts, press Esc - Take control, disengage AP (paddle), set flaps to Full and then press CPL.

Your flap position must be Full, not Auto or Half.

Master caution = low on fuel, change FPAS Home to WP1. No issues with the mission and a good wire 3 recovery. Ivo.trk

To me it seems that your controls are disengaging AP. Also check if there are roll-pitch axes assigned to other controls than the stick or if there's noise on the controller output.

Just tested A-10C II Navigation Training mission and found no issues, it's important to follow the instructions: TDC must go to the very bottom of the HUD, TMS must be hold UP until designation. (this part of the training is only used to show both the TDI and TVV rappresentation on the HUD)

The UTM FAIL is what that happen in all default Supercarrier CASE III recovery missions (DCS World\Mods\aircraft\FA-18C\Missions\Single), in order to have an active Datalink it's only necessary to start those missions from the editor. Since after the last updates there are other single and quick missions with strange bugs, for example MiG-29A - Marianas - Air Combat.miz and FC_Su-27_Sinai_A2A.miz are missing opponents, I suppose that a parameter has changed and the the waypoint action never starts. Default mission in the editor:

With all the case III recovery missions I get a "UTM FAIL" message, even if freq. is correct, but there are no issues if I start the mission from the Mission Editor (with and without saving). default mission: PG-SUPERCARRIER-HORNET-CASE III RECOVERY_UTM-FAIL.trk mission started from Editor: PG-SUPERCARRIER-HORNET-CASE III RECOVERY_from-Editor_ACL1.trk Anybody is having the same issue? Best regards PG-SUPERCARRIER-HORNET-CASE III RECOVERY_from-Editor_ACL1_dcs.log PG-SUPERCARRIER-HORNET-CASE III RECOVERY_UTM-FAIL_dcs.log

180 FPS with a 3070 8GB? You're askin' too much. BTW, my monitor has a fixed refresh rate, so for me 30 or 60 FPS are the only choice.

While watching the replay I've had no stutters and GPU usage was from 70% to 90%, flying your mission I've had no stutters and GPU usage was below 80% with some spike, then I decided to do some low passes above Puerto Natales with the Su-25, GPU usage was below 70% and no stutters at all! Quite strange... So I've also tried with different aircrafts, Mirage 2000 85% no sutters, Mirage F1EE 99% heavy stutters. Probably with this map and complex aircrafts my GPU reaches it's limits. (2D, limited at 60FPS, 2560x1440)

From Chuck's guide page 421: Changing Steerpoint Types with the Quick Access (QA) Menu You cannot cycle through different steerpoint types with the EHSD arrows alone. To change steerpoint type, you have to do it through the Quick Access (QA) menu. To access it: 1.Long press on the EHSD arrows or on the Waypoint Increment (WINC) button will bring it in the ODU (Option Display Unit). 2.Depending on whether you have a target designation or not: a)If you have a designation (DESG boxed on the EHSD), summoning the QA will bring the T0 between the arrows, select target in the ODU and “0” (T0) on the UFC scratchpad. b)If no designation exists, summoning the QA menu will have the current steer type selected in the ODU and point number populating the scratchpad. Also, while in the QA menu, you don't have the EHSD arrows available anymore, you need to exit/close the QA menu for them to reappear. 3.Once the QA is summoned, you can choose between WYPT (Waypoint), MKPT (Markpoint) or TGPT (Target Point) in the ODU , which will bring in the UFC scratchpad either the last selected number of this type or the first of them (if you didn't use any point of this type during the flight). 4.Write the number of the desired steerpoint (as an example, type “2” for “Markpoint 2”) in the UFC (Up-Front Control). 5.Press ENT. Performing this action will close the QA menu. 6.The selected point will then be displayed between the EHSD arrows, which means that you will be able to cycle through the points of the selected type with the EHSD arrows (and only this type).

I'm having severe stutters even above forests when flying below 900ft AGL... the only way to keep my usage GPU below 80% with this map is use this settings: Instead of the ones that I use for every other map: Scenery details factor, forest details factor, terrain textures and shadows settings had little impact on stutters, the biggest drop in GPU usage was achieved with medium visib range and no AA.