search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.15k stars 1.06k forks source link

Worms Ultimate Mayhem (70600) #433

Open Zero86Sk opened 6 years ago

Zero86Sk commented 6 years ago

Game runs full speed, with no big glitches or anything.

There is a tiny thing with a few sound effects not working in the Weapon Select and Pause Menus in game. But Its nothing game breaking.

I think its clear for white listing

My Specs: https://gist.github.com/Zero86Sk/d629f657c1ae861c36657cdf238a7765

steam-70600.log

felisucoibi commented 6 years ago

also working here perfect, ubuntu 18.04 intel x64

Lolihunter1337 commented 6 years ago

also no issues, Linux Mint 19 Tara x64 with 4.15.0-33-generic Kernel

Medath commented 6 years ago

No issues here as well. Didn't test the multiplayer. Specs

Ruedii commented 6 years ago

Works perfect for me, even the movies. Didn't test multiplayer.

ls-1N commented 6 years ago

For me (as well as for someone else on Steam Play Compatibility Reports) it is not working well enough. Landscape is visible but worms, mines, crates, weapons, projectiles are invisible.

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 18.0.5

Tell me if there's any other information i could be providing. I have some kind of quite new integrated Intel graphics (laptop) (how to check?).

EDIT: Tried with newer drivers (Padoka PPA) and same result:

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 18.3.3 - padoka PPA

EDIT: some more information:

$ lspci | grep VGA"
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
$ uname -a
Linux pc1 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
sergioperez commented 5 years ago

I'm having the same issue, I can't see any worm or weapon:

$glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 18.2.6
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

Proton version: 3.16-6 Beta Distro: Fedora 29

edtsz commented 5 years ago

Same issue. 20181226154531_1 20181226154540_1 20181226154544_1

I tested all options, with full screen and without it, with anti-aliasing and without it, all resolutions.. none worked. :cry: 

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 18.2.6

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)

$ uname -a
Linux pc1 4.19.10-300.fc29.x86_64 #1 SMP Mon Dec 17 15:34:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
DollyVolley commented 5 years ago

I am also experiencing the same issues as the others above. Is there any known solution for this problem?

harryausten commented 5 years ago

I just installed Worms Ultimate Mayhem on Steam on my Manjaro PC and tried to play it through Steam Play. I am also experiencing the invisible worms issue. Here are my machine's details:

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 18.3.4

$ uname -a
Linux Harry-LinuxPC 5.0.3-1-MANJARO #1 SMP PREEMPT Tue Mar 19 18:26:12 UTC 2019 x86_64 GNU/Linux

If anyone has discovered a solution, I would be very interested! Used to love playing this game on PS2 back in the day :smile:

harryausten commented 5 years ago

Also tried booting into my Ubuntu 19.04 partition and reinstalled the game to test it with Mesa 19 but no joy there either :cry: 

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 19.0.0

$ uname -a
Linux Harry-LinuxPC 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:27:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
AwesamLinux commented 5 years ago

Game worked fine except that videos are either skipped (or if you try to view unlocked videos, the game gets stuck on a video playback screen where the video is just black).

media_info.txt steam-70600.log

In the logs I spotted:

217018.489:002c:002d:fixme:quartz:Parser_QueryInterface No interface for {37d84f60-42cb-11ce-8135-00aa004bb851}!
217018.489:002c:002d:warn:debugstr:OutputDebugStringA "  11720 | ***Error   : Failed to render file `Data\\FMV\\NTSC\\Logos\\Team17NTSC.wmv\r\n"

1464 The game uses quartz and the videos are: WMV, VC-1 + WMA

ls-1N commented 5 years ago

Still the same problem (lacking worms, crates, mines, barrels) on another laptop. Kubuntu 18.04. Proton 4.2-4.

$ glxinfo | grep "OpenGL version
OpenGL version string: 3.0 Mesa 18.2.8
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
$ uname -a
Linux pc3 4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
harryausten commented 5 years ago

I decided to try it again using the latest software:

I was still receiving the same invisible worms/crates/weapons issue, so I enabled the logging option in the startup menu and looked in the XOM log file that was created within the steamapps/common/WormsXHD/ directory and discovered thousands and thousands of lines of the same Error log: ***Error : .\PCPostProcess.cpp(761): GL ERROR = invalid operation (1282) I'm not sure how to investigate this further but hopefully that is helpful to someone?

EDIT: I think it may have something to do with the CG/PostProcess.cg file

