ESTIM Coyote 2b - eu.daimonia.app

[aelskling]

@kairosJS:

I've been enjoying this app for a while. I've been enjoying the signal generation (in stereo mode and 2B earlier) and the scenarios. More variation is always welcome :)

In search of variation, I got local AI text and character generation working too, it actually sent me into a weeklong deepdive into the minutiae of AI technologies... there's a lot to take in! For eudaimonia, it works fairly well. Of the two AI options, I find that image generation works the best for me. The story generation can become weird and quirky sometimes, but that's just the state of AI.

I do have a few remarks and suggestions:

1. Occasionally a session will just freeze with a black screen halfway through and not continue. I noticed some javascript error in the browser's inspector console when it happened. Will try to write it down next time, if it's useful to you.

Other times, I got a black screen while the tease just kept running behind the scene. Strangely enough, the short video clips do continue to play, and sometimes it resolves itself after a few minutes.

2. The stereostim panel has no slider to manipulate the global volume. It seems to default to 5. However, the global volume can still be manipulated through the side panel in the tease, where it is set to the volume of the *2B*, which I had set to 8 previously. So one time I was playing a tease, and decided to adjust the level down. I moved the slider from 8 to 7 and pressed save, expecting to lower the volume by one step, but what it actually got was a jump from 5 to 7... giving me a bit of a jolt

I would prefer it if the global volume slider was available for stereostim as well, because the default of 5 produces a fairly weak signal, meaning I have to turn up my device to a level that would be a bit much for playing other e-stim content, so it frightens me a bit to turn it up so high.

3. In the stereostim mode, you restrict the signals frequency to a very sensible range of 500Hz to 1500Hz, but I guess it would be nice to be able to finetune this as well.

4. Finally, when playing with a stereostim device, there seems to be a bit too much intensity variability. For a given device volume, there are always a lot of signals that feel too weak to be effective, sometimes even barely perceptible, where the strongest signals are overwhelming. This has sometimes led to paradoxical situations where the "pleasure signal" that I received as an reward, was more difficult than the "punishment signal" that preceeded it.

Finally, I'd like to say thanks for developing this tool, I hope you will keep enhancing it!

[kairosJS]

Hey,
Thank you for your feedback!

1. Yes please, if you can catch the error, it might be really useful. Does it happen frequently? Only in normal mode or also in estimAI mode?
I will try to find what's wrong with the blackscreen.

2. My bad, I apologize for the jolt, I forgot to remove the global volume option from the ingame settings. This is now fixed.
I will probably add the global volume back for stereo box later, but I need to check few things first.
I'm really sorry about this.

3. For now, I don't want the user to be able to modify these values as they can be dangerous.

4. Do you know if this happens for both modes (normal and estimAI)?
If this is for normal mode, you can try to disable bad stims from your collection and add/create stims that fits you better.
But there are stims that are not available for customization yet. I will probably add this later.


Thanks for the inputs, and yes I will keep working on eudaimonia as I've still a lot of ideas and improvements to add!

[aelskling]

1. I will try to catch it, and report here. Last time it happened, I had myself tied up, and didn't want to untie and interrupt the session to look. It happened in the normal mode, I haven't used the AI mode for long sessions yet.

Maybe related, but I've also noticed some intermittent 403 errors when loading media sources, like it tries to load httpx://medias.daimonia.app/something/something.webm ... and it gets denied. During play, this displays itself as an image that stays on screen a bit longer than usual.

As an example that you can perhaps look up in your logs, here are a couple of images and videos that don't load:

https://medias.daimonia.app/94_cc30df97b5fc6bc3.webp
https://medias.daimonia.app/galleries/a ... 3531a.webm
https://medias.daimonia.app/galleries/m ... 3531a.webm

BTW it looks like you're using an nginx server to serve static content, perhaps the filesystem permissions are not correct on some files and directories, so the webserver can't access them?

