solved Terrible Performance when Extending Across Multiple USB Displays

[Callsign Munch]

SInce the latest update I have had massive stutter and lock up on the main menu when running across multiple USB displays (WinWing MIP).

Troubleshooting steps:

1. Renamed Saved Games/DCS Folder. No mods, no export.lua, closed WinWing software
2. Ran only on main monitor. Ran normally.
3. Extended game window across two DisplayPort Monitors. Ran Normally
4. Extended game window to USB monitors. Massive stutter an locking up.

Am I missing something?

 

dcs across usb displays.log dcs.log

Edited March 21 by MeatServo
Uploaded wrong log files

[rob10]

Sorry, can't help you with a solution, but I have 3 WW MFD's and haven't had an issue so keep digging because there should be a solution.   I have seen another post experiencing the same as you, not sure what the commonality is.

As a random thought: go into your SimAppPro wwexport.lua (\SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua) and at line 19 change the winwing interval value from 0.03 to 0.3.  Not sure it will help your scenario but that reduces how often SimAppPro polls DCS so it might.  That's assuming you weren't having issues with USB export without SimAppPro running as well in which case that won't likely help.

Edited March 21 by rob10
typo

[Callsign Munch]

20 hours ago, rob10 said:

Sorry, can't help you with a solution, but I have 3 WW MFD's and haven't had an issue so keep digging because there should be a solution.   I have seen another post experiencing the same as you, not sure what the commonality is.

As a random thought: go into your SimAppPro wwexport.lua (\SimAppPro\resources\app.asar.unpacked\Events\wwt\wwtExport.lua) and at line 19 change the winwing interval value from 0.03 to 0.3.  Not sure it will help your scenario but that reduces how often SimAppPro polls DCS so it might.  That's assuming you weren't having issues with USB export without SimAppPro running as wellin which case that won't likely help.

Its definitely related to input polling. I can get my system to unlock moving the mouse back and forth. I dropped mouse report rate down to 125per sec. No Joy. Keyboard inputs unlock it as well. wwexport.lua isnt installed for troubleshooting, Saved Games folder rebuilt to default. Slow repair searching for additional files. All no joy.

Edited March 22 by MeatServo
Typo

[Flappie]

If you are using Helios, ensure it is up-to-date:

 

[Arcc]

  I have exactly the same problem.

I spent an hour with WinWing support. It is looking for. I am waiting for a response.
I have not Helios

Christian

 

 

 

 

[Callsign Munch]

5 hours ago, Flappie said:

If you are using Helios, ensure it is up-to-date:

 

No helios here. I tested with a slow repair, and default generated saved games folder. No exports no mods. Only happens when extending the game window to the USB monitors.

[Callsign Munch]

DxDiag attached. Windows generates bluescreen errors in the Event Viewer. Moving mouse smooths out the frame rate and lowers the load on the system. Rolled back DisplayLink and Nvidia drivers. Same results.

DxDiag.txt

Edited March 22 by MeatServo
more info and testing

[Callsign Munch]

I rolled back to 2.9.13.6818.2 and can confirm that the issue is not present. Runs smoother while flying too. Guess Ill sit this month out and only do SP.

Edited March 22 by MeatServo

[Callsign Munch]

These all seem related. Plus a few more reports on the Discord help channel. 

https://forum.dcs.world/topic/370896-bugfreeze-erratic-behavior-after-dcs-29148222-march-19-2025-update/

https://forum.dcs.world/topic/371005-mouse-interaction-has-serious-lag-then-ctd/

https://forum.dcs.world/topic/370843-game-freezeno-responding/

https://forum.dcs.world/topic/370988-modeltimequantizer-antifreeze-enable/

https://forum.dcs.world/topic/370989-game-crashes-freezing-when-loading/

https://forum.dcs.world/topic/370900-come-back-version-29136818/

 

 

Edited March 23 by MeatServo
Added more threads

[bojote]

@MeatServo I assume you have your USB Displays connected to a HUB, as well as controllers. (I have virpil Stick+HOTAS) have you tried connecting ONLY the USB displays and disconnecting your controllers from the hub? I will try that next in my experiments as I can toggle the USB ports on off.

