Runefox
Published
The latest Proton updates remove the last visual bugs that were present in the game to date.
Appears to run pretty well, but be aware that alt-tabbing will cause the game to continue running but no longer display anything. Haven't been able to figure out a way around this. As long as you don't do that, though? Seems fine.
Minor graphical glitches when toggling the HUD (HUD area appears solid green until view is switched). Otherwise plays as expected with gamepad (Xbox One controller) support out of the box. Game uses the software renderer and does not seem to detect hardware acceleration - May need a Glide wrapper as the game does have 3dfx support.
Everything seems to work fine out of the box including rumble support on an Xbox pad; The selected-by-default 3DFX Glide renderer is recommended, as Direct3D has minor visual glitches and frame drops (but is otherwise fine). Uncertain, but this may also be the case on Windows.
No apparent issues. Game launches, runs, and plays perfectly, with no error on exit and good performance (~120fps at 1080p high).
Crashes with "Fatal error"
Tried with every selectable version Proton (latest: 5.13-2), with and without launch options. Nothing works.
FPS between 60 and 100 at 3440x1440. Intro fades don't work on vanilla Proton - Press ESC.
As said in another report, the game runs on both standard Proton and Glorious Eggroll with the following protontricks command:
protontricks 895870 d3dcompiler_47
Game fails to load with "OGRE EXCEPTION(3:RenderingAPIException): Failed to create Direct3D9 Device: Not available in D3D9RenderWindow::createD3DResources at ..\src\OgreD3D9RenderWindow.cpp (line 606)". Proton versions prior to 4.2-1 appear to either also show this message or not launch at all. Tried disabling Esync, D3d11, and using Wine D3d11 to no effect.
Game seems to run OK at first, but performance is quite poor compared to Windows. Controller support is unfortunately also very poor - It works, but not consistently or well. Menu navigation is difficult when the controller decides to be uncooperative (constantly presses "back"), and when binding axes, an axis (axis 3 on Xbox One controller) is considered to always be activated.
Honestly I forgot I was playing under Linux. Runs great and I've noticed no bugs whatsoever.
Crashes at startup; First started freezing when loading the port but now it won't fully launch to the login screen. Steam install works on Lutris with lutris-wf-nofshack-4.15-x86_64 by pointing to the existing install folder in steamapps/common/World of Warships/bin/#######/bin[64] and removing Steam integration by renaming or deleting steam_api[64].dll
Requires fixes due to recent Wargaming changes causing a bug with region selection, but otherwise plays perfectly fine.
Getting the game to run
You need to modify preferences.xml in the World of Warships install folder. You must have first selected a region when launching the game.
- For North America
<currentRealm> na </currentRealm> - For Europe
<currentRealm> eu </currentRealm> - For Russia
<currentRealm> ru </currentRealm> - For Asia
<currentRealm> asia </currentRealm>
Using a non-Steam account with the Steam version
Steam updates are more convenient, but the old method no longer works. Here's the new one:
- Delete or rename steam_api.dll or steam_api64.dll in the World of Warships/bin//bin32 and/or World of Warships/bin//bin64 folders.
- Copy platform.dll and wgc_api.dll from the official client into bin32 for 32-bit, or platform64.dll and wgc_api.dll into bin64
Purrfürst uploaded these files: https://steamcommunity.com/sharedfiles/filedetails/?id=1890831652
