The Last of Us Remake | March 28th 2023

  • Thread starter Thread starter mrk
  • Start date Start date
Do you know roughly where you are crashing?

I'm not that far into the game yet, but not had any crashes yet.

Running FSR2 and not DLSS, have you tried that yet?

Also, I've read that it might be better to run DLSS 3.1.1 rather than the TLOU version.
 
After that shader cache :eek: ...

Should have updated the driver first, oh well, it's going to cache again on a new driver isn't it?:cry:

Hope it's an old/ wrong driver problem or just broke, but Ultra settings are a mess on the 3080, ultra v medium comparison:

lou_2.png

Anyone else seen any of this?
 
  • Wow
Reactions: mrk
tommybhoy said:
After that shader cache :eek: ...

Should have updated the driver first, oh well, it's going to cache again on a new driver isn't it?:cry:

Hope it's an old/ wrong driver problem or just broke, but Ultra settings are a mess on the 3080, ultra v medium comparison:

lou_2.png

Anyone else seen any of this?
Click to expand...

Nope, running superb here on a 3080 TIFE.
 
Kelt said:
Do you know roughly where you are crashing?

I'm not that far into the game yet, but not had any crashes yet.

Running FSR2 and not DLSS, have you tried that yet?

Also, I've read that it might be better to run DLSS 3.1.1 rather than the TLOU version.
Click to expand...
It's completely random, could be just walking or turning around etc, could happen after 3 mins, could be after 30. Not tried FSR beyond just testing the image quality, nor the 3.1.1 DLSS version, one to try after the below test.

I'm just testing out something, on Steam forums someone mentioned they had the crash to desktop issue and completely fixed it by installing an older Nvidia driver (v522.25) - Multiple others confirmed that this fixed it for them too, so now I've got them installed and about to test. The game does a new shader compilation when new GFX drivers are detected, so used this chance to see if the shader comp is quick again and can confirm it is not quick this time, I'm at 18 minutes and it's only got to 34% - Whereas previously I could swear it was done in under 10 minutes.

w38B191.png

I opened up HWINFO64 earlier and saw that SSD read/write speed was woeful, whilst CPU was being maxed. Perhaps the first time round SSD write was much faster which meant the compilation finished faster. This 2nd time round I can see why some folks were waiting over an hour for shader comp :eek: Definitely needs to be patched in this area too.

Edit*
Looks like shader comp for me this time round took 23 minutes.
 
Last edited:
Yeah that's what I was on, back on it now though shortly as just had CTD on the older driver so that isn't a fix lol.

Just installing the latest driver again and will try FSR/DLSS 3.1.1.
 
tommybhoy said:
After that shader cache :eek: ...

Should have updated the driver first, oh well, it's going to cache again on a new driver isn't it?:cry:

Hope it's an old/ wrong driver problem or just broke, but Ultra settings are a mess on the 3080, ultra v medium comparison:

lou_2.png

Anyone else seen any of this?
Click to expand...


What up with the color artifacting on ultra? Looks like we might get some new complaints of "X Game killed my geforce GPU"
 
Last edited:
I think I may have solved the crash to desktop issue I have been seeing. It's not an answer people will like to hear, but I will just have another session to confirm the crash no longer happens and post back.

Edit*

I've been doing extensive testing (pulled an all nighter) and here's what I've found as have tried many things people have been suggesting all over the internet the last 9 hours or so.

1: Changing the DLSS dll file to the previous version 3.1.1 might solve crashing - It did not.

2: Using FSR on an Nvidia card might solve the crashing - It did not.

3: Using an older Nvidia driver might solve crashing - It did not, back to 543.31 Studio.

4a: Replacing the oo2core_9_win64.dll that the game ships with using a previous version might solve the crashing due to a memory leak known in the shipped version - It did not.

4b: Using the older dll will also fix the loading time and shader comp time - It did not, still 23 mins to shader comp on my system, and still 40-56 seconds to load back into my save state.

5: Lowering VRAM usage by lowering settings might solve the crashing - It did not.

In the end what i found to completely fix the crash to desktop for me is to not use FSR or DLSS at all. Granted with them off the fps is 20fps or more lower, but at native 3440x1440 y 3080 Ti is able to keep the fps at above 60 anyway, and I have Gsync to sort the motion smoothness etc out as well which works very well here.