Ruedii commented 5 years ago

Well OpenGL 3.0 is below the minimum specs for Proton, so that's the problem there. Likely that Intel 3rd Gen chip is the problem.

It would be nice to get an OpenGL 3.0 patch working in Proton. Likely the worm bodies use geometry shaders not supported in OpenGL 3.0

As of other issues with videos this game looks like it is another one that needs supplementary codecs in the cases where Patent Encumbered Codecs are not installed on the system. Proton should be able to install these in one manner or another if they are detected missing. I believe Valve has the appropriate licensing on this one.

It might be desirable to use a standard version anyhow, if hardware decoding support is not detected in the video driver.

Currently Intel drivers on newer chips and nVidia drivers ship with an extensive codec set, AMD's subset is smaller.

Valve may be able to get hardware assisted video decoder shaders or computer routines from AMD, Intel or one of the associated Industry groups.

I'd recommend getting all 3, SPIR-CL, SPIR-GLSLang (With versions compiled for GLSL versions 1.2 through 4.5. SPIR-V can be used instead of GLSL 4.6) and SPIR-V and selecting them based on available extensions for the use case, since onscreen or backbuffer beats offscreen in performance and load, but might not always be compatible. Notably SPIR-CL can run in SSIMD CPU extensions nicely as well. This is a big plus for including that in the bundle.)

Edit: broke up run-on paragraph for clarity.

kisak-valve commented 5 years ago

Hello @Ruedii, Mesa 18.2 on Kaby Lake (Gen 9.5 graphics) supports OpenGL 4.5 (core context) and Vulkan. The version mentioned by @harryausten is the compatibility context reported by the driver instead of the core context support.

Ruedii commented 5 years ago

Hello @Ruedii, Mesa 18.2 on Kaby Lake (Gen 9.5 graphics) supports OpenGL 4.5 (core context) and Vulkan. The version mentioned by @harryausten is the compatibility context reported by the driver instead of the core context support.

Yes, Thanks for the correction to both of us. My further research confirms your note and then some. Kaby Lake even support Vulkan. It is more than sufficient. Some other Intel chip support cases might be an issue, but not this one.

So long as the Mesa version is recent, Kaby Lake should work fine. Some older Intel chips might not have as much luck.

As of video issues, we need a solution for patent encumbered codecs. That seems to be the big barrier as of "videos don't work" on this game and many others.

I think Valve has the unlimited license patent rights to provide this if you could check. It might be good to add this function to Steam Runtime as well as Proton.

If Valve does have the Patent rights, they may be able to go and grant rights for use in "Steam Games, and General Non-Commercial Use" to all Linux users who download steam. This would be a good way for them to give back to the Open Source community, and really win over the naysayers about them. I'd recommend complete licensing, but I suspect that is well beyond the scope of what Valve can sub-license without paying per-user fees.

Kron4ek commented 5 years ago

The solution for invisible worms and weapons on intel GPUs (Gen8+) is to use Mesa 19.1+ and enable new Iris driver:

export MESA_LOADER_DRIVER_OVERRIDE=iris
ls-1N commented 5 years ago

I will test it out when Mesa 19.1 trickles down to Ubuntu 18.04's bionic-updates.

Ruedii commented 5 years ago

Good luck on it ever getting into bionic updates. It might make it into the LTS stack updates, but it would be preferable to use the Padoka Mesa Stable PPA recommended in the Proton documentation.

On Mon, Jul 8, 2019, 8:00 AM i-need-to-tell-you-something < notifications@github.com> wrote:

I will test it out when Mesa 19.1 trickles down to bionic-updates https://packages.ubuntu.com/bionic-updates/libegl1-mesa.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/433?email_source=notifications&email_token=AAYFL2OEJ7HF3W4ESWTBEA3P6MT5TA5CNFSM4FRPQ2WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZM3RPI#issuecomment-509196477, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYFL2M6UCM2O5CWS3R6GR3P6MT5TANCNFSM4FRPQ2WA .

ls-1N commented 5 years ago

@Ruedii Ah thanks a lot! I was mentioning that specifically in the hopes that someone would correct me if I'm wrong. I guess I'll eventually try that then.

hakzsam commented 4 years ago

Are you guys able to reproduce the problem reported by @edtsz with Mesa 19.3?

kisak-valve commented 4 years ago

Dropping the Mesa drivers label due to lack of feedback.

Ruedii commented 4 years ago

