Memory access violation on Unity games (I am Bread, Stick Fight) (327890 674940)

[timschumi]

I am experiencing crashes on Unity based games (only tested on "I am Bread" and "Stick Fight: The Game" so far), caused by an memory access violation right after starting the game.

I'll attach a few crash logs from both games (which are automatically generated by Unity, I can't attach the dumps because of a GitHub limitation) and my system/driver information (I added the information that is inside the square brackets).

iambread_1_error.log
iambread_1_output_log.txt
iambread_2_error.log
iambread_2_output_log.txt
stickfight_1_error.log
stickfight_1_output_log.txt
stickfight_2_error.log
stickfight_2_output_log.txt
system_information.txt

[timschumi]

I've seen reports across the web that Stick Fight works on Manjaro KDE (which has a base similiar to Arch Linux) with Linux Kernel 4.14.65. I'll test a few configurations (different kernel versions and/or Proton versions) and see if I can achieve different results.

[timschumi]

Followup to my last comment: Neither downgrading to the mentioned kernel nor using another Proton version (3.7-4 in this case) helped solving the problem. However, I was able to confirm that both games are starting successfully using wine-3.14 from the Arch Linux repositories.

[t1m0thyj]

I encountered the same error trying to run Stick Fight using Steam Play in Linux Mint 19, on a laptop with Intel HD 520 integrated graphics.

[pmykc1]

I also have this very same problem.

Here is my error log for the unity game Overcooked:
https://gist.github.com/pmykc1/99f0a67b61fdb6cd4765f030147bf372
my system details are here:
https://gist.github.com/pmykc1/5c6eedd49b631980f3718aa3dc530b98

Having looked around at a few system specs, it seems that ALL of the people who can run unity games have Nvidia graphics cards, and all of us who cannot have Intel graphics cards. I think this is where the problem lies! But I am not knowledgeable enough to sleuth more than that.

[timschumi]

@pmykc1 I have a friend who I think has a relatively old Nvidia card and he said that Stick Fight is crashing for him as well. I'll try and get some logs and system information from him, that may help.

[pmykc1]

The upgraded graphics drivers not included in 18.04 have allowed me to run unity games:
sudo add-apt-repository ppa:paulo-miguel-dias/mesa
sudo apt dist-upgrade
sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386

[timschumi]

@pmykc1 Huh, doesn't work for me (at least on Stick Fight)

[bla-rs]

+1 for access violation with Unity.

Over here i can start the game "Battlerite Royale" just fine (Ubuntu 18.04, latest Nvidia drivers) and the performance/appearance looks very good but as soon as i hit something networking related, the game crashes. See the logs below for details.

error.log
output_log.txt

[PCFreak2000]

Getting the same issues here on Stick Fight, with an Nvidia GPU though.

error.log
output_log.txt
system_information.txt

[kisak-valve]

Hello @PCFreak2000, in your case your hardware is not capable of directx 11. You could try some of the Proton runtime options or unity 5.6 options.

From that, maybe adding -force-d3d9 or -force-glcore33 in the game's launch options would help.

[timschumi]

Forcing D3D resolved the problems for me. I assume that Unity does query our hardware and assumes that we support some Graphics API (or some extension of it). The setting for the used Graphics API seems to persist when restarting the game, even if the launch option is then removed, so starting the game with the launch option once is enough.

[feimosi]

PROTON_USE_WINED3D11=1 %command% in Launch Options did the trick for me.

[gwemmie]

Nope, not only Intel. I'm AMD and I too had this issue, and @feimosi's workaround fixed it for me, too. However, now I'm getting extremely dark 3D objects to the point that I can only even see the very brightest bits of them, making the whole thing almost just a black screen with music.

[douglasg14b]

Also occurs with Dig or Die.

PROTON_USE_WINED3D11=1 %command% did resolve it. Though closing dig or die causes the steam client to crash...

[timschumi]

I can't replicate this anymore, neither using the most recent Proton 3.7 build, nor on any other version (using the default settings and without any launch arguments).

Is anybody else still having this issue? Otherwise, I'm going to assume that this has been fixed somewhere along the way.

[Turantel]

I was getting this issue with The Forest. feimosi's solution helped out with getting it running again