[Gereral1]

FSE can be left on if you use NVidia driver 378.92 (nothing newer). This allows 10bit/12bit. With FSE enabled it also conforms with 3D MVC so now no user intervention is needed for any format selected. Everything is automated now. Nvidia should be updating newer drivers to also dynamic switch Windows native HDR on start and stop. MS may also update 10bit support for windowed mode. So, FSE or windowed - both will work.

Still going to code windows switch for custom presenter filter to pass 10bit hdr main 10 to intel amd. Guess nvidia is all good. Still going to finish this program for users who want to break out hdr and unlock there tv controls to add more color or contrast. This will help watching hdr material in high ambient backlight. Hdr suffers from this. Ill code it for all 3 and leave option to run pure hdr or xdr. 90 hrs and over 90 lines of code. Im making this program for my pc. If others want to use it thats great. If not thats fine too. My goal is to do hdr microsofts way using enhanced custom presenter filter to padd meta data rgb,luma, max adv nit, white point and the 2 set hdr modes. Xdr will eventually have hdr meta tags in xdr.cal and will use c++ to pass these values to hdr tv. No generic switch. Problem is my project is not compatible with madvr as im using only mircosofts hdr methods thru enhanced custom presenter filter. Madvr was great in software mode but my computer is 8 years old and I have to totally rely on polaris gpu. The green screen colors is a promising sign madshi is getting close. Xdr has a right click play with xdr feature to use outside kodi and still load xdr.cal values. Im just starting on coding hdr switch for all 3 gpus. I will release a simple turn on off beta to everyone then add it to xdr and finally release xdr2.0.0.0.
The code i was looking at sends out a request for compatible device then asks tv for its hdr abilities then windows sets the correct hdr mode. Each hdr tv is different.