-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash Bandicoot N.Sane Trilogy (731490) #731
Comments
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:
It looks like this has been fixed already in upstream wine by checking for context == null: wine-mirror/wine@ec418e7 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? |
Crash Bandicoot N. Sane Trilogy Black screen Issue transferred from #2001. Compatibility Report
System Information
I confirm:
SymptomsBlackscreen Reproduction |
@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. |
@briangular I noticed that one of the more recent playabilit reports on ProtonDB says that it worked only after installing the |
@briangular 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 ...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 😄 |
@briangular I haven't tried SteamOS but I do know Linux, so I can think of a few ways to escape Big Picture:
Maybe @kisak-valve has a better idea? Hope this helps 😄 |
@runejuhl |
@dribbleondo
installed, and Crash is working fine. |
@runejuhl 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
it works without any problems
|
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 |
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
|
My cursor disappears when I press a keyboard key, making it impossible to attack or navigate the menus. |
This comment has been minimized.
This comment has been minimized.
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. |
Game crashes after I click at the title menu, audio keeps playing though. EDIT: |
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. |
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: So far, I can say that this configuration works: Fedora 30 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
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: |
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: |
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. |
Hello @aqxa1, please copy your system information from Steam ( |
System information 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. 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
System Information
LOG: SymptomsWorks on my machine. I have not gotten to "un-bearable" yet though. |
I can confirm that this issue still persists with Proton 5.0-9 |
On latest updated manjaro as of today. |
Same problem as #2001 |
In Crash 2, I was able to play the "pre" level. 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 Proton 5.0.9 |
Spent a couple hours. If you want to do it manually yourself, follow the guide here: 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 See the tutorial for a example from my case on how much shorter the path got. Some additional notes: |
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
|
Hi All, 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, |
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. |
I just had a chance to try this out again today. I am using Proton 5.13-4 and 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 |
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. |
I think Proton 5.13-4 fixes the issues with Unbearable, but |
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... |
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: |
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. |
Hello @minionprocyk, please add |
The game will randomly crash within a few minutes of launching unless steam is set to offline mode.
Tested on Ubuntu 18.04.1
Proton 3.7-4 Beta
Ryzen 7 1700
GTX 1070 w/ driver 396.54
The text was updated successfully, but these errors were encountered: