Series X Pixelated Visual Artifacting FSR 2.1 | DRS

[Maxedracer]

Good morning all,

Quick update. Nothing too eventful sadly but Support did get back in touch with me and said that the only thing they can share is that they are still collecting data on the issue.

 

[FritoSandwitch]

Has anyone that may have filed a bug for this issue actually had any response from the Dev team? I did get one initially but was a long time ago and have no idea if they are still looking into it.

I got a response back in 12/21/2022 for this issue and nothing since. It said they are looking into it.

 

[SigilFey]

Yup. Not all problems can be fixed. Unless the source of the issue can be located, there's not a lot that can be done about them. In other cases, the solution to one bug would knowingly break something far more serious.

For the graphical artifacting issue, it may actually be up to AMD to work on FSR via the console updates. There may not be anything that CDPR can do to affect it.

As stated, if you want to send a follow-up, feel free. Especially if you're noticing any difference in the behavior, let the devs know. (Not better or worse, necessarily -- just any sort of different manifestation of the bug.)

 

[FritoSandwitch]

Yup. Not all problems can be fixed. Unless the source of the issue can be located, there's not a lot that can be done about them. In other cases, the solution to one bug would knowingly break something far more serious.

For the graphical artifacting issue, it may actually be up to AMD to work on FSR via the console updates. There may not be anything that CDPR can do to affect it.

As stated, if you want to send a follow-up, feel free. Especially if you're noticing any difference in the behavior, let the devs know. (Not better or worse, necessarily -- just any sort of different manifestation of the bug.)

It doesn't effect the PS5 version and as far as I know PS5 and Xbox series S/X are basically the same tech in different boxes.

 

[SigilFey]

It doesn't effect the PS5 version and as far as I know PS5 and Xbox series S/X are basically the same tech in different boxes.

Ha! -- -- not even slightly. Back in the 1980s and '90s, consoles were pretty standardized world-wide. Hardware, software, and firmware were almost universal. Nowadays, depending on the region in which your console is produced, it will have the same specs as the rest, but the hardware and software inside can be completely different. It all depends on which local manufacturers and marketplaces can provide which components.

Thus, modern day consoles can suffer from almost the same disparity of issues as any PC. That's why you're seeing the pixelization issue...and the other 20 million+ players on that same "XBOX Series X" or "Playstation 5" system are not.

The fact of the matter for this particular bug is that graphics processing happens in real-time. Hence, if the problem were somehow in the game's code, then ALL players on that system would be seeing exactly the same artifacting problem in exactly the same way. Since it's a relatively extreme minority that are reporting it, it's clearly not the game. It's something between the game, the drivers, the APIs, and the OS on that particular build of said console(s).

My recommendation is simply to document what you can and send it in to CDPR Support. Sometimes, the fix is simple. Most likely...it's not.

 

[mrpattyswag]

Ha! -- -- not even slightly. Back in the 1980s and '90s, consoles were pretty standardized world-wide. Hardware, software, and firmware were almost universal. Nowadays, depending on the region in which your console is produced, it will have the same specs as the rest, but the hardware and software inside can be completely different. It all depends on which local manufacturers and marketplaces can provide which components.

Thus, modern day consoles can suffer from almost the same disparity of issues as any PC. That's why you're seeing the pixelization issue...and the other 20 million+ players on that same "XBOX Series X" or "Playstation 5" system are not.

The fact of the matter for this particular bug is that graphics processing happens in real-time. Hence, if the problem were somehow in the game's code, then ALL players on that system would be seeing exactly the same artifacting problem in exactly the same way. Since it's a relatively extreme minority that are reporting it, it's clearly not the game. It's something between the game, the drivers, the APIs, and the OS on that particular build of said console(s).

My recommendation is simply to document what you can and send it in to CDPR Support. Sometimes, the fix is simple. Most likely...it's not

That really sucks. If I can’t play this game like everyone else then why would I want to play it at all? It’s like I and a group of others got the walmart version of the XSX while everyone else (20+million people) can play without visual breaking bugs like this one. At this point, if this isn’t fixed before the game’s live service is over, I’m going to buy a high-end PC and get the game there, cause like this is very stupid imo. It’s frustrating to want to play a game you really love and be instantly railed by a bug like this and all just because of something as stupid as my Xbox’s hardware and software is different than more than half the player count. Unbelievably stupid.

 

