sexdemon wrote:Hello, first of all thanks for the awesome program.
Thanks to you all for giving it a try.
sexdemon wrote:I would like to add a few suggestions to add to the program:
Suggestions and feedback are always welcomed
sexdemon wrote:
1- Make failing to suck in time be able to add more sucks
2- Make making a noise add more sucks
3- Make not making a noise (noisy blowjob) add more sucks/time or both
Seems ok to me, thanks for the ideas. In fact the random time in the first program I released was an idea given by an user (and the random charachters were a Lizerd contribution).
sexdemon wrote:4- Make a variable sucking rate that you cant go to fast or to slow else you will add sucks or time or both.
Sorry, but my English is not good enough to understand that point.
Could you please explain a little what do you mean?
sexdemon wrote:5- Add a optional 3rd box for occasional forced deep throats
The idea was that you can resize the boxes to make you choose how deep do you want to suck, but it would be pretty easy to include a random deepthroat function. Once again thanks for giving ideas.
sexdemon wrote:6- Option where if you fail it will take a video of you sucking and upload it to a xvideo account or something where the user cant log onto remove it as they dont have the password, and they cant be released until the video has uploaded(set time limit to prevent lost connections from keeping you in bondage forever)
7- Same as 6 but pictures and a picture website.
At first I though about the possiblity of doing something similar: After the blowjob, when you are tied waiting for the final countdown, I wanted to simulat that the program sended via mail the images taken during the session to all your contacts (opening Outlook, etc..) or simulate a blue screen of death (just to make the users think about the importance of using an alternative release method), but it stills a work in progress, and I think that that could cause some heart attacks. About the video, I have not the knowlegment or the time to do that, sorry. Remember that I'm not a professional coder (in fact I'm not a coder neither)
sexdemon wrote:I hope you like my ideas as I do love your program.
Thanks
As said above ideas are very welcomed (I'm not smarter than the rest of us all together). Thank you very much.
pansexual wrote:After doing some more tests I am a bit confused. The manual states "This is extremely important because the computer will force you to cover one of the rectangles and to go back showing the desired color on the other rectangle"
At first I took for granted that if you have rectangle A and B, where A is closer to the dildo, then you need to cover A (and therefore B) to trigger a suck in, and release B to trigger a suck out. The virtual strain to force you keeping the dildo in is covered by rectangle C (C works totally fine for me btw.). This way you can set how to deep you got to suck to trigger via the border at A, and how far to go out with your mouth again by the border of B. So far it's alright that you can set both rectangles A and B as only one total rectangle.
But with using the Silverlight Version I did some tests on it and discovered that for me it seemed to be vice versa. So I only need to cover B to trigger suck in, and release A to trigger suck out, so at the end I only need to hold the area of B to trigger one suck after another without really doing a blowjob. Is this a bug? I tried it both with the defaul direction and according camera setting, and also top down perspective and setting. Very strange so far. Anybody got a hint?
At fisrt when I readed your post I thought "oh shit, I have updated one of the versions and I didn't copy the code to the another (from Silverlight to non silverlight version). But I have checked it and I haven't find any difference at all at the searching color area of code.
It would be great if anyone else have the same problem that (s)he reports it.
It could be a problem with the Tolerance that you are using (or the color to be looked for).
The program works like that:
Let's going to imagine that the blue object is the dildo. The arrow is the direction of the blowjob.
·
While the program sees the blue color on the square "1" it will be running the countdown
·
If the countdown (the progress bar) ends and the programs stills "seen" the blue color inside the square "1" it counts as a fail
Perharps,
·
When the program is not able to find the color inside the square "1" it starts to look for the color inside the square "2"
(so you have to go back to show the color in square "2")
·
If it finds the color inside the square "2" it will check again that it can see the color inside square "2" and will start looking for the color again inside square "1"
If you choose a high tolerance level the program will look for more gradients of blue, and it can happen that it gives false positives.
That's the function that the Test Session button will have: test that with your setting the program can recognise the color without giving false positives
needles to say that light must be from an artificial source, direct, the color of the dildo must be very different than the color of the face or the background, a hd webcam is a great idea... and another problem: seems that silverlight show the image of the webcam a little blurred, so it can give more false positives. The best tip is to use blue or black tones and a not so high tolerance level.
When I get more coding skills the program will look for a pattern (something like a codebar) and not for a color.
Once again thanks for trying the program and for giving feedback.
s1th1s wrote:This program looks really promising!
I still hadn't got the time to test this release to it's full extent but here are my observations so far:
I used the standard, non-silverlight version.
It's running really smoothly under Win XP 32bit (Desktop), had some troubles with the color matching but that's probably my century old webcam's fault, was planing to get a HD one soon.
Running under Win 7 64bit, the program gets incredibly slow, especially the moving and resizing of the boxes. The sucking delay and pretty much everything else time-based is really screwed up, sometimes it only takes seconds, sometimes a couple of minutes (for the sucking delay).
Running it under Wine1.3.25-2 in both Ubuntu 11.04 64bit and the new Mageia 1 Cauldron 64bit (both on a Notebook) looks really promising, the program itself runs as smoothly as under Win XP, but I'm still trying to figure out how to get Wine to detect my build-in webcam, so I couldn't test any related functions such as color-matching.
Thanks a lot for the other OS feedback. At the ends the silverlight plugin is only needed to show the webcam stream on screen. When you see the webcam area inside the gui of the program you are watching a html file that is included inside the Webcam folder. You can perfectly overwrite it with any other html file and it will be show on the main gui. It is because some people found that my programs didn't recognise their webcams.
If there is any flash or java coder that can do it, it would be great to have more html files that just show the webcam stream on screen using the 100% of the width and the 100% avaible height so we will have more options and maybe a smoother version (non silverlight version works like pain in the ass in my old computer, and the laptop where I use to code has died, so is going to take some time before I can afford in a new laptop. Performance feedback will be much apreciatted)
The Slinky wrote:I love your work. I tried this last night. I read the instructions and the forum many times but when i get to the big moment where i have already sucked 20 or so times it crashes. why is this?
Hello The Slinky, thaks for testing the program and for the feedback (not just this post, you have commented most of my programs, thanks a lot).
Well, I don't know why it crashes. The program freezes? It just exits?
What OS are you using? Wht do you mean when you say that it crashes? What configuration where you using (number of total blowjobs, time added or not, etc, etc).
If you can repeat the crash it would be very unteresting because that would mean that you've find a bug. I will prepare a little pdf with instructions to compile the program in computer, and if you are interested you can run the code from the compilator, so when it crashes you can see why it happened (a non declared variable or something like that).
Thanks a lot to you all for testing the program and giving feedback or ideas. Please remember that the are other programs from other coders that are waiting to get some feedback (is very fustrating to spends a lot of time without getting any feedback at all or at least a "hey, I'm not going to use this program but thanks for releasing it")
Greets from Barcelona