Perhaps related to #162 ?

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.

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.

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.

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

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

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

is it possible to reopen this issue?

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.

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

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 

Any news about this issue??

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]"

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.

Proton Experimental works aswell

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

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.

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.

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.

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.

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

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:

• Lines 1-8 occurs after clicking on the Play button on Steam.
  • The error portion is just a notification about my choice to not have a Steam Overlay active while playing the game.
• Lines 9-14 occurs after entering into the game's initial menu.
• Lines 15-55 occurs after clicking on the game's Deploy button.

Few things to note:

• The game does not seem to recognize my in-game rank (displays as None), but does display the game's "War Stats" in terms of how many players have died in each faction, as well as how many "war days" (aka hours) the war has progressed.
• Very rarely, the "Deploying" (aka the attempt to connect to the game's server) message does show a player queue, so there is an attempt to connect, but the application freezes up before crashing.
• If you click on "Exit Game" from the menu, Lines 15-55 still appear on the log.

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

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

Problem
My game has constant stutters here and there, but it gets so much worse when I rotate my camera around. The frametime graph on the monitoring program is going crazy every time I do it. I've tried setting the graphics to the lowest and setting my GPU performance to high yet the problem persists. Tried a couple of different proton versions too from hotfix, experimental, to the GE version and still nothing.

My PC specs
OS: Nobara Linux 41
CPU: AMD Ryzen 5 5600
GPU: AMD Radeon RX 7600 XT
RAM: 32GB

Screenshot of the game with 'DXVK_HUD=full' command

Log file
steam-505460.log

System Information

• GPU: 1080 Ti
• Video driver version: nvidia-570.133.0
• Kernel version: 6.11.0-26-generic, Linux Mint latest
• Link to full system information report as Gist: https://gist.github.com/TZer0/58a9151ff54c6ffc81e7ee4e274138c0
• Proton version: Proton-Experimental, also crashed under default proton and GE-proton-10.4

steam-505460.log
steam-505460-2.log

Symptoms

Crash to desktop after short freeze, error logging window comes up.

Proton log includes the following message:

44243.612:017c:0180:warn:seh:dispatch_exception backtrace: --- Exception 0xc000001d.
44243.612:017c:0180:trace:seh:dispatch_exception code=c000001d (EXCEPTION_ILLEGAL_INSTRUCTION) flags=0 addr=00000001431388B0
44243.612:017c:0180:trace:seh:dispatch_exception rip=00000001431388b0 rsp=0000000000b9eb18 rbp=0000000000b9ebe9 eflags=00010202
44243.612:017c:0180:trace:seh:dispatch_exception rax=0000000000000dc3 rbx=00000000c0ffe080 rcx=00000000c0ffe080 rdx=000000000000139b
44243.612:017c:0180:trace:seh:dispatch_exception rsi=0000000000b9ecd0 rdi=00000000bcf53300  r8=0000000000000000  r9=00000000b5fc09f0
44243.612:017c:0180:trace:seh:dispatch_exception r10=0000000000000000 r11=0000000000b9eb78 r12=0000000000000001 r13=0000000000006e18
44243.612:017c:0180:trace:seh:dispatch_exception r14=000000007fda3580 r15=0000000000000dc3 mxcsr=00001fa0

Reproduction

None, randomly occurring, just play

Edit: I only have minor visual-only mods installed, they only change textures.

@TZer0 I've had no luck reproducing the issue yet, spent about 40 minutes in the training grounds and then another 40 minutes on an active zone. It's not specified in your report, does the issue happen at startup or after a random time? If it's the latter, how long does it usually take? And is it more likely to happen under certain scenarios? Like, for example, when loading a new part of the map from deploying or spawning into a new location.

If the issue happens again, run this: sudo dmesg > dmesg.log and upload the resulting dmesg.log file, which should be in your home folder.

The unreal engine log might also be useful. If you know where your steam prefixes are stored then /pathtoyourprefixes/505460/pfx/drive_c/users/steamuser/AppData/Local/Foxhole/Saved/Logs should contain a file called CrashReportClient.log

@simifor thank you for the reply! The frequency of the crashes is roughly once every 1-2 hours. I will have to however mention that I've not heard from other Linux users in my group about similar crashes (and they would've complained to me if this happened, I even checked with one of them).

I will make sure to provide a dmesg log should this occur again.

Right now I am testing running it in windowed, no crashes so far. I will try to provoke one if none occur after a few hours of gameplay by running it in either windowed fullscreen or fullscreen.

Edit: I will also provide a report here if this all turns up as a negative within 10 hours of gameplay.

Edit # 2: here are the crash logs Logs-tzer0-foxhole-505460.tar.gz

Update: I have not had a crash in 10 hours of gameplay in windowed mode. I will see if I can provoke a crash with windowed.

My 1080 Ti died unfortunately, so I am no longer able to contribute to debugging any of these issues.

I even ordered new fans for the thing and before they arrived the GPU had crashed multiple times and made a monitor flicker in a new and interesting way.

I have yet to have any crashes on the 9060 XT I put in to replace it (and I have 30-40 hours on it in Foxhole now).

Have some issues with keyboard char codes. W on keyboard is "UnknownCharCode_1062" and so on.
Mod keys work ok, only affected ranges are A-Z.
Debian 13, Wayland, Gnome, Nvidia driver, Proton experimental.
I have two keyboard layouts: EN and UK (ukrainian).

Charcode 1030 is ukrainian "І" which has the same button as latin "S".
Charcode 1062 is ukrainian "Ц", on button "W".
Switching keyboard layout in game does not help. Changing layout to EN before starting the game also does not help.

Does anyone know how to fix it? Via wineconfig or protontricks, what option should that be?

Currently I have only 2 games that run via proton: Foxhole and Rain World. The latter does not have such issues. however it is Unity game, not Unreal game:

Updates on my previous message about keyboard layout issue:

From https://unix.stackexchange.com/questions/595046/running-games-with-steam-proton-doesnt-respect-your-current-keyboard-layout and https://askubuntu.com/questions/472562/how-to-change-keyboard-input-method-system-to-none-in-ubuntu-gnome

• Changing order of keyboard layouts fixed the issue. Before it was UK -> EN, now it is EN -> UK and game works fine.
• Changing keyboard input system to None did not help (or i did it incorrectly).

System Information

• OS: OpenSUSE MicroOS 20260214
• GPU: RTX 4070 Ti
• Video driver version: Nvidia 580.126.09
• Kernel version: 6.18.9-1-default
• Proton version: experimental-10.0-20260210
• Audio interface: Focusrite Vocaster Two

Symptoms

In-game voice chat doesn't work when using an audio interface with a lot of audio tracks (14 in my case). When leaving a default PulseAudio Output and PulseAudio Input in audio settings, the game fails to create a pipewire node. Changing the Input Device to any other device with fewer tracks and hitting Reconnect creates a pipewire node with a correct output and selected input. That allows to hear others but uses an undesired microphone. It is possible to change the microphone to the preferred one using Qpwgraph, but that method is not persistent and will reset on reconnect or region travel.

Edit: Found a temporary mitigation. Create a virtual microphone that forwards first two tracks from the default microphone using following command:

pw-loopback -n VirtualMic -o 'node.description=VirtualMic node.name=virtmic media.class=Audio/Source'

Then select it in game's settings to use it. That allows both to hear and speak in game as expected.

Reproduction

1. Log in and deploy to home region.
2. Unable to hear and talk to anyone.

steam-505460-default-settings.log
steam-505460-other-input.log