Could it be because the game is calling to a server? I wonder, try to block the crash.exe file in the firewall.

I would try it, but i dont own the game on pc (yet)

Confirm the same. Although it seems to crash as I'm entering the menu where you select Crash 1, 2, or 3. Restarting steam in offline mode allows me to play.

From the backtrace it seems like it crashes here:

=>0 0x000000007bc9362e NtGetContextThread+0x7e(handle=0x558, context=(nil)) [/home/proton/proton/wine/dlls/ntdll/signal_x86_64.c:2163] in ntdll (0x000000000022ce10)

It looks like this has been fixed already in upstream wine by checking for context == null: https://github.com/wine-mirror/wine/commit/ec418e7f55f5e38f8825187ae5dfe33fec31689b

But the version shipped with Proton doesn't include that fix yet, so it's probably just a matter of waiting until the change makes its way through.

I don't own this game but it's on my wish list. From commit history it seems this patch is already in for Wine 3.16, which is the base of Proton 3.16, which has been out for a while already. So this issue on latest Proton may not exist anymore.

@oblitum yes it works perfectly now.

Nice :-)

it runs welll enough to be qualify as whitelisted?

@briangular, what version of proton are you using? What GPU and what graphics driver version?

Could you enable logs and then post the log here? Via the config file, see all the way down in the https://github.com/ValveSoftware/Proton readme.

I'm experiencing a somewhat similar issue, but in my case it crashes right after the "Preparing to launch" popup shows up on the screen.

I've attached my system information and a debug log.

steam-731490.log
sysinfo.txt

@briangular I noticed that one of the more recent playabilit reports on ProtonDB says that it worked only after installing the mesa-vulkan-drivers package. I can confirm that it worked for me as well, so that might be something to try...

@briangular
Offline or not doesn't seem to affect my game. The offline mode some posts refer to is the Steam app offline mode; you can find it from the regular user interface (not Big Picture) by opening the Steam menu (upper left corner) and selecting "Go Offline..."

Besides using the most recent version of Proton, 3.16-5 beta, I also needed to disable esync.

The version can be forced by going to Steam -> Settings -> Steam Play -> "Use this tool instead of game-specific selection from Steam".

Disabling esync can be done by following the instructions on https://github.com/ValveSoftware/Proton/blob/proton_3.16/README.md#runtime-config-options . The command should be PROTON_NO_ESYNC=1 %command%.

...and you're welcome. I have fond memories of playing Crash Bandicoot at a friends house some 20+ years ago and having it work on Linux is awesome :smile:

@briangular
Ah, that makes sense. I think the default version of Proton is pretty old, so that could very well be the reason why it's not working for you.

I haven't tried SteamOS but I do know Linux, so I can think of a few ways to escape Big Picture:

• use this guide to exit Big Picture: https://steamcommunity.com/groups/steamuniverse/discussions/1/1733212454824662267/
• add a shortcut to Steam for /usr/bin/xterm, /usr/bin/gnome-terminal or similar and use that to kill steam and start it again with steam -nobigpicture (actually, not sure if this'd work; maybe killing Steam would kill children, i.e. the terminal?)
• hit ctrl+alt+f2 to get a TTY. Log in with regular user, run DISPLAY=:0 xterm to spawn an xterm and hit ctrl+alt+f1 to get back to graphical environment (or ctrl+alt+f7, or any other F-button, not sure which one it is)

Maybe @kisak-valve has a better idea?

Hope this helps :smile:

@runejuhl
Proton_no_esync=1 does nothing for me either. Using 3.16.6 beta version of Proton. Perhaps the game doesn't like Vulkan or later Mesa versions?

@dribbleondo
Hmm, that could be. FWIW, on one of my devices I've got

mesa-vulkan-drivers/bionic-updates,now 18.0.5-0ubuntu0~18.04.1 amd64 [installed]
xserver-xorg-video-amdgpu/bionic,now 18.0.1-1 amd64 [installed,automatic]

installed, and Crash is working fine.

@runejuhl
Hrm. Interesting. I'm on the Oibaf PPA, so Mesa 19 Git is what i'm rocking for Vulkan and AMDGPU drivers. My bet is that something makes the Vukan renderer stop rendering the levels on later Mesa versions. As much as I wanna play crash, I need the latest Mesa for improved native performance.

Here's a log file for the game should you need it.

Also, tried running the game in steam offline mode, no dice.

Got crash on a sale so i tested it

System Information

• GPU: GTX 1070
• Driver/LLVM version: Nvidia driver 415.27
• Distro version: Linux Mint 19.1
• Kernel version: 4.18.0-13
• Link to full system information report Gist
• Proton version: 3.16-6 beta

it works without any problems

• sometimes the fps gets lower to 47 fps but its perfectly playable on nvidia gtx 1070

I take it it's not on sale anymore? I see $40

I have a recent AMD card and Mesa 19 to test

Yeah, not on sale anymore @parkerlreed

Fell free to test it and give results

I'm seeing a similar black screen issue. After the level loads, I get a blank screen with no music or sound effects, but I can get to the pause screen to return to the warp room or map.

In Crash 1 I can play N. Sanity Beach but at Jungle Rollers I start to get the black screen when the level loads.

In Crash 2 I can play a few more. Working: Turtle Woods, Snow Go, Crash Dash. Not Working: Hang Eight, The Pits.

Haven't really tested Crash 3 in Linux yet.

Tested on Fedora 29
Proton 3.16-4 and Proton 3.16-6 Beta (switched back and forth to see if that would fix it).
Core i7-4770
GTX 760 with 415.27 Drivers

thats odd cause i played crash 1 on linux till boulder dash and it works fine

crash 2 i finished the 1st warproom and 2 levels in the 2nd

and finished 3 levels in crash 3

other than the lower frame rate nothing out of the ordinary

System Information

• GPU: GTX 1070
• Driver/LLVM version: Nvidia driver 415.27
• Distro version: Linux Mint 19.1
• Kernel version: 4.18.0-13
• Link to full system information report Gist
• Proton version: 3.16-6 beta

My cursor disappears when I press a keyboard key, making it impossible to attack or navigate the menus.

Game crashes right after window is created. No graphics or audio. Very frustrating.

Found out this only happens when game starts up on a monitor that is not my leftmost one (which is also the same monitor steam likes to start up on). If I frequently click on said monitor or move the steam window over to it and launch, the game will start on that monitor and everything works. I can also move the game window afterwards just fine.

Provided sample log for when opened on another monitor.

steam-731490.log

Game crashes after I click at the title menu, audio keeps playing though. PROTON_NO_ESYNC=1 %command% does not help nor does switching to any other proton version (currently running proton-4.2.3, sys specs are here and crash log here )

EDIT:
I had downgraded mesa to stable and it now works (even though I'm pretty sure I tried that once before and it didn't help but oh well ¯\_(ツ)_/¯ )

As many others I also had a problem of a black screen when a level would finish loading, the menu worked etc. I tried tons of stuff to no avail - reinstall, driver changes, proton version changes, etc.
Turns out the problem indeed is in the length of the path to your save files (or perhaps the game itself, no sure tbh). I've created a new steam library folder ~/Steam Library and moved the game files there (via game's settings menu). Everything works perfectly now!

Aha! That seems to be the exact issue I was having. The default steam folder's path seems to be too long. By setting my Steam library folder to be ~/Steam (and re-installing), I can now play Hang Eight (I couldn't play that level before). I wonder if the path issue is actually a bug in the game and not in Proton that was only manifested because of the default paths that Steam uses in Linux.

Also, if anyone is trying to run this game on an optimus laptop using bumblebee, I was able to get it to work quite well on my new laptop (MSI GS65 Stealth). The only caveat is that you have to use the Wine DirectX layer instead of DXVK. Here's are my command-line options that I set: PROTON_USE_WINED3D=1 primusrun %command%.

So far, I can say that this configuration works:

Fedora 30
Proton 4.2-9
NVIDIA RTX 2060 (using Bumblebee)

I'm guessing that my desktop with my GTX 760 would work flawlessly after moving the steam library into my home folder, but I'll have to test later this week.

Note, I've only played one level that I couldn't before, so obviously this isn't exhaustive.

System Information

• Proton version: 4.11-1

With a 144Hz refresh rate, the game will incorrectly use a "Max FPS" value of 48. Unsurprisingly, this does not occur with Proton 4.2-9.

The setting will show a value of 60 if the display's refresh rate is set to 60Hz, so I'm not sure whether this is a issue with Proton or with the game.

Here's the log and a screenshot of the graphics options menu after launching the game with the refresh rate set to 144Hz:

steam-731490.log

With a 144Hz refresh rate, the game will incorrectly use a "Max FPS" value of 48. Unsurprisingly, this does not occur with Proton 4.2-9.

Worth noting that even though the game can run at 144 FPS, the "Max FPS" setting will display a value of 60 regardless.

System Information

• Proton version: 4.2-9 (also 4.11-1)

There seems to be a bug in the level "Un-bearable", where the giant bear does not break the wooden planks, making the secret area in the level inaccessible.

More references:

• https://www.protondb.com/app/731490
• https://www.reddit.com/r/crashbandicoot/comments/blxtp5/unbearable_bug_cant_access_bonus_level_on_linux/
• https://www.reddit.com/r/wine_gaming/comments/8w3iv2/crash_bandicoot_n_sane_trilogy_wine_staging/e36gkoy/

steam-731490.log

System Information

• Proton version: 4.11-1

With a 144Hz refresh rate, the game will incorrectly use a "Max FPS" value of 48. Unsurprisingly, this does not occur with Proton 4.2-9.

The setting will show a value of 60 if the display's refresh rate is set to 60Hz, so I'm not sure whether this is a issue with Proton or with the game.

Here's the log and a screenshot of the graphics options menu after launching the game with the refresh rate set to 144Hz:

steam-731490.log

This is a known issue on Windows too, which affects people with high refresh rate monitors, as well as not playing nice with Variable Refresh Rate technologies See Here and Here for the discussions.

Thanks for reporting. In Proton 4.11-1, we report only the current display rate. 48 is one third of 144, so the game seems to be doing some integer fraction of the current framerate. Anyway, I am adding a set of modes to fallback to 60 FPS, similar to what we had before, for games that don't work well on other refresh rates. This will be in an upcoming release.

@aeikum thank you for this: I tried it on 4.11-2 and the game is still locked to 34/48 FPS, so it would seem that there is an issue with the game itself rather than with Proton, as @dribbleondo pointed out.

I forgot to attach a log:

steam-731490.log

RADV (Mesa) still has the crash issue during the opening cutscene (with audio continuing to play), as of mesa-19.3.0-git (Vega 56). What is the last working version of Mesa?

EDIT: Seems to affect all drivers (RADV, AMDVLK, and AMDGPU-PRO) so it might not be fixed by older RADV.

@kisak-valve

System information
steam-731490.log

EDIT: Looks to be a fsync issue, not sure how that slipped my mind. Works fine with esync at least. I think it's the first game I've personally seen fsync cause problems with, though.

The bug where the bridge doesn't break in the Crash 2 level "un-bearable" seems to be the only issue remaining preventing the game being "100%" complete-able. I have a log from opening the game, playing the level until the issue occurs then quitting.
steam-731490.log

For reference this is what's supposed to happen

I also tested with proton-tkg 4.17.r12 and wine-staging 4.17 where the issue still exists.

Compatibility Report

• Name of the game with compatibility issues: Crash Bandicoot™ N. Sane Trilogy
• Steam AppID of the game: https://steamdb.info/app/731490/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.64
• Kernel version: 5.5.10-arch-fsync
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 5.0-5

LOG:
steam-731490.log

Symptoms

Works on my machine. I have not gotten to "un-bearable" yet though.

The bug where the bridge doesn't break in the Crash 2 level "un-bearable" seems to be the only issue remaining preventing the game being "100%" complete-able. [...]

I can confirm that this issue still persists with Proton 5.0-9

On latest updated manjaro as of today.
Specs are all in line.
Black screen that never goes away after trying to enter a level.

Same problem as https://github.com/ValveSoftware/Proton/issues/2001
REEEEEEEEEE

In Crash 2, I was able to play the "pre" level.
See this:
https://imgur.com/nW3tLqb
My theory is that it was because the level was backed in with the cutscene.
But as with crash 1, when I entered the first real level in Crash 2, I see the loading text and then the fucking black screen. Same thing as with that issue I mentioned, I can open the pause menu.

Something is wrong when it tries to specifically load a level, that's my theory. but WHY!!!!!!!!! REEEEEEEEEEEEEEEE

Offline mode on steam did not help.

Mentioning my specs:

OS: Manjaro Linux
KERNEL: 5.4.43-1-MANJARO
CPU: Intel Core i7-6700K @ 4.00GHz
GPU: NVIDIA GeForce GTX 1080
GPU DRIVER: NVIDIA 440.82
RAM: 16 GB

Proton 5.0.9