[SigilFey]

That really sucks. If I can’t play this game like everyone else then why would I want to play it at all? It’s like I and a group of others got the walmart version of the XSX while everyone else (20+million people) can play without visual breaking bugs like this one. At this point, if this isn’t fixed before the game’s live service is over, I’m going to buy a high-end PC and get the game there, cause like this is very stupid imo. It’s frustrating to want to play a game you really love and be instantly railed by a bug like this and all just because of something as stupid as my Xbox’s hardware and software is different than more than half the player count. Unbelievably stupid.

How would you suggest Microsoft or Sony cover the demand for consoles in different regions of the world, then? Say no? That kills business. Only ship tiny quantities of the product when available? That kills business. Magically make hardware manufacturers increase their production to cover the massive, new demand? That's impossible.

So -- Microsoft / Sony hire on new manufacturers, in that region of the world, and ensure that they can meet the specs of the console. They try to keep things as uniform as possible...but that's not going to be 100% possible because there are different components being used. They can get really close, but not perfectly identical. That would require perfectly identical hardware.

This sort of industry is (like most everything in life) vastly more complicated than people want to give it credit for. However, that doesn't change the simple reality that if things get big, then there will be more moving parts. If there are more moving parts, then more things can and will go wrong. If we want to keep things small, then people just won't have video game consoles, and they'll have to do something else with their time, because supplies will always be more limited.

In short: nothing's perfect. It happened. Now, the issue exists. Regardless of how "stupid" it is, it's not going to fix itself. The only thing to do is try to identify key details about the issue that will let the devs figure out what's causing it. If they can't re-create it, there's nothing that can be done.

 

[mrpattyswag]

How would you suggest Microsoft or Sony cover the demand for consoles in different regions of the world, then? Say no? That kills business. Only ship tiny quantities of the product when available? That kills business. Magically make hardware manufacturers increase their production to cover the massive, new demand? That's impossible.

So -- Microsoft / Sony hire on new manufacturers, in that region of the world, and ensure that they can meet the specs of the console. They try to keep things as uniform as possible...but that's not going to be 100% possible because there are different components being used. They can get really close, but not perfectly identical. That would require perfectly identical hardware.

This sort of industry is (like most everything in life) vastly more complicated than people want to give it credit for. However, that doesn't change the simple reality that if things get big, then there will be more moving parts. If there are more moving parts, then more things can and will go wrong. If we want to keep things small, then people just won't have video game consoles, and they'll have to do something else with their time, because supplies will always be more limited.

In short: nothing's perfect. It happened. Now, the issue exists. Regardless of how "stupid" it is, it's not going to fix itself. The only thing to do is try to identify key details about the issue that will let the devs figure out what's causing it. If they can't re-create it, there's nothing that can be done.

Well, like I said. If this issue doesn’t somehow get fixed I’ll have to find a way to fix it for myself. Whether that means building a high-end PC, or miraculously finding an xbox series x console that won’t give me this issue. Let’s see what happens….

 

[SigilFey]

Well, like I said. If this issue doesn’t somehow get fixed I’ll have to find a way to fix it for myself. Whether that means building a high-end PC, or miraculously finding an xbox series x console that won’t give me this issue. Let’s see what happens….

Being a "high-end PC" owner, and having built my own "high-end PCs" since the 1990s -- I don't recommend anyone get into "high-end PC" gaming as a "solution" for anything. If you do decide to swap to PC, think of it as investing in a customized sports car. It's expensive, very fun, and you will definitely see performance...but you will also spend a lot of time working on your car. PCs will introduce endless waves of tweaking. You'll encounter many, many more issues compared to consoles, and you will spend much more time learning how to fix them. While they can normally all be fixed or worked around, you'll work for it.

Plus, it won't save anyone from situations like you're describing. Weird, exclusive issues like this can still pop up on PC, too. In fact, it will be more common on PC.

In the end, there are just some things that go wrong that will take time to sort out. Nothing that anyone can do will make that better or faster. It's just the nature of huge, sprawling, game code.

 

[FritoSandwitch]

