The Ultimate Site of Worms Armageddon
Worms: Armageddon => Tech Support => Topic started by: Alien on August 16, 2020, 10:21 AM
-
problem 1: menu & lobby
explorer, browser etc changing from screen 2 to screen 1 and vice versa when minimize/maximize (menu & lobby). this also happens when i start wa.exe, join host (from snooper), game starts (lobby), game ends and goes back to lobby, exit the game.
problem 2: in game
minimize works without problems when in game. not always but often enough to be very annoying the game/screen freeze for like 30 seconds when maximizing. after the 30 seconds wait the screen unfreeze and i can try to maximize the game again, if i am lucky the game/screen wont freeze again. mostly im gettting a little black box top left of the screen and sometimes black screen or just normal screen when freezing. other players in the game getting big lag because of this.
3.7.2.1. update works without any problems at all, its only with 3.8 update.
i have the cd version and also tried the gog version (clean install). same problems with both versions.
windows 10 home 2004 (installed all updates)
intel core i7-4790 @ 3.60ghz
geforce gtx 1060 6gb (latest driver version 451.67)
16gb ram
-
https://worms2d.info/SuperFrontendHD
-
Hi Alien,
Problem 2 can be worked around by disabling full-screen optimisations (WA.exe Compatibility tab)
You could also try enabling Windowed mode in advanced settings (this might solve both problems).
https://worms2d.info/SuperFrontendHD
also this.
-
I have the Steam version and experience the second issue, although it's rare for me. When it does happen, like you, the WA screen is black for a while and I can confirm that other players experience lag when this happens. Wasn't an issue in 3.7.2.1. Possible workaround is to use windowed mode, full resolution (so it's like full screen on the monitor) and use the New Desktop feature in Windows 10 (WINDOWS KEY + TAB) and alternate between desktop and WA instead of minimizing.
Not sure about the first issue but I it would be good if WA could recall which screen it was run on and support full screen on secondary monitor without having to first set the monitor as primary in Windows.
-
did you update to 3.8? open game files, go to Tweaks and open "WindowedMode_On.reg" with admin
-
thank you all for the answers and help.
wksuperfrontend solved problem 1 and disabling full-screen optimisations (WA.exe Compatibility tab) solved problem 2.
windowed mode worked too.
-
...and use the New Desktop feature in Windows 10 (WINDOWS KEY + TAB)
...just for clarification - ⊞ + Tab also works with win7 so this is nothing new :)
-
...and use the New Desktop feature in Windows 10 (WINDOWS KEY + TAB)
...just for clarification - ⊞ + Tab also works with win7 so this is nothing new :)
"New Desktop" as in add a "New Desktop" - not saying the feature is new. Have you managed to ABX .opus vs .wav yet Mr.Smarty Pants? ;)
-
Yeah i've had nothing but issues with 3.8 as well, the fact it doesn't work on it's own without pissing around with it puts me right off.
-
i'm pretty sure for whatever game you are playing you want to have "disable fullscreen optimizations" checked in the compatibility tab on each games .exe that you play on win10. i know i do that for games like CS:GO, left4dead2, etc... idk if i'm right or wrong but pretty sure you want to do that... i play all my games fullscreen 1080p
-
Yeah i've had nothing but issues with 3.8 as well, the fact it doesn't work on it's own without pissing around with it puts me right off.
Unless these are issues that have already been reported, please document these clearly so they can be fixed rather than just generically moaning about them which will achieve absolutely nothing.
-
Yeah i've had nothing but issues with 3.8 as well, the fact it doesn't work on it's own without pissing around with it puts me right off.
Unless these are issues that have already been reported, please document these clearly so they can be fixed rather than just generically moaning about them which will achieve absolutely nothing.
Muzer, my man.. Some ppl will rather spend time looking for the hair in the egg, than eating it.
-
Yeah i've had nothing but issues with 3.8 as well, the fact it doesn't work on it's own without pissing around with it puts me right off.
Unless these are issues that have already been reported, please document these clearly so they can be fixed rather than just generically moaning about them which will achieve absolutely nothing.
Muzer, my man.. Some ppl will rather spend time looking for the hair in the egg, than eating it.
Who wants to eat eggs with hair in it? :D
-
Hi everyone, I got 3.8 update and after I set graphics to OpenGL 4.0 (shader) it gave me the following window:[attachment=1]
When I switch it back to Direct3D 9 it works fine.
My laptop is Dell Latitude E5410 with Intel HD Graphics.
-
Hi everyone, I got 3.8 update and after I set graphics to OpenGL 4.0 (shader) it gave me the following window:[attachment=1]
When I switch it back to Direct3D 9 it works fine.
My laptop is Dell Latitude E5410 with Intel HD Graphics.
can you translate the error message into english?
-
Yes.
Failed graphics initialization
OpenGL error: wglGetProcAddress (glCreateShader)
-
you can probably stick to direct3d shaders for now
-
Hi everyone, I got 3.8 update and after I set graphics to OpenGL 4.0 (shader) it gave me the following window:[attachment=1]
When I switch it back to Direct3D 9 it works fine.
My laptop is Dell Latitude E5410 with Intel HD Graphics.
Your graphics card is very weak and does not support OpenGL 4.0 with fragment shader. You cannot use OpenGL Shader.
You can use this utility to check what versions of OpenGL are supported: http://www.realtech-vr.com/support/deeplink.php?SKU=15&target=UrlWin32
-
Oh, I expected that, thank you... But is there any visual difference from Direct3D 9?