Very sluggish UI after Alt-Tabbing back to command

Very sluggish UI after Alt-Tabbing back to command (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support

Message

NimrodX -> Very sluggish UI after Alt-Tabbing back to command (5/19/2018 2:27:53 AM)
I'm running into this weird problem. It resembles very slow processing of UI events and seems to affect the whole UI of the whole game when this happens. For example, in the Lua console if I type then there is a delay before letters appear. Same with delays on mouse clicks on buttons, other objects, etc. Windows like the mission editor or event editor draw very slowly with a delay between widgets being drawn (you can see them drawn in slow motion.) It happens in the normal game and scenario editor even and it seems to happen after backgrounding the application for a few minutes when there are other windows open (other than just the main application window). For example the Lua console or mission editor would be additional windows that show up on the taskbar with their own previews. Minimizing Command and maximizing it again seems to fix the problem until next time I switch to a background application. I doubt providing a save game file will help since it seems to happen even with a blank scenario loaded in the scenario editor. Here's a DxDiag file in case it reveals anything. I'm also going to try some windows debugging stuff to see if it reveals any event handling issues. I have not run into this problem with any other software.

VPaulus -> RE: Very sluggish UI after Alt-Tabbing back to command (5/19/2018 10:32:05 AM)
Are you running the stand alone or the Steam version of the game?

NimrodX -> RE: Very sluggish UI after Alt-Tabbing back to command (5/19/2018 6:58:37 PM)
Steam version. I'm pretty sure this is being caused by the UI hooks that steam tries to install even when you disable the overlay. Here's what I've found using Procmon (really just procmon so far). Even with the steam overlay disabled, steam still hooks the UI. Why it insists on doing this I have no idea. Procmon reveals command.exe writing to [steam install dir]\GameOverlayRender.log which contains stuff like this: (can't post log messages because the forum software thinks I'm trying to "post links" and this account is too young) Running command.exe directly doesn't prevent this. I'm assuming that steam_api.dll probably loads the overlay and is needed for stuff like steam workshop support and DRM/license stuff. Disabling both the in-game overlay and the DirectWrite support does seem to address most of the problems, but the thing is still trying to hook stuff for some reason and disabling DirectWrite support is highly undesirable since it affects Steam globally and makes the fonts harder to read. That's something I really don't want to disable. I hope these steam issues can be fixed somehow because this creates a sort of "broken window" effect (people see broken windows, assume they're in a trashy neighborhood). Even if everyone didn't buy the game through Steam, a lot of people did and just trying to work around it isn't a good solution in the long term. I haven't had this sort of problem with any other software downloaded or launched from steam.

RoryAndersonCDT -> RE: Very sluggish UI after Alt-Tabbing back to command (5/19/2018 10:14:53 PM)
Hi, sometimes software like Nahmic, Raptr or Sonic Suite can decrease Command's UI performance.

Dimitris -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 6:30:41 AM)
Thanks for the info! We'll discuss this with our production guys to see what we can find.

