search

ValveSoftware / Proton

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

World of Warships (552990) #333

Open dtanderson opened 6 years ago

dtanderson commented 6 years ago

I played several matches and did not experience any issues.

Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD FX(tm)-6300 Six-Core Processor
Speed: 3500 Mhz

Operating System Version: Ubuntu 18.04.1 LTS (64 bit) Kernel Name: Linux Kernel Version: 4.15.0-32-generic X Server Vendor: The X.Org Foundation X Server Release: 11906000 X Window Manager: GNOME Shell

Video Card: Driver: NVIDIA Corporation GeForce GTX 1060 6GB/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 396.51 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 20.91" x 11.77" (23.98" diag) 53.1cm x 29.9cm (60.9cm diag) Primary Bus: PCI Express 16x Primary VRAM: 6144 MB Supported MSAA Modes: 2x 4x 8x 16x

Sound card: Audio device: Realtek ALC889

Memory: RAM: 16022 Mb

nightsky30 commented 4 years ago 
Linux
- Fixed “STOP” button in the Library having no effect for non-Steamworks titles

Looks like this might be fixed. Will retest and see :)

Konfuz commented 4 years ago

The game freezes very often right after the end of the match, before getting the scores, then i can only kill all processes and restart the game. Also the armory page after last update doesn't load. I attach the log after last freeze.

I'm running Arch linux (Linux archlinux 5.6.13-arch1-1 #1 SMP PREEMPT Thu, 14 May 2020 06:52:53 +0000 x86_64 GNU/Linux), i3wm, latest nvidia drivers, latest steam beta version, proton 5.0-7, launch options: gamemoderun %command%

wowsfreeze.txt

I had the same probem. About 90% of match ends froze my Game, sometimes the entire PC. However setting PROTON_NO_FSYNC=1 did resolve that issue for me.

ghost commented 3 years ago

Lately my game keep crashing a lot after the logo screen. Usually after 3-4 restarts the game works again.

log.txt crit

nightsky30 commented 3 years ago

Screenshot_2020-11-24_12-41-34

Darxus commented 3 years ago

Mine was working great until it stopped working at all yesterday. Looks likely to be the same problem as the last two people who posted. I suspect it is related to these files that got updated yesterday:

