Tease AI General Discussion

[Notay]

I was thinking of just having the re-write, I thought the current scripting was ok, the part that bothered me was when you asked to stroke faster twice, "can i stroke even faster" counting as something different, I've come across that a few times, so I thought the same but run it through regex, which should still work as it did before but with enhanced functionality.

The other thing is that there's a lot of scripts for Tease AI as it is, and I thought it'd be better to keep it the same so people don't have to learn the new one..

I thought it was quite good how 1885 had it, I suppose it depends how different it'd be and how much we'd gain from changing it, a lot of these things are going to need quite a bit of discussion, I suppose we could just run another strawpoll, to see how the content creators would prefer it,..

If your just thinking of a re-write, I don't think a new scripting language is worth it.
The main advantages I see to a new scripting language are speed, consistency, and expand-ability. But if you don't end up changing much of how Tease AI works, then none of those matter much compared to backwards-compatibility.

... with the startup time, I doubt it'd be noticeable, if you get procmon onto TeaseAI you see that it's almost constantly checking settings and reading files, computers are good at that sort of thing..

Tease AI runs a bit slow on my computer, so performance is something I think about. With better design decisions and multi-threading that shouldn't be an issue. (preloading media would be nice)
But yes translations shouldn't account for even 1second of startup time.

[Mat]

If your just thinking of a re-write, I don't think a new scripting language is worth it.
The main advantages I see to a new scripting language are speed, consistency, and expand-ability. But if you don't end up changing much of how Tease AI works, then none of those matter much compared to backwards-compatibility.

Well this isn't my project, it depends what the other's want, I just wasn't thinking of an overhaul of the scripting, I've no idea what they'd want.. another poll would be in order I think..

To be honest I probably won't get much coding done myself, I've got a LOT of work to do outside of Milo.. I'll help when I have time though.

Regarding the speed, mine loaded images really slowly, but before he left 1885 pm'd me about it and included multi-threading in Patch 48, so now my images load quite quickly, at least without hanging the program every time..

[genome231]

Hi Mat and Notay :)

Interesting debate! A thought just occurred when i was through reading all of it, and it was at the end of Mat's post.
Who will actually be working on something new?
I myself will help in any way I can, i'll even try learn a little bit of coding, but I certainly dont have the skills for something like this, other than script writing. All i'm saying is I think we need to know who's actually interested in joining this project because if none or too few is interested this project isn't going to launched anyway.
I know Notay that you worked on your Vdom for a short period of time before 1885's 3 month deadline was posted in the thread.

Well just a thought I considered to be worth sharing :)

Regards
Genome

[avatarbr]

I would like to give my 2 cents. I am not a developer, but I created some scripts for TeaseAI and I think my view could be helpful.

I think the focus should be a stable version. I know the 1885'code its not easy to edit, but OxiKlein already was able to fix a bug in the patch 48.

Without a stable version, the community will die if we need to wait 2 or 3 months for a new version. We already have so few creators here (some already gone).

In my case, I have a big update in my previous release, but with some issues I need to wait for a stable version to figure out if the problem its in my script or in the application. And I can't use patch 48 features because I dont know if will be released without major bugs. So, I am stucked here waiting.

With a stable version released (like PCMistress and TeaseMe), the community can create while developers works in another version. But, like I said, I am not a developer and not the one investing time in the project.

[NEGEV]

I think what we need at the moment is a list of people which want to be part of the developers. So that these people can make decisions in a closer group. So we would have a more structured environment and could make faster decisions. I can't code so I don't think I should be part of it but we are need of making actual decisions.

[Lestat]

I don't have enough knowledge to help in any way about the recoding project. I already find writing scripts not so easy when you're not used to coding if I compare to other "programs" (like CM, rip...). So I'm not going to say anything, it would be useless.