Spent a couple hours.
I have written a shell script (.sh) that applies the fix for you if you don't want to do it yourself.
(THIS IS IN RELATION TO THE BLACK SCREEN ISSUE THAT APPEARS WHEN TRYING TO LOAD ANY LEVEL
AS OBSERVED HERE: https://github.com/ValveSoftware/Proton/issues/2001 ).
https://github.com/MxOrbulent/FBSCNST

If you want to do it manually yourself, follow the guide here:
https://steamcommunity.com/sharedfiles/filedetails/?id=2165936424

I take no responsibility if the script blows your computer up. But I doubt it. There's only one single rm in the entire script and I have tested it rigorously so it can't fuck anything else up.

The issue seems to be related to path lengths. If you get a black screen after trying to load a level, you have the same
problem, and you need to apply this hacky fix is shortening the installdir name (in the games appmanifest) (and folder install name, installdir in appmanifest and the installation folder itself needs to be the exact same).
If it's not enough, everything before (and including your library name) is to long. Try shortening the name of your library folder too (steam>Settings>Downloads>STEAM LIBRARY FOLDERS).
If push comes to shove, you might have to get extreme and also fiddle around with the mounting of your harddrives to get the path shorter.
Note that my script will only help rename the installation folder to "cr4sh" and also do the appmanifest for you + take backups of the path strings. It won't help you do remounting or Steam Library Folder shenanigans.

See the tutorial for a example from my case on how much shorter the path got.

Some additional notes:
It has nothing to do with if the game and it's library is on another drive.
It does not seem to have to do anything to do with the spaces in the original installation folder name, as
for others seemingly just shortening other parts of the path length helped.

That seems a little overkill when you can just move the game install between library folders...

Create an extra library folder on a shorter path and then game properties > local files tab > move install folder

I can confirm that Unbearable glitches and the planks that the second Bear falls through do not disappear.

However, this glitch does not happen every time I play. I have been working on a 100% play through and I'm currently trying to get the yellow gem. I have made a total of 4 attempts at this level and level works as it is supposed to at least 50% of the time.

I haven't figured out if there is a pattern or not to the glitch.

System Information

GPU: GTX 1080 ti
Driver/LLVM version: NVIDIA 440.100
Distro/Kernel: Fedora 32/5.7.8
Proton version: 5.0-9

Hi All,
Just posting to say that the issue within the Crash 2 level Unbearable still impacts Proton 5.0-9. I have also tested using Proton-5.9-GE-5-ST from GloriousEggroll without any luck.
I have only had one instance of the bridge breaking, however all subsequent tries failed. Attached is the Proton log, frustratingly there are no timestamps so I can't be sure where exactly the events in-game would occur within the log. I am hoping both the success and the failures will show in the log.
I had to restart the level because on the final chase whilst you're riding the polar bear cub, the chasing polar bear failed to detonate 2 out of 3 of the TNTs leaving me on 56/58 ... such a pain in the arse :grin:

If there is any other information that I can provide to assist in someone looking into this, let me know. I can produce the logs but unfortunately they don't make any sense to me.

Cheers,
mAd.
steam-731490.log

An update. I was lucky enough for the bear to go through the bridge again tonight. However, the fact that the bear doesn't always detonate the TNT at the end of the level had me thinking that maybe there is something specifically going wrong with the big bear that chases you, either the hit-box is skew-whiff or some other bug relating to the bear. I don't think the bridge is an issue.
Whether this is helpful or not? :man_shrugging:

I just had a chance to try this out again today.

I am using Proton 5.13-4 and PROTON_SET_GAME_DRIVE=1. I have made it to the bridge four times now and the bear broke through each time. I'm not sure if I got lucky, more testing is needed.

Since I needed to get the gem, I finished the level. The one missed TNT box was blown up. I finished the level with 58/58 boxes.

GPU: GTX 1080 ti
Driver/LLVM version: NVIDIA 455.45.01
Distro/Kernel: Fedora 32/5.9.16
Proton version: 5.13-4

I've run the level a few more times. It looks like the issues with Unbearable are resolved in Proton 5.13-4. I was able to confirm that going back to 5.0-10 causes the glitches to happen again.

Why are you using PROTON_SET_GAME_DRIVE? I don't think that should be needed for this game.

Probably due to the long file paths breaking levels. If they game is then run from S: the paths are much shorter.

Thanks for the tip, I was unaware that was added.

PROTON_SET_GAME_DRIVE is a workaround for the black screen issue, but I thought that maybe the Unbearable bugs were related to the path length issue too so I tried using it.

I think Proton 5.13-4 fixes the issues with Unbearable, but PROTON_SET_GAME_DRIVE or moving the game Steam library somewhere with a shorter path length fixes the black screen issue.

That seems a little overkill when you can just move the game install between library folders...

Create an extra library folder on a shorter path and then game properties > local files tab > move install folder

Very late reply: Sure it might seem overkill but I made the script to help people not as knowledgeable. All they need to do is to follow the instructions the script gives.

Hi. Having a problem with DS4 controller. With Proton above 5.0-10 the LED keeps blinking blue, even on Experimental version. WIth 5.0-10 that doesn't happen but the vibration doesn't work...

Replying to https://github.com/ValveSoftware/Proton/issues/731#issuecomment-439952334

I follow this tutorial to play (https://www.reddit.com/r/crashbandicoot/comments/tqixb3/comment/i2koo20/). was having the same screen problem (Crash Bandicoot N. Sane Trilogy Black screen). I used a secondary HD to put the games, but the steam was intall in the main SSD (default o the S.O) ~/home/.steam/

installed the game on the main SSD (default the Operating System) and the problem was solved.

My Operating System Version:
Linux Mint 20.3 (64 bit)
Kernel Version: 5.4.099-generic
Proton version: 7.0-3

a regression seems to have surfaced with proton 9.0-1 where the ui elements are cutoff on certain sections of the screen depending on the screen. E.g. loading screen the bottom left and right side are partially cutoff. When you are in-game and press start menu the right side is cutoff.