What I find hard to believe is that there is people running USB Displays and have no issues. Only explanation is either an OLD NVIDIA or DisplayLink driver that lacks a feature that does not conflicts with this. I;m running latest drivers for pretty much everything in a vanilla DCS install

[rob10]

1 hour ago, bojote said:

@MeatServo I assume you have your USB Displays connected to a HUB, as well as controllers. (I have virpil Stick+HOTAS) have you tried connecting ONLY the USB displays and disconnecting your controllers from the hub? I will try that next in my experiments as I can toggle the USB ports on off.

What I find hard to believe is that there is people running USB Displays and have no issues. Only explanation is either an OLD NVIDIA or DisplayLink driver that lacks a feature that does not conflicts with this. I;m running latest drivers for pretty much everything in a vanilla DCS install

I'm running a newly built system as of middle of Feburary, with fresh install of everything except DCS (copied), so for those without problems it's not due to old drivers not having an issue.  Drivers for GPU would be new and I downloaded DisplayLink fresh.

[Callsign Munch]

Someone discovered the cause in another forum. Turn off running DCS as admin. Check your shortcut. Working fine now. One thing I didn't think to check.

Edited March 23 by MeatServo

[Flappie]

Thanks for your feedback.

I still don't know why people starts games in Admin mode but this is not a good practice.

[BJ55]

Because some SW has issues with UAC/standard account. Running as Admin can solve some issues but isn't enough, UAC must be disabled and also some policy changes are required (3p security required to tamper protection).

Edited March 24 by BJ55

[Flappie]

Which software?

[BJ55]

My professional CAD-CAM software for example, since it needs to read/write on system owned folders.

[Flappie]

Ah right, I thought you were talking about DCS-oriented software such as Tacview and LotATC.

[MAXsenna]

Ah right, I thought you were talking about DCS-oriented software such as Tacview and LotATC.

Just a heads up. VoiceAttack 1.x needs admin permissions for plugins to work, but that doesn't really matter as VoiceAttack just happily "types" for you, oblivious to the recipient of the keystrokes. So to the contrary, VoiceAttack isn't even aware of DCS. And VAICOM as the plugin doesn't need admin permissions, and works only through the export.lua like the other applications you mention, and it wouldn't matter for DCS if those apps need admin permissions or not to work.
(Don't know if it has changed with VoiceAttack 2.x).
Cheers!

Sent from my SM-A536B using Tapatalk

[Callsign Munch]

17 hours ago, Flappie said:

Thanks for your feedback.

I still don't know why people starts games in Admin mode but this is not a good practice.

I run into read and write issues if I dont. I cant join MP servers.

[Flappie]

34 minutes ago, MeatServo said:

I run into read and write issues if I dont. I cant join MP servers.

That's probably because you started running DCS as admin in the first place. I assume DCS as admin created files that your own account cannot write to/access.

 

[MAXsenna]

That's probably because you started running DCS as admin in the first place. I assume DCS as admin created files that your own account cannot write to/access.
 

They should all be en Saved Games, which makes it very easy to fix.

Sent from my SM-A536B using Tapatalk

[bojote]

21 hours ago, Flappie said:

Thanks for your feedback.

I still don't know why people starts games in Admin mode but this is not a good practice.

DCS-BIOS and Helios REQUIRE to run as Administrator. If for any reason, you have DCS *NOT* to run as Admin BUT you have, say, process control in Helios automatically launch DCS for you it will inherit the original process priviliges (Administrator). So, EVEN if you don't have DCS to run as administrator this problem  is something you could experience.  

[Flappie]

I understand.

[MadKreator]

Just to note:

* Helios does not and should not ever be required to run as administrator. If you have to run Helios as administrator to get it to function then you most likely have other permission settings/issues on the PC. 
* Helios versioning has no effect on displays. Helios has absolutely no control over exported displays or monitor types. Other than taking the monitor configuration as set in windows display settings and writing a compatible monitor file for DCS. Exports are solely a function of DCS, not helios. Helios does not need to be running for your monitor file to be read and executed by DCS. It only tells DCS where in the total screenspace to place which export and how large it should be. The same way if you created or re-created the monitor file manually.