When using DXGI and adding a Screen Latency larger than zero, my screen gamma seems to be thrown out of whack. Funnily enough I can't capture it on a screenshot because it corrects it. It works with BITMAP recording method just fine.
Hotscreen using profile : default Hotscreen Overlay starting at Max FPS : 60 Translations added from ./CUSTOM_DATA/translations.csv — languages : ["en", "zh", "es", "fr", "ar", "ru", "pt", "ko", "ja", "de"] Using saved language code : en Windows version : Microsoft Windows NT 10.0.26200.0 CPU : Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz, Cores : 6, Threads : 12, Max clock : 2904 MHz Using video adapter : AMD Radeon RX 7600 XT from AMD type DiscreteGpu Driver infos : d3d12 version 12_0 api 12_0 Adapter 0 AMD Radeon RX 7600 XT Screen Rect 0 : Rect { X = 0, Y = 0, Width = 1920, Height = 1080, Top = 0, Bottom = 1080, Left = 0, Right = 1920, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 1920, Height = 1080 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 1920, Y = 1080 } } Orientation : 1 Adapter 1 AMD Radeon RX 7600 XT Adapter 2 Microsoft Basic Render Driver Starting Screen Recorder Initializing DXGI using Video card 0 and monitor 0 DXGI initiated with a resolution of 1920 x 1080 Max FPS Record start at 60 Hotscreen version : Windows - Full version - v0.7 Max FPS of Overlay set to 60 Frame Latency of screen set to 1 MaxFPSRecord at 60 Avx is supported. Detection starting using model : ./models/hs-real-anime-y11n-640-fp16.onnx Detection starting using eye model : ./models/eyes-detection-01.onnx Detection starting using device : 0 Max FPS Detection start at 60 Use double Detection start at True Update time of eyes detection start at 0,1 Setting MaxFPSDetection at 60 Setting usePreciseEyesDetection at 1