Hey I hope you are doing well! I was browsing lewd games on Steam like a degen and it occurred to me that Hotscreen would be awesome to have on Steam and would probably attract more attention. As far as I'm aware, there is a $100 fee to get a game on Steam, but I'm pretty sure that is the only cost. In any case, just thought it was worth considering. Cheers!
theguywhodidit
13
Posts
2
Topics
1
Following
A member registered Mar 12, 2025
Recent community posts
Hello there! Thank you very much for your work on this amazing program. I can't goon any other way now!
I was wondering if it would be possible to add filters that only activate around a specific trigger, like a blur trigger on a penis that only activates when a face is detected. I was also wondering if you could add the option for the app to send out notifications through Windows that remind you to edge and goon.
Thank you very much for your consideration. I can't say enough how incredible this software already is. Thank you for all your hard work.
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!
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!
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!
This is genuinely an incredible program! To my knowledge there exists no other real-time censoring software that works with videos in the browser, and I have been searching. Super excellent work, honestly.
After using the software for a little while, three things stuck out to me. The first is that the process of drawing new censored areas each update seems somewhat inefficient, in that it often seems unnecessary to draw new areas each update. Would it not be possible (and I say this as barely a programmer, so take my words with a grain of salt) to translate and scale the preexisting censored areas to new locations, particularly if the new area is not in much different of a spot than the previous area? I don't know if it would actually speed things up, but I figured I would throw it out there.
Secondly, could a false positive system be implemented for preexisting areas, as in could an area remain in a similar position (if we are talking about translating them rather than redrawing them; the case is even more pressing in the current redrawing model) for a set amount of time? That way, it could help to alleviate the flickering effect that currently happens when small body movements occur, or things otherwise obstruct certain body parts that are supposed to be censored. It may make censored areas linger for too long in the same screen positions, but I'd rather have that than body parts exposed when they shouldn't be. Just to reiterate, I believe that using translation rather than redrawing also helps greatly to correct this issue.
Lastly, although I think this is part of NudeNet, it seems like breasts and butts are not easily detected as such (even when clothed and with the "sexy" censoring turned on), unless they are shown head on, or without clothes or other obstructions, and even when nothing is in the way, butts are rarely registered correctly if they're not at an almost dead-on angle (i.e. they often are registered incorrectly if someone isn't bending over).
Again, excellent, excellent work. This is seriously already a game changer for me, and I couldn't be more excited to see where this goes in the future. I'd be happy to pay a chunk of change for a fully polished version of this product.
Thank you for your time and consideration!
P.S. Could we get a standard pixelation censor, pretty please?