2. Thanks, that will prevent confusion and jolts for new players, still I'd really like to have a global volume control for the stereo stim :)

3. Ah, but I meant that the range should be customizable while staying within the bounds of your sensible limits. For example, I prefer my signals between 600Hz and 1200Hz, or even 1000Hz. There should be no danger in that.

4. Happens on all modes. I think this is because the usable amplitude range of a stereostim signal is rather small. Like 30%-40%. The correlation between amplitude of the signal and the sensation is not linear.

What I mean by that is: if you calibrate to a signal playing at 100% amplitude, and then you play the same signal at 30% amplitude. It will feel very very weak to non-existent instead of 1/3 of the intensity. By comparison, I believe the 2B normalizes the volume somewhat.

What I'd suggest to remedy this, is to add an amplitude floor and ceiling that are closer together.

[kairosJS]

Thank you for all of this!
I will see what I can do to fix this.

[Thomas92755]

Yeah all on the same computer, same browser, in private or not in private no difference.
Weird thing is I can reach the localhost with postman, but not from a browser :/

[aelskling]

@kairosJS

Had some time to play this weekend, and looks like you've done some work on the app. The 403s and black screens appear to be gone, and you've added global volume for DIY stim. Excellent!

I had an interesting session too... after some warmup, I committed to a 30 minute session and set the volume a bit higher than I had warmed up with, to a level that I knew would be a bit uncomfortable. This made the pain signals actually challenging and something to fear, and during the more intense pleasure and edge scenes I had to use all my willpower not to cum prematurely.

But I persevered, looking forward to the 5 minute orgasm phase at the end... Yet when it came, it was a difficult signal at a significantly lower intensity than during the session. To make matters worse, it was interleaved with short pain bursts that interrupted the flow any time I got into a bit of a groove. So I struggled to get near an orgasm as the timer slowly continued to count down... during the last 60 seconds the signal changed to something a bit more pleasing, but apparently only tame SFW pictures were shown during this phase (deliberately?) ... With just a few seconds left before the clock running out I started to cum, only to have it abruptly cut short giving me a wonderfully ruined orgasm. Don't think this has ever happened to me before with an estim tease.

[kairosJS]

I think you kinda got lucky with that ruined orgasm, but I'm glad you had a good experience!

[Dolgian]

I tried 2 times now the app (I had tried the AI version earlier)

I must say, good job, this looks very promising!

I tried with triphase, it felt better than dual, for me at least.
2 things quickly:
-edge signals, one of them is good, the other feels 50% power of the first one. So i suggest either keep only 1 signal or fix the one that is something like __--__--__
-cum signal, it lacking, I would never be able to cum on it, not enought ramp and too many down times

keep up the good work though!

[kairosJS]

Thank you for your feedback, I will check this!

[Megusta187]

Hey kairosJS, I finally had the time to play on a DIY box. I played with the settings quite a bit and did 3 back to back sessions to really grasp how the signals are supposed to feel:

First off: THANK YOU FOR ALL THE EFFORT AND WORK YOU'VE PUT INTO THIS. We can't thank our contributors enough.

As for the positives:
- The signals are great. Most if not all felt how they're supposed to be
- The signals and signal progressions matches the pace and text of the session
- This is the first "webtease"/game to incorporate hentai, which is totally up my alley
- There are enough sliders to fine tune max volume for pain files
- Story and buildup towards the end is amazing! The game really knows how to deny and tease you!

As for the negatives:
- When you pick a short session duration let's say 3 or 5 minutes, the pacing of the story gets a bit messed up
- There are no sliders to fine tune the min/max volume for teasing files. This is super important on DIY stim! This really hurt me during the first session. I set the global volume to max in order to keep the output of the DIY box as low as possible, turned down the max pain threshold, tested 100% pain file and thought I was good to go. The calibration sound felt fine, not overpowering or strong. Yet, halfway through the session one signal came on that was way way way too strong and I struggled to turn down the volume. At first I thought I messed up the pain thresholds and did another session. This time I set the session settings to painless. However, the same thing happened again halfway through the session. This time I kept an eye on the volume, and it seems like even if you set max global volume to max, the calibration signal oscilates between 40 and 60% volume. The extremely intense signal, however, has a volume of 80 or 90%. That kind of jump on a DIY box feels magnitudes stronger than a 2B.

