Ok. That's weird.
Maybe try to put this save in the Hotscreen 0.3 folder. https://gofile.io/d/U11QCF It will force using the Compatible record method at startup.
Does it also crash if there is nothing to censor ?
I can refund you untill I find a way to fix this.
I replaced the save with the one you provided, and it was indeed using the other recording method, as evidenced by the log:
Hotscreen Overlay starting at Max FPS : 60
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : Intel(R) Core(TM) Ultra 7 155U, Cores : 12, Threads : 14, Max clock : 1700 MHz
Adapter 0 Intel(R) Graphics
Screen Rect 0 : Rect { X = 0, Y = 0, Width = 1920, Height = 1200, Top = 0, Bottom = 1200, Left = 0, Right = 1920, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 1920, Height = 1200 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 1920, Y = 1200 } } Orientation : 1
Adapter 1 Microsoft Basic Render Driver
Starting Screen Recorder
BitmapCapture initiated with a resolution of 1920 x 1200 at the location 0, 0
Max FPS Record start at 60
Hotscreen version : Windows - Full version - v0.3
Max FPS of Overlay set to 60
Frame Latency of screen set to 0
MaxFPSRecord at 60
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 60
Use double Detection start at False
MaxFPSDetection at 60
However, I still have the same crashing effect unfortunately. To answer your other question, it does also crash if there is nothing to censor. No worries about the refund! I want to be in on the ground floor of this haha. Thank you for your time!
Here is the save file for version 0.4 https://gofile.io/d/9eZmIh
However, be sure to update your graphics drivers as it was the solution for theguywhodidit.