./platform64.dll ./bin/3052606/bin64/platform64.dll ./bin/3052606/bin32/platform.dll ./bin/3052606/res/texts/*/LC_MESSAGES/global.mo

The splash screen loads fine, it says logging in, then it crashes before it gets to the main screen. Every time.

I'm running ubuntu 20.04. Tried default proton (5.13-2) and 5.0-10.

https://steamcommunity.com/app/221410/discussions/0/2962768718544364573/ https://www.protondb.com/profile#wup0GbJlpr

Darxus commented 3 years ago

This launch option makes it work: PROTON_USE_WINED3D=1 %command% To verify, I removed it and it stopped working, and I added it back, and it started working again.

Distro:Ubuntu 20.04.1 LTS Kernel:5.4.0-54-generic RAM:32 GB GPU Driver:4.6 Mesa 20.0.8 GPU:AMD Radeon RX 5700 XT CPU:AMD Ryzen 7 3700X 8-Core

Darxus commented 3 years ago

With PROTON_LOG=1 (and not PROTON_USE_WINED3D=1), when it crashes, files generated attached. (Found by running "touch ~/now" then running wows, then "find . -newer ~/now".)

WorldOfWarships64_d3d11.log debug.log monitor_20201124_2336560443.log python.log wowscrash.zip

.zip contains .dmp and .crash files, which I wasn't otherwise allowed to attach.

agolovanov commented 3 years ago

I have the same crash as the folks above. I've tried testing it on different Proton versions (without setting PROTON_USE_WINED3D): crashes on 5.13-2, 5.0-10, 4.11-13, 4.2-9, but seems to be working on 3.16-9. I assume all of the use DXVK by default, so perhaps it's some regression in DXVK.

anonymous133 commented 3 years ago

Same here.

I downgraded packages

lib32mesa, mesa vulkan radeon and linux kernel to 5.9.9

since they all got an update today but that didn't help.

I'm running it via Lutris with Proton 5.13 with same crash after 'logging in'.

I think the Wargaming Gamecenter Update might be responsible for the crash which got installed also just before the game stopped working.

Darxus commented 3 years ago

The response in the DXVK bug I opened above is: "TL;DR use wined3d for this game, I can't fix this."

Which means using the launch option: PROTON_USE_WINED3D=1 %command%

So, it looks like the default settings need to be updated to default to wine3d?

Which is a shame, because it works better with DXVK than wine3d.

Who has experience trying to talk software developers into making their stuff work with things like DXVK, and can provide advice?

Darxus commented 3 years ago

And I just realized it's basically unplayable with wined3d. I can't see smoke, which is critical for judging speed / aiming. It's there, but maybe the ocean is rendered too dark to be able to see it.

Where do we report wined3d bugs? Against wine itself? This https://wiki.winehq.org/Bugs ?

agolovanov commented 3 years ago

And I just realized it's basically unplayable with wined3d. I can't see smoke, which is critical for judging speed / aiming. It's there, but maybe the ocean is rendered too dark to be able to see it.

I played 8 matches on Proton 3.16-9 with DXVK today, didn't notice any significant bugs, although the game hang once at the moment a match ended. So this older Proton version might be the best temporary solution at the moment.

Darxus commented 3 years ago

I played 8 matches on Proton 3.16-9 with DXVK today, didn't notice any significant bugs, although the game hang once at the moment a match ended. So this older Proton version might be the best temporary solution at the moment.

Thank you very much, that also worked for me. I think it's also more stuttery than the default proton had been. But otherwise worked great for a game. Far more usable than PROTON_USE_WINED3D=1

It may be worth mentioning that the first time I tried proton 3.16-9, it got to the main menu, and basically hung there. I could hear music, but couldn't interact with the screen at all. Then I tried more versions:

5.0-10 Crashed before main screen 4.11-13 Crashed before main screen 4.2-9 Didn't even load splash screen 3.16-9 Second time, it worked

I was also able to confirm that with wined3d, the problem is the ocean getting rendered so dark that I can't see the smoke. Which is critical.

It looks like after alt-tabbing away from it, I can't get back to it.

hatani commented 3 years ago

Thank you so much, downgrading from originally proton-5.6-GE2 (also trying 5.13-2 without success) to suggested 3.16-9 fixed the issue for me too, was failing during Loading step of game startup on some mem/virtualmem errors. My system is Fedora W32 with custom llvm, mesa-aco.

Darxus commented 3 years ago

There has been progress on getting it to work with newer versions of proton in the DXVK bug. If you're interested, go subscribe to that: https://github.com/doitsujin/dxvk/issues/1834#issuecomment-734266900

Darxus commented 3 years ago

Looks like the crashes that started being reported here on November 23rd magically fixed themselves: https://github.com/doitsujin/dxvk/issues/1834#issuecomment-736011682 ¯\_(ツ)_/¯

Darxus commented 3 years ago

Before the recent crashing problem first reported eight days ago, November 23rd, I was regularly leaving WoWS idling in the background while I did everything else. With no problems. Now it's using more CPU, and more annoyingly, audio playback in things like youtube is stuttery. I certainly have no idea where to begin, but I figured I'd mention it. Would this be wine, not dxvk?

Darxus commented 3 years ago

Very similar to last bug, it's now crashing every time at "synchronizing". Lots of files updated in the game today.

Darxus commented 3 years ago

And like last time, it works with Proton 3.16-9. So it might be a problem with the way DXVK reports its version information.
https://github.com/doitsujin/dxvk/issues/1834#issuecomment-734266900

anonymous133 commented 3 years ago

@Darxus I can't reproduce it this time. It runs with my modified DXVK as well as with their latest release 1.7.3 and Proton 5.13-4.

Maybe attach the proton log of yours so the devs can take a look (PROTON_LOG=1 %command%).

Darxus commented 3 years ago

Proton log: steam-552990.log.gz

nightsky30 commented 3 years ago

PROTON_USE_WINED3D=1 %command% no longer fixes the crashing for me :unamused:

jcochran26 commented 3 years ago

PROTON_USE_WINED3D=1 %command% no longer fixes the crashing for me

Same... crashes on synchronizing.

Darxus commented 3 years ago

I should clarify that the armory doesn't work for me, with proton 3.16-9. Which I miss.

@anonymous133 since you can't reproduce it, we should probably figure out what's different. I have: World of Warships version 0.9.11.0 (which it says in the upper left corner when it crashes, WorldOfWarships.exe modified December 10th) PowerColor Red Devil AMD RX 5700 XT Ubuntu 20.04, up to date. Mesa 20.0.8 My PPA that updates all firmware from the kernel repo: https://launchpad.net/~darxus/+archive/ubuntu/linux-firmware-daily (Everything else is stock Ubuntu.)

No launch options. Default proton.

I'm super amused that AMD mentions my amdgpu PPA in their latest linux software release notes: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-45

anonymous133 commented 3 years ago

@Darxus Wows 0.9.11 Radeon Vega 64 Arch Linux 5.9.14 mesa-20.3.1-1 No launch options. Default proton via lutris.

I'm running all the latest packages provided via the arch repository. Nothing special on my side regarding anything else.

agolovanov commented 3 years ago

Like the previous time, it magically seems to have stopped crashing after a couple of days. I currently can run WoWs with the latest Proton (5.13-4), although I couldn't two days ago.

Darxus commented 3 years ago

Same, I can now get to the main menu without a crash, with the latest proton. I don't see any local files that have been updated. So again it looks like a server side change. Thanks @agolovanov.

Darxus commented 3 years ago

Oh that's fun. The game went from "0.9.11.0" to "0.9.12.0" on the loading screen, without any changes to local files.

RonnySvedman commented 3 years ago

Recently stopped working for me again. Crash with dialog box:

Critical Error Occurred

Message: Interface::enumerateDevices: No fullscreen display modes were detected!

As before, going back to proton 3.16-9 gets it working, but with stuttering graphics, and (i kid you not) 15 minutes of 400%cpu "processing vulkan shaders" before opening. The crash with newer versions happens within a minute of clicking "play" in the steam library.

I have a crash dump if it helps.

Ubuntu 20.04.1 LTS, i53570, 16G ram, rx580

Darxus commented 3 years ago

Recently stopped working for me again. Crash with dialog box:

When are you getting this crash? Are you getting to the main menu? Is it in game play? Most of the crashes lately have been just before the main menu. I can currently get to the main menu. Mine says version 0.9.12.0 in the upper left hand corner while "synchronizing".

It looks like I haven't had any files updated since Dec 18, the last crash. Either I haven't gotten the update that's causing your crashes, or this one is different, or it's not effecting me.

I haven't been playing this game much lately. I'm tired of how much development of this game is motivated by greed instead of trying to make a good game.

kisak-valve commented 3 years ago

World Of Warships Proton 5.13.5 crash (dump included)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4623. @webaake posted on 2021-02-16T08:45:25:

Compatibility Report

System Information

Symptoms

Crash Dump:

``` Application Z:/mnt/506GB/STEAM/steamapps/common/World of Warships/bin/3343484/bin64/WorldOfWarships64.exe crashed 02.16.2021 at 09:14:39 Message: Unhandled exception Hash: 51319 EIP: 0x00000000410A1550 Current thread #276 native trace: (0) : WorldOfWarships64.exe!0x00000001410A1550 (0) : WorldOfWarships64.exe!0x00000001410E590E (0) : WorldOfWarships64.exe!0x00000001410E2C3C (0) : WorldOfWarships64.exe!0x00000001410E6699 (0) : WorldOfWarships64.exe!0x000000014113A645 (0) : WorldOfWarships64.exe!0x000000014114DFE9 (0) : WorldOfWarships64.exe!0x00000001410B89D0 (0) : WorldOfWarships64.exe!0x00000001410E69F6 (0) : WorldOfWarships64.exe!0x00000001411B0011 (0) : WorldOfWarships64.exe!0x00000001411ADFD3 (0) : WorldOfWarships64.exe!0x00000001411ADB32 (0) : WorldOfWarships64.exe!0x00000001411AC2FD (0) : WorldOfWarships64.exe!0x000000014114DFE9 (0) : WorldOfWarships64.exe!0x00000001410E1113 System info: OS Name: Windows 7 OS Version: 6.6 SP1 OS Architecture: x86_64 Memory info: Virtual memory: 64Kb/137438953343Kb (1%) Working set (process physical memory): 2735752Kb/16795388Kb (16%) Commit charge (working set + process page file usage): 2375564Kb/16795392Kb (14%) Global physical memory: 5319884Kb/16795388Kb (31%) Global commitable memory (physical + pagefile): 4833232Kb/16795392Kb (29%) System info: APPLICATION = DISPLAYDEVICE 0 = \\\.\\DISPLAY1, GeForce GTX 745, PCI\\VEN_10DE&DEV_1382&SUBSYS_00000000&REV_00 ```

Reproduction

webaake commented 3 years ago

Exactly the same problem with Proton 5.13.6 and experimental. 3.16 works, but can't get into armory. I had it working, so it's a bummer. And this is with both WoS 0.10.0 and 0.10.1. Same dump text as above.

gbschenkel commented 3 years ago

After the last updated, the game started crash again while log in. Appears the game do a regression with proton compability each time happen a update release.

webaake commented 3 years ago

I hope they will solve this. It's a bit jittery with proton 3.16 and you can't use the Armory. Without the Armory the game is very crippled. I've been playing for a couple of months now without any problems and suddenly crashes started to appear. Between Steam, Proton and Wargaming it gets very complicated and complex to figure out. Let's hope for the best. It's a great game.

gbschenkel commented 3 years ago

The Proton Experimental(Steam) which just released today have restored the game.

tomaszg7 commented 3 years ago

Proton Experimental doesn't work for me. I also had to downgrade to 3.16. Note that 5.0-10 or 4.11-13 are also broken.

webaake commented 3 years ago

Todays Wows server update fixed the big login problem with Proton 5.13.6! And the Armory works, at least in 5.13.6.

billyb13 commented 3 years ago

Hello, I have problem running game in Linux Ubuntu mate 18.04.5 LTS. I've tried all of Proton versions but none work. Can someone help me? Attached error dump.

WorldOfWarships64-2021-02-27_08-56-27.dmp.zip zaslonska_slika-2021-02-27 09-09-32 zaslonska_slika-2021-02-27 09-10-46

webaake commented 3 years ago

The "'.dmp"-file isn't readable. If you look carefully in the crash log directory there's an exactly the same file but with another file suffix (.log or .crash ?) That's a plain textfile, which is a lot easier to open and read.

The second "DirectX" message seems for me, to not do anything or cause anything. I get that all the time. I think it's misconfiguration in Proton from the developers.

Do you open Wows inside Steam or from a desktop link? From inside Steam you ger better control of what's happening with updates and stuff. Is your Wows updated? Do you have a reasonably new graphics card? I have an older GTX745, which I suspect will not hold out for long. Older cards can't take the newest drivers, and Wows depends on somewhat new drivers. I hope the newest update coming soon (0.10.2?) will not crash my setup.

mjrk commented 3 years ago

I join the club, getting a similar error like @billyb13 , here my workaround (linux mint xfce):

It won't start next time. But it starts again, when I perform the steps above (I don't know if I can trigger a first time setup manually, but I think, this has to be done to start the game). So, maybe there is some issue with the setup of the redistributable packages, however, I cannot tell.

dfryer1193 commented 3 years ago

On my system, I get the same error as billyb, webaake, and mjrk on my first startup, but the game launches fine on subsequent launches - the problem I have now is that it looks like light/reflection textures are failing to load, resulting in the water having a neon green hue to it.

Edit: Setting PROTON_USE_WINED3D11=1 resolves the light/reflection textures issue, but introduces translucent red shapes over the game UI.

kisak-valve commented 3 years ago

DxDiag seems faulty - Proton 5.13.6

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4761. @webaake posted on 2021-04-18T14:26:53:

Proton 5.13.6 - DxDiag always shows a message just after starting World of Warships in Steam. The message is (translated): "Usage: dxdiag[/whql :off] | [/whql:on] | [/t filename] | [/x filename]"

This is always when starting Wows and has been with version 5.13.6.

The problem is that it really seems to take a lot longer to start the game. Is there a fix for this in Proton? Can I edit some text file and tell Dxdiag to relax?

Wows/Steam/Proton works really wonderful so this is a small problem. I am very thankful for Proton and how well it works. So thanks for the hard work guys!

Other info: Ubuntu LTS 18.04, Nvidia 450.102.04

MancombSeepgoodsMom commented 3 years ago

Interface::enumerateDevices: No fullscreen display modes were detected!

I'm getting this same error every time I try to launch the game through steam. I've been trying to set up wows for the first time - haven't been able to start the game, yet. As I understand from previous posts, it might have to do with the age of the gpu. I'm using an R7 360, so I guess this might be the root of the problem?

gbschenkel commented 3 years ago

Since the last patch the game "stop responding" when entering the first battle. What I mean is when the first battle is found and the 30s countdown for battle start, the interface spots responding, when 5s arrive, was to the screen change to the actual battle, but, it not change, I can receive invites but can't do nothing. Then I need to kill the game and start again, when entering the game, WoWs rejoin you in battle you was suppost to be playing, and you are able to play. This happen always in the first time, and after the first battle, it happen sometimes, appears having relation when changing ship or the type match(rank/random/...)

I asked about this for others members, but didn't found none with this problem, but everyone I have asked, play on Windows.

gbschenkel commented 3 years ago

Interface::enumerateDevices: No fullscreen display modes were detected!

I'm getting this same error every time I try to launch the game through steam. I've been trying to set up wows for the first time - haven't been able to start the game, yet. As I understand from previous posts, it might have to do with the age of the gpu. I'm using an R7 360, so I guess this might be the root of the problem?

I was using NVidia GTX 1980 and I didn`t have any problem for a old card, right now using a Radeon Asus TUF 6800XT.

anonymous133 commented 3 years ago

I'm having the DXdiag warning appear with wine 6.6 as well.

I'm using a Radeon Vega 64

But on my end it doesn't seem to slow down anything. Just a window that pops up during start up. screenshot

MancombSeepgoodsMom commented 3 years ago

I was using NVidia GTX 1980 and I didn`t have any problem for a old card, right now using a Radeon Asus TUF 6800XT.

Maybe your cards are new enough. they're both newer than my r7. Not by much but they are.

webaake commented 3 years ago

Unexpectedly started crash in start this morning again. No updates since lastnigth when it worked 100% with Proton 5.13.6. Here's my Wows-ticket: In Steam (Linux) Wows do not start. I've tried everything in Steam; different Proton versions, check local files, delete local file cache. Restarts and reboots. It worked 100% okay last night and just this morning Wows wouldn't start. There wasn't even a reboot in between. My system is updated including Steam and Wows.

Wows crashfile:

``` Application Z:/mnt/506GB/STEAM/steamapps/common/World of Warships/bin/3747819/bin64/WorldOfWarships64.exe crashed 04.29.2021 at 10:03:37 Message: Unhandled exception Hash: 37539 EIP: 0x00000000405D94AF Current thread #248 native trace: (0) : WorldOfWarships64.exe!0x00000001405D94AF (0) : WorldOfWarships64.exe!0x00000001405D8A28 (0) : WorldOfWarships64.exe!0x0000000140B79B5D (0) : WorldOfWarships64.exe!0x00000001400C9D11 System info: OS Name: Windows 7 OS Version: 6.6 SP1 OS Architecture: x86_64 Memory info: Virtual memory: 64Kb/137438953343Kb (1%) Working set (process physical memory): 487672Kb/16795348Kb (2%) Commit charge (working set + process page file usage): 428176Kb/16795352Kb (2%) Global physical memory: 2034312Kb/16795348Kb (12%) Global commitable memory (physical + pagefile): 1546892Kb/16795352Kb (10%) System info: APPLICATION = DISPLAYDEVICE 0 = \\.\DISPLAY1, GeForce GTX 745, PCI\VEN_10DE&DEV_1382&SUBSYS_00000000&REV_00 ```

The crash file looks nearly the same when using Proton version 6.3.x (Win 10).

I hope it will unexpectedly fix itself.

kisak-valve commented 2 years ago

World of Warships not launching

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5434. @demib72 posted on 2021-12-22T09:17:09:

Compatibility Report

Your system information https://gist.github.com/demib72/2f915c3c97a29f3d722006f6dab0b173

Tried Proton Experimental, 6.3-8, 5.13-6, 3.16-9

Please describe your issue in as much detail as possible: I recently reinstalled World of Warships and got it to work once. Afterwards, the game would start but fail to properly render the game and now it will not start at all. It might be related to ValveSoftware/Proton#5340, but one of the fixes like no_fsync option has made any difference for me.

Command and cli logs: https://gist.github.com/demib72/5c5cbbc74d10bd98ea9fad92c8e21689 Proton log: https://gist.github.com/demib72/bed3f92807e1a24cdeac80acc192ca3b

The Proton logs aren't telling me anything, so I think I need some help in figuring this out.

Steps for reproducing this issue:

  1. Run World of Warships from Steam
RokeJulianLockhart commented 2 years ago

I am unable to play it:

Audio plays, but

image

appears, so no graphics are presented.