Open mrjustaguy opened 1 month ago
It's the DisplayResolution setting that broke it. Use DisplayResolution=app until I can figure out why. The GOG version doesn't have this issue, so it might also be fixable by one of the (semi-)official patches. Have you checked PCGamingWiki?
I'm using a CD copy (european, not sure which version though) but I haven't tried any yet patches.
DisplayResolution=app works, it just breaks full res gameplay (crashes) so basically the old 3.2 functionality, but without the 3.2 driver problem (which for me tbh is functional, just not optimal) log.zip
However I have further information
Setting DisplayResolution=1024x768 (max supported res) results in no crash in gameplay, and it also shows why I was not seeing the UI in some menus, such as weapons and game options menus in singleplayer/multiplayer game configurator (top right option) The UI was moved Down Left, and was oversized, indicating that the UI is attempting to scale to display resolution and not window resolution
setting DisplayResolution=640x480 fixes the menus, and allows for 1024x768 gameplay without crashing, it's just a bit blurry (functionally it's better as you're able to see more)
I've also toyed around with 640x480 windows compat and it just made a small window on the top left of the screen.
Worms Armageddon using ddrawcompat 3.2 works fine minus having to run the games at the minimum resolution of 640x480
versions 3.2 above, the game runs at highest resolution, but now some menus and the map editor are broken (just displays background and nothing else) the game behaves the same from 4.0 to the latest, so the only difference happens changing from 3.2 to 4.0+
On latest Windows 11, Adrenaline 24.8.1 (9.1 breaks 3.2 completely), RX 6600
The logs between the versions are identical, aside from the added information from in newer versions, so I'm just adding the Newest version Log, though I don't expect the log to be all that useful, as more useful would be knowing what was changed on the rendering side from 3.2 vs the next version
EDIT: I've figured out that I can get the Debug log into a zip to make it shippable on Github and that's the one that may actually be useful as it was above 25mb uncompressed (at like 95MB)
log.zip