Ha! -- -- not even slightly. Back in the 1980s and '90s, consoles were pretty standardized world-wide. Hardware, software, and firmware were almost universal. Nowadays, depending on the region in which your console is produced, it will have the same specs as the rest, but the hardware and software inside can be completely different. It all depends on which local manufacturers and marketplaces can provide which components.

Thus, modern day consoles can suffer from almost the same disparity of issues as any PC. That's why you're seeing the pixelization issue...and the other 20 million+ players on that same "XBOX Series X" or "Playstation 5" system are not.

The fact of the matter for this particular bug is that graphics processing happens in real-time. Hence, if the problem were somehow in the game's code, then ALL players on that system would be seeing exactly the same artifacting problem in exactly the same way. Since it's a relatively extreme minority that are reporting it, it's clearly not the game. It's something between the game, the drivers, the APIs, and the OS on that particular build of said console(s).

My recommendation is simply to document what you can and send it in to CDPR Support. Sometimes, the fix is simple. Most likely...it's not.

Digital foundry tested it. It only effects all Xbox Series systems and not PS5 systems so I don't know if your trying to say that are Xbox,s are defective but their not. Not everyone that plays cyberpunk goes to forums and reddit to complain about stuff like this. So just because you don't see a lot of people complaining doesn't mean it's not happening.

 

[Notserious80]

Digital foundry tested it. It only effects all Xbox Series systems and not PS5 systems so I don't know if your trying to say that are Xbox,s are defective but their not. Not everyone that plays cyberpunk goes to forums and reddit to complain about stuff like this. So just because you don't see a lot of people complaining doesn't mean it's not happening.

I would guess if its a issue with the implementation it should happend to pretty much everyone. FSR should be universal across plattforms unless you need a way diffrent way of implementing it on consoles vs PC. Im no expert tho so and its kinda hard to get a feel for it without seeing it happend. the fotage seems to indicate some issue with how its rendered tho, especially the gun flashes in that video is very odd.

 

[FritoSandwitch]

I would guess if its a issue with the implementation it should happend to pretty much everyone. FSR should be universal across plattforms unless you need a way diffrent way of implementing it on consoles vs PC. Im no expert tho so and its kinda hard to get a feel for it without seeing it happend. the fotage seems to indicate some issue with how its rendered tho, especially the gun flashes in that video is very odd.

I just don't like the admins suggesting that it's a hardware issue it's not Wise going around telling people their is something rong with their expensive system.

 

[SigilFey]

Digital foundry tested it. It only effects all Xbox Series systems and not PS5 systems so I don't know if your trying to say that are Xbox,s are defective but their not. Not everyone that plays cyberpunk goes to forums and reddit to complain about stuff like this. So just because you don't see a lot of people complaining doesn't mean it's not happening.

I specifically acknowledged that it's happening. Where did you get the idea that I said it's not happening?

I'm also well aware of the other social media outlets. What many people may not realize is that even if 10,000 people making a complaint about something, represents around 1% of the playerbase. That's not a lot to go on, as there are literally millions of people on Xbox and Playstation that to not suffer from the issue. How do we account for that?

Identifying "that" a problem exists is not even beginning to identify what's causing it and how it might be rectified. In order to correct the issue, the bug needs to be re-created reliably on the developers' end. Hence, posting "me too" accomplishes exactly nothing. What's needed are specifics:

• make and model of the console
• version and potentially version history.
• specific steps to re-create the issue on your end.
• include a save file.
• if possible, test the bug on a brand new playthrough.
• as updates are released, try to identify changes with the issue (for example, new areas in which it occurs, frequency of occurrences, different sorts of artifacting, etc.)

It could even be down to the way certain console versions are communicating with certain televisions, monitors, or other displays, potential firmware variations in different regions, other components or peripherals plugged in for streaming or such, even the physical wires being used to connect the console to the display.

Data. As I stated, this is most likely not going to be an easy one to track down. It may even be fixed in some future update, and we'll never know why.

 

[Lu_131]

I have the same problem. Xbox Series X. So annoying.. reported it months ago and got no response yet.
CDPR what kind of info do you need from us for this!?

 

[Loewe1983]