So yeah, for now if you have the crash to desktop issue like I did, then simply turn off DLSS/FSR and run native until the devs release a patch to fix whatever is causing all this.

And because I am not using DLSS any more, I have had to lower the first two Texture quality settings from Ultra to High (hard to tell the difference between them too). All other settings are on Ultra apart from the usual naff stuff which are off (Motion blur, chromatic aberration, depth of field minimised etc).

This is probably not what people with 10GB or less VRAM cards want to hear, especially anything below a 3080 class because the fps will be much lower still, and a such those folks will have to lower even more settings until a patch is out that fixes the crashing.

My issue specifically related to crashing to desktop, I have no stuttering or anything like that.
 
Last edited:
I did wonder why I hadn't had any crashes, I'm not using DLSS or FSR. I tried both but preferred native at 1440 and capped fps at 120. Every setting maxed out (4090fe).

I usually game at 4K using DSR, and for every other game it's a good visual improvement, but Last of Us actually looks better to me at native 1440.

I did make the mistake of updating the graphics drivers to the latest, just to watch all the Shaders build again :rolleyes: at least it's only 15mins on my system.:)
 
mrk said:
Someone on the PCMR Facebook page said they fixed their crash to desktop by changing manually managed pagefile in Windows to system/max. I have a 2GB fixed pagefile as it's never used by anything. I guess this is the rare instance where a larger pagefile simply existing may be necessary even if it's not used. I will try this shortly and put those 2 texture settings back to Ultra and see if I get the crash again.
Click to expand...
Whether this is the solution or not, the need to set the page file manually is a piece of advice that was last relevant in Windows XP. How it's somehow surving as a "tip" today is baffling.
 
This game clearly has issues but some users have PC's that are brute forcing past some of the issues.

Previous ports like Spiderman have really positive steam reviews. It's clear it's a mess based on the lack of Steam Deck verification despite hype to that effect before hand
 
Hmmmm, only played around 20 mins last night and had zero issues. Admittedly I'm on a 3060ti at 1440p, so not got all the bells and whistles turned on. Also running an old driver (516.94) :eek:
 
As a lover of TLOU games, it's a real shame that this game is pretty much unplayable for me on a 3080. I'm not too bothered about the shaders thing, which was only 10-15 mins for me, but appreciate it will be longer for people on older/lesser core processors. Even if it had taken an hour, I wouldn't mind too much if the game performed well enough. I've not experienced any crashes but I've even tried turning the settings all the way down to low (makes the game looks like crap), and I'm still getting a poor frame rate, enough to give me a headache. Ultra is not possible on a 3080, which is fair enough, but according to the minimum specs I shouldn't be having issues running it on High @ 1440p. It starts off at an ok 70 fps, but after 10-15 mins in game and/or scenes that have anything more than standing still going on, it drops to ~50 fps with frequent drops much lower than that. It also seems to make my PC unstable after I've closed the game, as it's making MW2 either crash or have significant frame drops mid-game... a reboot after closing TLOU resolves the issue.

I'm going to wait until hopefully there's some patches that improve things. I've completed this game several times before on PS5 (original and remaster) and had eagerly awaited getting the PC release before completing Part One. I feel sorry for anyone that is experiencing this game for the first time on PC, as it's one of the best games ever made and so far, they've made a right pigs ear of this port...
 
It's made by the same people who did Batman Arkham Knight, so no surprise it's running poorly. We shouldn't already be needing the latest GPU and CPU to brute force games into running at passable frame rates.
 
Didn't even manage to get through the shader compile last night (only reached about 28%) and I have up as it was just taking too long ... Not great but look forward to actually giving it a go at some point once I leave it long enough to actually complete the process!

This is on a 5800x3D and 7900XTX so maybe it setting everything to ultra maxed out isn't ideal!
 
Interesting, I am using DLSS and getting precisely zero crashes.
3080Ti

Here is the game running on my system:


Ultra preset, 4K, DLSS balanced.
 
Last edited:
Mesai said:
It's made by the same people who did Batman Arkham Knight, so no surprise it's running poorly. We shouldn't already be needing the latest GPU and CPU to brute force games into running at passable frame rates.
Click to expand...
Hahaha, priceless. Currently playing through AK for the first time as it was a PowerPoint on release. And even 8 years later, it's still a bit flaky e.g. noticeable stutter when I use the brake in the Batmobile.
 
You must log in or register to reply here.
Back
Top Bottom