If you encounter a bug, please describe me the problem and paste the content of the file hotscreen_logs.txt. I will try to fix it for the next update.
Hi. I no longer have the issue of a censor appearing on one screen when intended for another. However, the program will still not work on my ultrawide monitor, and setting 'Screen latency to correct delay' counter above 0 for my ultrawide still completely covers my screen in a strange glitch pattern. Also, the 'Detect small bodyparts on wide screen' button still crashes Hotscreen.
Here are my logs:
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : 13th Gen Intel(R) Core(TM) i7-13700KF, Cores : 16, Threads : 24, Max clock : 3400 MHz
Adapter 0 NVIDIA GeForce RTX 4070 Ti
Screen Rect 0 : Rect { X = 0, Y = 0, Width = 3440, Height = 1440, Top = 0, Bottom = 1440, Left = 0, Right = 3440, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 3440, Height = 1440 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 3440, Y = 1440 } } Orientation : 1
Screen Rect 1 : Rect { X = 435, Y = -1440, Width = 2560, Height = 1440, Top = -1440, Bottom = 0, Left = 435, Right = 2995, Location = Point { X = 435, Y = -1440 }, Size = Size { Width = 2560, Height = 1440 }, TopLeft = Point { X = 435, Y = -1440 }, BottomRight = Point { X = 2995, Y = 0 } } Orientation : 1
Screen Rect 2 : Rect { X = -1080, Y = -280, Width = 1080, Height = 1920, Top = -280, Bottom = 1640, Left = -1080, Right = 0, Location = Point { X = -1080, Y = -280 }, Size = Size { Width = 1080, Height = 1920 }, TopLeft = Point { X = -1080, Y = -280 }, BottomRight = Point { X = 0, Y = 1640 } } Orientation : 2
Adapter 1 NVIDIA GeForce RTX 4070 Ti
Adapter 2 Microsoft Basic Render Driver
Starting Screen Recorder
Max FPS of Overlay set to 165
Frame Latency of screen set to 0
DXGI initiated with a resolution of 3440 x 1440
DXGI using Video card 0 and monitor 0
Max FPS Record start at 165
MaxFPSRecord at 165
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 165
Use double Detection start at False
MaxFPSDetection at 165
Now usePreciseEyesDetection is at 1
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 1
Closing...
Screen recorder thread ends correctly.
Thanks :3
I managed to reproduce and fix the "small bodyparts" crash. I will probably publish a small update next week.
Thank you for submitting your issue.
Can confirm that the issues are fixed in version 0.3.
Great job! Looking forward to future updates.
The monitor of laptops are directly connected to the integrated GPU so the code Hotscreen uses to get the screen data doesn't work. I have the same thing on my laptop. In a next update, I will create another way to get the screen data (probably slower but working for laptops).
What you can try now is launching Hotscreen with your integrated Intel GPU ! You can select that in the nvidia parameters, or even in the Windows settings : Graphics Settings.
Hey ! Thanks for your logs, it's very interesting since I can't test HDR myself.
In 0.3 Hotscreen don't allow HDR at all. You said "Screen latency to correct delay above 0 will break HDR" and I also suspect that even the detection doesn't work with HDR.
I will try to handle HDR in next updates. It's not hard but I can't be sure that it works when I publish it.
The recordable window is intended to be used only by your recording software. Once you created the recordable window (move it a bit out the way), open your recording software and start recording the recordable window. You can now click on the button Hide the window so it doesn't bother you.
If you want to know why it's like this : if the overlay was recordable, the boxes would flicker as the bodies would be detected then hidden by the overlay the next frame. So Hotscreen has to be "invisible" by screen recording softwares and create a duplicated recordable window when necessary.
Thank you for the comment. I forgot to make Hotscreen start on the screen which has focus. I will correct that in the next update.
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!
Update! Just updated my graphics drivers and now both recording methods are working great and there is no more crashing!! For anyone else having immediate crashes on their laptop, I recommend they try to update their graphics drivers! Thanks for your help!
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.
Indeed, having 0 images with stretched option was causing a crash. This will be fixed, thank you for the report.
The image filter is not empty by default to show new users how it works. You can save yourself a custom empty image filter to avoid uncheck them every time.
I will add a disable collection button.
0.3 works great, but 0.4 seemed to break something. Nothing shows up in the overlay and below is what happens when I try to take a screenshot. The only thing I had enabled was a single collection with the default color censor.
Here's the log but there isn't an error showing up:
Hotscreen Overlay starting at Max FPS : 60
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : AMD Ryzen 7 5700G with Radeon Graphics, Cores : 8, Threads : 16, Max clock : 3800 MHz
Adapter 0 AMD Radeon RX 6600 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(TM) Graphics
Adapter 2 AMD Radeon RX 6600 XT
Adapter 3 Microsoft Basic Render Driver
Starting Screen Recorder
BitmapCapture initiated with a resolution of 1920 x 1080 at the location 0, 0
Max FPS Record start at 60
Hotscreen version : Windows - Demo version - v0.4
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 True
MaxFPSDetection at 60
Now usePreciseEyesDetection is at 1
Now useDoubleDetection is at 0
Now usePreciseEyesDetection is at 0
Switching recording method from 1 to 0
DXGI initiated with a resolution of 1920 x 1080
DXGI using Video card 0 and monitor 0
Now useDoubleDetection is at 1
Closing...
Screen recorder thread ends correctly.
Did your PC freeze ? Hotscreen always let 1 pixel at the bottom of the screen to be able to click on the Hotscreen icon to close it.
Be sure to use the save file for version 0.4 https://gofile.io/d/9eZmIh
Also, be sure to have the graphics drivers updated.
Okay, I made some tinkering with drivers and some setting and I figured in armory crate/g helper if you choose gpu mode as the ultimate (which uses dgpu exclusively) fixes the problem. My guess is, in the standart mode system uses cpu as the main render option, in desktop and that causes dxgi not getting opened because it is not the gpu. İt is pretty easy to change the system mode with a restart, but maybe you can write some codes to activate the gpu manually.
Had the same issue. Between clicking the "Select position" button and pressing Enter, did you click somewhere? Try not clicking anywhere when moving your mouse, before pressing Enter. At least that's how I managed to make it work.