- Joined
- May 22, 2015
- Messages
- 13,843 (3.95/day)
Processor | Intel i5-12600k |
---|---|
Motherboard | Asus H670 TUF |
Cooling | Arctic Freezer 34 |
Memory | 2x16GB DDR4 3600 G.Skill Ripjaws V |
Video Card(s) | EVGA GTX 1060 SC |
Storage | 500GB Samsung 970 EVO, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 2TB Crucial MX500 |
Display(s) | Dell U3219Q + HP ZR24w |
Case | Raijintek Thetis |
Audio Device(s) | Audioquest Dragonfly Red :D |
Power Supply | Seasonic 620W M12 |
Mouse | Logitech G502 Proteus Core |
Keyboard | G.Skill KM780R |
Software | Arch Linux + Win10 |
That was a limitation of HDMI that applied across the board: it didn't have enough bandwidth for both the signal and HDCP2.2 at the same time. Moron.nvidia, "the way its meant to be reduced"
they have done this before, when hdmi 2.0 was new, they would reduce to signal to 4:2:0 to push it to televisions/monitors, yes it works in 4k, but looks like crap