Series X Pixelated Visual Artifacting FSR 2.1 | DRS

+
I think FSR and the REDengine just don't get along very well. I've never used FSR myself, only seen it in action, and I do know that the image quality is noticeably lower than DLSS (...but the fact that it does what it does entirely through software is very cool. That's probably the future, in the end.)

I also notice that the type of artifacting that results is very similar to the way mail armor and the edges of plate armor would tend to "glitter" in TW3. The shaders used by the engine for specular mapping and glow mapping seem to want to get in there no matter how slightly. As I mentioned some years ago, it's like if there's even one pixel that it can draw to show a reflection, by golly, the engine is going to draw that dang pixel.

Hopefully, now that CDPR has included more direct support for FSR, things like that can be ironed out. Or at least be made less noticeable. Apparently, whatever is actually causing this is going to be an involved fix.
 
This has happened in avatar frontiers of Pandora too but Ubisoft quickly fixed it (I haven't seen any people talking about it either) so it's clear that fixing it is in fact possible.
The game didn't have this issue. I think it started with 1.6 or 2.0. can't remember which update. But yeah, they broke the game and they could fix it, but the issue is not mainstream or talked about enough for them to actually bother.

Already did 4 playthroughs. I think it's time to forget about it and move on
 
It broke when the added FSR 2.1 to consoles, except this doesn't happen on the PlayStation version. I had quite a bit of hope this may get resolved with this patch, but I also noticed that it may have got worse. I may be wrong but according to the patch notes, the new updates for FSR are only applying to the PC. Why wouldn't they take this opportunity to add it to the console versions as well? It may have fixed this problem with the Xbox version.
 
It broke when the added FSR 2.1 to consoles, except this doesn't happen on the PlayStation version. I had quite a bit of hope this may get resolved with this patch, but I also noticed that it may have got worse. I may be wrong but according to the patch notes, the new updates for FSR are only applying to the PC. Why wouldn't they take this opportunity to add it to the console versions as well? It may have fixed this problem with the Xbox version.
It's not as simple as, "Just put it here." It's also not a guarantee that just because it works well on one engine (Unreal, CryEngine, Creation Engine, Unity, etc.) that it's going to work the same way on REDengine. Engines, themselves, are different and complex in their own ways. Again, no idea what the actual circumstances are, but if the situation were simple and straightforward, there would no reason not to have incorporated it. There is clearly a more substantial challenge with it, somewhere in the process.
 
It seems that the New VRR mode is broken on the Xbox Series consoles compared to the PS5 and PS5 Pro just reinforcing the lack of care for the Xbox and the focus on the PlayStation when introducing these new features.
 
Not to mention there's a bug in the next gen version of the Witcher 3 that causes foliage draw distance to be way worse on the series x. The only way to "fix this" is to play the game on a completely different account.
There's clearly more care put in the playstation versiond
 
Not to mention there's a bug in the next gen version of the Witcher 3 that causes foliage draw distance to be way worse on the series x. The only way to "fix this" is to play the game on a completely different account.
There's clearly more care put in the playstation versiond
You're sure about that?
I'm on Series X and never saw a real issue with draw distance on TW3... On the other hand, there are many threads and posts here on the forum by people complainng that there is a draw distance issue on PS5, way worse than on Xbox :(

Edit : Or it's foliage/bushes pop in... But well... both version have their own issue :D
 
Yeah, they 100% don't give a crap about Xbox players for some reason.
I assure you, they care about it. The trouble is the issue may not be completely fixable by CDPR. Rendering techniques like super-sampling and dynamic downscaling are developed and updated by the GPU manufacturers (presently DLSS by Nvidia, XeSS by Intel, and FSR by AMD). Those need to be specifically configured to work with this or that engine within the confines of the resources available on a given platform during runtime.

I have no idea what the actual situation is with CP2077 and FSR on Xbox, but if there were a direct and simple fix, I'm sure it would have been introduced a long while ago. There's something in the way involving hardware, software, licensing and contracting, or a pleasant mixture of them all. It doesn't make any sense for a studio to have the ability to make their graphics cleaner and sharper and not implement it. If that's what's happening, it's because there's a larger and more complex problem.
 
They dis not fix this issue
Post automatically merged:

You know guys it's become some kind of twisted joke, every patch we wait that this problem will be solved and nothing new is happening. I regret that i bought xbox series x for this game.
It's very frustrating. I'm angry because after 2.3 the flying aerozep (the one with search lights) in Dogtown is missing. Either my game is bugged or we got the watered down steam deck version where they also removed flying cars and the aerozeps from the skies. For me that's what makes the immersion so good. Is the hovering aerozep in Dogtown missing for you as well?
 
Is the hovering aerozep in Dogtown missing for you as well?
Nope, I'm on Series X (performance mode) and flying vehicles and the "aerozeps" (the one in dogtown and those wandering around Night City) are there :)
Cyberpunk 2077-2025_07_23-13-03-45.jpgCyberpunk 2077-2025_07_23-13-13-38.jpg
 
Not to mention there's a bug in the next gen version of the Witcher 3 that causes foliage draw distance to be way worse on the series x. The only way to "fix this" is to play the game on a completely different account.
There's clearly more care put in the playstation versiond
Yes, this error occurs. I had it myself. The solution is simple. The error is caused by cross-save (from my observations). Simply delete all data and saves related to The Witcher 3 on the console drive. After restarting the game, LOD will return to normal.
 
Nope, I'm on Series X (performance mode) and flying vehicles and the "aerozeps" (the one in dogtown and those wandering around Night City) are there :)
View attachment 11419994View attachment 11419997
Thank you for confirming, that's good news to hear! My previous game saves must not be correlating with update 2.3 then.
I'll have to troubleshoot bug fixes i.e. completing a mission or restarting the game altogether with version 2.3.
I'm probably only 75% played through with my save and started my career after patch 2.2.
 
Thank you for confirming, that's good news to hear! My previous game saves must not be correlating with update 2.3 then.
I'll have to troubleshoot bug fixes i.e. completing a mission or restarting the game altogether with version 2.3.
I'm probably only 75% played through with my save and started my career after patch 2.2.
You're welcome ;)
A bit weird they're not there on your playthrough... Did you try to clear the cache just in case?
 
Let's keep the topic on the pixelated artifacting. If you'd like to discuss other issues, please add them to existing threads. If none exist, everyone can post new topics anywhere under Technical -- even if you have not passed the 10-post limit.
 
You're welcome ;)
A bit weird they're not there on your playthrough... Did you try to clear the cache just in case?
Tried clearing the cache, but the only thing that worked was going to an earlier game save. None of the saves from a particular date will load the flying cars/aerozeps for some reason. Maybe they'll reappear as I progress at some point, but not sure I want to chance it and may just sacrifice 4 hours of gameplay reverting back to the older save.
 
I assure you, they care about it. The trouble is the issue may not be completely fixable by CDPR. Rendering techniques like super-sampling and dynamic downscaling are developed and updated by the GPU manufacturers (presently DLSS by Nvidia, XeSS by Intel, and FSR by AMD). Those need to be specifically configured to work with this or that engine within the confines of the resources available on a given platform during runtime.

I have no idea what the actual situation is with CP2077 and FSR on Xbox, but if there were a direct and simple fix, I'm sure it would have been introduced a long while ago. There's something in the way involving hardware, software, licensing and contracting, or a pleasant mixture of them all. It doesn't make any sense for a studio to have the ability to make their graphics cleaner and sharper and not implement it. If that's what's happening, it's because there's a larger and more complex problem.
Or can they simply remove the FSR??? How about that? 😐🙄
 
Or can they simply remove the FSR??? How about that? 😐🙄
After all the demand to include it and get it working better, I doubt it. As it stands, FSR is not directly controllable, and it will definitely decrease performance if turned off. It may not even be possible for the Playstation to render the game at full resolution without crashing. (I don't know that, but it seems logical speculation, as there are other games that do offer the option to disable FSR on PS4 and PS5.)

What I think needs to happen is for consoles to give players more direct control over which techniques are used as system or game settings. Things are getting almost as complex as PCs in many regards. Just having a Graphical Settings page on a per-game basis with more options that can be manually altered by the player is probably going to be necessary, eventually.
 
CDPR has the ability to work with AMD and Microsoft Xbox to find out what is happening with FSR on the Xbox I'm not saying CDPR doesn't care about the Xbox version but between all the versions Xbox seems to be at the bottom of priority, I absolutely love this game & just want to play without these issues I don't feel that's unreasonable.
 
Like I've said before. The exact same issue happened on the avatar game but it for fixed fairly quickly after only a handful of users reported it. So no, it's definitely not impossible or even difficult to fix!
It's just not a mainstream issues that affects sales or their image so they're just ignoring it.
If it was a playstation issue, a lot more people would be talking about it and it would definitely get fixed in a matter of days.
 
Top Bottom