DCS hangs / freezes with Winwing MIP screens(3)

[EvilTea]

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)

[silverdevil]

5 hours ago, EvilTea said:

drivers/service ntoskrnl.sys and Wdf01000.sys

hello

both files you mentioned are core windows files

ntoskrnl.exe or ntoskrnl.sys

Hardware Abstraction: How the operating system interacts with the computer's hardware. 
Process Management: Handling the creation and management of running programs. 
Memory Management: Allocating and managing system memory for all processes. 
Security: Containing the security reference monitor for system security functions. 

Wdf01000.sys

is a Windows driver file that belongs to the Windows Driver Framework (WDF), which hosts other device drivers like USB devices, Bluetooth, or graphics.

loads on those two files is not surprising. but problems can also introduce BSODs.

my suggestion is to run SFC /scannow

https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

also check to see if there are any updates to the WINWING and associated drivers.

[rob10]

You're better to post this in the WinWing section of the hardware/input subforum here.  IIRC there was someone else with similar symptoms.  I don't remember if they figured it out or not.

One thing you could try is going into SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua and changing the value at  Line 19 -- winwing.interval=0.03 to 0.3.  That reduces how often it is checking for inputs (although that should have no impact if it's just the screens causing issue.  If you're connecting/disconnecting the frames at the same time it might).

 

[EvilTea]

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 ! 

[sleighzy]

Also confirm that you aren't running DCS as administrator, can check under the shortcut for the exe as well under the Shortcut and Compatibility tab and make sure that Run as administrator isn't ticked. This was a known issue a while ago with WinWing MFDs.

If you have modified the Windows UAC settings then this can also lead to things being run as administrator.

Looking for another reference as I believe there is also another app that DCS can be launched from that can cause this issue as well.