Xbox one s color 10 bit issues.

On the xbox one s I play destiny and when I choose color 10bit in the options I get screen shudder but its smooth on 8bit. I have a samsung ks9000 tv that supports 10 bit so was wondering if its the game itself that does not support 10bit? If so I wonder
if they will bring out an auto option as a choice because changing that value for each game will become annoying lol. I play in game mode on the tv too.

:)

 

Samsung HDR tv

Dashes mean that the sampling for those color schemes are not available. The zeros are equivalent of checkmarks, that in this color scheme, sampling is available. And with UHD Color setting turned on, the 10-bit and 12-bit sampling for color depths YCbCr
4:2:2 and YCbCr 4:2:0 are available. Xbox One S supports all of the color depths. And 10-bit sampling is the equivalent of HDR10. So as long as you turn UHD Color on the TV, you will get HDR color support with this TV set.

 

Xbox one S with Panasonic DX780 no HDR

I have the same issue, but with a LG 55UB8500. It has UHD Deep Color, I get 4k resolution, and 10 bit color but the Xbox One S will not allow HDR. It says here on xbox.com under the troubleshooting that UHD Deep Color is one of the many other names for HDR,
yet it doesn't work. Could this be a firmware issue on the xbox?

 

Hey StevenDraven! If you would like to see this idea implemented, I would suggest posting to our
Feedback site so the right people see it. Thanks!

 

Hi StevenDraven,

I have the same issue with my Samsung KS9090 + Xbox One S. When I play Destiny I notice screen flickering in the character screen- and only when I choose 4K+10Bit color. All the other games and HDR Blu Rays are running fine in 4K and HDR, except Destiny.

 

Hi,

In addition I tried 3 different HDMI 2.0a capable cables (includes the original one). The result is the same. A couple of days ago my KS9090 has got the firmware 1151.1. Nothing helps.

 

Hi, sorry I made a typing error: the correct firmware is 1125.1

 

Hi jaddowj,

This thread is a bit old, and it looks like the OP has their answer for this issue, I would suggest following Mister Cizl's
feedback suggestion above and using the 8bit option until Microsoft pushes out an update for this.