Alistunut wrote: Sun Feb 11, 2024 7:44 am
Maybe the holder's apikey should just be stored so that it is not easily seen anywhere.
In the end I guess it doesn't matter, if you enter it, you have it anyway.
On the other hand, hiding doesn't hurt also, ... noted on the ToDo-list, but don't expect anything anytime soon (see below, pause on development).
Thx for the input!
kong wrote: Wed Feb 14, 2024 12:51 am
Do you think adjusting the code is necessary for this, or is there a setting within Tease AI Awakening that could do the trick?
Hi!
I don't wanna sound like a smart-ass, but in this case terms are important, ... 'adjusting the code', ... when we talk about 'code', that's what I do in C#, coding -> programming the application Tai Awakening, ... while 'to script' or 'scripting', or 'adjusting the script(s)', that's editing those text-files (scripts) which are read and interpretated by Awakening.
(Sorry for this excursion).
So, if you talk about scripts, yes, they have to be adjusted.
From the release notes:
- New command to control remote- / Buttplug.IO- driven toys:
@BioVibToyListen(X,Y)
X -> That is the toy, works the same like with @BioToyStart( -commands, could be i.e.: 'CockRing1'
Y -> That is to what the toy should listen to, can be 'Audio' or 'Speakers'
---> Without telling Awakening that it should listen, it won't.
but despite audio playing in the test run or in the game, no output were detected. I think the save button in that menu does not work, because everytime I go into that menu, I have to rescan for the device, but it is connected to Intiface.
Yes, when you re-enter the settings, the already connected toys are not listed, ... I'll take a look at that (one far day -> it's not perfect but it works, so I don't see a reason to hurry on that).
The save button is part of the 'Selected Device' group box, it saves that stuff, not the at-the-moment-connected-toys.
I've discovered a temporary workaround for this issue. Open two instances of Tease AI Awakening. In one instance, refrain from loading the session. Instead, navigate to the settings and activate the listening mode. Keep this window open. In the second instance of Tease AI Awakening, you can proceed to play the session as usual.
*cough*

... from the release notes:
And yes, this could be 'misused' to have at least one toy being controlled by any sound your PC can produce, for that you'd have to keep the settings window open.
---> You should give the release notes a try!

But don't get me wrong, it's amazing to see people working with Awakening, coming up with ideas of it's usage and so on, ... in a way your workaround shows that you have spend some thoughts about it!
By the way, I have to say, Tease AI Awakening 3.5 is really impressive!
Thx, much appreciated!
Another question: is there a way to resize the chat window in both windowed and fullscreen modes? It would be a great addition for customization, especially when the text is too small and I want to enlarge it, but it doesn't fit the container then.
No. In the preview release version you can move (fullscreen only -> F8 and F9), but not resize it.
GUI customization is on the to-do-list, but far down.
And I guess that I won't work on a resize in windowed mode, ... that would be too much work, it's different in fullscreen, that is the better mode anyway, it would be less work also.
'Pause on development'
So, as a remark, I'm aiming for a pause, ... before that I will finish up what I have started in the preview release, then one bug about censor-bars has to be fixed, I will look into the video-problem reported by FrozenWolf, and I'll take another look at the long-protocol thing ... but then that will it be for a while (new pc, new GPU next month, so I'm going to be off for some good gaming then *yay*! ... not to forget about the upcoming spring, sun and all of that!

)
Best greetings,
Markus