Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

World of Warships (552990) #333

Open
dtanderson opened this issue Aug 23, 2018 · 162 comments
Open

World of Warships (552990) #333

dtanderson opened this issue Aug 23, 2018 · 162 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton XAudio2 Uses the XAudio2 subsystem

Comments

@dtanderson
Copy link

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

@kisak-valve kisak-valve added the Whitelist Request Community tested games to be whitelisted in Steam label Aug 23, 2018
@kisak-valve kisak-valve changed the title [Whitelist] World of Warships [Whitelist] World of Warships (552990) Aug 23, 2018
@ElricleNecro
Copy link

I do have a crash preventing the game to launch. The message it gives is: "Could not create new SimpleThread".
I am running on Arch Linux 64bit, with a Nvidia GTX 980 and Intel i7-2600 CPU @ 3.40GHz with 16GB of RAM.

@kisak-valve
Copy link
Member

world of warships (steam) unhandled exception, access violation

Issue transferred from #595.
@Demonslayer2011 posted on 2018-08-25T22:10:24:

usually happens in game, when lots of things are going on at once. causes a fatal crash, sometimes freezes and has to be force closed, sometimes just crashes and exits.
system
Distributor ID:\tUbuntu
Description:\tUbuntu 18.04.1 LTS
Release:\t18.04
Codename:\tbionic
hardware: ryzen 1600x, asus crosshair VI hero rev 1 firmware ver. 1201
8gbx4 DIMM DDR4 Synchronous Unbuffered (corsair vengeance) 2133 MHz (0.5 ns)
dual boot windows 10. both ubuntu and windows run on their own 1tb hdd, and share a third ntfs formatted drive.

have at time of post, newest steam update, the one that rolled out today.

here is the crash and dump files.

WorldOfWarships-2018-08-25_13-38-43.crash.txt
WorldOfWarships-2018-08-25_13-38-43.dmp.txt

if more info is needed please let me know.

@dtanderson
Copy link
Author

Just played about 5 more matches tonight, it is running great for me.

@nightsky30
Copy link

nightsky30 commented Sep 1, 2018

I've played a ton and only had 1 freeze at a loading screen and 1 crash. The crash could have just been Steam as Steam crashed completely as well.

75fps, default gfx detail settings...haven't really messed with that stuff yet other than the window resolution.

System: https://gist.github.com/nightsky30/9a7078abf4346ad7225819a971e5c7f9

@Demonslayer2011
Copy link

Follow up on my crash report. It's gotten much more stableseems to improve the longer I play the game. Maybe proton has a learning algorithm built in? 720p windowed default graphic settings seem to work fine. High settings there is artifacting and outlines of the bottom of ships and landmasses below water appear as black lines.
Full screen does not work at all almost immediately crashes when joining a match. Same crash report, about memory.
But it is playable for the most part as long as I'm windowed

@viggy96
Copy link

viggy96 commented Sep 10, 2018

Would it be possible to not include the 'steam_api.dll' file with World of Warships (including on Windows)? Without this file, the game works perfectly fine, but it brings up a login screen, instead of trying to create a new account with your Steam username. This way, people can use their existing WarGaming account.

@doitsujin
Copy link
Collaborator

@Demonslayer2011 do you have DirectX 11 or DirectX 9 enabled in game? What's your hardware/driver configuration? The game runs completely stable for me with Dx11, using RADV with any Mesa version starting with 18.1.3.

@Demonslayer2011
Copy link

@viggy96 open game, let it get to that screen, close it, find that file, and rename it 2steam_api.dll and voila, you can use your wargaming account. This was not something steam did, this is wargaming being idiots for whatever reason.
@doitsujin I've tried both, at first direct 11 didn't work at all, but now it does. Latest mesa drivers, have dailys ppa.

@viggy96
Copy link

viggy96 commented Sep 10, 2018

@Demonslayer2011 I already know that, I'm using my WarGaming account on WoWS. I just wanted to see if it would be possible to just not include that file in so that other new users don't have this issue.

@Demonslayer2011
Copy link

