EvilTea

The flight director in the vertical sense dosen't command correctly for intercepting the glidslope. When intercepting from below - I'm getting a signal and a fly up indication which is correct but does not follow the glideslope down when intercepting. Interceptions from above show a full scale fly down, and once the glide is captured the flight director shows and stays at half scale fly down. Localizer and radial intercepts are just about perfect as you want ! Admittedly I've only used it on the Nevada ILS 21L 109.10...

Looks like that did the trick (sleighzy) ! I ran both SimAppPro and DCS "without" the admin and it solved the issue immediately. Also, ensured the properties / compatibility boxes were unchecked. Unusual that for years I'd been running it "with" admin with no issues whatsoever - but thankful for the assist.

For some reason those windows files seems to leap up in usage anytime I connect the MIP screens, I usually run the SFC / scannow process every now again - it came back clean with no issue. I'd thought I'd try to run the screens without SimAppPro, but I get the same hanging / freeze. Double checked my power plan and CPU cores all unparked etc... rob10 : I'll take look at the .lua line your suggesting - Thanks !

Until recently the WW MIP screen(3) have performed flawlessly, with SimAppPro open and the MIP loaded and arranged correctly - DCS now hangs / stutters or freezes once into the initial loading screen. This only occurs when the screens(3) are connected. I've applied all the usual stuttering fixes found in other forums, Process Lasso is running as advertised, separate powered hub for the screens, tired different versions of SimAppPro, fresh DCS install, different DisplayLink drivers, different versions of the Nvidea drivers and tried numerous settings within the DCS graphics setting... (Not a VR user - yet) ...once the screens(3) are disconnected everything runs like butter, even with SimAppPro, Buttkicker, TrackIR, and multiple Virpil control panels I've reached out to Winwing and ED and they both confirm theres is an issue, but have yet to identify / isolate or offer a possible solution, so I'd thought I throw the issue here, see if anybody has any suggestions. Expanding on this, I ran LatencyMon and found high numbers on drivers/service ntoskrnl.sys and Wdf01000.sys Im not sure what these are but it clear that CPU resources are spending all their time in those 2. any thoughts gents...? Asus Z790 Hero, Intel 14900K, 96GB RAM Dominator, RTX 4090 Suprim, Samsung 990 Pro 2TB M.2(2)

So, I took your advice Czar66 and had a nose at the Event Viewer... Interestingly "Kernal-Power / Event 41" !!! After a quick google-around... how many times would someone bother to check your power supply, or least how the power is getting to your PC. I rearranged the power cabling at the back and gave the PSU its own dedicated socket (not via a surge protector / multi-socket)... and voila just had about 4hrs worth of crash-free aviation ! The stutters are still there unless I disable e-core #8 and if I dial back the display settings sliders (clutter, Scenery Details, Pre-load etc) to around 75-80% gives a nice sweet spot, and that's running the F-15E on one of the Caucasus' low level Mission / Training - an easy 150-180fps (obviously not VR)

Hi, latest attached... further fiddling shows "Terrain Textures" HIgh / Low having a marked effect on gameplay stability

so, after a lot of forum reading I'm still getting random crashes (all maps / modules), changed the page file / uninstalled mods / disabaled e-cores / disabled XMP / disabled hyper-threading / MemTest = 100%. / tried Process Lasso / No OC / latest GPU Driver... I've just about reached the end of what I can fathom and brain cells are running dry - however, my skills don't run to decyhpering the .log - would a kind soul take look and make a suggestion ? The only consistent result was turning off CPU #8 which stopped the stutters dcs.log DxDiag.txt dcs.log-20240314-214722.zip

same issue here, ACLS to a water-landing...!!! specifically, what seems to be an issue is the HUD & VDI selection to ACL - it causes the glide-slope HUD indicator to go full down off-scale. Doesn’t seem to matter where you are when this selection is made, but chasing it down finds it active again at 600’ with a glide indication into the wet stuff. All other functions appear to work normally - anyone found a workaround ?