Cyberpunk 2077 | Update 2.0 | FSR 2.1 / DRS Pixelation Artifacts | Xbox Series X

Checking out update 2.0 on Xbox Series X and PS5 and whether the FSR 2.1 issue is still present. Sadly the issue persists on Xbox and is still absent on the PS5 version. Oliver over at Digital Foundry has also mentioned this in his latest video where he states that there is a "significant" issue on Series consoles where sometimes the FSR implementation breaks and then re-resolves over the next few frames. His video referencing this can be found below.
• Cyberpunk 2077 Phantom...
As the issue is also present on PC when FSR and DRS are enabled but is not present on PS5, it may be something to do with DirectX 12 or possibly where the Xbox consoles are concerned, may be some sort of compatibility issue or bug with FSR when variable rate shading is enabled.
I have reached out to the developers over at the official forums a number of times as well as many others but the issue is still being looked into. I can confirm that the issue has been present on Xbox consoles since the initial introduction of FSR 2.1
If you are experiencing this and would like to report the issue in the hope that it may one day be resolved, please use the link below.
support.cdproj...
If you would like to add to the discussion please visit the link below.
forums.cdproje...
Please subscribe if you like our content: / @gamingletloose

[@gamingletloose]

Checking out update 2.0 on Xbox Series X and PS5 and whether the FSR 2.1 issue is still present. Sadly the issue persists on Xbox and is still absent on the PS5 version. Oliver over at Digital Foundry has also mentioned this in his latest video where he states that there is a "significant" issue on Series consoles where sometimes the FSR implementation breaks and then re-resolves over the next few frames. His video referencing this can be found below. kzbin.info/www/bejne/boa3hmNpidSii6ssi=uU2Y3x4z8jcwX-Al&t=262 As the issue is also present on PC when FSR and DRS are enabled but is not present on PS5, it may be something to do with DirectX 12 or possibly where the Xbox consoles are concerned, may be some sort of compatibility issue or bug with FSR when variable rate shading is enabled. I have reached out to the developers over at the official forums a number of times as well as many others but the issue is still being looked into. I can confirm that the issue has been present on Xbox consoles since the initial introduction of FSR 2.1 If you are experiencing this and would like to report the issue in the hope that it may one day be resolved, please use the link below. support.cdprojektred.com/en/cyberpunk/xbox/gameplay/issue/1742/i-want-to-report-a-visual-issue-2 If you would like to add to the discussion please visit the link below. forums.cdprojektred.com/index.php?threads/series-x-pixelated-noise-flashing-on-screen-fsr-2-1.11109590/#post-13521125 Please subscribe if you like our content: kzbin.info/door/Yb6thI1-6qAkOZ2prUoC1A

[@Vendigo_11]

Sadly this problem still exists , and I think it will never be fixed 😢

[@catzilla91]

Big disappointment that it's still present on the 2.1 update :c

[@MrPink-ul6co]

they did not fixed this at 2.11 patch.

[@raphaelhatake8706]

This error is so frustrating! And CDPR does nothing about it.... :/ I also don't understand why a lot more people don't complain about this!!!! I also tried on several Xbox consoles & several TVs.... And everywhere I had this problem!!! But it's definitely more noticeable on an OLED TV than an LCD/LED TV. This is probably due to the self-luminous pixels of an OLED TV. This makes the artifacts "glow" brighter.... I was so looking forward to the 2.0 & Phantom Liberty update because I assumed CDPR would fix the bug with this big update.... But NOTHING!!! :(

[@chadeverettpipkin]

You tried it on multiple series x? I've posted about this issue on reddit and a handful of people on series x swear they don't have it lol but it's in every video I've seen.

[@raphaelhatake8706]

@@chadeverettpipkin Yes, I have tested it on 3 different Series X consoles & on several TVs & monitors. (With & without HDR, with & without VRR) The result was the same everywhere, or the error was present. What I noticed, however, is that it is more noticeable on an OLED TV than on an LCD/LED TV... This is probably due to the OLED TV's self-luminous pixels...

[@chadeverettpipkin]

@@raphaelhatake8706 so you think it's safe to say every single series x has it and the people on reddit saying they don't just aren't seeing it even though it's there? I sit about 2 feet from a 2k 144hz IPS screen

[@raphaelhatake8706]

@@chadeverettpipkin I would say that every Xbox has this problem with Cyberpunk & suspect that some people just don't really notice it. A friend sat next to me & didn't notice the flickering, whereas I almost go crazy with the flickering. I thought I was imagining it.... I think it's similar to 30fps & 60fps... There are people who don't notice any difference and don't even notice the additional FPS. One of these people is my friend, who doesn't see the flickering either...

[@chadeverettpipkin]

@@raphaelhatake8706 yeah that makes a lot of sense. Not sure what to do. I hear it doesn't happen on ps5 but don't really want to buy a new console just for one fuckin game

[@vornamenachname5589]

i never heard about this issue in any gaming media. they should do their job better and don't let CDP get away with everything. i regret my purchase of this game for xbox so much. should have waited for GOTY-version for PS5.

[@valdis6014]

Hey ! I report this bug too ! It's like white points pop in, ect... Frustating.. So yeah, probably FSR bug. Hope it will be fix in 2.01 but CDPR not mentioned it..

[@kiloftugano2693]

Name car?

[@chadeverettpipkin]

How about now?

[@catzilla91]

After update still the same. It ruins immersion. I'm disappointed. Since idk almost year and a half it's the issue.

[@chadeverettpipkin]

@@catzilla91 lol wow fucking sad. They obv don't give a fuck about Xbox

[@elshowdelwendigopixeliento4345]

@@catzilla91 Maybe, it is a problem with DirectX.

[@pantonpg]

Is this fixed in 2.01 ?

[@bbttkk88]

Unfortunately, it seems not, although perhaps it is less visible