NimrodX -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 2:48:41 PM)
I uninstalled Raptr a while back because it was causing problems all over the place and I'm not even sure how it got installed. Don't have the others installed. Anyway, stuff like that causes trouble all over the place. Looks like code formatting is messed up on the forum. I attached the GameOverlayRenderer.log Summary: It tries to hook functions even with the overlay disabled. I see billions of these messages: Sun May 20 14:51:08 2018 UTC - Timed out waiting for mutex in PutInternal() Followed by this: Sun May 20 14:51:08 2018 UTC - Clearing input stream because it is about to overflow That pattern tends to repeat every once in a while. quote: Sun May 20 14:33:39 2018 UTC - Module file name: C:\Program Files (x86)\Steam\gameoverlayrenderer.dll Sun May 20 14:33:39 2018 UTC - GameID = 321410 Sun May 20 14:33:39 2018 UTC - System page size: 4096 Sun May 20 14:33:39 2018 UTC - Hooking SetCursorPos, GetCursorPos, ShowCursor, and SetCursor Sun May 20 14:33:39 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Sun May 20 14:33:39 2018 UTC - Failed hooking RegisterDeviceNotificationA() Sun May 20 14:33:39 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Sun May 20 14:33:39 2018 UTC - Failed hooking RegisterDeviceNotificationW() Sun May 20 14:33:39 2018 UTC - Aborting HookFunc because pHookFunctionAddr is null Sun May 20 14:33:39 2018 UTC - Failed hooking UnregisterDeviceNotification() Sun May 20 14:33:39 2018 UTC - Modules at GameOverlayRenderer.dll attach Sun May 20 14:33:39 2018 UTC - 01: Command.exe - (00E70000 to 018D2000) Sun May 20 14:33:39 2018 UTC - 02: ntdll.dll - (77030000 to 771C0000) Sun May 20 14:33:39 2018 UTC - 03: MSCOREE.DLL - (6E180000 to 6E1D5000) Sun May 20 14:33:39 2018 UTC - 04: KERNEL32.dll - (756C0000 to 757A0000) Sun May 20 14:33:39 2018 UTC - 05: KERNELBASE.dll - (743F0000 to 745D3000) Sun May 20 14:33:39 2018 UTC - 06: apphelp.dll - (73840000 to 738DD000) Sun May 20 14:33:39 2018 UTC - 07: AcLayers.DLL - (71E30000 to 720B1000) Sun May 20 14:33:39 2018 UTC - 08: msvcrt.dll - (76E70000 to 76F2F000) Sun May 20 14:33:39 2018 UTC - 09: USER32.dll - (73A30000 to 73BBD000) Sun May 20 14:33:39 2018 UTC - 10: win32u.dll - (752D0000 to 752E7000) Sun May 20 14:33:39 2018 UTC - 11: GDI32.dll - (751C0000 to 751E2000) Sun May 20 14:33:39 2018 UTC - 12: gdi32full.dll - (76BD0000 to 76D34000) Sun May 20 14:33:39 2018 UTC - 13: msvcp_win.dll - (74370000 to 743ED000) Sun May 20 14:33:39 2018 UTC - 14: ucrtbase.dll - (76D40000 to 76E5E000) Sun May 20 14:33:39 2018 UTC - 15: SHELL32.dll - (75880000 to 76BCA000) Sun May 20 14:33:39 2018 UTC - 16: cfgmgr32.dll - (74BC0000 to 74BF9000) Sun May 20 14:33:39 2018 UTC - 17: shcore.dll - (73F10000 to 73F99000) Sun May 20 14:33:39 2018 UTC - 18: RPCRT4.dll - (740A0000 to 74160000) Sun May 20 14:33:39 2018 UTC - 19: SspiCli.dll - (738F0000 to 73910000) Sun May 20 14:33:39 2018 UTC - 20: CRYPTBASE.dll - (738E0000 to 738EA000) Sun May 20 14:33:39 2018 UTC - 21: bcryptPrimitives.dll - (73E50000 to 73EA8000) Sun May 20 14:33:39 2018 UTC - 22: sechost.dll - (75820000 to 75864000) Sun May 20 14:33:39 2018 UTC - 23: combase.dll - (73BC0000 to 73E1C000) Sun May 20 14:33:39 2018 UTC - 24: windows.storage.dll - (74C00000 to 751BA000) Sun May 20 14:33:39 2018 UTC - 25: advapi32.dll - (757A0000 to 75818000) Sun May 20 14:33:39 2018 UTC - 26: shlwapi.dll - (75670000 to 756B5000) Sun May 20 14:33:39 2018 UTC - 27: kernel.appcore.dll - (745E0000 to 745EF000) Sun May 20 14:33:39 2018 UTC - 28: profapi.dll - (752F0000 to 75308000) Sun May 20 14:33:39 2018 UTC - 29: powrprof.dll - (74740000 to 74785000) Sun May 20 14:33:39 2018 UTC - 30: FLTLIB.DLL - (76F30000 to 76F38000) Sun May 20 14:33:39 2018 UTC - 31: OLEAUT32.dll - (74000000 to 74096000) Sun May 20 14:33:39 2018 UTC - 32: SETUPAPI.dll - (74790000 to 74BBB000) Sun May 20 14:33:39 2018 UTC - 33: MPR.dll - (721A0000 to 721B8000) Sun May 20 14:33:39 2018 UTC - 34: WINSPOOL.DRV - (715D0000 to 7163C000) Sun May 20 14:33:39 2018 UTC - 35: PROPSYS.dll - (72E90000 to 73010000) Sun May 20 14:33:39 2018 UTC - 36: IPHLPAPI.DLL - (73710000 to 73740000) Sun May 20 14:33:39 2018 UTC - 37: bcrypt.dll - (73090000 to 730A9000) Sun May 20 14:33:39 2018 UTC - 38: sfc.dll - (01900000 to 01903000) Sun May 20 14:33:39 2018 UTC - 39: sfc_os.DLL - (72180000 to 72190000) Sun May 20 14:33:39 2018 UTC - 40: IMM32.DLL - (73E20000 to 73E46000) Sun May 20 14:33:39 2018 UTC - 41: gameoverlayrenderer.dll - (700F0000 to 70234000) Sun May 20 14:33:39 2018 UTC - 42: ole32.dll - (75310000 to 7540C000) Sun May 20 14:33:39 2018 UTC - 43: PSAPI.DLL - (75870000 to 75876000) Sun May 20 14:33:39 2018 UTC - 44: WINMM.dll - (737F0000 to 73814000) Sun May 20 14:33:39 2018 UTC - 45: WINMMBASE.dll - (732B0000 to 732D3000) Sun May 20 14:33:39 2018 UTC - ---------------------------- Sun May 20 14:33:40 2018 UTC - GetProcAddress Direct3DCreate9 returned wrong module (73840000='C:\WINDOWS\SYSTEM32\apphelp.dll'), proceeding anyway Sun May 20 14:33:40 2018 UTC - Game is using D3D9 or D3D9Ex, preparing to hook. Sun May 20 14:33:40 2018 UTC - GetProcAddress Direct3DCreate9Ex returned wrong module (73840000='C:\WINDOWS\SYSTEM32\apphelp.dll'), proceeding anyway Sun May 20 14:33:43 2018 UTC - hookDirect3DCreate9 called Sun May 20 14:33:43 2018 UTC - IWrapIDirect3D9::CreateDevice hook called (type: 1, behavior flags: 46!) Sun May 20 14:33:43 2018 UTC - Creating D3D9 renderer Sun May 20 14:33:45 2018 UTC - Initializing Audio... Sun May 20 14:33:47 2018 UTC - Game is using dxgi (dx10/dx11), preparing to hook. Sun May 20 14:33:48 2018 UTC - Releasing all resources for device: 07FAEF20 Sun May 20 14:33:59 2018 UTC - Releasing all resources for device: 07FAEF20 Sun May 20 14:34:05 2018 UTC - Trying to setup input hook... Sun May 20 14:34:05 2018 UTC - Set input hook... Sun May 20 14:35:11 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:35:11 2018 UTC - Hooking vtable for factory Sun May 20 14:35:11 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:35:11 2018 UTC - hookCreateDXGIFactory1 called Sun May 20 14:35:11 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:35:11 2018 UTC - Hooking vtable for factory Sun May 20 14:35:11 2018 UTC - DXGIFactory1_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory2 Sun May 20 14:35:11 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:35:11 2018 UTC - Hooking vtable for factory Sun May 20 14:35:11 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:35:37 2018 UTC - Reattaching input because g_hWndGame has changed... Sun May 20 14:35:37 2018 UTC - Detaching input hook... Sun May 20 14:35:37 2018 UTC - Set input hook... Sun May 20 14:35:40 2018 UTC - Reattaching input because g_hWndGame has changed... Sun May 20 14:35:40 2018 UTC - Detaching input hook... Sun May 20 14:35:40 2018 UTC - Set input hook... Sun May 20 14:35:40 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:35:40 2018 UTC - hookCreateDXGIFactory1 called Sun May 20 14:35:40 2018 UTC - Hooking vtable for factory Sun May 20 14:35:40 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:35:40 2018 UTC - Hooking vtable for factory Sun May 20 14:35:40 2018 UTC - DXGIFactory1_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory2 Sun May 20 14:35:40 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:35:40 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:35:40 2018 UTC - Hooking vtable for factory Sun May 20 14:35:40 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:36:24 2018 UTC - Reattaching input because g_hWndGame has changed... Sun May 20 14:36:24 2018 UTC - Detaching input hook... Sun May 20 14:36:24 2018 UTC - Set input hook... Sun May 20 14:36:31 2018 UTC - Reattaching input because g_hWndGame has changed... Sun May 20 14:36:31 2018 UTC - Detaching input hook... Sun May 20 14:36:31 2018 UTC - Set input hook... Sun May 20 14:37:54 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:37:54 2018 UTC - Hooking vtable for factory Sun May 20 14:37:54 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:37:54 2018 UTC - hookCreateDXGIFactory1 called Sun May 20 14:37:54 2018 UTC - hookCreateDXGIFactory called Sun May 20 14:37:54 2018 UTC - Hooking vtable for factory Sun May 20 14:37:54 2018 UTC - DXGIFactory1_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory2 Sun May 20 14:37:54 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1 Sun May 20 14:37:54 2018 UTC - Hooking vtable for factory Sun May 20 14:37:54 2018 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1