I have not been able to replicate the issue at all on Mesa/AMDGPU Rx480. I suspect it is a hardware specific issue.

ls-1N commented 4 years ago

Adding MESA_LOADER_DRIVER_OVERRIDE=iris %command% to the game's launch options in Steam fixed it for me!

My system info:

Kubuntu 18.04 Proton 4.11-12 Intel 9th gen integrated GPU ``` $ glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 19.2.8 ``` ``` $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) ``` ``` $ uname -a Linux pc3 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ```
Ruedii commented 4 years ago

Adding MESA_LOADER_DRIVER_OVERRIDE=iris %command% to the game's launch options in Steam fixed it for me!

My system info:

Definitely a driver bug.

The question is that since a lot of people use Intel Integrated GPUs and this game SHOULD be able to run on most newer Intel Integrated GPUs, should this be considered a blocking for whitelist or not?

Another question to bring up is there a way to correct the WineD3D stack for this, or is this a behavior that should be fixed in the Mesa stack itself? Also, as always on such things, two things can be true: so patching WineD3D and submitting a bug report and/or patch to Mesa is not a bad idea.

edtsz commented 4 years ago

Just worked with MESA_LOADER_DRIVER_OVERRIDE=iris %command%. I tried without custom launch command but didn't work.

$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 19.2.8
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop 9 Series) (rev 02)
           /:-------------:\          me@edtsz
        :-------------------::        OS: Fedora 
      :-----------/shhOHbmp---:\      Kernel: x86_64 Linux 5.5.10-200.fc31.x86_64
    /-----------omMMMNNNMMD  ---:     Uptime: 2d 4h 46m
   :-----------sMMMMNMNMP.    ---:    Packages: 2156
  :-----------:MMMdP-------    ---\   Shell: bash
 ,------------:MMMd--------    ---:   Resolution: 2560x1080
 :------------:MMMd-------    .---:   DE: LXDE
 :----    oNMMMMMMMMMNho     .----:   WM: OpenBox
 :--     .+shhhMMMmhhy++   .------/   WM Theme: FlatStudioDarkOB
 :-    -------:MMMd--------------:    GTK Theme: Adwaita-dark-my [GTK2]
 :-   --------/MMMd-------------;     Icon Theme: Fedora
 :-    ------/hMMMy------------:      Font: Sans 10
 :-- :dMNdhhdNMMNo------------;       CPU: Intel Core i7-9700T @ 8x 4.3GHz [27.8°C]
 :---:sdNMMMMNds:------------:        GPU: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) 
 :------:://:-------------::          RAM: 4269MiB / 7736MiB
 :---------------------://
tralph3 commented 3 years ago

Hi, the command worked and now I can see the worms in game, however the performance is crap. I was getting 60 FPS before and now I have 10. I have an Intel HD 4000. Any idea why it's going so slow?

The-Shotgun commented 2 years ago

Works nearly perfectly, but there is a notable glitch in that PIP camera after damaging a worm on AMD graphics card and processor. According to the ProtonDB page this also affects the Steam Deck.

Blisto91 commented 2 years ago

@The-Shotgun would it be possible for you to show a screenshot of the issue?

The-Shotgun commented 2 years ago

@The-Shotgun would it be possible for you to show a screenshot of the issue?

I think a video will demonstrate it better. The camera is supposed to follow the fired weapon, then the worm that's hit by it.

hakzsam commented 2 years ago

@The-Shotgun What Mesa version are you using?

hakzsam commented 2 years ago

Are you still able to reproduce this issue with up-to-date driver? I tried on Steam Deck and the camera looked fine.

Poomex commented 1 year ago

Can confirm the issue with the Picture in Picture mode on AMD. My config:

poomex@debian:~$ lspci | grep VGA 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c1)

OS: Debian GNU/Linux bookworm/sid x86_64 Host: GL702ZC 1.0 Kernel: 5.10.113-xanmod1 Uptime: 4 days, 3 hours, 33 mins Packages: 5042 (dpkg), 32 (flatpak) Shell: bash 5.2.15 Resolution: 1920x1080, 1920x1080 DE: Plasma 5.26.90 WM: KWin WM Theme: Prof-Dark Theme: Breeze Dark [Plasma], Breeze [GTK2/3] Icons: Fluent-dark [Plasma], Fluent-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 7 1700 (16) @ 3.000GHz GPU: AMD ATI Radeon RX 470/480/570/570X/580/580X/590 Memory: 7706MiB / 32107MiB