I modified all my EDGING scripts to use that command to make them different from the normal ones (in some for example she punishes me for edging without her asking me to, in others she doesn't, in others she make me hold the edge as punishment and so on).

Could you share one of your edge module where "she punishes you for edging without her asking you to" please? Because I tried to write exactly that months ago! But mine was never working fine enough to be shared...

[q55x8x]

Without a stable version, the community will die if we need to wait 2 or 3 months for a new version. We already have so few creators here (some already gone).

That is something that really bothers me too for quite some time now. It's why i started with my personality creator. But Sadly I think it's just the hard to find documentation that drives people away trying to even make a personality. We could maybe change that by making a wiki (something i think png tried already). But to be able to make a wiki we would need a base programm we can rely some information on the wiki on. So it's basically a big pile of stuff thats needs work to grow to a well maintained project.

I decided to mess around with the code and I was able to make the current Patch usable

WOW! Someone who actually did dig into the code. Nice work I have to admint I was a bit scared at first because it's really nested everywhere and I didn't want to break even more stuff by trying to fix something.

I think what we need at the moment is a list of people which want to be part of the developers. So that these people can make decisions in a closer group. So we would have a more structured environment and could make faster decisions. I can't code so I don't think I should be part of it but we are need of making actual decisions.

I think that would be a step into the right direction. To have an easy overview over everything I created a TitanPad here https://titanpad.com/mYlpxXE45a

We could sum up ideas there and everyone who wants to contribute could explain there how. So we have a quick place for brainstorming.

[pepsifreak]

I decided to mess around with the code and I was able to make the current Patch usable

Unofficial Patch 48.1

I looked into the increased cpu usage that Patch 48 has, and tracked it down to "MetronomeTick()", line 26882 in form1.

This slightly modified function seems to solve the issue:

Code: Select all

    Public Sub MetronomeTick()
		Do
			If StrokePace > 0 Then
				If CBMetronome.Checked Then
					My.Computer.Audio.Stop()
					My.Computer.Audio.Play(Application.StartupPath & "\Audio\System\metronome.wav")

					Thread.Sleep(StrokePace)
				End If
			Else
				Threading.Thread.Sleep(1000)
			End If
		Loop
	End Sub

This will fix the broken images when resetting: (line 22810 form1)

Code: Select all

SettingsList.Add("FormLoading: " & False)

It looks like this should have been a bug in 47, but I guess 1885 only just added a check for "formloading" while loading images.


This will fix a crash while resuming a session: (line 23828 form1)

Code: Select all

DisplayImage()

Replace "ImageThread.Start()" with that.


Lastly, for @EdgingDecide the best/easiest fix I could find was renaming the command to @DecideEdge: (line 12180 form1)

Code: Select all

If StringClean.Contains("@DecideEdge") Then

Line 12253

Code: Select all

StringClean = StringClean.Replace("@DecideEdge", "")

Doing this brought me to another bug involving the new uppercase stuff and blank/command only lines: (line 5298 form1)

Code: Select all

If SysMes = False And EmoMes = False And Not DomTask = "" Then

I'm posting this here so that tease ai won't get split into a bunch of separate repos doing their own thing.

[OxiKlein]

I looked into the increased cpu usage
-snip-
This will fix the broken images when resetting:
-snip-
This will fix a crash while resuming a session:
-snip-
Lastly, for @EdgingDecide the best/easiest fix I could find was renaming the command to @DecideEdge
-snip-

That's awesome that you were able to do all of that, I've been trying to figure out a few of those bugs for the past two days with no luck. Thanks for sharing your fixes with the community.

I've just updated my repo with the code and I'll try to post a patch with the fixes when I get a chance, credit given of course.

Edit: I messed something up when I went to generate the patch. I'm about to fall asleep in my chair so I'll try to rebuild it and get it posted within a day.

[closetwanker]

Spoiler: show

I decided to mess around with the code and I was able to make the current Patch usable

Unofficial Patch 48.1

I looked into the increased cpu usage that Patch 48 has, and tracked it down to "MetronomeTick()", line 26882 in form1.

This slightly modified function seems to solve the issue:

Code: Select all

    Public Sub MetronomeTick()
		Do
			If StrokePace > 0 Then
				If CBMetronome.Checked Then
					My.Computer.Audio.Stop()
					My.Computer.Audio.Play(Application.StartupPath & "\Audio\System\metronome.wav")

					Thread.Sleep(StrokePace)
				End If
			Else
				Threading.Thread.Sleep(1000)
			End If
		Loop
	End Sub

This will fix the broken images when resetting: (line 22810 form1)

Code: Select all

SettingsList.Add("FormLoading: " & False)

It looks like this should have been a bug in 47, but I guess 1885 only just added a check for "formloading" while loading images.


This will fix a crash while resuming a session: (line 23828 form1)

Code: Select all

DisplayImage()

Replace "ImageThread.Start()" with that.


Lastly, for @EdgingDecide the best/easiest fix I could find was renaming the command to @DecideEdge: (line 12180 form1)

Code: Select all

If StringClean.Contains("@DecideEdge") Then

Line 12253

Code: Select all

StringClean = StringClean.Replace("@DecideEdge", "")

Doing this brought me to another bug involving the new uppercase stuff and blank/command only lines: (line 5298 form1)

Code: Select all

If SysMes = False And EmoMes = False And Not DomTask = "" Then

I'm posting this here so that tease ai won't get split into a bunch of separate repos doing their own thing.

Where do I find form1? What folder?

[Daragorn]

Could you share one of your edge module where "she punishes you for edging without her asking you to" please? Because I tried to write exactly that months ago! But mine was never working fine enough to be shared...

Sure, not a problem (bear in mind this worked up to patch 47, though, because as i said patch 48 and 48.1 don't recognize @EdgingDecide anymore).
It is a modified version of the deleteHentai module, based on softcore pictures instead (so you'll need to set up a softcore image folder in local images for it to work):

Spoiler: show

Have you heard me asking you to edge?
[no] I imagine i should feel honored to see that you can't control yourself when you look at me #Lol
@AcceptAnswer I imagine i should feel honored to see that you can't control yourself when you look at me #Lol
@EdgingDecide
#LetTheEdgeFade
You know i don't like when you do <i>anything</i> without me ordering you to do it
You're here to <b>serve</b> your #DomHonorific
And serving means doing <b>only</b> what you are asked to do
Not taking initiatives on your own
Until you learn that and start to behave like the little bitch you're supposed to be
I'll have to punish you... @CBT
@NullResponse @CheckFlag(DeletePictures)
I don't know if we've ever really talked about it
But there's just something so damn <i>fascinating</i> about teasing and denial when you really think about it
The way you let me take your pleasure from you
Essentially to use it for myself, because my orgasms feel twice as good when I think about your suffering #Grin
The thing is, it makes me feel <i>so</i> good
That I start wondering what else I can take from you
That's when I start thinking about that softcore collection of yours
I think about how interesting those pictures are
How long you must have spent collecting them
And it makes me wonder what it would do to you
If I made you have to <i>really</i> suffer in order to keep them
So here's what I think we should do
I'm going to look through your softcore pictures, and when I find a really good one I'll show it to you and offer you a choice
You can say "keep", but then you'll have to hurt yourself in some way in order to keep it
Or you can say "delete" and save yourself the pain while I trash that picture. Permanently #Grin
And when I say permanent, I mean it. Don't think you can fish these out of the recycle bin when we're done
They won't be there #EmoteHappy @SetFlag(DeletePictures)
So now that you know how this works @Goto(Let's Get Started)
(DeletePictures)
You know, I had so much fun playing keep it or delete it with your softcore pictures last time
That I think we should play it again right now
(Let's Get Started)
Let's get started #Grin @Chance20(Selected) @LockImages
(Cycle Pictures)
@NullResponse @ShowSoftcoreImage @Chance70(Cycle Pictures)
(Selected)
@NullResponse @ShowSoftcoreImage
#DeleteSoftcore_KeepOrDelete
[keep] #DeleteSoftcore_Keep1
[delete] #DeleteSoftcore_Delete1 @Goto(Chose Delete)
@DifferentAnswer Keep it or delete it #PetName?
Since you like it so much, I'll leave it up for you @Chance25(Keep CBT) @Chance25(Keep CBT2)
While you edge for me #Grin @Edge
#LetTheEdgeFade
I hope that one was worth it #Lol @Chance25(Finished)
Let's do it again @Chance20(Selected) @LockImages
@NullResponse @Goto(Cycle Pictures)
(Keep CBT)
While you punish those #Balls for me @CBTBalls
I hope that one was worth it #Lol @Chance25(Finished)
Let's do it again @Chance20(Selected) @LockImages
@NullResponse @Goto(Cycle Pictures)
(Keep CBT2)
While you punish that #Cock for me @CBTCock
I hope that one was worth it #Lol @Chance25(Finished)
Let's do it again @Chance20(Selected) @LockImages
@NullResponse @Goto(Cycle Pictures)
(Chose Delete)
#DeleteSoftcore_Delete2 @DeleteLocalImage
I hope that was worth saving yourself a little pain @Chance25(Finished)
Especially since we're going again #Grin @Chance20(Selected) @LockImages
@NullResponse @Goto(Cycle Pictures)
(Finished)
I think that's enough for now @UnlockImages
Don't get too comfortable though
You have a pretty good collection of porn on that computer
And by now you should know that none of it is truly safe from me #Grin
@End

If during a stroke cycle you tell the domme you're on edge, she can goes to this _EDGING module (remember to name it ending with _EDGING (i.e. something_EDGING.txt) for teaseAI to recognize it as an edging module), which start with the domme asking you why you are edging....then she decides what to do with the edging (hold or stop) and, finally after she let you stop, she punishes you with CBT....then the "real" module part starts

[Daragorn]

I looked into the increased cpu usage that Patch 48 has, and tracked it down to "MetronomeTick()", line 26882 in form1.
....

Thx a lot mate!!
Sadly i don't have the tools installed to compile it so i'll wait for someone kind enough to put a compiled version online
But, between you and OxiKlein , you two made a really great job in fixing patch 48....thx again.

Btw...in the meantime, i found another bug (i know you hate me )
Using the @CallReturn() command to call an Interrupt module works fine but there is a small problem....if the interrupt contains some @CBT, it wont work properly...the domme gives you a first CBT instruction and then goes on with the module (she doesn't wait for your input, nor gives you eventual new CBT instructions, she simply goes on with the Interrupt module and then calls back to where she was before the call); moreover, if you call back again the same interrupt, she doesn't start it normally, but goes on from the @CBT part she was before (but she doesn't tell you to stop stroking either, the metronome goes on.....it's basically as she @Bookmarked the interrupt at the CBT part and then restart from there).

[OxiKlein]

Thanks to pepsifreak for sharing his fixes with the community

Without any further ado I present:

Unofficial Patch 48.2

https://mega.nz/#!bBUjXJzK!HBc7zONQW6uB ... bzj1ZlG1Ws

Important: @EdgingDecide has been replaced by @DecideEdge to get its functionality working. Any scripts that use it will need to be updated, but it it used the same way and does the exact same thing.

Changelog:

Images now show up on a reset

Program no longer crashes on resuming a suspended session

Program uses less CPU

@EdgingDecide command replaced with @DecideEdge to restore functionality

And finally, Fixed the @Glitter command

Link to repository:
https://bitbucket.org/OxiKlein/tai

[Daragorn]

Thanks to pepsifreak for sharing his fixes with the community

Once again, thank you both for the quick fixes! Tease AI is much better now with the new functionalities added (and fixed ) in patch 48

[tBone]

I'm down to help code

As for the name, I vote for TeaseAI CE (community edition).
Emphasis on removing the space between tease and ai