Dimitris -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 6:03:33 PM)
I am still trying to recreate this here, but noticed a possible solution: https://steamcommunity.com/app/321410/discussions/1/1488866813758451960/#c1692669912399361635 quote: I have an update, that might be potentially a good news. Go to Steam/Setting/Shader pre-caching and disable it. I ran one of the scenarios and didn't get any freezing. Please report back if it works for you .. thanks.

NimrodX -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 6:41:00 PM)
I think I tried that before the current run and that didn't seem to fix it. I'll verify though. Also I tried disabling the steam overlay globally (in global steam settings, not just for the one game) and that didn't seem to have any effect. I left Command running in the foreground and walked away from the computer for 2-3 hours. When I came back, now I have an official windows "application not responding" condition. If it will help any I can use a tool like ProcDump https://docs.microsoft.com/en-us/sysinternals/downloads/procdump to save off a process dump of what's going on when this happens so someone can look at it in WinDbg etc. BTW, I just tried to reinstall all prerequisites in D:\Steam\SteamApps\common\Command Modern Air Naval Operations\_CommonRedist just to make sure. The 2015 vccredist won't install because it says there's a newer version. Some of the .net stuff also says there's a newer version installed. How do I verify that I have the proper versions of all the runtime libraries installed? [image]local://upfiles/59618/897630F4FF034FA6844748B334CAA78B.jpg[/image]

