.....why did nobody notice The Witcher 3 - PS5 port was a glitchy mess?

vitopursuer said:
just for anyone who says to ignore this bug - how can you ignore if this is just happening every few seconds, it is madness, it got so much worse for some reason. Tired of cleaning the cache, feels like it made it only worse -
Click to expand...

What are we looking at? Is it the textures popping near the end. Did you play it on base ps5 or pro?
 
dreamstation said:
How is the PS5 version now? Still not fixed?
Click to expand...
still nothing, feels only like it got worse. I am just sitting and trying to see what caused 2 times for game to run without bug, 2 times out of like 50 times when suddenly there was no trace for bug but it appeared right after rest mode or just restarting the console
 
after each restart of the game, if you stand still, do nothing, there is no weird bug or anything, but as soon as you start to run, all is normal, but only for like 5-6 seconds, after this time the bug always triggers, or at least like 99% of the time. That is another example -
it works okay for 5-6 seconds, but then sudden massive grass texture pop in, and then part of it disappear, and then seconds after new patches of grass appear, then again new. It is happening pretty often, in some places very visible and annoying and extremely often, in others not so often which is weird again, like some part of the map are more bugged out.
 
ps4 version is great for ps4, I played it for hundreds of hours but it is not graphically really outdated, ps5 version is extremely beautiful and its hdr make the picture absolutely bright and vibrant, very detailed and it is only enhances the bug visibly sadly, as all is crisp and nice and you just see these grass textures shifting and popping out everywhere
 
This must be a recent issue as I platinumed the PS5 version when it came out and do not remember anything like this at all.
 
I just talked with a guy who switched his playstation 2 times and all of 3 console that he had has this bug. That is shocking. What a bad luck. Funny thing is that you can get lucky and console will never have the bug. Which really makes me think there is possibly some small componet that is different and specifically causing this bug, or else how is this happening...
 
J
vitopursuer said:
I just talked with a guy who switched his playstation 2 times and all of 3 console that he had has this bug. That is shocking. What a bad luck. Funny thing is that you can get lucky and console will never have the bug. Which really makes me think there is possibly some small componet that is different and specifically causing this bug, or else how is this happening...
Click to expand...
JUST BUY THE PRO GUY, YOU ARE STILL OBSESSING OVER THIS GARBAGE, I HAD TOLD YOU THE SOLUTION BROTHER



JUST.DO.IT
 
vitopursuer said:
I just talked with a guy who switched his playstation 2 times and all of 3 console that he had has this bug. That is shocking. What a bad luck. Funny thing is that you can get lucky and console will never have the bug. Which really makes me think there is possibly some small componet that is different and specifically causing this bug, or else how is this happening...
Click to expand...
There is simply not enough info to judge this accurately. It would require a giant undertaking.

First one must find a 2 PS5s. One where the issue happens and one where it does not.

Then they would need to do some testing to see if they could create a situation where the game was fixed or working based on reinstalls, restarts. We are trying to find out if the game is 100% always working on one console and 100% not working on another. Testing would need to be done after reinstalls, with a full ssd, an empty ssd, a 3rd party ssd, ect. We would need extensive testing in this phase.

Then if we could verify that one console always had the the issue and the other never had it and we were 100% sure about that with no room for error, then we could move on to getting the serial number and batch number and finding similar consoles to see if this holds up to our logic. If so we could then get Sony to check and see what is different between the batches.

However, I think you would get hung up on the second phase. I don't think you would be able to prove with testing with 100% certainty that two consoles always behave differently towards the popups of grass in this game. It doesn't feel like a hardware issue so I don't think it is, but to test the above would need to be performed and I don't think we can compile the data from a mishmash of online reports, we need real scientific testing to confirm the issue.
 
Last edited:
Zacfoldor said:
There is simply not enough info to judge this accurately. It would require a giant undertaking.

First one must find a 2 PS5s. One where the issue happens and one where it does not.

Then they would need to do some testing to see if they could create a situation where the game was fixed or working based on reinstalls, restarts. We are trying to find out if the game is 100% always working on one console and 100% not working on another. Testing would need to be done after reinstalls, with a full ssd, an empty ssd, a 3rd party ssd, ect. We would need extensive testing in this phase.

Then if we could verify that one console always had the the issue and the other never had it and we were 100% sure about that with no room for error, then we could move on to getting the serial number and batch number and finding similar consoles to see if this holds up to our logic. If so we could then get Sony to check and see what is different between the batches.

However, I think you would get hung up on the second phase. I don't think you would be able to prove with testing with 100% certainty that two consoles always behave differently towards the popups of grass in this game. It doesn't feel like a hardware issue so I don't think it is, but to test the above would need to be performed and I don't think we can compile the data from a mishmash of online reports, we need real scientific testing to confirm the issue.
Click to expand...
I did many of the tests, extreme tests, such as full factory reset with software reinstallation, nothing helps the bug, it randomly disappears for one playtime session before either restart, turning off or rest mode, after these the bug just returnes. There is no working way to fix it even just for one play session, I did the researches for over a year, for a year and 2 months already and I often monitor the situation and get comments in my videos about bugs and people are desperate to fix it but no way to fix it, the only way is to have CDPR fix it but they simply don't want to or it is so difficult they can't fix it themselves, which I had argument about with few peole and everyone but me believes it is just laziness that bug is not fixed
 
SkyHighTrees said:
J

JUST BUY THE PRO GUY, YOU ARE STILL OBSESSING OVER THIS GARBAGE, I HAD TOLD YOU THE SOLUTION BROTHER



JUST.DO.IT
Click to expand...
I am afraid I got 2 reports of bug being on ps5 pro as well, so I don't know, either those people just liers or it happens on PS5 pro too but maybe rarer? so far on youtube videos of W3 on PS5 I watched I did not noticed any popping but it could be a coincidence
 
Could be patches over time causing issues, but I also think people just have different thresholds for performance issues.

I literally played the PS4 version on a friend's machine, which he said was great, and I was getting fps in the 20s through an entire swamp area. I also got obvious traversal stutter transitioning into certain areas like towns, but he never noticed/cared about either.
 
vitopursuer said:
I did many of the tests, extreme tests, such as full factory reset with software reinstallation, nothing helps the bug, it randomly disappears for one playtime session before either restart, turning off or rest mode, after these the bug just returnes. There is no working way to fix it even just for one play session, I did the researches for over a year, for a year and 2 months already and I often monitor the situation and get comments in my videos about bugs and people are desperate to fix it but no way to fix it, the only way is to have CDPR fix it but they simply don't want to or it is so difficult they can't fix it themselves, which I had argument about with few peole and everyone but me believes it is just laziness that bug is not fixed
Click to expand...
I admire the work you have done for this and I am trying to help.

You are telling me that rarely the bug will randomly disappear but only for one play session? I'm assuming you have tried different areas of the map. If only you could identify the variable that changes when this bug doesn't happen, that would likely give us the cause of the bug.

Since you have rebooted and even reformatted and reinstalled we can assume that this likely isn't a simple memory issue. I'm also assuming a few things like the save file that it happens and doesn't happen is the same save file. I'm also assuming things like you tested this both connected and disconnected from the internet, with headphones on, headphones off, mute on, mute off, hdr on, hdr off, vrr on vrr off, ect.

Using the scientific method we would try to list and document any potential variables and test each one. In game things, like what time of day, if certain scenery is visible and specific location of testing will need to be defined as well. Also physical variables like the ambient temperature.

Thinking of what could cause this, just off the top of my head I would assume resolution or something within the game that scales up and down as the game is being played. Perhaps there is an overload of effects that is causing a queue on some of the resources causing popins specifically in the grass. Many games have a foliage setting that can be adjusted and can have major performance impacts. Perhaps they simply have the foliage up one level too high for the average PS5 in their settings behind the scenes because perhaps their dev kit could handle it but some PS5s cannot. Have you tried playing on a 1080p or 1440p monitor to see if the issues persist? Perhaps this would offload resources enough from the console in order to prevent the error. That isn't a fix but if we could verify that fixed the issue then we could present this to Sony and CDPR for further review. Sorry I'm late joining this and hope to see it be resolved.
 
Zacfoldor said:
I admire the work you have done for this and I am trying to help.

You are telling me that rarely the bug will randomly disappear but only for one play session? I'm assuming you have tried different areas of the map. If only you could identify the variable that changes when this bug doesn't happen, that would likely give us the cause of the bug.

Since you have rebooted and even reformatted and reinstalled we can assume that this likely isn't a simple memory issue. I'm also assuming a few things like the save file that it happens and doesn't happen is the same save file. I'm also assuming things like you tested this both connected and disconnected from the internet, with headphones on, headphones off, mute on, mute off, hdr on, hdr off, vrr on vrr off, ect.

Using the scientific method we would try to list and document any potential variables and test each one. In game things, like what time of day, if certain scenery is visible and specific location of testing will need to be defined as well. Also physical variables like the ambient temperature.

Thinking of what could cause this, just off the top of my head I would assume resolution or something within the game that scales up and down as the game is being played. Perhaps there is an overload of effects that is causing a queue on some of the resources causing popins specifically in the grass. Many games have a foliage setting that can be adjusted and can have major performance impacts. Perhaps they simply have the foliage up one level too high for the average PS5 in their settings behind the scenes because perhaps their dev kit could handle it but some PS5s cannot. Have you tried playing on a 1080p or 1440p monitor to see if the issues persist? Perhaps this would offload resources enough from the console in order to prevent the error. That isn't a fix but if we could verify that fixed the issue then we could present this to Sony and CDPR for further review. Sorry I'm late joining this and hope to see it be resolved.
Click to expand...
oh, what did I not try, I was even so mad that I had to buy Witcher 3 ps5 standard edition because me and guys thought it could be bug only with witcher 3 GOTY and my friend even bought a physical copy of Witcher 3, we ruled out that version of the game does not effect bug. HDR on and off, vrr I do not even have but my friend has and VRR on and off no difference. He also has SSD m2 2TB, in system memory or ssd m2, there is no difference too. Headphones on and off no difference, mute off and on did not really try but I could try. I tried resolutions 720p 1080p, I have specifically monitor 1440p, tv and one monitor that is 4k. I tried also combinations l like cleaning cash, restarting, restarting and then cleaning cash, rebuilding database, then again restarting, combining all 3 together, also I heard unplugging can make cache clean up, unplugging during rest mode.. whatnot I have tried. There is so much discussion in this formus in this topic about this bug, me and guys tried out whatnot, and I would be so really happy if at least cause of this bug could be figured out, but closest to the cause that we came to is untold differences of PS5 models or how to make sense that some consoles have 100% absence of bug any time and other consoles have it on 99% of the times. And it is like 50/50 consoles that have never experienced bug and others experience it unstoppably. Maybe also these 50% of other users who play game and never have bug done something specifically and they are not aware of it, but it is only assumption.
 
Durin said:
Could be patches over time causing issues, but I also think people just have different thresholds for performance issues.

I literally played the PS4 version on a friend's machine, which he said was great, and I was getting fps in the 20s through an entire swamp area. I also got obvious traversal stutter transitioning into certain areas like towns, but he never noticed/cared about either.
Click to expand...
ps4 version after patch 4.00 has serious performance issues I can confirm it because I have ps4 aside of ps5, but except that ps4 version is good old version, pretty playable despite the performance issues or for some unplayable because they are too spoilt by constant stable fps, which is normal these days, I am the one insane and ubnormal lol, because I played games on 17-20 fps in my younger years, I had really weak pc, so console issues like drops to 25 fps do not bother me so much, graphical issues like grass popping out all over right in front of your eyes and changing every few seconds - that's the issue, that is what breaks immersion unbearably
 
Zacfoldor said:
I admire the work you have done for this and I am trying to help.

You are telling me that rarely the bug will randomly disappear but only for one play session? I'm assuming you have tried different areas of the map. If only you could identify the variable that changes when this bug doesn't happen, that would likely give us the cause of the bug.

Since you have rebooted and even reformatted and reinstalled we can assume that this likely isn't a simple memory issue. I'm also assuming a few things like the save file that it happens and doesn't happen is the same save file. I'm also assuming things like you tested this both connected and disconnected from the internet, with headphones on, headphones off, mute on, mute off, hdr on, hdr off, vrr on vrr off, ect.

Using the scientific method we would try to list and document any potential variables and test each one. In game things, like what time of day, if certain scenery is visible and specific location of testing will need to be defined as well. Also physical variables like the ambient temperature.

Thinking of what could cause this, just off the top of my head I would assume resolution or something within the game that scales up and down as the game is being played. Perhaps there is an overload of effects that is causing a queue on some of the resources causing popins specifically in the grass. Many games have a foliage setting that can be adjusted and can have major performance impacts. Perhaps they simply have the foliage up one level too high for the average PS5 in their settings behind the scenes because perhaps their dev kit could handle it but some PS5s cannot. Have you tried playing on a 1080p or 1440p monitor to see if the issues persist? Perhaps this would offload resources enough from the console in order to prevent the error. That isn't a fix but if we could verify that fixed the issue then we could present this to Sony and CDPR for further review. Sorry I'm late joining this and hope to see it be resolved.
Click to expand...
and I need to stress it again, it never appears on some consoles, some PS5 I mean, my other friend has played 150 hours, and I played and watched also him play, it is like perfect game . Also every PS5 console that has grass bug has sky flicker in Toussaint. It is double bug I can say, if you have no flickering of sky in DLC Toussaint you do not have grass bug, if you have flickering of the sky, then grass bug will be there too.
 
I played through the Ultimate Edition on PC after the 'final' patches had come out.

Bugs were frequent and included:

horse physics, trail tracking, mount/dismount frequently not working;
hit detection during combat it three or more enemies not working;
Geralt not leaving fight mode after all enemies were killed, making interacting with the environment impossible;
Geralt falling through the ground geometry;
Geralt getting stuck on some piece of the floor requiring a reset;
some graphics not loading during a scene transition;
the battle music staying on after the enemies were killed;
physics and animations going completely haywire while swimming;
not being able to enter dialogue with NPCs;
in general very inconsistent input lag making the DLC boss fights very annoying in particular.

I sure there were more, but you get my point. It is a very ambitious, expansive, and bloated Euro-Jank game. It's actually amazing that it loads at all considering the c2013 Nvidia features its optimized for.

I still like the game a lot and beat it twice, but it ain't a 10/10 on the playability front.
 
vitopursuer said:
ps4 version after patch 4.00 has serious performance issues I can confirm it because I have ps4 aside of ps5, but except that ps4 version is good old version, pretty playable despite the performance issues or for some unplayable because they are too spoilt by constant stable fps, which is normal these days, I am the one insane and ubnormal lol, because I played games on 17-20 fps in my younger years, I had really weak pc, so console issues like drops to 25 fps do not bother me so much, graphical issues like grass popping out all over right in front of your eyes and changing every few seconds - that's the issue, that is what breaks immersion unbearably
Click to expand...

Yeah, I remember when I was younger playing games at sub 30, and just getting used to higher as tech improved. Pop-in I also just remember so much during the 360 gen with Unreal 3, or Dragon's Dogma on 360 where a tree in front of me was stuck on it's 2d billboard LOD, and I had to wait like 6-8 seconds for it to load in the proper model.

I'm just at the point where since graphics are stagnating, I definitely think games should just target 60, and focus on keeping things as stable as possible. Knock whatever down to get there, lower detail on assets if it means less pop-in, etc.
 
vitopursuer said:
and I need to stress it again, it never appears on some consoles, some PS5 I mean, my other friend has played 150 hours, and I played and watched also him play, it is like perfect game . Also every PS5 console that has grass bug has sky flicker in Toussaint. It is double bug I can say, if you have no flickering of sky in DLC Toussaint you do not have grass bug, if you have flickering of the sky, then grass bug will be there too.
Click to expand...
Such a curiosity. Thanks for the explanation.

I will try to check my launch PS5, I am wondering if the manufacturing date or manufacturing location of the consoles has any correlation to the issue.

It would not be a fix but perhaps if we were able to determine that only newer serial numbers had the issue or perhaps only units made with a certain parts vendor then the issue could be identified. IIRC there was an early revision that reduced the weight of the heat sink quite a bit. Perhaps only a single revision is immune to the issue or vice versa.

If we could notate the s/n of each unit tested and keep a list of all units that work perfectly and all units that do not work perfectly we could send them to sony and they could determine the cause.

Based on what you say I don't think CDPR is the bad guy, because their development hardware probably plays the game properly. Granted it should be caught in testing but perhaps their testbed is bad. ie perhaps all their PS5s they use for testing are in a batch without the issue. If that is the case the logic would lead one to believe that earlier PS5 hardware may be immune to the issue(when CDPR bought their PS5 testing array) and that newer units only may experience the issue. Have you noticed any correlation on those PS5s that do work, as far as their manufacturing date? Are they older units? Have you seen any slim PS5 that doesn't have the issue? Curious this would not be identified by cdpr in testing. That is a clue. There also may be separate manufacturing locations and the issue is exclusive to a certain location or certain vendor. Stranger things have happened.
 
Last edited:
vitopursuer said:
I am afraid I got 2 reports of bug being on ps5 pro as well, so I don't know, either those people just liers or it happens on PS5 pro too but maybe rarer? so far on youtube videos of W3 on PS5 I watched I did not noticed any popping but it could be a coincidence
Click to expand...
I am the OP, I do think these people are confused about it. It doesn't happen on PS5 Pro, on moment to moment gameplay. It can happen when you first load the game for like 2 seconds.

I know about the bug to a fault, the Ps5 Pro gets rid of it automatically.

From watching the Cerny talk, Id guess it has something to do with how the console processes shaders, which is pretty different to regular PS5, but this theory has a fault - some PS5s base dont appear to have the bug.

I didnt play this game for 3 and a half years after buying it launch. I am lucky the Pro fixes It. If I get my hands on the base PS5 I will compare them again. If you want to play this without the bug - PC, XSX, PRO or lucky PS5.
 
Zacfoldor said:
Such a curiosity. Thanks for the explanation.

I will try to check my launch PS5, I am wondering if the manufacturing date or manufacturing location of the consoles has any correlation to the issue.

It would not be a fix but perhaps if we were able to determine that only newer serial numbers had the issue or perhaps only units made with a certain parts vendor then the issue could be identified. IIRC there was an early revision that reduced the weight of the heat sink quite a bit. Perhaps only a single revision is immune to the issue or vice versa.

If we could notate the s/n of each unit tested and keep a list of all units that work perfectly and all units that do not work perfectly we could send them to sony and they could determine the cause.

Based on what you say I don't think CDPR is the bad guy, because their development hardware probably plays the game properly. Granted it should be caught in testing but perhaps their testbed is bad. ie perhaps all their PS5s they use for testing are in a batch without the issue. If that is the case the logic would lead one to believe that earlier PS5 hardware may be immune to the issue(when CDPR bought their PS5 testing array) and that newer units only may experience the issue. Have you noticed any correlation on those PS5s that do work, as far as their manufacturing date? Are they older units? Have you seen any slim PS5 that doesn't have the issue? Curious this would not be identified by cdpr in testing. That is a clue. There also may be separate manufacturing locations and the issue is exclusive to a certain location or certain vendor. Stranger things have happened.
Click to expand...
you see, funny thing is that I am in Ukraine, I have Ukrainian version of PS5, my frind is from US, his version has the same bug, other guy I found screaming proven me he has no bug during the stream and that he never noticed it. my other friend is from Czech republic, one revision is latest, 3rd, my friends revision with bug is 1st revision, my czech republican friend is in 2nd revision, so I I can say on 1st and 3rd revision bug exist, the other guy from russia I just found online said he changed 3 PS5 and they had a bug, dozen of videos on youtube from random people, I cannot say what revision they had but half of them had bug and other half did not. It is all maximum confusing. I could not find any link between bug or non bug console. And streatmer guy I mentioned earlier had 1st revision and no bug. SO you cannot say that only 2nd revision is bugless. It is total madness and confusion, but I sometimes check on here and also on comments on my other videos to see if people maybe found any link to the bug or any solution, even one time solution that works only one time, but none so far, and I have no idea what is next step to do to try to figure to figure out what is going on with us unlucky people.
 
SkyHighTrees said:
I am the OP, I do think these people are confused about it. It doesn't happen on PS5 Pro, on moment to moment gameplay. It can happen when you first load the game for like 2 seconds.

I know about the bug to a fault, the Ps5 Pro gets rid of it automatically.

From watching the Cerny talk, Id guess it has something to do with how the console processes shaders, which is pretty different to regular PS5, but this theory has a fault - some PS5s base dont appear to have the bug.

I didnt play this game for 3 and a half years after buying it launch. I am lucky the Pro fixes It. If I get my hands on the base PS5 I will compare them again. If you want to play this without the bug - PC, XSX, PRO or lucky PS5.
Click to expand...
I had my doubt about it too bro, that these people might be confused, since I never found any gameplay with bug on any PS5 pro videos online, and I also asked one person to tell me specifically and there was not response after that, so I think it might be confusion. I would gladly get PS5 pro, but for now it would cost me almost 500 dollars to exchange ps5 to ps5 pro, so I wait for now.
 
Durin said:
Yeah, I remember when I was younger playing games at sub 30, and just getting used to higher as tech improved. Pop-in I also just remember so much during the 360 gen with Unreal 3, or Dragon's Dogma on 360 where a tree in front of me was stuck on it's 2d billboard LOD, and I had to wait like 6-8 seconds for it to load in the proper model.

I'm just at the point where since graphics are stagnating, I definitely think games should just target 60, and focus on keeping things as stable as possible. Knock whatever down to get there, lower detail on assets if it means less pop-in, etc.
Click to expand...
now check this, madness of ps4 pro version launched on ps5, it supposed to have 4k checkerboard with normal draw distance of ps4 but only higher resolution, but you get ultra low draw distance that is not even present on minumal settings on PC, while it was not the case on ps4 pro before the 4.0 patch. There is some really big mess in CDPR to ruin ps4 pro version on ps5 and ruin 50% of ps5 experience with grass bug and flickering sky bug in Toissant
 
Dorago said:
I played through the Ultimate Edition on PC after the 'final' patches had come out.

Bugs were frequent and included:

horse physics, trail tracking, mount/dismount frequently not working;
hit detection during combat it three or more enemies not working;
Geralt not leaving fight mode after all enemies were killed, making interacting with the environment impossible;
Geralt falling through the ground geometry;
Geralt getting stuck on some piece of the floor requiring a reset;
some graphics not loading during a scene transition;
the battle music staying on after the enemies were killed;
physics and animations going completely haywire while swimming;
not being able to enter dialogue with NPCs;
in general very inconsistent input lag making the DLC boss fights very annoying in particular.

I sure there were more, but you get my point. It is a very ambitious, expansive, and bloated Euro-Jank game. It's actually amazing that it loads at all considering the c2013 Nvidia features its optimized for.

I still like the game a lot and beat it twice, but it ain't a 10/10 on the playability front.
Click to expand...
smh, my god, some of theses fucking issues existed at launch of this game.
 
vitopursuer said:
now check this, madness of ps4 pro version launched on ps5, it supposed to have 4k checkerboard with normal draw distance of ps4 but only higher resolution, but you get ultra low draw distance that is not even present on minumal settings on PC, while it was not the case on ps4 pro before the 4.0 patch. There is some really big mess in CDPR to ruin ps4 pro version on ps5 and ruin 50% of ps5 experience with grass bug and flickering sky bug in Toissant
Click to expand...
Good eye. I played Witcher 3 at 1080p because of this Draw distance bug back then on PS4.

It was awful
 
for anyone who cares, if you have a bug and a minute of your time, you can leave a comment under DF video about witcher 3 PS5/Xbox - asking to review grass bug that is happening on about half of PS5. Just for anyone who cares



I think if fairly enough people do it, it might enable DF to make a video about bug and then chance is really huge that the bug will be fixed
 
You must log in or register to reply here.

Similar threads

Why is nobody talk about the portables war?
2 3
102
4K
GigaBowser replied
Tom Warren: Starfield PS5 port was originally dropping with the first expansion - Halo Switch Port might not include all games
Rumor  2
57
3K
Pop replied
Why is frame time such a mess on PC?
32
912
forsakkenSoul replied
Digital Foundry: Indiana Jones and the Great Circle - PS5/PS5 Pro Tech Review - Excellent Game, Decent Port
2 3 4
187
6K
Mibu no ookami replied
FFXV is such a hot mess (spoilers)
2 3
112
3K
Calverz replied
Top Bottom