WorldOfWarships-2018-09-15_21-52-48.crash.txt
WorldOfWarships-2018-09-15_21-52-48.crash.txt
back to square one, crashing within five minutes, and the one game i did manage to play, the textures dissapeared completely i had the hud, and player icons, but nothing else.

@linuxtek-canada
Copy link

linuxtek-canada commented Sep 25, 2018

Linux Mint 19, Geforce 1070 GTX with 396.52 Driver. Graphics are perfect, but there is a crackling issue with audio in port and in game.

Edit: Worked around using this article: https://psyq123.wordpress.com/2017/04/07/fix-crackling-audio-in-some-games-in-wine/

@lauromoura
Copy link

I do have a crash preventing the game to launch. The message it gives is: "Could not create new SimpleThread".
I am running on Arch Linux 64bit, with a Nvidia GTX 980 and Intel i7-2600 CPU @ 3.40GHz with 16GB of RAM.

Same here on a XPS 15 9560 ( GTX 1050M // i7-7700HQ @ 2.80 GHz, 32GB RAM).

It showed the region select, but after selecting North America the error dialog appeared.

WorldOfWarships-2018-09-26_23-28-30.crash.txt

@wentam
Copy link

wentam commented Oct 31, 2018

I do have a crash preventing the game to launch. The message it gives is: "Could not create new SimpleThread".
I am running on Arch Linux 64bit, with a Nvidia GTX 980 and Intel i7-2600 CPU @ 3.40GHz with 16GB of RAM.

Increasing my file descriptor limit fixed this for me.

@lauromoura
Copy link

I do have a crash preventing the game to launch. The message it gives is: "Could not create new SimpleThread".
I am running on Arch Linux 64bit, with a Nvidia GTX 980 and Intel i7-2600 CPU @ 3.40GHz with 16GB of RAM.

Increasing my file descriptor limit fixed this for me.

ulimit already showing unlimited here.

@ashtonx
Copy link

ashtonx commented Dec 11, 2018

Can't even launch it.

First launch managed to get launcher to pick the server, (EU). After that there was nothing.
Further launches don't even show a launcher. Both native/runtime have same effect.
Tested on Proton 3.7-8 and 3.16-4 Beta

i5 3550k
gtx 970
Antergos. 4.19.8-arch1-1-ARCH
nvidia 415.22-3

I'm guessing I'm missing either some windows redist or some linux library/drivers for stuff to go this way.

not getting any crashlogs, not in game dir at least
clientrunner doesn't show anything wrong:

[2018-12-11 11:15:22] ================ Log started at 2018-12-11 11:15:22 ================
[2018-12-11 11:15:22] Found client with product version 0.7.11.1167524 and file version 0.7.11.0
[2018-12-11 11:15:22] Found client with product version 0.7.11.1194326 and file version 0.7.11.1
[2018-12-11 11:15:22] Selected realm: eu
[2018-12-11 11:15:22] Checking client Z:\data\Games\steamapps\common\World of Warships\bin\1167524\WorldOfWarships.exe with version 0.7.11.1167524.
[2018-12-11 11:15:22] Reading CSIS URL for realm: eu
[2018-12-11 11:15:23] Detected server version release.7.11.1.1194326
[2018-12-11 11:15:23] Checking client Z:\data\Games\steamapps\common\World of Warships\bin\1194326\WorldOfWarships.exe with version 0.7.11.1194326.
[2018-12-11 11:15:23] Reading CSIS URL for realm: eu
[2018-12-11 11:15:23] Detected server version release.7.11.1.1194326
[2018-12-11 11:15:23] Found best client with matching version 0.7.11.1194326
[2018-12-11 11:15:23] Starting client with version 0.7.11.1194326
[2018-12-11 11:15:23] Running Z:\data\Games\steamapps\common\World of Warships\bin\1194326\WorldOfWarships.exe.
[2018-12-11 11:15:23] ================ Log closed at 2018-12-11 11:15:23 ================`

edit: added proton log
steam-552990.log

@kisak-valve
Copy link
Member

Hello @ashtonx, your log contains err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased, please run ulimit -Hn and verify it gives you a high value and not 4096.

@tonyrh
Copy link

tonyrh commented Mar 7, 2019

Works fine for me with NVidia 415.27 but the in-game browser (used for News and Arsenal sections) does not work. It works the very first time I open it but after that it only shows a loading wheel. Someone on reddit said it has to do with the CEF (Chromium Embedded Framework) process.

@tonyrh
Copy link

tonyrh commented Mar 30, 2019

With Proton 4.2 News and Arsenal seem to work fine. There are still problems opening the Clan section.

EDIT: On closer analysis the problem with web content served through the game client is still there.

@minecraft2048
Copy link

minecraft2048 commented Apr 9, 2019

System setup:

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Laptop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    CPU Family:  0x6
    CPU Model:  0x5e
    CPU Stepping:  0x3
    CPU Type:  0x0
    Speed:  3500 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    "Arch Linux" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  5.0.5-arch1-1-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12004000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  <Runtime disabled>

Video Card:
    Driver:  Intel Open Source Technology Center Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2
    Driver Version:  3.0 Mesa 19.0.0
    OpenGL Version: 3.0
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x8086
    DeviceID:  0x191b
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 1920 x 1080
    Primary Display Size: 13.54" x 7.64" (15.51" diag)
                                            34.4cm x 19.4cm (39.4cm diag)
    Primary VRAM Not Detected

Sound card:
    Audio device: Realtek ALC898

Memory:
    RAM:  15946 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.utf8
    Total Hard Disk Space Available:  794613 Mb
    Largest Free Hard Disk Block:  20759 Mb
    VR Headset: None detected

Recent Failure Reports:

Nvidia driver: 418.56

I'm running this game on a nvidia optimus gaming laptop, and the only way I can run this game perfectly is by using nvidia-xrun.

If I use Intel integrated graphics and DXVK, the game starts and it loads up to 413.6 MiB of ram, then it hangs and need to be killed.
steam-552990.log

If I use primusrun and PROTON_USE_WINED3D so that Wine is in opengl mode, the game starts but there are serious artifacts:
20190328095018_1
steam-552990.log

If I use DXVK and https://github.com/felixdoerre/primus_vk, it hangs similarly to Intel integrated graphics case

@kisak-valve kisak-valve added Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver and removed Whitelist Request Community tested games to be whitelisted in Steam labels Apr 9, 2019
@kisak-valve kisak-valve changed the title [Whitelist] World of Warships (552990) World of Warships (552990) Apr 9, 2019
@OvermindDL1
Copy link

Same issue as @minecraft2048 but using AMD Vega with MESA 19. Game would not launch without PROTON_USE_WINED3D=1, it does launch with it but displays the same image as @PROTON_USE_WINED3D with the weird reflective/glossy squares fading in and out as the view rotates around, no water shown, etc...

@doitsujin
Copy link
Collaborator

Both World of Tanks and World of Warships currently do not work with DXVK, even with old DXVK versions that used to be fine. Not sure what's going on there.

@anonymous133
Copy link

anonymous133 commented Jul 19, 2019

Hi,

I'd like to report constant crashes with this game. It is not obvious to me what causes it and it just started after the last game patch.

During Battle the game freezes. Somtimes after 10, sometimes after 3 games played.

Please find my proton log attached:
steam-552990_.log

I'm playing on Vega 64.

@kisak-valve
Copy link
Member

World of warships on i3. Cursor bound to very small space in center of screen. Proton 4.11-1

Issue transferred from #2939.
@anonymous133 posted on 2019-08-02T08:47:07:

Hi,

After switching workspaces I encountered a bug where the mouse is bound to a very small space in the center of the screen of the game so I can no longer look around properly. As if another window has focus and I can only move my mouse inside that space.

This doesn't happen for me with 4.2-9

@DAM1173
Copy link

DAM1173 commented Aug 29, 2023

There is no GE-Proton anywhere... there is Proton 7.0 and Proton 8.0. Also there is no option to install 8.4 only 8.0-3 in the steam UI. What is GE anyhow?

You can download and install GE-Proton 8.4 into Steam by using ProtonUP-Qt at https://github.com/DavidoTek/ProtonUp-Qt. And you can manually download and install GE-Proton 8.4 at https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton8-4.

@webaake
Copy link

webaake commented Aug 29, 2023

I followed these instructions, which I found plain and simple:

https://github.com/GloriousEggroll/proton-ge-custom/wiki

@vonschutter
Copy link

vonschutter commented Aug 29, 2023 via email

@vonschutter
Copy link

vonschutter commented Aug 29, 2023 via email

@DAM1173
Copy link

DAM1173 commented Sep 15, 2023

World of Warships has just released version 12.8, see https://worldofwarships.eu/en/news/game-updates/update-128-wows-celebrates-its-8th-anniversary/. I hope that this version will also play well with GE Proton 8-4 or higher.

@webaake
Copy link

webaake commented Sep 15, 2023

12.8 works fine here with GE 8.4.

@DAM1173
Copy link

DAM1173 commented Sep 18, 2023

But I think that World of Warships must run on any Proton version greater than GE-Proton 8.4. Has GE already been noticed about the logging in issues since WoWs 12.7 had been released?

@webaake
Copy link

webaake commented Sep 24, 2023

But I think that World of Warships must run on any Proton version greater than GE-Proton 8.4. Has GE already been noticed about the logging in issues since WoWs 12.7 had been released?

There was an issue with older Nvidia drivers and earlier Protons/Wows, but Nvidia versions 525.x and newer fixed that issue.

@jonkoops
Copy link

Another issue that I am experiencing is related to input. When pressing the Shift key once quickly to zoom in, the zoom automatically gets reset. Only when pressing Shift for ~0.5s and holding it down will the zoom remain in the correct position.

This works perfectly fine under Windows, but breaks in Proton. Is anyone else experiencing this issue?

@DAM1173
Copy link

DAM1173 commented Sep 25, 2023

But I think that World of Warships must run on any Proton version greater than GE-Proton 8.4. Has GE already been noticed about the logging in issues since WoWs 12.7 had been released?

There was an issue with older Nvidia drivers and earlier Protons/Wows, but Nvidia versions 525.x and newer fixed that issue.

What was that issue?

I tried to run WoWs 12.8 with GE-Proton 8.16 and Nvidia driver version 535.104.05 and it was still stuck at logging in.

@Henry-ZHR
Copy link

Another issue that I am experiencing is related to input. When pressing the Shift key once quickly to zoom in, the zoom automatically gets reset. Only when pressing Shift for ~0.5s and holding it down will the zoom remain in the correct position.

This works perfectly fine under Windows, but breaks in Proton. Is anyone else experiencing this issue?

Same issue here (months ago only, not tested recently). Don't know why, but solved by changing the key binding to Space.

@DAM1173
Copy link

DAM1173 commented Sep 25, 2023

To get debug info when running WoWs with a Proton version other than GE-Proton 8.4, you can run it in the Linux terminal by running this command: steam steam://rungameid/552990, in the terminal output you can see important debugging info. In the ~/.local/share/Steam/logs/ you can see several log files of Steam. This debug info can be used by the developers of Steam and Proton for fixing this login issue which appeared since WoWs has released version 12.7 and higher.

@GloriousEggroll
Copy link
Contributor

GloriousEggroll commented Oct 16, 2023

bisected the login hang:

0b74f0b5f55b02df23160fcaf64226e1a8658309

Reverting that on top of current experimental fixes the login hang and allows the game to work again.

I've released GE-Proton8-19 with a workaround that allows it to work again until the commit can be properly fixed.

@jonkoops
Copy link

Very nice @GloriousEggroll! Is there a place to track a fix for this in in Wine? (PR, issue, etc.)

@GloriousEggroll
Copy link
Contributor

GloriousEggroll commented Oct 16, 2023

Very nice @GloriousEggroll! Is there a place to track a fix for this in in Wine? (PR, issue, etc.)

You're looking at it. This doesn't affect upstream wine because the commit causing the issue only exists in proton-wine. Codeweavers has an internal bug tracker for proton-wine specific issues which is not publicly accessible.

@deri821
Copy link

deri821 commented Oct 16, 2023

indeed 8.19(GE) works in World of Warships, I played one round for a test. I was finally able to replace 8.4(GE) version

@Etaash-mathamsetty
Copy link

proper fix: ValveSoftware/wine#201

@DAM1173
Copy link

DAM1173 commented Oct 20, 2023

At https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton8-20:

GE-Proton8-20 Released

HOTFIX:

-updated world of warships workaround patch with proper fix, no longer requires environment variable (thanks OOOOOF123)

@deri821
Copy link

deri821 commented Oct 20, 2023

I took 8.20GE in use and deleted old GE versions.

@Etaash-mathamsetty
Copy link

proton experimental bleeding edge beta also works (will eventually be part of an actual proton experimental release)

@alasky17
Copy link
Collaborator

This is in the current non-bleeding edge experimental release from last Friday as well (experimental-8.0-20231019).

@deri821
Copy link

deri821 commented Nov 24, 2023

I recently upgraded proton-ge 25 and it worked some time, but now I am again unable to play the game, steam just wont launch the game.

@deri821

This comment was marked as duplicate.

@jonkoops
Copy link

Posting the same comment multiple times in a row isn't going to get your issue fixed any faster.

@Etaash-mathamsetty
Copy link

is it still working for other people? I uninstalled the game

@deri821
Copy link

deri821 commented Nov 25, 2023

I don't know why it printed same message twice. I didn't do that on purpose.

@deri821
Copy link

deri821 commented Nov 30, 2023

for some reason I was able to get it working again ( proton-ge 25).

@webaake
Copy link

webaake commented Dec 7, 2023

Wows 12.11 "Santas Gift shop" hangs when clicking around in it. Proton GE 8.4 and experimental and GE8.20 too. No mods. No biggie - I'll survive. Here are some seemingly pertinent lines from terminal:

Wows 12.11 errors 2023-12-06
...........
[1207/201633.734:INFO:cef_handler.cpp(893)] CefHandler::CreateWebView: id=1 SUCCESS; Exists: No
[1207/201633.904:INFO:cef_handler.cpp(584)] CefHandler::OnBeforeBrowse: https://armory.worldofwarships.eu/category/new_year_contai
ners/ cancel = 0
[1207/201703.416:INFO:CONSOLE(-1)] "Service Worker is not responding.", source: https://armory.worldofwarships.eu/sw.js (-1)
[1207/201719.302:INFO:render_frame_host_impl.cc(11505)] RenderFrameHostImpl::MaybeGenerateCrashReport url = , status = 4, exit_cod
e = 258
[1207/201750.561:INFO:cef_browser_app.cpp(23)] Running process with commandline "Z:/mnt/GAMES/SteamLibrary/steamapps/common/World
of Warships/bin/7814610/bin64//cef_subprocess.exe" --type=renderer --log-severity=info --user-agent="Mozilla/5.0 (Windows NT 10.0;
Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 Safari/537.36 WOWS/1.0" --user-data-dir="Z:\mnt\GAMES\St
eamLibrary\steamapps\common\World of Warships\profile\cef_cache" --disable-features=AudioServiceOutOfProcess --autoplay-policy=no-
user-gesture-required --disable-gpu --disable-gpu-compositing
[1207/201750.563:INFO:cef_handler.cpp(893)] CefHandler::CreateWebView: id=2 SUCCESS; Exists: No
[1207/201750.724:INFO:cef_handler.cpp(584)] CefHandler::OnBeforeBrowse: https://warehouse.worldofwarships.eu/ cancel = 0
[1207/201820.624:INFO:render_frame_host_impl.cc(11505)] RenderFrameHostImpl::MaybeGenerateCrashReport url = , status = 4, exit_cod
e = 258
.............

@Etaash-mathamsetty
Copy link

Etaash-mathamsetty commented Dec 7, 2023

Replying to #333 (comment)

try WINE_SIMULATE_WRITECOPY=1

@webaake
Copy link

webaake commented Dec 20, 2023

Even the ingame chat is working! That crashed the game for long time, but it's fixed now.

So thanks Proton Dev-team and Merry Xmas!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues Mesa drivers Possibly involves an issue with a Mesa video driver Regression Confirmed working on an older version of Proton XAudio2 Uses the XAudio2 subsystem
Projects
None yet
Development

No branches or pull requests