Hi, I love this software, however, it runs very poorly on my main (4k) monitor. Like 15 fps even with a rtx 5080. And the entire screen is locked to the framerate of Hotscreen. I've tried using it on my second monitor (1440p) but it detects the screen as 4480x2520 instead so the censors are misaligned.

Logs:

Hotscreen using profile : default

Hotscreen Overlay starting at Max FPS : 999

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.22621.0

CPU : 13th Gen Intel(R) Core(TM) i7-13700KF, Cores : 16, Threads : 24, Max clock : 3400 MHz

Using video adapter : NVIDIA GeForce RTX 5080 from NVIDIA type DiscreteGpu

Driver infos : d3d12 version 12_0 api 12_0

Adapter 0 NVIDIA GeForce RTX 5080

Screen Rect 0 : Rect { X = 0, Y = 0, Width = 3840, Height = 2160, Top = 0, Bottom = 2160, Left = 0, Right = 3840, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 3840, Height = 2160 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 3840, Y = 2160 } } Orientation : 1

Screen Rect 1 : Rect { X = 6720, Y = 1097, Width = 4480, Height = 2520, Top = 1097, Bottom = 3617, Left = 6720, Right = 11200, Location = Point { X = 6720, Y = 1097 }, Size = Size { Width = 4480, Height = 2520 }, TopLeft = Point { X = 6720, Y = 1097 }, BottomRight = Point { X = 11200, Y = 3617 } } Orientation : 1

Adapter 1 NVIDIA GeForce RTX 5080

Adapter 2 Microsoft Basic Render Driver

Starting Screen Recorder

Initializing Windows10Capture using Video card 0 and monitor 0

Hotscreen version : Windows - Full version - v0.8

Max FPS of Overlay set to 999

Frame Latency of screen set to 1

Windows10Capture initiated on : 3840x2160

Max FPS Record start at 999

MaxFPSRecord at 999

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 999

Use double Detection start at True

Update time of eyes detection start at 0,1

Setting MaxFPSDetection at 999

Setting detectOnlyArea at 0.36328125;0.26620370149612;0.26692706346512;0.4375

Setting detectOnlyArea at 0.0;0.0;1.0;1.0

Setting useDoubleDetection at 0

Setting useDoubleDetection at 1

Max FPS of Overlay set to 1

Max FPS of Overlay set to 999

MaxFPSRecord at 999

Setting MaxFPSDetection at 999

MaxFPSRecord at 1

Max FPS of Overlay set to 999

MaxFPSRecord at 999

Setting MaxFPSDetection at 999

Setting MaxFPSDetection at 1

Setting usePreciseEyesDetection at 1

Max FPS of Overlay set to 999

MaxFPSRecord at 999

Setting MaxFPSDetection at 999

Setting usePreciseEyesDetection at 0

Pausing screen recording

Recording is too slow. Stopping screen latency.

Max FPS of Overlay set to 1

Max FPS of Overlay set to 999

MaxFPSRecord at 999

Initializing Windows10Capture using Video card 0 and monitor 1

Windows10Capture initiated on : 2560x1440

Resuming screen recording

Setting MaxFPSDetection at 999

Initializing Windows10Capture using Video card 0 and monitor 0

Windows10Capture initiated on : 3840x2160

Initializing Windows10Capture using Video card 0 and monitor 1

Windows10Capture initiated on : 2560x1440

Setting detectionDevice at 1

Setting useDoubleDetection at 0

Setting useDoubleDetection at 1

Setting modelName at ./models/hs-real-anime-y11n-640-fp32.onnx

Setting modelName at ./models/hs-real-anime-y11n-640-fp16.onnx

Not a bug but a suggestion, an option for a fade away or delay for hiding an effect. Would help for when detection isnt quite perfect, so if it stops detecting, it will way the delay value before uncensoring that region of the screen, unless a detection is nearby in which it will move to there. Not sure how feasible this would be. 

I'm not really sure how to explain this bug but when starting hotscreen sometimes the window becomes completely invisible.  It will show up in alt+tab and on the task bar but clicking on it does nothing and the same with alt-tab. Trying to use WIN+arrow keys doesn't bring it back. The overlay still functions and stays above most things but the main window can't be brought to focus . I'm not sure how to replicate it. Sometimes it just fixes itself when I launch it from a different monitor and other times I have to delete my .save file. I only came across this while repeatedly closing and relaunching the application because I was trying to make a powershell watcher to make it so the app relaunches if closed, if that gives you a lead. 

I also had the remember last used screen and prevent the overlay from being minimized settings toggled

This is a log from when the bug was happening. I closed it manually. 

Hotscreen using profile : default

Hotscreen Overlay starting at Max FPS : 30

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.19045.0

CPU : Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, Cores : 8, Threads : 16, Max clock : 3600 MHz

Using video adapter : NVIDIA GeForce RTX 2070 SUPER from NVIDIA type DiscreteGpu

Driver infos : d3d12 version 12_0 api 12_0

Adapter 0 NVIDIA GeForce RTX 2070 SUPER

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

Screen Rect 1 : Rect { X = 1920, Y = 96, Width = 1920, Height = 1080, Top = 96, Bottom = 1176, Left = 1920, Right = 3840, Location = Point { X = 1920, Y = 96 }, Size = Size { Width = 1920, Height = 1080 }, TopLeft = Point { X = 1920, Y = 96 }, BottomRight = Point { X = 3840, Y = 1176 } } Orientation : 1

Adapter 1 Microsoft Basic Render Driver

Starting Screen Recorder

Initializing DXGI using Video card 0 and monitor 1

DXGI initiated with a resolution of 1920 x 1080

Max FPS Record start at 10

Hotscreen version : Windows - Full version - v0.8

Max FPS of Overlay set to 30

Frame Latency of screen set to 0

Loading mod scene : ./CUSTOM_DATA/Built-in mods/level_up_increase_lock_timer.mod.tscn

Loading mod scene : ./CUSTOM_DATA/Built-in mods/select_fps_preset_when_locked.mod.tscn

MaxFPSRecord at 10

Avx is supported.

Detection starting using model : ./models/hs-real-y11n-320-fp16.onnx

Detection starting using eye model : ./models/eyes-detection-01.onnx

Detection starting using device : 0

Max FPS Detection start at 10

Use double Detection start at False

Update time of eyes detection start at 0.1

Setting MaxFPSDetection at 10

Closing...

Screen recorder thread ends correctly.