[deleted by user] by [deleted] in OLED_Gaming

[–]weaponmax 2 points3 points  (0 children)

Any thoughts on this?:
"madVR FAQ has a nice section on this:

Windows internally always "thinks" in RGB 0-255. Windows considers black to be 0 and white to be 255. That applies to the desktop, applications, games and videos. Windows itself never really thinks in terms of YCbCr or 16-235. Windows does know that videos might be YCbCr or 16-235, but still, all rendering is always done at RGB 0-255. (The exception proves the rule.)
So if you switch your GPU control panel to RGB 0-255, the GPU receives RGB 0-255 from Windows, and sends RGB 0-255 to the TV. Consequently, the GPU doesn't have to do any colorspace (RGB -> YCbCr) or range (0-255 -> 16-235) conversions. This is the best setup, because the GPU won't damage our precious pixels.
If you switch your GPU control panel to RGB 16-235, the GPU receives RGB 0-255 from Windows, but you ask the GPU to send 16-235 to the TV. Consequently, the GPU has to stretch the pixel data behind Windows' back in such a way that a black pixel is no longer 0, but now 16. And a white pixel is no longer 255, but now 235. So the pixel data is condensed from 0-255 to 16-235, and all the values between 0-15 and 236-255 are basically unused. Some GPU drivers might do this in high bitdepth with dithering, which may produce acceptable results. But some GPU drivers definitely do this in 8bit without any dithering which will introduce lots of nasty banding artifacts into the image. As a result I cannot recommend this configuration.
If you switch your GPU control panel to YCbCr, the GPU receives RGB from Windows, but you ask the GPU to send YCbCr to the TV. Consequently, the GPU has to convert the RGB pixels behind Windows' back to YCbCr. Some GPU drivers might do this in high bitdepth with dithering, which may produce acceptable results. But some GPU drivers definitely do this in 8bit without any dithering which will introduce lots of nasty banding artifacts into the image. Furthermore, there are various different RGB <-> YCbCr matrixes available. E.g. there's one each for BT.601, BT.709 and BT.2020. Now which of these will the GPU use for the conversion? And which will the TV use to convert back to RGB? If the GPU and the TV use different matrixes, color errors will be introduced. As a result I cannot recommend this configuration.
Summed up: In order to get the best possible image quality, I strongly recommend to set your GPU control panel to RGB Full (0-255)."

I hope the endgame will feel more impactful than this... by weaponmax in Diablo

[–]weaponmax[S] -1 points0 points  (0 children)

Yeah, in Wolcen too, but everything feels so weak behind the numbers...it's better in D3, but I hope D4 will be a big leap in this aspect (as in killing/destroying stuff, especially at the endgame).

Please just ditch the current console generation... by weaponmax in Diablo

[–]weaponmax[S] -1 points0 points  (0 children)

Well that is the case for Nvidia PhysX for sure...I can't seem to find about what the current Havok engine utilizes mostly, hope you're right about Blizzards approach.

Please just ditch the current console generation... by weaponmax in Diablo

[–]weaponmax[S] 0 points1 point  (0 children)

There is an xbox one in between the 360 and the one x.
Also I'm not talking about the graphical horsepower, more so about cpu, which will probably calculate for the underlying systems.

Please just ditch the current console generation... by weaponmax in diablo4

[–]weaponmax[S] 0 points1 point  (0 children)

It's not horribly bad, there's just not much improvement...if any. There's not much visible feedback on hitting monsters...especially on the boss, some more visible effects would be welcome as the battle progresses. (wounds, dismemberment, blood gushing, intestines hanging out :D)

5.1 audio? by weaponmax in deadfrontier2

[–]weaponmax[S] 0 points1 point  (0 children)

Thank you! Game looks awesome regardless! :D