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.
Hotscreen may contain content you must be 18+ to view.
The creator of this page has specified that it contains mature themes and content. Please enter your birthdate to verify you are 18 or older:
Hi there. I tried the demo, and the program seems to have trouble when displaying the censored output on multimonitor setups. It detects the images on screen 2 or 3 but then displays the censored frame on screen 1. 'Screen latency to correct delay' counter above 0 on an ultrawide completely covers it in an unintentional glitchy filter. The program also will not gather input from my ultrawide. Clicking the 'Detect small bodyparts on wide screen' button will also crash HotScreen. So much potential, can't wait to see how HotScreen evolves.
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 = -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
Screen Rect 2 : 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
Adapter 1 NVIDIA GeForce RTX 4070 Ti
Adapter 2 Microsoft Basic Render Driver
No corresponding godot screen found for (-1, 0)
No corresponding godot screen found for (-1, 0)
No corresponding godot screen found for (-1, 0)
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
Avx2 is supported
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
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 wrote in another thread about this but might as well post it here. I'm using the paid version.
It doesn't seem to remember which filters should be on or off upon restart.
The option "Detect small bodyparts on wide screen" seems to crash the app.
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : AMD Ryzen 7 7800X3D 8-Core Processor, Cores : 8, Threads : 16, Max clock : 4201 MHz
Adapter 0 NVIDIA GeForce RTX 3080
Screen Rect 0 : Rect { X = 0, Y = 0, Width = 3840, Height = 1600, Top = 0, Bottom = 1600, Left = 0, Right = 3840, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 3840, Height = 1600 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 3840, Y = 1600 } } Orientation : 1
Adapter 1 AMD Radeon(TM) Graphics
Adapter 2 Microsoft Basic Render Driver
Starting Screen Recorder
Max FPS of Overlay set to 999
Frame Latency of screen set to 5
DXGI initiated with a resolution of 3840 x 1600
DXGI using Video card 0 and monitor 0
Avx2 is supported
Max FPS Record start at 999
MaxFPSRecord at 999
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 999
Use double Detection start at False
MaxFPSDetection at 999
Now usePreciseEyesDetection is at 1
Now useDoubleDetection is at 1
Hello! I am really excited to try this out. Unfortunately, mine crashes about ten seconds after opening, even if I don't do anything after opening it (I am using the demo version). Here are my logs:
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
Max FPS of Overlay set to 60
Frame Latency of screen set to 0
DXGI initiated with a resolution of 1920 x 1200
DXGI using Video card 0 and monitor 0
Avx2 is supported
Max FPS Record start at 60
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
Thank you for your hard work!
For me the program is always crasing if i turn on the small body parth thing. I think my monitor too big (2560x1080) i tryed my small monitor (1440x900) but when i switch the screen is glitched. This glitch is always have, if turn on the small body parth if not. I use the paid version and the updated.
Windows version : Microsoft Windows NT 10.0.19045.0
CPU : AMD Ryzen 5 3600X 6-Core Processor, Cores : 6, Threads : 12, Max clock : 3800 MHz
Adapter 0 AMD Radeon RX 6700 XT
Screen Rect 0 : Rect { X = 0, Y = 0, Width = 2560, Height = 1080, Top = 0, Bottom = 1080, Left = 0, Right = 2560, Location = Point { X = 0, Y = 0 }, Size = Size { Width = 2560, Height = 1080 }, TopLeft = Point { X = 0, Y = 0 }, BottomRight = Point { X = 2560, Y = 1080 } } Orientation : 1
Screen Rect 1 : Rect { X = -1440, Y = 188, Width = 1440, Height = 900, Top = 188, Bottom = 1088, Left = -1440, Right = 0, Location = Point { X = -1440, Y = 188 }, Size = Size { Width = 1440, Height = 900 }, TopLeft = Point { X = -1440, Y = 188 }, BottomRight = Point { X = 0, Y = 1088 } } Orientation : 1
Adapter 1 AMD Radeon RX 6700 XT
Adapter 2 Microsoft Basic Render Driver
Starting Screen Recorder
Max FPS of Overlay set to 59
Frame Latency of screen set to 1
DXGI initiated with a resolution of 2560 x 1080
DXGI using Video card 0 and monitor 0
Max FPS Record start at 59
MaxFPSRecord at 59
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 59
Use double Detection start at False
MaxFPSDetection at 59
DXGI initiated with a resolution of 1440 x 900
DXGI using Video card 0 and monitor 1
Max FPS of Overlay set to 60
MaxFPSRecord at 30
MaxFPSDetection at 30
Max FPS of Overlay set to 60
MaxFPSRecord at 60
MaxFPSDetection at 60
DXGI initiated with a resolution of 2560 x 1080
DXGI using Video card 0 and monitor 0
Now useDoubleDetection is at 1
It seems that my laptop doesn't support this software. What should I do?
（The detector can't get the data of this screen. Try to use another screen in the Performance tab.）and（The detector doesn't seem to work on your PC. Try to start it on another GPU or screen.）
Windows version : Microsoft Windows NT 10.0.19045.0
CPU : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, Cores : 4, Threads : 8, Max clock : 2419 MHz
Adapter 0 NVIDIA GeForce MX350
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 Intel(R) Iris(R) Xe Graphics
Adapter 2 Microsoft Basic Render Driver
Starting Screen Recorder
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Max FPS of Overlay set to 60
Frame Latency of screen set to 0
Retrying Desktop Duplication 1
Detection starting using model : ./model_fp16.onnx
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Max FPS Detection start at 60
Use double Detection start at False
MaxFPSDetection at 60
Now usePreciseEyesDetection is at 1
Retrying Desktop Duplication 2
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Frame Latency of screen set to 1
Retrying Desktop Duplication 3
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Retrying Desktop Duplication 4
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Retrying Desktop Duplication 5
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Retrying Desktop Duplication 6
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 2
Retrying Desktop Duplication 7
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Frame Latency of screen set to 1
Retrying Desktop Duplication 8
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Retrying Desktop Duplication 9
Failure of DuplicateOutput : 0x887A0004 (HRESULT: [0x887A0004], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_UNSUPPORTED/Unsupported], Message: 指定的设备接口或功能级别在此系统上不受支持。
)
Desktop Duplication seems not working. Restart the application.
Max FPS Record start at 60
MaxFPSRecord at 60
Closing...
No data in lastFrameData for the detection.
Screen recorder thread ends correctly.
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.
Hi, liking this project a lot, hope you are doing well.
I'm using the paid version 0.2 Having problem with ultra wide screens and noticed several problems
1. When I click Detect small bodyparts on wide screen (any resolution above including 2560 1440) it will crash
2. The Filters doesn't seem to work on Ultra wide(3440 1440), tried tuning down resolution works out, (1920 1080 worked best, anything above could cause some filters to be dislocated) .
3. Screen latency to correct delay above 0 will break HDR (making screen super bright and that will cause filters to stop working)
4. Setting Screen Latency to correct delay above 0 frame at 3440 1440 resolution will make the screen glitch and tear (not a HDR issue)
I've also found out that this program works way better with HDR off (not sure if this is just me being slow to figure but you might include in an announcement for other people) .
Logs:
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : Intel(R) Core(TM) i9-14900KF, Cores : 24, Threads : 32, Max clock : 3200 MHz
Adapter 0 NVIDIA GeForce RTX 4090
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 = -1080, Y = -127, Width = 1080, Height = 1920, Top = -127, Bottom = 1793, Left = -1080, Right = 0, Location = Point { X = -1080, Y = -127 }, Size = Size { Width = 1080, Height = 1920 }, TopLeft = Point { X = -1080, Y = -127 }, BottomRight = Point { X = 0, Y = 1793 } } Orientation : 4
Adapter 1 Microsoft Basic Render Driver
Starting Screen Recorder
Max FPS of Overlay set to 164
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 164
MaxFPSRecord at 164
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 164
Use double Detection start at False
MaxFPSDetection at 164
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 0
Max FPS Record start at 164
MaxFPSRecord at 164
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 164
Use double Detection start at False
MaxFPSDetection at 164
Now usePreciseEyesDetection is at 1
Now usePreciseEyesDetection is at 1
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 2
Frame Latency of screen set to 3
Frame Latency of screen set to 4
Frame Latency of screen set to 5
Frame Latency of screen set to 4
Frame Latency of screen set to 3
Frame Latency of screen set to 2
Frame Latency of screen set to 1
Frame Latency of screen set to 0
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 2
Frame Latency of screen set to 3
Frame Latency of screen set to 2
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 2
Frame Latency of screen set to 3
Frame Latency of screen set to 4
Frame Latency of screen set to 5
Frame Latency of screen set to 4
Frame Latency of screen set to 3
Frame Latency of screen set to 2
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 3440 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 3440 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Frame Latency of screen set to 1
Frame Latency of screen set to 0
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 1920 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Error during DXGI capture : HRESULT: [0x887A0026], Module: [SharpDX.DXGI], ApiCode: [DXGI_ERROR_ACCESS_LOST/AccessLost], Message: The keyed mutex was abandoned.
DXGI initiated with a resolution of 1920 x 1080
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
DXGI initiated with a resolution of 2560 x 1440
DXGI using Video card 0 and monitor 0
Bad format from duplicated desktop :R16G16B16A16_Float
Closing...
Screen recorder thread ends correctly.
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 option doesn't really work for me, it just flickers trying to draw over the overlay (i think it doesn't disable the overlay while its active? so its duplicating it). It also seems to break with the screen buffer option set to at least 1 frame, and starts copying the window bar at the top downward until it fills the whole screen
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.
I'm running version 0.3. I'm trying to make Hotscreen use screen 3 by default, at startup. However, it always defaults to screen 1 at startup. If I change the setting manually it works perfectly fine on screen 3. If I then close the application and start it again it goes back to screen 1 by itself. Below my logfile.
Hotscreen Overlay starting at Max FPS : 60
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : AMD Ryzen 5 7600 6-Core Processor, Cores : 6, Threads : 12, Max clock : 3801 MHz
Adapter 0 AMD Radeon RX 7800 XT
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 = -7560, Y = 0, Width = 1800, Height = 2880, Top = 0, Bottom = 2880, Left = -7560, Right = -5760, Location = Point { X = -7560, Y = 0 }, Size = Size { Width = 1800, Height = 2880 }, TopLeft = Point { X = -7560, Y = 0 }, BottomRight = Point { X = -5760, Y = 2880 } } Orientation : 4
Screen Rect 2 : Rect { X = -5760, Y = 0, Width = 3840, Height = 2160, Top = 0, Bottom = 2160, Left = -5760, Right = -1920, Location = Point { X = -5760, Y = 0 }, Size = Size { Width = 3840, Height = 2160 }, TopLeft = Point { X = -5760, Y = 0 }, BottomRight = Point { X = -1920, Y = 2160 } } Orientation : 1
Adapter 1 AMD Radeon(TM) Graphics
Adapter 2 Microsoft Basic Render Driver
Starting Screen Recorder
DXGI initiated with a resolution of 3840 x 2160
DXGI using Video card 0 and monitor 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 1
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
Hello! Unfortunately, even with the new 0.3 version (on both the demo and the paid version) I get the same error:
Can't open file ./hotscreen.save during file_to_dict_params.
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
Hotscreen version : Windows - Demo version - v0.3
Max FPS of Overlay set to 60
Frame Latency of screen set to 0
DXGI initiated with a resolution of 1920 x 1200
DXGI using Video card 0 and monitor 0
Max FPS Record start at 60
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
The program functions normally for a few seconds, freezes for another few seconds, and then closes automatically. This error persists even when I set my computer to use the program in high performance mode, and I have been experiencing the same error since version 0.1, although the line "Can't open file ./hotscreen.save during file_to_dict_params." is new to this version. I should also mention that the censor works just fine, and then the effect freezes and disappears after a few seconds, much like the program itself.
Thank you for your hard work!
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.
Every time the program launches, the filter does not "remember" the pixels size setting that is set. Very noticeable if you have what should be a high strength pixel setting on, launch it and then move the setting you do have "saved" a tiny bit to the left or right where it will actually adjust to the level u actually set.
Also a feature request, but it would be nice to be able to move the filters around in priority (or numerically set a priority), since it wasn't made obvious when setting them up that they overwrite each other. My text filter has a bunch written in it and configured but setting up a pixel filter later down the line, I saw that it will completely block the text filter i had already established. You can work around it by just deleting the filter and adding it again through your saved custom filters however
opens not responsive then closes version 0.4 but its the same on 0.3
Can't open file ./hotscreen.save during file_to_dict_params.
Hotscreen Overlay starting at Max FPS : 64
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : AMD Ryzen 3 5300U with Radeon Graphics, Cores : 4, Threads : 8, Max clock : 2600 MHz
Adapter 0 Microsoft Basic Render Driver
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 Microsoft Basic Render Driver
Starting Screen Recorder
DXGI initiated with a resolution of 1920 x 1080
DXGI using Video card 0 and monitor 0
Max FPS Record start at 64
Hotscreen version : Windows - Demo version - v0.4
Max FPS of Overlay set to 64
Frame Latency of screen set to 0
MaxFPSRecord at 64
It seems that my computer can run version 0.3, but not version 0.4.
Hotscreen Overlay starting at Max FPS : 60
Windows version : Microsoft Windows NT 6.2.9200.0
CPU : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz, Cores : 4, Threads : 8, Max clock : 2419 MHz
Adapter 0 NVIDIA GeForce MX350
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 Intel(R) Iris(R) Xe Graphics
Adapter 2 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 - Full 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 False
MaxFPSDetection at 60
Closing...
Closing...
Screen recorder thread ends correctly.
My computer can run version 0.3, but not version 0.4 .
Hotscreen Overlay starting at Max FPS : 288
Windows version : Microsoft Windows NT 10.0.26100.0
CPU : AMD Ryzen 5 5600 6-Core Processor, Cores : 6, Threads : 12, Max clock : 3501 MHz
Adapter 0 AMD Radeon(TM) Graphics
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 Microsoft Basic Render Driver
Starting Screen Recorder
DXGI initiated with a resolution of 1920 x 1080
DXGI using Video card 0 and monitor 0
Max FPS Record start at 288
Hotscreen version : Windows - Full version - v0.4
Max FPS of Overlay set to 288
Frame Latency of screen set to 0
MaxFPSRecord at 288
Detection starting using model : ./model_fp16.onnx
Max FPS Detection start at 288
Use double Detection start at False
MaxFPSDetection at 288
Switching recording method from 0 to 1
BitmapCapture initiated with a resolution of 1920 x 1080 at the location 0, 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.
crashes a lot more after update when editing filters; would suggest having a "pause" feature to pause the overlay and tracking so you can edit filters, especially if you plan on introducing more and more filter functions (which is good!)
one crash was repeatable 90% of the time, where on an image filter selection, unselecting an image so it goes from 1 total selected to 0 would result in a crash almost every time so i had to juggle them around (also why is there a set of default images selected making me need to unselect them every time?), which was extremely frustrating given the program has no clear way to save your progress; for anyone having trouble, i noticed closing the program manually saved your edits most of the time, so periodically doing after a couple changes would help a ton. Not sure if it's the case but I noticed the crashing more with image and text filters but it crashes with other filter setups too.
the logs didn't seem helpful, but i do have some event viewer errors:
Application: hotscreen.exe
CoreCLR Version: 8.0.1224.60305
.NET Version: 8.0.12
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at Godot.NativeCalls.godot_icall_2_838(IntPtr, IntPtr, Godot.NativeInterop.godot_string_name, System.ReadOnlySpan`1<Godot.Variant>, Godot.NativeInterop.godot_string_name)
at BoxesDetector._Process(Double)
at Godot.Node.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name ByRef, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant ByRef)
at BoxesDetector.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name ByRef, Godot.NativeInterop.NativeVariantPtrArgs, Godot.NativeInterop.godot_variant ByRef)
at Godot.Bridge.CSharpInstanceBridge.Call(IntPtr, Godot.NativeInterop.godot_string_name*, Godot.NativeInterop.godot_variant**, Int32, Godot.NativeInterop.godot_variant_call_error*, Godot.NativeInterop.godot_variant*)
----------------------------------------------
Application: hotscreen.exe
CoreCLR Version: 8.0.1224.60305
.NET Version: 8.0.12
Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FF9C41A2654 (0x00007FF9C4130000) with exit code 0x80131506.
-------------------------------------------
Application: hotscreen.exe
CoreCLR Version: 8.0.1224.60305
.NET Version: 8.0.12
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException: Godot Object not registered. (Parameter 'weakReferenceToSelf')
at Godot.GodotObject.Dispose(Boolean disposing)
at Godot.GodotObject.Finalize()
------------------------------------------
so basically a lot of errors reading storage (ie for custom resource selection), net runtime errors, and kernalbase.dll and coreclr.dll were also referenced a lototherwise when not editing filters and running it for a video normally it works fine most of the time, still the occasional crash but more random and not tied to any specific action
the update is great otherwise though! the filter collection is a neat feature, but i wish there was a one click option to disable all the collection's filters (can remove the collection and add it back later but with the saving thing i sometimes don't trust that if i've made edits)
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.