search

ValveSoftware / Proton

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

Foxhole (505460) #725

Open ptkato opened 6 years ago

ptkato commented 6 years ago

Every time I try to either join the war (after I pick a faction) or browse the servers, the game crashes. However, if I add PROTON_LOG=1 %command% to the launch options, it stops crashing and starts loading indefinitely instead. If I run proton directly (/tmp/proton_run), it doesn't crash nor load indefinitely, but returns an error asking to check for internet connection.

System info:

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected
Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 5 1600 Six-Core Processor            
    CPU Family:  0x17
    CPU Model:  0x1
    CPU Stepping:  0x1
    CPU Type:  0x0
    Speed:  3200 Mhz
    12 logical processors
    6 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported
Operating System Version:
    Linux 4.x (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.18.4-arch1-1-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12001000
    X Window Manager:  LG3D
    Steam Runtime Version:  <Runtime disabled>
Video Card:
    Driver:  X.Org Radeon RX 550 Series (POLARIS12, DRM 3.26.0, 4.18.4-arch1-1-ARCH, LLVM 6.0.1)
    Driver Version:  3.1 Mesa 18.1.7
    OpenGL Version: 3.1
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x1002
    DeviceID:  0x699f
    Revision Not Detected
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1600 x 900
    Desktop Resolution: 1600 x 900
    Primary Display Size: 17.44" x 9.80" (20.00" diag)
                          44.3cm x 24.9cm (50.8cm diag)
    Primary VRAM: 2048 MB
Sound card:
    Audio device: ATI R6xx HDMI
Memory:
    RAM:  7973 Mb
Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  233237 Mb
    Largest Free Hard Disk Block:  111907 Mb
    VR Headset: None detected
mijofa commented 6 years ago

Perhaps related to #162 ?

ptkato commented 6 years ago

Perhaps. Note that it doesn't make a difference if I use steam-runtime or not, also the news & highlights section works just fine, but that can be retrieved from an unrelated source.

ptkato commented 6 years ago

Update: now with Proton 3.7-5 Beta, it throws me a little "Fatal error" window with an OK button and the game closes itself shortly after.

ptkato commented 6 years ago 
audit: type=1701 audit(1536973247.900:13): auid=1000 uid=1000 gid=1000 ses=8 pid=28637 comm="War-Win64-Shipp" exe=2F686F6D652F70746B61746F2F2E6C6F63616C2F73686172652F537465616D2F737465616D617070732F636F6D6D6F6E2F50726F746F6E20332E3720426574612F646973742F62696E2F77696E6536342D7072656C6F61646572 sig=11 res=1

Now I'm getting this audit log from dmesg.

h1z1 commented 6 years ago

@ptkato Makes sense, it's just auditd catching the segfault from proton

ptkato commented 6 years ago

Now with Proton 3.16-4, the game is working as intended.

NooneAtAll commented 5 years ago

proton 4.11-1 / 4.2-9 / 3.16-9 / 3.7-8 ubuntu 18.04 Nvidia GP108M [GeForce MX150] drivers up to version 430 (or whatever apt had installed as last version)

I get "DX11 feature level 10.0 is required to run the engine" error on launch https://i.imgur.com/wlbcdQU.png

NooneAtAll commented 5 years ago

is it possible to reopen this issue?

mungr commented 4 years ago

proton 5.0.9 ubuntu 18.04

Upcoming release which is available by running "devbranch" beta introduces SteamSockets which crashes on startup with:

[2020.08.01-12.20.18:468][  0]LogSteamSocketsAPI: Warning: SteamSockets API: Warning SDR network config fetch first attempt failed.  HTTP 504.  .  Trying again.

Which basically regresses the support level from platinum to borked. When running under strace the game gets past the startup (possibly a race condition is avoided by introducing extra latency), but fails on some network issues when trying to connect to the game server.

Dyskord commented 3 years ago

Foxhole developers reintroduced SteamSockets in a recent patch. Game does not start up (initial load screen briefly flashes) then the game immediately crashes. On proton 6.3-4 the log mentions the "SDR network config fetch" line posted above, on proton experimental it does not.

Furthermore the game / proton seems to load nvidia_uvm kernel module, which i never noticed it doing before. Verified with another proton game, path of exile, after unloading the module, and it did not load it in. Might be nothing, but i am reasonably certain it did not load this module before with this game.

Tried with 6.3-4 and experimental proton, both logfiles provided. Using debian testing, 5.10.0-6-amd64 kernel, 460.71.01 nvidia driver.

steam-505460 (6.3-4).log

steam-505460.log

spacekitteh commented 3 years ago

Foxhole developers reintroduced SteamSockets in a recent patch. Game does not start up (initial load screen briefly flashes) then the game immediately crashes.

I can confirm this, on NixOS, kernel 5.12.7, ROCM AMD driver. foxholeCrash-proton-experimental.log

This part is interesting:

Fossilize INFO: Overriding serialization path: "/home/spacekitteh/.local/share/Steam/steamapps/shadercache/505460/fozpipelinesv5/steamapprun_pipeline_cache".
>[0610/112331.008:ERROR:angle_platform_impl.cc(36)] rx::SwapChain11::resetOffscreenColo
rBuffer(278): Could not get offscreen texture shared handle, HRESULT: 0x80004001

(process:147607): GLib-GObject-CRITICAL **: 11:23:34.453: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
pid 147278 != 147277, skipping destruction (fork without exec?)
Game removed: AppID 505460 "", ProcID 147383
kisak-valve commented 3 years ago

Foxhole stop working. Black Screen and closes upon start.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4895. @pbaesse posted on 2021-06-12T10:32:08:

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction

pbaesse commented 3 years ago

Any news about this issue??

newhinton commented 3 years ago

Just to add a little information: Foxhole on Proton 4.2-9 starts fine with the latest version, but when trying to join a game it errors out with "failed to download player data[0]"

Dyskord commented 3 years ago

Since latest small patch, game seems to work again. Briefly fired it up, walked around, seemed fine. Version 6.3-5 Sadly cant find any patchnotes for it.

newhinton commented 3 years ago

Proton Experimental works aswell

Edit: And for future reference the current proton-experimental-version: Proton: 1624992881 experimental-6.3-20210629

MazdaRazda commented 3 years ago

So, not sure how everyone is playing Foxhole, but compared from the Windows version, there are Mouse issues. Specifically, the in-game mouse doesn't respond to my actual mouse's location. The in-game mouse just stays at the top-left corner of the screen (it's icon is a white circular dot), preventing me from interacting with the game's built-in hud menus fully.

Right-clicking in the Refinery building, for example, doesn't always work, and when it does, the options are appearing at the top-left, where the in-game mouse resides. The right-click options are also appearing top-left when it comes to building structures (when equipped with a Hammer), joining a squad, selecting a specific player, and in-game items.

Apart from that, there's also the game's map that is meant to follow wherever the mouse is located on screen when you zoom in or out. What happens instead, is that the zoom function only zooms in and out from wherever the mouse's "last known" location was.

Attached I have some GIF videos displaying my findings. I am on Proton Experimental, and have seen that other versions do not fix this mouse behavior. Changing the resolution, or switching between the available Fullscreen, Windowed, and Windowed Fullscreen does not fix the problem either.

If more elaboration is needed, please do inform me. Thank you.

Click to expand https://user-images.githubusercontent.com/90406487/132724485-2c4b09ae-544e-4e1d-acff-6c34d1c34cb9.mp4 https://user-images.githubusercontent.com/90406487/132724512-b4c5d3d9-94a1-4f1c-ace8-a392f9328ef5.mp4 https://user-images.githubusercontent.com/90406487/132724528-e83efbef-eaf7-43e4-a32d-4f788224216b.mp4 https://user-images.githubusercontent.com/90406487/132724552-4b717bcc-bbba-4c18-8313-61a6759be28d.mp4
Metal-spoon commented 3 years ago

My framerate tanks when getting close to factory buildings and on a specific part of the warden home island. GPU is getting hammered at a constant 100% and cpu is fine so i'm thinking this might be a dxvk issue, does not happen when running it on windows with the same settings and hardware. Proton 6.3-7, i7 8700k, gtx 1070 (driver 470.65) on pop!_os 21.04.

I'll try other proton versions aswell.

Runlevel-zero commented 2 years ago

Have been playing for months without issue. Upon upgrading to kernel 5.15 experiencing strange performance issue.

Upon loading into the home island everything seems in order. However upon deployment FPS immediately drops so single digits. All proton versions and protonGE tested with no change. 6900xt on AMDGPU.

MazdaRazda commented 7 months ago

Reviving this issue.

Latest Foxhole Update 56 (Build ID: 13956640) crashes after initial menu. Menu appears as normal, but after selecting a faction, the game freezes up and shuts down with no warning or error.

I ran Experimental, Proton 8.0-5, latest Glorious Eggroll 9-2, and Steam's latest Proton 9 Beta. All resulted in same shut down/crash.

I used to carry .pak mod files, so I initially assumed it was an incompatible mod version. I removed all mod files and ran the game on base (vanilla) version, and same shut down/crash occurs.

If there are Launch Option commands that others have used, I am unaware of them, as I never had to use them before on my Linux OpenSuse distro.

It has been a while since I last reported an issue, so if a log file is needed, I'll need a refresher on how that is meant to be done.

Dyskord commented 7 months ago

Running debian unstable, but the issue seems to affect all people on various distros, including the steam deck, going by this thread: https://steamcommunity.com/app/505460/discussions/0/4355618117945804944/

Attached logs from trying to run it with proton 7, 8 and 9 (beta), none of them get past "deploy"

foxhole-proton7.0-6.log foxhole-proton8.0-5.log foxhole-proton9.0.log

MazdaRazda commented 7 months ago

Figured out the logging process. The following log file encapsulates the same crash sequence no matter which compatibility version (Experimental, Proton 9 Beta, Glorious Eggroll, etc.) is implemented.

foxhole-proton-experimental.log

For easier understanding:

Few things to note:

Dyskord commented 6 months ago

Most recent patch seems to have fixed the issue. At least logging into the game, and running around on home island works.

MazdaRazda commented 6 months ago

Can confirm. Build ID: 14027711 included a fix for Linux users. I'll place their hotfix update here as well for further confirmation https://www.foxholegame.com/post/update-56-release-notes