Really hoping for another patch that will address the crashing issue in Japantown when ray/path tracing is enabled

+
Please CDPR...I just can't enjoy the game anymore because of those crazy crashes happening while driving in Japantown. I don't know what you guys changed to ray/path tracing in 2.1 but it just messed things up for some people, because these crashes instantly stop if I remove the Phantom Liberty folder, revert to patch 2.0, or turn of ray tracing.

I have been waiting for the last few months hoping for a fix but it doesn't seem to be happening...This was my favorite game back in 1.63 and 2.0 with 300+ hours of crash-free experience. But now I can't do any gigs or quests in Japantown due to these random crashes.

Please fix the game for those of us severely affected by this!

This is the thread where I go into details about the exact bug and my testing methods that helped me pinpoint the source of the problem.
 
Last edited:
Please CDPR...I just can't enjoy the game anymore because of those crazy crashes happening while driving in Japantown. I don't know what you guys changed to ray/path tracing in 2.1 but it just messed things up for some people, because these crashes instantly stop if I remove the Phantom Liberty folder, revert to patch 2.0, or turn of ray tracing.

I have been waiting for the last few months hoping for a fix but it doesn't seem to be happening...This was my favorite game back in 1.63 and 2.0 with 300+ of crash-free experience. But now I can't do any gigs or quests in Japantown out of fear for these random crashes.

Please fix the game for those of us severely affected by this!
If it's the crash on the curved section of waterfront road, it seems to happen only on that curved section and doesn't happen if you slow down for that segment of the road. I'm guessing it's a streaming problem of some kind, with too many graphical assets / effects having to be loaded in at once if you go too fast.
 
If it's the crash on the curved section of waterfront road, it seems to happen only on that curved section and doesn't happen if you slow down for that segment of the road. I'm guessing it's a streaming problem of some kind, with too many graphical assets / effects having to be loaded in at once if you go too fast.
yeah the crash there is reproducible for sure, but it's not the only place that crash. Another 100% reproducible crash is during the "send in the clown" mission right after picking up Ozlo. It will crash even when driving at 5mph. Other places in Japantown also can lead to random crashes.
Post automatically merged:

If you don't use mods (and well, also never used on this playthrough), feel free to send a ticket directly to the support ("contact us" button), because I doubt everyone on PC experience these crashes :(
I have already. It didn't help because there's nothing they can tell me that I don't already know/haven't tested yet. I already know that the issue is with some changes to ray/path tracing in 2.1 but unless the support convey my testing findings to the dev team, my problem can't be solved.
 
Are you with a 13th or 14th gen intel?

Those CPUs seem to have a high rate of defects that lead to crashes. That it is localized in the game may only mean that certain scenes trigger the issue with the CPU.

Slowing down DRAM may hide the issue with such a CPU.

 
yeah I have a 13th gen CPU. Thanks for the suggestion, I will take a look at this. However, I had the exact same setup for 1.63 and 2.0 and had zero crashes during this time. It only happened since 2.1.

Also no crashes with other games.
 
I have already. It didn't help because there's nothing they can tell me that I don't already know/haven't tested yet. I already know that the issue is with some changes to ray/path tracing in 2.1 but unless the support convey my testing findings to the dev team, my problem can't be solved.
Support might not being able to help you right away, but by reporting the issue, that could help them to fix it in an upcoming update, which at the end, will help you and everyone who encounter the same issue ;)
 
yeah I have a 13th gen CPU. Thanks for the suggestion, I will take a look at this. However, I had the exact same setup for 1.63 and 2.0 and had zero crashes during this time. It only happened since 2.1.

Also no crashes with other games.
Yeah, it's interesting though not so surprising. Cyberpunk 2077 is the heaviest game there is out there right now.

I can say that being with the 12th gen and 3090 didn't raise any grief for me yet.

If the root cause is so-called cpu bending due to that terrible new clamping mechanism, then the problems will start for me too.
 
Last edited:
If you don't use mods (and well, also never used on this playthrough), feel free to send a ticket directly to the support ("contact us" button), because I doubt everyone on PC experience these crashes :(
Mods have nothing to do with it. If it were mods, then the crashes would be in all districts. This is not the case, it is in Japantown only, therefore something about Japantown is the issue, just by process of elimination. I have the same issue, with Japantown, and it is just Japantown the crashes happen, especially driving.
Just to be clear, I have no mods for cars, or changing how they operate in game, only clothing mods.
 
Mods have nothing to do with it. If it were mods, then the crashes would be in all districts. This is not the case, it is in Japantown only, therefore something about Japantown is the issue, just by process of elimination. I have the same issue, with Japantown, and it is just Japantown the crashes happen, especially driving.
Just to be clear, I have no mods for cars, or changing how they operate in game, only clothing mods.
Never said it was due to mods, but if the support ask you a save and if you send a modded save, I'm afraid it won't help. It's already hard enough the track down the cause of issues. So if you use mods whatever the origin of an issue, I think you should just consider not sending a ticket to the support.
 