So I would suggest for anyone on a DIY box to be careful. And for feedback I'd suggest a minimum volume and maximum volume slider for tease/edging files. This way the volume interval can be shrinked/widened to anybodys' liking.

From experience and playing pretty much every estim tease 100s of times, a 60 or 80% volume baseline for calibration is a good start. Depending on how long the session is, you can increase the volume by 1% per minute. Prevent any volume jumps bigger than 5%. Even 5% is A LOT! on a DIY box.



If it wasn't for that one file, I would've had an amazing time! Really looking forward to get teased by Midori again! Also more hentai mistresses please!

[Electro]

I had that same problem, but I didn't boost any global volume settings. I tested pain volume at 100% and also noted where it was within the Windows volume dialog and somewhere during the tease it went from the usual spot of around about 1/3 volume to something more resembling 80-90%, I wasn't sure what caused that and I haven't played with this since. I also wasn't sure if having a 100% censored/blurred ending sequence from the previous run would happen again this time, which isn't going to have me finish and so I decided to walk away from this until it gets properly tested. Playing with the custom audio files, none play at the blast volume that I received and the domme character text didn't suggest it was supposed to be painful either. This is all with the "middle mode", not slideshow or LLM driven.

[kairosJS]

Hey @Megusta187,
Thank you for your feedback, that's greatly appreciated!

I'm really sorry about the bad experience you had. I will try to fix this as soon as I can, first I need to identify what is causing this.
But I don't own a DIY box, and as Electro said, I can't properly test it, this isn't the first time I receive bad reports about DIY and I can't do much by myself. So I'm actually closer to completely remove DIY support to be honest.
If I keep it, I will definitely add a min/max volume for normal stims, but I think that will probably alter the overall quality of stims.

About session's duration, you're right this hasn't been designed with very short sessions in mind. I will try to fix this (but probably not for now).

If you like hentai and have a gpu, I strongly encourage you to try the image generation feature (well if 6 fingers girls doesn't throw you off too much). I will probably add one or two more anime characters soon.

I apologize again, and thank you for your message!

[Electro]

A DIY box isn't needed to test what's going on, from inside the Windows volume mixer the volume can be seen when it's doing it.

[Megusta187]

First and foremost, when doing Estim everyone is responsible for their own safety! You don't have to apologise or feel sorry, bc I was impatient.

Secondly, I really was contemplating whether to post anything bc I didn't want to discourage you. Let me reiterate, you did an amazing job and the DIY stuff works really well. It's just that one file/feature, which needs refinement. If you can't be bothered, the quickest fix would most likely be to let us increase the global volume higher. The slider goes from -5 to +5 I believe. If we could bump that up to +10, you probably don't have to change anything with your project at all.

Thridly, as Electro stated the bump in volume can be seen with EarTrumpet or the Windows Audio interface. The scenario appears halfway through the session and keeps reappearing once it was played for the first time. However, if you need a beta tester, I'll gladly try and help you iron out things. I don't have much time on my hand though and it would take some time. There are also a lot of other people besides me, who have vastly more experience like Electro or lolol, who I'm sure can chime in or you can reach out to via Discord.

Anyways, thx for all your work so far!

[MrDigital]

I tried a little the ai-mode.
Usually i get 1-2 stims per answer and the are nice.
The only problem are the pain Signals.they are always only a number of jolts with the same length.
In the normal mode there are more different Signals. Weaker and then seconds later stronger ones.
Is this also possible in ai mode?