RoryAndersonCDT -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 8:29:52 PM)
quote: ORIGINAL: NimrodX I uninstalled Raptr a while back because it was causing problems all over the place and I'm not even sure how it got installed. Don't have the others installed. Anyway, stuff like that causes trouble all over the place. Could you please check that you have uninstalled Raptr? It shows up as "Gaming Evolved" in the uninstall list.

RoryAndersonCDT -> RE: Very sluggish UI after Alt-Tabbing back to command (5/20/2018 8:32:00 PM)
I've even heard that Raptr installs its own modified graphics drivers (for streaming), might be worth reinstalling graphics drivers just to be sure. Looking through your DXDiag file you have almost the exact same laptop as I do [:D], so definitely no issues there.

NimrodX -> RE: Very sluggish UI after Alt-Tabbing back to command (5/21/2018 5:16:45 AM)
I searched the "add/remove programs" ctrl panel for "rap" and "gaming", can't find any evidence of it. I have installed new nVidia driver updates after removing the raptr thing (maybe two weeks ago). I'll try reinstalling anyway just to make sure. I also made sure no nVidia overlay was enabled. (I have it disabled globally as I have no need for it at all.) Edit: actually I never had Raptr installed since that's some AMD thing. The thing I removed a while back was Razer https://www.razer.com/surround some surround sound processing crap which was causing problems and had no benefit at all. In any case it seems like there's an unusual level of fragility here with Steam settings considering the explicit steam integration. Is it not possible to just disable hooking of the executable in the Steamworks SDK or something?

Dimitris -> RE: Very sluggish UI after Alt-Tabbing back to command (5/21/2018 7:41:21 AM)
Can you please try this: 1) Install a free VM solution like VMWare Player or VirtualBox (assuming you're not into VMs already; if you are, go ahead with your existing poison). 2) Set up a fresh Windows 10 VM (if you don't have installation media, you can get from here: https://www.microsoft.com/en-us/software-download/windows10). 3) When the OS is set up and updated, install in it Steam and then Command. This _should_ create a pristine environment, free of wierd graphics drivers and add-ons that break more stuff than they fix (looking at you especially, MSI & ASUS). Give Command a try on this environment and see how it behaves. Thanks.

NimrodX -> RE: Very sluggish UI after Alt-Tabbing back to command (5/22/2018 6:36:27 PM)
Ok, will give that a try. (I usually use virtualbox since it's used by some things like docker and vagrant that I occasionally use.) I've only played the game for a little over 2 hours in the past two days and haven't run into any major problems during that time. I may have found something that could be contributing to problems but I'll post more when I have a better idea what's going on.

RoryAndersonCDT -> RE: Very sluggish UI after Alt-Tabbing back to command (5/23/2018 2:26:42 AM)
Please give us an update when you have a clear idea of what is going on. (If it is some other piece of software interfering with Command we would really like to know) And thanks for everything you are doing to help Command! Cheers, Baloogan

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.796875