Never said it was due to mods, but if the support ask you a save and if you send a modded save, I'm afraid it won't help. It's already hard enough the track down the cause of issues. So if you use mods whatever the origin of an issue, I think you should just consider not sending a ticket to the support.
Yeah for testing I used a vanilla save without any mods on a freshly installed game on a newly reset Windows with latest drivers. Crashes still happen on both GOG and Steam version, but stop when I turn off ray/path tracing or roll back to 2.0.
I basically already did all the heavy lifting with 20+ hours of testing and troubleshooting, and pinpointed the source of the problem. I wish support would at least acknowledge this and say they will send this back to the dev team but they never even replied to my report.
Guess I should send another ticket then :/
 
Never said it was due to mods, but if the support ask you a save and if you send a modded save, I'm afraid it won't help. It's already hard enough the track down the cause of issues. So if you use mods whatever the origin of an issue, I think you should just consider not sending a ticket to the support.
Apologies for misunderstanding you.
 
Apologies for misunderstanding you.
Don't worry :)
I know that it could sound like "mods are bad and cause all bugs".

It's just that we know that there is no more devs working on Cyberpunk anymore... So in case there is still someone at CDPR who keep working on the game to fix the remaining game bugs, I prefer to see him spend every single secondes of his time fixing bugs which without a doubt, come from the game for sure (which every single player could encounter) rather than wasting time on bugs which might potentially due to mods (bugs he won't be able to fix anyway).
 
Yeah for testing I used a vanilla save without any mods on a freshly installed game on a newly reset Windows with latest drivers. Crashes still happen on both GOG and Steam version, but stop when I turn off ray/path tracing or roll back to 2.0.
I basically already did all the heavy lifting with 20+ hours of testing and troubleshooting, and pinpointed the source of the problem. I wish support would at least acknowledge this and say they will send this back to the dev team but they never even replied to my report.
Guess I should send another ticket then :/
Have you also noticed a split-second pause when it auto-saves as well?? Again driving only in Japantown.
 
Have you also noticed a split-second pause when it auto-saves as well?? Again driving only in Japantown.
Yup, I notice these all the time, don't think it's only in Japantown though, but everytime when it autosaves, regardless of where you are.
I've been patch 2.0+ for so long tho and forgot whether I had these before so it didn't even occur to me this isn't intended/normal LOL. Is this not supposed to happen? (I mean it certainly would be nice because the stutter is annoying but not enough for me to think it could actually be a bug.
 
Yup, I notice these all the time, don't think it's only in Japantown though, but everytime when it autosaves, regardless of where you are.
I've been patch 2.0+ for so long tho and forgot whether I had these before so it didn't even occur to me this isn't intended/normal LOL. Is this not supposed to happen? (I mean it certainly would be nice because the stutter is annoying but not enough for me to think it could actually be a bug.
Most of the time the auto save goes off without effecting the game at all, until Japantown. Complete shut down and restart of the game is the only fix that I am aware of.
 
Most of the time the auto save goes off without effecting the game at all, until Japantown. Complete shut down and restart of the game is the only fix that I am aware of.
huh interesting. I've been playing for so long so maybe the auto-save mini-freeze is actually only happening in Japantown but I just don't remember anymore given how I'm used to it. I will pay attention next time and see if this is the case for me too. I kinda doubt it for me though because I literally don't go to Japantown anymore but I do still remember getting these mini-freezes when autosave happens, I spent most of my time in Dogtown now so chances are I experience them there, I wonder if these mini-freezes happen to you there as well?
 
The more news come out about Intel's 13th and 14th gen, the more wild it looks to me.
It really could explain the loads of complaints of the game crashing I've been seeing in these forums since their launch.

Steve says they have been poking this with Intel 6-7 months if I recall correctly, what they talk about didn't just suddenly start now, it has been a thing for a while.

 
The more news come out about Intel's 13th and 14th gen, the more wild it looks to me.
It really could explain the loads of complaints of the game crashing I've been seeing in these forums since their launch.

Steve says they have been poking this with Intel 6-7 months if I recall correctly, what they talk about didn't just suddenly start now, it has been a thing for a while.
Ya, the fun part is I do have do have a I9 13900 in my desk top. That said Cyberpunk's instability, on that processor is everywhere from instantly to say 5 min into the game: not just Japantown. The game became stable after I shut down the hyper threads, AND have Intel's Extreme Tuning Utility slowing the Performance Core Ratio from x55 to x52. Hogwarts was even worse it would not run at all, until I made those changes.

The truth is simon_93 hit the nail on the head, and he has done a butt ton of experimenting. I used Nvidia Optimizing and took my game from Path Tracing to Ray tracing, and so far (not a lot of time in Japantown of this writing, but a couple of hours) seem to be doing okay. .... hopefully. Video card is a 4080, so ya it can use Path Tracing, but Nvidia thinks the game is not.

Ironically my laptop has I9 13980, and has no stability issues at all. I have not needed to tinker with its CPU performance at all.
 
Seeing the Error and crash report would make troubleshooting much easier.
But if you're on a 13/14 gen intel, that is most likely the issue. I changed my Power settings for my 14900kf, which fixed the crashes for me.
 
Top Bottom