Yes, it is. Devs answers me and I send them a clip where you can see the issue. The respond me that they want to take a look into it. But there is no information in the patch notes so I believe we have to wait until the release of FSR 3.

 

[ragent23]

I can confirm that this issue is still present after the 2.0 update on the Xbox Series X. I've tried the game in both performance and ray tracing mode, enabled/disabled all of the visual toggles, enabled/disabled 120hz, enabled/disabled VRR, I even cleared my Xbox cache and reinstalled the game. The issue remains.

The visual issues were enough for me to give up and get the game on the PS5 and I can confirm that the PS5 does not have this pixelated artifacting issue.

Side note, the visual issues on the Xbox Series X are most prominent in highly populated areas or when driving around the city in my experience. There is one particular troublesome area where Viktor is and post 2.0 update there are various visual bugs that occur in the alleyway (there is a person taking flash pictures and steam is coming up from the sewer) that are not present at all on the PS5.

 

[Loewe1983]

I exported the frames. After rotating the viewing direction, some assets "disappear" for exactly one frame (pay attention to the window on the right and the smoke). Then they appear again. I've already contacted support, but nothing seems to have happened with 2.0.

 

[Lu_131]

I can confirm that this issue is still present after the 2.0 update on the Xbox Series X. I've tried the game in both performance and ray tracing mode, enabled/disabled all of the visual toggles, enabled/disabled 120hz, enabled/disabled VRR, I even cleared my Xbox cache and reinstalled the game. The issue remains.

The visual issues were enough for me to give up and get the game on the PS5 and I can confirm that the PS5 does not have this pixelated artifacting issue.

Side note, the visual issues on the Xbox Series X are most prominent in highly populated areas or when driving around the city in my experience. There is one particular troublesome area where Viktor is and post 2.0 update there are various visual bugs that occur in the alleyway (there is a person taking flash pictures and steam is coming up from the sewer) that are not present at all on the PS5.

This problem seems even stronger after 2.0.. i also thought about getting a PS5 (again) only because of this ugly annoying bug...

 

[Maxedracer]

Yes, it sadly is still happening with the latest update. I think it is fairly clear as to what is happening here and why the PS5 version may not be affected or noticeably affected. It's more prominent when driving and heavily populated areas as these are the areas that are causing massive swings in DRS (Dynamic Resolution). Tom Morgan very briefly mentioned this issue in one of his videos where I believe he referred to it as "fizzle".

When the resolution drops on Series X due to DRS, FSR 2.1 is having to re-adjust. I believe that normally this process should not be anywhere near as noticeable as it is in Cyberpunk on Xbox but for some reason it is extremely intrusive. The PS5 version is most likely better in this regard because either due to a lower base resolution, the PS5 version just being more performant or slightly different settings such as crowd density etc. (if they are still different) it is able to maintain a more consistent resolution profile where DRS is not needing to kick in as much. That is just my theory, it could also be due to DX12 as I know that Xbox also shares this issue with the PC version if you use FSR with DRS turned on. Like myself, I can only suggest that everyone contact Digital Foundry in the hope that they can bring some awareness to this issue. PC exampe

 

[Loewe1983]

Yes, it sadly is still happening with the latest update. I think it is fairly clear as to what is happening here and why the PS5 version may not be affected or noticeably affected. It's more prominent when driving and heavily populated areas as these are the areas that are causing massive swings in DRS (Dynamic Resolution). Tom Morgan very briefly mentioned this issue in one of his videos where I believe he referred to it as "fizzle".

When the resolution drops on Series X due to DRS, FSR 2.1 is having to re-adjust. I believe that normally this process should not be anywhere near as noticeable as it is in Cyberpunk on Xbox but for some reason it is extremely intrusive. The PS5 version is most likely better in this regard because either due to a lower base resolution, the PS5 version just being more performant or slightly different settings such as crowd density etc. (if they are still different) it is able to maintain a more consistent resolution profile where DRS is not needing to kick in as much. That is just my theory, it could also be due to DX12 as I know that Xbox also shares this issue with the PC version if you use FSR with DRS turned on. Like myself, I can only suggest that everyone contact Digital Foundry in the hope that they can bring some awareness to this issue. PC exampe

That's the reason why I never noticed it in closed areas like buildings... Good explanation. Thanks for this!