itch.io

Hello! Thank you as always for your continued development of Hotscreen, which is by far and away the best censoring tool out there. 

As I continue to work on more things within Hotscreen, the more I find myself having the need for logical operations (AND, NOR, NOT, etc.) and counters (e.g. if exposed breasts are detected five times for over a second each, implement a censor. I know this is possible with the level collection, but being able to reset a counter directly would be a nice level of control to have). Additionally, being able to reward certain behaviors (e.g. if both a penis and breasts are detected, show a filter with positive fast text) or discourage others (e.g. if penises are not detected, show a filter with negative fast text) would be very nice to have, and would likely not be too hard to implement, asssuming that Hotscreen is already keeping track of what body parts specifically are being detected at any one time.

Counters could also be used in combination with a logic gate. For example, you could set it up so that a person had to detect a minute of penises on their screen ten times, and a minute of mens' faces on their screen ten times before they could get reduced pixelation on breasts, almost like a way to condition someone overtime. Another instance could be that someone hasn't seen enough armpits, and so if the counter for armpit detections is below five (assuming they have to be on the screen for a second each time to count) and breasts are detected, you could set it to slightly unblur the breasts, and do it even more if a penis is detected as well. 

With these counters, it would be nice to have the ability to easily reset them, and to preform basic math operations with them (e.g. you must get your count to be greater than 10 of a combined viewing of armpits and tummies before you can view breasts). 

These are just some ideas that I've had floating around in my head, and I apologize if they are not the most comprehensible. I'd be curious to hear what others think about this as well!

Thank you very much for your continued work on Hotscreen!!

I'd love to see this become a reality! All the concepts you've talked about sound super fun and would hopefully reinforce gooning even deeper into our edged out minds!

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!

This is incredible. Thank you so much for your hard work!

loooool "I have become goon. The destroyer of minds".

I studied Japanese for a few years at university, although I haven't done much translation work. That being said, I'd love to try!

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.

You have to press enter after you've finished typing for the word list to update, which definitely had me confused at first as well.

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!

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!

Yep lool the anticipation is killing me!

Thank you very much for your thoughtful reply! 

I am incredibly excited to hear that you have a quicker version in the works!! I can't wait to get my hands on it!

Thank you also for making a pixelation filter!

Have a good rest of your day!

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?