Ratchet & Clank: Rift Apart (1895880) #6968
Comments
AQDuck97
changed the title
|
It also doesn't start here with default settings, but setting Texture Quality down to Medium lets me get to the main menu. Anything higher freezes after the intro video. Proton version: GE-Proton8-9 |
|
I tried setting everything to low but still hangs in the same spot and the same errors. |
|
just added my Proton version and launch options to my last comment, try the exact same used the "High" graphics preset, only dropped texture quality to prevent the freeze, I could get in-game now: |
|
Same with your options |
kisak-valve
changed the title
kisak-valve
added
the
Game compatibility - Unofficial
|
GTX 3080, using PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%, it gets past the intro where it shows the Wrench loading icon until I hear a beep, then it freezes. |
kisak-valve
added
the
NVIDIA drivers
|
Yeah, setting to Med gets me in, so the issue is NV cards on Higher or above textures. |
|
Can confirm that setting it to MEDIUM got me in! |
|
I've played for about an hour now, most settings (aside from textures which are medium) on high (including RT, with DLSS), runs pretty well up until it crashed during one of the "rifts". |
|
I thought so too at first, but medium textures seems to be the only option that doesn't crash, so there has to be something else. |
|
For sure anything related to DS or RTX IO does not work atm, rifts are painfully slow. Sadly the only way i see it working is if VKD3D adds RTX IO support and forwards DS calls to RTX IO. Then its just up to mesa to implement the extensions. |
|
+1 Setting textures to medium allows getting past game freezing after intro logos, but setting it back to high/very high once in game locks it up again. |
|
cpu: amd 5800x Originally encountered two error dialogs, one after the other on launch. The first described not being able to detect the GPU. The second described that although my 3090Ti meets the minimum specs, my nvidia driver was outdated. The number listed for the driver version it thought I had was the 32bit max int. Clicking ok through both errors presented me with the launcher. Clicking play would move through the intro videos and then freeze on the first load screen with the wrench icon. The driver fields in the log file located at "/home/jaster/.local/share/Steam/steamapps/compatdata/1895880/pfx/drive_c/users/steamuser/Documents/Ratchet & Clank - Rift Apart/Ratchet & Clank - Rift Apart.log" appeared to be emtpy which may explain why the driver version was incorrect in the error dialog. Edit: Set the game to low preset and disabled raytracing completely. Enabled dlss. This allowed me to move past the rift cinematic section. Edit2: Setting texture quality specifically to low although everything else is on high allows me to move past the rift cinematic section. |
|
Game brings up a error on launch and then crashes when using proton 8.0-3 but runs perfectly fine with proton Experimental
Log: https://gist.github.com/coreybruce/2fe4947b599ab93ed312df9ec6b8c547 |
|
@coreybruce That's an issue with an older version of vkd3d-proton, when you use Proton Experimental that error will go away. |
Yeah I know that's why I said "but runs perfectly fine with proton Experimental" :P |
|
Just as confirmation, the AMD gpu deck has no issues at all with high textures. |
|
Slightly unrelated to the initial crash, but I get the same dmesg error when I get stuck in this rift |
|
im having the same issue too. my specs are as follows i can max every setting except textures past medium |
|
I've played for a bit now and got to the planet "Savali". It's completely unplayable on Nvidia and immediately crashes the game regardless of settings. I tried to get through the cutscene on my RX 570 and made a save once I got on the planet, but just 2 seconds after loading the save on the Nvidia card I got the same error as before in dmesg. The planet was loaded and I could run around for those 2 seconds, but it still crashes. I am now softlocked as this is a "forced" section and the backup file the game creates is on this planet, so I cannot go back and choose the other planet. |
|
I can get game to run at medium preset (every other preset crashes). However, once I get to the nefarious juggernaut and go through the rift that opens in that boss fight the game immediately crashes. Unfortunately, you have to go through this rift. Ratchet & Clank Log File attached, error appears to be the following:
@justbugs97 What does your log file say? I suspect a similar error. Log file can be found at: Furthermore, Proton log file showed three important messages:
Ratchet & Clank and Proton log files: Relevant info: |
|
Yeah, same errors @cbacary. I managed to play a bit more on the planet by reducing the graphics to very low, disabling DLSS and changing resolution to 1080p, however I then made the mistake of trying to up the graphics and accidentally put textures on High (which froze the game), since then I have not been able to load the save at all and I'm fearing it's corrupt. |
I got the same issue, I avoided the juggernaught portal issue by switching to my steam deck then loading a save after the fight. I can do the same for this plannet as it works fine on the deck but yeah ... This plannet is a pain, crashes every time it loads. I also get the same message in my RCRA log file. I am running with: game settings presets high with medium textures and launched with: Plannet crashed the game just like juggernaught portal, and not much in the game logs other than: |
|
That's odd that you have to turn your graphics to low, I'm playing at high preset with a 6700XT |
|
As was concluded pretty early in the issue, this bug seems to be entirely contained to Nvidia cards. |
|
Having the same issue as cbacary . At first I used Proton Experimental with all default. The game succeeded to start, but freezed trying to show start menu. I have changed game settings to medium and managed to get to Nefarius. But beating him is not possible because the game freezes trying to render rifts. The log ends with this: |
|
I am also experiencing these issues. The game needs to be run with Medium textures, everything else functions as expected when maxed out, even RayTracing. I was able to work around the first juggernaut by playing that section on SteamDeck. However, now I am getting stuck trying to get to Savali. Logs: Game Log, Proton log I have done some digging and have found the following: From the game log, the failed The other wine warnings about stubbed methods appear to happen when alt-tabbing and seem unrelated: |
|
So after today's update I'm completely unable to get past the menu, once I've loaded a save (auto save, manual save, brand new save, etc.) I'm stuck on a black screen with the menu music playing in the background. |
I can confirm that deleting dstorage.dll and dstoragecore.dll allows game startup with very high texture quality and progression past rift during boss fight on RTX 3090. Thanks for the tip. |
|
rather than deleting dstorage.dll and dstoragecore.dll can you instead try launching the game with: WINEDLLOVERRIDES="dstorage=d,dstoragecore=d" %command% |
this reads as a giant run on sentence.. it's proton-experimental and vkd3d-proton devs that are doing all the work here. Just want to clarify that. Proton-GE builds on top of proton-experimental wine and vkd3d-proton changes that have already been upstreamed. Basically if it works in proton-experimental, then it should work in proton-ge, and usually it's bleeding edge that receives game fixes before any other forks such as my own. |
Same result, game starts correctly even with very high quality textures. |
|
sure gloriouseggroll, and i watching how my little program been doing all those years as this late after calling quits way back then when creator just vanish from this planet , since i did started the idea of manipulating windows dlls from wine itself since its free from them, and i been getting tired of it for them not gonna anywhere with wine dlls by installing dx9 redist files over it. so i thought it would be neat hack the code from wine creators since i am not a coder in my experience just tweaking and tinker what is established and by then the team grew fast in that approach then i quit when someone took over it from github, the reason i quit is valve , i don't like valve business |
Thats why I was confused, didn't make any sense that you somehow we're getting DS to run when that's not your field. Though I wonder where he got his info from about the work being done on it. I had assumed those RTX IO extensions would be the key but Ive heard zero work on them being added to mesa or VKD3D-Proton. |
then this is very likely a much better workaround than deleting game files. I can add a proton-ge protonfix for it but valve will also likely want to do something similar |
|
The newly released Proton Experimental includes some vkd3d-proton work which should help the Nvidia direct storage issues. |
|
Looks like with the new game update, there's no way to enable raytracing on AMD cards on Linux. On Windows, you need a specific recent driver version that doesn't seem to even appear in Radeon Software's updates section in order for the game to let you enable raytracing. Has anyone had any luck getting it working with RT on Linux with an AMD GPU? |
Confirming the same issue, was attempting to find a solution by faking the reported driver version, but I have no understanding of any ability of Proton to do this. My mesa driver is the latest pull from around 2~ hours ago, so I definitely have the "latest". |
|
after update from 08/09 break the game here with nvidia driver. |
rollback to previous update game start again
|
@tuxtergames Can you try on Proton Experimental again without being on the Ratchet & Clank beta? We just pushed out an update that should fix it. |
|
@AJuujarvi I can load into game now on Nvidia 3090 on Very High settings with latest Proton Experimental, with no custom command args. |
Testing here, its working again with experimental bleeding edge, but without RT and DLSS, if you leaving this options on launcher game won't launch, I using here just gamemode and mangohud with a 3060ti on a desktop in high settings, tks for this fix guys, you rock!!!!! |
|
Recent series of game and proton patches have now rendered it unplayable. Game struggled to get past the menu without freezing, and then if it did, would crash moments after being ingame. So I reinstalled, and now it wont get past the sony entertainment presents screen, it does get past it with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% only to crash after all the logos finish GTX 3080, dunno whats going on here, yes the dstorage dlls are present. |
|
@Bitwolfies Hello. Would you be able to post a Proton log? |
|
@Blisto91 Have at er Gonna guess it has to do with since its spammed 800 times. |
I'm playing right now and game works nice smoooth here, take out parameters of launch, doesn't work with RT or DLSS. |
|
Works even less without them, so thats not the fix. Also worked fine with RT before this. |
|
Just tried it seconds ago; proton experimental, no launch options, 3090 535.98, max details, debian trixie, kde plasma, wayland. Launches and plays fine. |
|
oh, you wanted ray tracing. In that case: game launched fine, started playing, performance was ok with RTX features on very high, however game crashed during reload after dying, so there's still something going on here. |
|
seems that crash was a one time occurrence. Wanted to catch a log of it, and no luck. Played for 15 mins with some deaths (new game+ on max difficulty ;p) and decided to quit before getting hooked again ;) |
|
With last update ( v1.922.0.0) Ray tracing options are no longer available on AMD GPU. There is a startup message indicating that the driver is not up to date. Tested with Proton-Experimental No problem when rolling back to v1.831.0.0, this is not a Mesa issue. |
Can you try with Proton Exp Bleeding Edge? This commit might have fixed that. |
|
I think there's maybe been a regression. With Proton Experimental, it's specifically when you are aiming a weapon, the performance tanks down to about 20fps (from 100). It seems specific to this action and it happens every time you aim (mouse or controller). I tried with Proton-GE 8.20 afterwards and the issue was completely gone, while also getting a 20fps boost. Edit: Nvidia |
|
Hello @hjpaul7, please add It would be useful to note how the game behaves with Proton 8.0-4. |
|
@kisak-valve Here is the Proton log. I'm not able to open the |
|
Unsure if this is proton, but on the OLED deck the game doesn't display any controller glyphs, just question marks. Unsure if the OLED represents itself differently? |
and others
Proton: Proton 8.0-3, Proton Experimental, GE-Proton 8-9
Distro: Arch Linux, 6.4.6-zen
GPU: Geforce RTX 3080, 535.86.05
Platform: X11
Launch options:
DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 3080" PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr11,dxr VKD3D_FEATURE_LEVEL=12_2 mangohud PROTON_LOG=1 %command%The game completely freezes after the Playstation intro and if I don't kill the process fast enough the entire desktop (Plasma 5.27) hangs as well.
Running dmesg I get this error during the crash:
NVRM: Xid (PCI:0000:0b:00): 109, pid=30603, name=RiftApart.exe, Ch 00000016, errorString CTX SWITCH TIMEOUT, Info 0x1c00cAnd in the Proton log I get this:
warn:vkd3d-proton:d3d12_command_list_IASetIndexBuffer: Invalid index format 0. This will map to R16_UINT to match observed driver behavior.The text was updated successfully, but these errors were encountered: