existensmaximum
Member
I think it's the only PS5 game that I've had freezing on me regularly.
That's the thing... sometimes it does, other times it doesn't.
It's just an odd problem. Sent another ticket to CDPR support, but now with clips. I have no idea how this works or if the devs ever see it, but I know that if I was the lead graphics artist/engineer I would be disappointed to see this glitch ruining all my work. As Vick put it, it's an amazing looking game when it works, the modded textures + great HDR and vast draw distances are crazy, all at a great IQ. Hope they can fix it someday
Apparently, it's fixed when playing on the pro.still no solution?
I’ve been cross playing this on PC and PS5 recently and I’ve noticed no issues on my PS5. I do have a Pro but I can’t see how that would make a difference.still no solution?
Unrelated, but Death Stranding has vegetation pop in after the directors cut which is bizarre to me since the original on PS4/PC has a draw distance that feels like it absolutely shouldn't be possible.Yep, that's the reason why I haven't played the blood and wine extension where vegetation pop in is imo more visible. It's quite visible in Skellige too, not so much in Vellen.
I heard it's a ps5-only issue, that's really disappointing to see that they haven't, and will likely never, address it because it really ruins the immersion.
Its even more bizarre. PS5 Pro fixes it for some hardware reason, but with the PS5, select PS5s dont have this glitch.I’ve been cross playing this on PC and PS5 recently and I’ve noticed no issues on my PS5. I do have a Pro but I can’t see how that would make a difference.
You should buy Xbox Pro with Win 11 instead!Its even more bizarre. PS5 Pro fixes it for some hardware reason, but with the PS5, select PS5s dont have this glitch.
I has 2 base models, one launch and one from 2021, both exhibited this glitch. Some peoples base consoles just dont have this and I'm 100% sure about this.
And no, not playing the PS4 version on the PS5, not a dense person.
Its the most random bug I think Ive ever seen. But so so Glad that the PRO absolutely fixes this.
There is no problem. I just played PS5 version over the past few days and it's flawless. (OG launch console)still no solution?
Not trueOP is playing the PS4 version of The Witcher 3 on PS5, the PS5 version doesn't do this, only the PS4 version on the PS5.
Its even more bizarre. PS5 Pro fixes it for some hardware reason, but with the PS5, select PS5s dont have this glitch.
I has 2 base models, one launch and one from 2021, both exhibited this glitch. Some peoples base consoles just dont have this and I'm 100% sure about this.
And no, not playing the PS4 version on the PS5, not a dense person.
Its the most random bug I think Ive ever seen. But so so Glad that the PRO absolutely fixes this.
That's fine lol. At that point you can ignore it. On regular PS5 it was a miracle whenever it stopped doing that, lasted for 40 mins or so. Some people never had it thoughI'd say after playing the expansion for a good 10 hours that it's mostly fixed but not completely. It appears randomly from time to time in some areas, for a few seconds, and then nothing for an hour. That's really weird ^^
Its even more bizarre. PS5 Pro fixes it for some hardware reason, but with the PS5, select PS5s dont have this glitch.
I has 2 base models, one launch and one from 2021, both exhibited this glitch. Some peoples base consoles just dont have this and I'm 100% sure about this.
And no, not playing the PS4 version on the PS5, not a dense person.
Its the most random bug I think Ive ever seen. But so so Glad that the PRO absolutely fixes this.
there is like 40-50 thousand players on PC according to top games by player's count on steam, not counting gog, so I imagine on PS5 there would be like at least few thousand players. There is dozen of posts on reddit and also videos on youtube, but not crazy ammount of people to make this issue seen. I even went to DigitalFoundry discord channel, one of their manager had the issue too but did not care enough to even report it. But still, I do not feel like totally giving up and constantly checking if there are new people who experience the issue and there is more of them each time, so hope is not dying that it might get fixed.Even taking your claim as true at face value, chances are nobody gave a fuck.
It's a 2015 game and most people didn't play it on a PS5 anyway.
I highly doubt CDPR is going to do any further updates at this time, so for PS5 players the only way to fix it would be getting the Pro.there is like 40-50 thousand players on PC according to top games by player's count on steam, not counting gog, so I imagine on PS5 there would be like at least few thousand players. There is dozen of posts on reddit and also videos on youtube, but not crazy ammount of people to make this issue seen. I even went to DigitalFoundry discord channel, one of their manager had the issue too but did not care enough to even report it. But still, I do not feel like totally giving up and constantly checking if there are new people who experience the issue and there is more of them each time, so hope is not dying that it might get fixed.
but ps5 pro is terrible when it comes to performance/value/quality. The biggest issue for me is quality, you get ps5 pro, and you do not even get full 4k in witcher 3, which is weird, since Witcher 3 on ps5 had a dynamic 4k, which was around 1800p, dropping and raising depend on the scene. You cannot also get higher resolution in most games, because they run just basic resolution that was made either for ps5 or even ps4. It was worth getting ps5, but pro, it is just like blatant money waste, unless somebody have a lot of it. I'd get it myself if I had a nice job and lived in an economically developed country.I highly doubt CDPR is going to do any further updates at this time, so for PS5 players the only way to fix it would be getting the Pro.
you are just among those lucky people who does not have this bugPut about 30 hours into the PS5 version and encountered no bugs or glitches
you are just among those lucky people who does not have this bug
this shit still crazy, the most random bug ever imo.it is unlikely after 30 hours of play, I had it like from few hours of playing, I first played through Velen where it does not show itself so much really, but then started noticing more and more, googled it, and found out it is unfixable bug that happens only on some consoles and never happens on others
t
this shit still crazy, the most random bug ever imo.
the fact that some people don't have it on regular ps5s bewilder me.
fact is, want it fixed, buy the pro. it also has a significant boost in IQ and draw distance compared to XSX so it's the best console version. the draw distance is better on PS5 regular too but the bug hampers it
sorry, it isn't really draw distance. it's more about the extra grass draw-in that is present on PS5 and PC version. Seems like there's more grass in the PS and PC version, like it's "fuller" around the player.FYI that was a bug on Xbox that happened near launch for DF when moving saves from one console to the other. I recall John mentioning it in one of their Direct's after their video too.
It does not happen during normal plays and I think further patches fixed the bug even when transferring saves altogether.
DF's initial coverage:
Actual on SX:
sorry, it isn't really draw distance. it's more about the extra grass draw-in that is present on PS5 and PC version. Seems like there's more grass in the PS and PC version, like it's "fuller" around the player.
I've read about this somewhere, maybe DF or on the countless forums and subreddits I've visited trying to find a fix for the glitch present on the base PS5.
I've always thought it was this that caused the awful pop in and pop out on the playstation console but it isn't, it's just an odd bug present on 75% of the sony base consoles. For some really odd reason Pro almost fixes this fully so it's not a disadvantage anymore imo, it can actually look better this way. You're right tho the XSX draw distance problem was fixed early on
but the thing is having it work correctly is pretty rare. I have 2 PS5s and both show the glitchso as it turns out, the bug is totally absent on ps5 pro, so the what the hell is wrong with at least half of ps5 basic consoles? so then is it an evidence to blame half of the ps5 for having the bug or what is any logic in this insanity that is going on? I feel on the verse of buying ps5 pro but then when I start to think of it, and doing it only for one game - it start to sound like insanity. and at the same time I am totally confused why can't I play the game normally on basic console that still costs 500 dollars and is among those unlucky half or even more than half of consoles to have the stupid frigging bug. Curse either CDPR or Sony for it, who among them really to blame???
SkyHighTrees
Here's a quick and dirty from the starting of the game, don't have a later save on PS5 to check later areas, sorry.
Doesn't seem like that issue is happening on my game.
SkyHighTrees
Here's a quick and dirty from the starting of the game, don't have a later save on PS5 to check later areas, sorry.
Doesn't seem like that issue is happening on my game.
how many times did you try rebuilding data base? it did nothing for me, it never fixed the issue, not even one time. Buy ps5 pro that probabaly cost like 900 after all taxes for witcher 3? I wanted to do it myself, for me it cost even more, almost 1100 dollars, but I started to think it is a little bit insane, even leaned towards buying better graphics card to play on PC, but at the same time to buy Graphics card for one game only is not best idea either.Hey man, I thank you for the effort here!!!
Really appreciate this, but after dissecting your video to find it, I found it happening at 0:18, 0:30 and 0:40.
That pop-out is *not* intended, it doesn't happen on the XSX, PC and the odd PS5 that doesn't have the bug. Also PS5 Pro fixes 99% of this.
The intended LOD transition is not immediate, it happens with a smooth draw-in animation.
EDIT: you can look for Bojji's video in this thread, it shows PS5 gameplay without the bug. Also I could fix it after countless database resets, then it started happening again. It's something to do with the cache I think, but the weirdest part is how some PS5's don't have it, so that points towards differences between PS5s?
I don't care about this anymore after I saw how Pro fixes it, I will just buy the Pro to play this man
I can see the pop in as well in the moment of the game, it is going to get some much worse in some areas, especially in Toussant and Skellige
oh, that is ps4 pro verison working on ps5, and it is broken because of new gen patch broke draw distance for ps4 pro. Bascially when you install witcher 3 from ps4 on your ps5, and keep it resolution 4k, then it launches checkerboarded 4k ps4 pro version. If you set your resolution to 1080p, you get normal base ps4 draw distance. CDPR really messed up things, and just abandoned the game for playstation community in general. With a new patch, even on my old ps4 the game is having a lot of frame drops, so much more than before the next gen patch.Yeah there's some minor pop-in but that's also there on the Xbox version.
Though it's nothing like the example Bojji shared earlier in this topic where it's literally drawing grass 10 ft in front of gerry.
I played the game at 1080p on the Pro, the 4k cb was crap.oh, that is ps4 pro verison working on ps5, and it is broken because of new gen patch broke draw distance for ps4 pro. Bascially when you install witcher 3 from ps4 on your ps5, and keep it resolution 4k, then it launches checkerboarded 4k ps4 pro version. If you set your resolution to 1080p, you get normal base ps4 draw distance. CDPR really messed up things, and just abandoned the game for playstation community in general. With a new patch, even on my old ps4 the game is having a lot of frame drops, so much more than before the next gen patch.
I've barely finished it 5 times, who plays this crap right?It's that game nobody really plays but everyone feels they have to pretend it's the best game ever.
I finished it once on release... and that's more than enough
I've made a video about a similar problem almost 2 years ago, is this the same thing still not fixed?