Tease AI General Discussion

1885 · Post by **1885** » Sat Apr 16, 2016 5:07 am

Forgot to add a Command that was added in Patch 51:

Added @ClearModes Command - This will clear all active modes and return them to normal

genome231 · Post by **genome231** » Sat Apr 16, 2016 7:53 am

Hi 1885

Thank you and everyone else working on this for an awesome job :D
I just read through your end script and I like how its built up with multiple types of chat possible depending on different variables :) Its a neat script

Just one line had me wandering, line 11.

Code: Select all

@RandomText(Cum for me, Hurry and cum for me, I want you to explode, Give me that cum, I want all that cum, Cum for me #SubName, Give me that cum #SubName, I want that cum #PetName, Make it feel so good for me) @Wait(20) @Goto(Allow Cum Loop)

Is it possible to add @Commands within @RandomText?
I imagine it would look something like this:

Code: Select all

@RandomText(Cum for me! @Goto(SecondOrgasm), I want you to hurry up and cum! @Chance40(OrgasmTorture))

Regards
Genome

1885 · Post by **1885** » Sat Apr 16, 2016 8:48 am

genome231 wrote:Is it possible to add @Commands within @RandomText?
I imagine it would look something like this:

You can't use Commands that use parentheses such as @Goto() or @ChanceXX(), but you can use anything else (#Keywords, @Commands without () like @ShowBlogImage and bracketed Commands like @ShowImage[])

genome231 wrote:@RandomText(Cum for me! @Goto(SecondOrgasm), I want you to hurry up and cum! @Chance40(OrgasmTorture))

That example wouldn't work. If I had to do the exact thing as the above example, I would do it like this

(Cum For Me Loop)
@RandomText(Cum for me!, I want you to hurry up and cum!) @Goto(SecondOrgasm, TortureCheck)
(Torture Check)
@NullResponse @Chance40(OrgasmTorture)
@NullResponse @Goto(Cum For Me Loop)
(Second Orgasm)
...
...
(Torture Check)
...
...

schefflera · Post by **schefflera** » Sat Apr 16, 2016 9:14 am

Yay. I like it

1885 wrote:
Added @AllowsOrgasm() Command Filter - will only display a line if the domme's "Allows Orgasms" settings matches what's in parentheses. You may enter as many options as you want. You may also use "Not" as a modifier. For example:

@AllowsOrgasm(Never) - Will only display if the domme never allows orgasm
@AllowsOrgasm(Often, Sometimes) - Will only display if the domme often or sometimes allows orgasm
@AllowsOrgasm(Not, Always) - Will only display if the domme does not always allow orgasm
@AllowsOrgasm(Always, Never, Not) - Will only display if the domme does not always allow orgasm and does not never allow orgasm

@AllowsOrgasm() replaces the Command Filters @AlwaysAllowsOrgasm, @OftenAllowsOrgasm, @SometimesAllowsOrgasm, @RarelyAllowsOrgasm, @NeverAllowsOrgasm, @NotAlwaysAllowsOrgasm and @NotNeverAllowsOrgasm. These are now legacy commands which will continue to function.

Do the old commands (@SometimesAllowOrgasm, etc.) still work? Or do I have to replace all?

1885 · Post by **1885** » Sat Apr 16, 2016 9:17 am

schefflera wrote:Does the old commands (@SometimesAllowOrgasm, etc.) still work? Or do I have to replace all?

Everything that works now will continue to work, I don't want anybody to have to go back and change work they've already done. Those legacy Commands will remain in and remain functional, so you don't have to worry about that. The Command overhaul is just to simplify things for everyone (and myself

) going forward.

meaculpa_uk · Post by **meaculpa_uk** » Sat Apr 16, 2016 12:13 pm

Hi folks,

Gripe alert!!!

Can something please sit still for a while.. say a month or so.. for those of us trying to create an erotic tease to be enjoyed by others, all of this new stuff and all of the errors it's throwing up is making it become a really thankless and un-enjoyable task. I used to rate my work by how turned on it made me feel to do.. at the moment I'm suffering a serious flop-on! Or.. alternatively let writers (not developers, not people who care about the intricacies of the programme per se) know when it's safe to start work.

I've spent days upon days trying to make Spicy viable (I love you genome.. but she's seriously broken still!) I had her to the point where she would run smoothly 80% of the time and now she'll make a successful run-through maybe 1 in 10 times and is totally un-publishable. I feel like I'm fighting a tide but at the same time time I don't want to be another passive member of the community. For me, success is about creating a stable tease, with enough kink and 100% continuity from day to day that actually turns people on.

I know this sounds like a QQ and it's not meant to be.. I love all of the new possibilities and 1885, I'm so happy that you're back, but at the moment I'm resorting to using alternative means for actual stimulation.. doesn't this defeat the entire purpose? I'm sure I'm not the only one who feels this way.

Mea

schefflera · Post by **schefflera** » Sat Apr 16, 2016 2:32 pm

meaculpa_uk wrote:Hi folks,

Gripe alert!!!

Can something please sit still for a while.. say a month or so.. for those of us trying to create an erotic tease to be enjoyed by others, all of this new stuff and all of the errors it's throwing up is making it become a really thankless and un-enjoyable task. I used to rate my work by how turned on it made me feel to do.. at the moment I'm suffering a serious flop-on! Or.. alternatively let writers (not developers, not people who care about the intricacies of the programme per se) know when it's safe to start work.

I've spent days upon days trying to make Spicy viable (I love you genome.. but she's seriously broken still!) I had her to the point where she would run smoothly 80% of the time and now she'll make a successful run-through maybe 1 in 10 times and is totally un-publishable. I feel like I'm fighting a tide but at the same time time I don't want to be another passive member of the community. For me, success is about creating a stable tease, with enough kink and 100% continuity from day to day that actually turns people on.

I know this sounds like a QQ and it's not meant to be.. I love all of the new possibilities and 1885, I'm so happy that you're back, but at the moment I'm resorting to using alternative means for actual stimulation.. doesn't this defeat the entire purpose? I'm sure I'm not the only one who feels this way.

Mea

I cannot speak for everyone, but I don't have these problems. I 'play' the wicked personality with some self created modules and it runs perfect. Just sometimes it crashes at the beginning, when it tries to load a local image or so.

I know how you feel. Nothing is worth than being in the middle of a tease and than... gone..
That just ruins everything.

But as I said, i have no problems with wicked. So it may not depend on the teaseAI, but on the personality/modules

Harry2stroke · Post by **Harry2stroke** » Sat Apr 16, 2016 5:44 pm

hmmm
thats what i get when i just try to open Tease AI with Patch 51

Spoiler: show: Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.InvalidOperationException: Fehler beim Erstellen des Formulars. Weitere Informationen finden Sie in Exception.InnerException. Fehler: Can't find the given directory: 'Images\System\DislikedImageURLs.txt'. ---> System.IO.DirectoryNotFoundException: Can't find the given directory: 'Images\System\DislikedImageURLs.txt'
bei Tease_AI.URL_Files.URL_File_BGW.set_DislikeListPath(String value) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Classes\URL_Files_BGW.vb:Zeile 173.
bei Tease_AI.FrmSettings.InitializeComponent() in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form2.Designer.vb:Zeile 12979.
bei Tease_AI.FrmSettings..ctor() in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form2.vb:Zeile 38.
--- Ende der internen Ausnahmestapelüberwachung ---
bei Tease_AI.My.MyProject.MyForms.Create__Instance__[T](T Instance) in 17d14f5c-a337-4978-8281-53493378c1071.vb:Zeile 190.
bei Tease_AI.My.MyProject.MyForms.get_FrmSettings()
bei Tease_AI.Form1.Form1_Load(Object sender, EventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1.vb:Zeile 873.
bei System.EventHandler.Invoke(Object sender, EventArgs e)
bei System.Windows.Forms.Form.OnLoad(EventArgs e)
bei System.Windows.Forms.Form.OnCreateControl()
bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bei System.Windows.Forms.Control.CreateControl()
bei System.Windows.Forms.Control.WmShowWindow(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.Form.WmShowWindow(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1076.0 built by: NETFXREL3STAGE.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
Tease AI
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///F:/Games/TAI50/Tease%20AI.exe.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1068.2 built by: NETFXREL3STAGE.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
System.Speech
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll.
----------------------------------------
AxInterop.WMPLib
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///F:/Games/TAI50/AxInterop.WMPLib.DLL.
----------------------------------------
Interop.WMPLib
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///F:/Games/TAI50/Interop.WMPLib.DLL.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.81.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.81.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1055.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.1067.0 built by: NETFXREL3STAGE.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
Microsoft.VisualBasic.resources
Assembly-Version: 10.0.0.0.
Win32-Version: 14.6.81.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll.
----------------------------------------
Microsoft.mshtml
Assembly-Version: 7.0.3300.0.
Win32-Version: 7.0.3300.0.
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

SensEx · Post by **SensEx** » Sat Apr 16, 2016 7:31 pm

Hi there for those of you who experience errors with patch 51
create two files

DislikedImageURLs.txt
LikedImageURLs.txt

And put them into

Tease AI Open Beta 51\Images\System\

Voila! :)

avatarbr · Post by **avatarbr** » Sat Apr 16, 2016 10:09 pm

This new patches are so good for more ramdom/natural interaction in TeaseAI. Its great.

Some little things:
- when you use @MultipleEdges with a Glitter contact (like @Contact3 #Edge @EdgeNoHold @MultipleEdges(8, 5, 100)), TeaseAI use Domme images. Its possible to change that?
- when TeaseAI dont find a Vocabulary file, instead of a popup message, would be possible to just show the #File in the chat? Maybe in other color. Its a little distract to get that popup in the middle of the session.
- Not sure if something with my configuration, but ShowBoobsImage shows Butt images
- When using @FollowUpXX() command, I got this:

Code: Select all

COMMAND: It's going to feel so good when you finally get to cum @FollowUp50(If you are lucky)

CHAT:

07:37 Rachel: It's going to feel so good when you finally get to cum you are lucky)
07:37 Rachel: If you are lucky

Works fine if using just @FollowUp()

rayray77 · Post by **rayray77** » Sat Apr 16, 2016 10:27 pm

1885 wrote:
rayray77 wrote:How does the new Domme tags App work? In Patch 47 it opened a seperat window, in which all images of one folder were displayed. Now I dont know how to get this back since Patch 48... I don't want to use the old system and with the new one I can only work on 1 image at a time (and this is worse than with the old one, because every tag is deselecting itself with the next image) :D
The domme tag App that currently exists in Tease AI is tied to the domme's slideshow in the main window. When you want to tag something that appears in the current image of the domme, click the button in the app. It will then be highlighted in green to show you that domme tag exists. You can remove a domme tag by clicking it and it will turn back to its normal color. This was an interim solution I came up with when integrating the old apps into the main form. The domme and image tag system needs an overhaul, and it's on my to do list. I hope the final system will be as versatile as possible and provide a lot of feedback, but I can't really take a look at it until my immediate work has been finished so please bear with me

Don't worry, I won't put you on any pressure

Just wanted to ask in case I was missing something (wouldn't be the first time).
Until you overhaul it, I will just use the old Domme tags App from 47.0. Works fine

Mat · Post by **Mat** » Sat Apr 16, 2016 11:15 pm

Just a quick suggestion/request..

Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?

Normally it's not a problem but sometimes it randomly selects a set with only a few images in.

avatarbr · Post by **avatarbr** » Sat Apr 16, 2016 11:56 pm

Mat wrote:Just a quick suggestion/request..

Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?

Normally it's not a problem but sometimes it randomly selects a set with only a few images in.

Just a tip, you can use @NewDommeSlideshow at any point in the scripts to change that.

1885 · Post by **1885** » Sun Apr 17, 2016 11:46 am

PtheV wrote:Sorry if this already came up somewhere and I missed it, but could you explain the difference between @CallReturn and @Miniscript? From the description in the patch notes they seem very similar to me. In what context would you use one and not the other?

@CallReturn() stops everything you're doing and runs a new script. When that sc4ript ends, it tried to remember what you were doing, and put you back in that state where you left off. It's a Command I was working on right before the hiatus and I never could get it to work right. It seems like the community was able to fix that Command in my absence, which is awesome, but I wanted to be able to do the same thing without interrupting what you were doing in the transition.

@MiniScript() uses a much more elegant (read: less insanely complicated) system than what I was trying to do with @CallReturn(). And @MiniScript() doesn't interrupt what you're doing. So if you call one from stroking, you're still stroking. Call one from holding the edge, you're still holding the edge. So I use it to run more complicated setups as Taunts and things like that. I'm sure people can find great uses for both, but I use @MiniScript() exclusively

So @CallReturn() - Interrupt and return
@MiniScript() - No interruption and return

meaculpa_uk wrote:Can something please sit still for a while.. say a month or so.. for those of us trying to create an erotic tease to be enjoyed by others, all of this new stuff and all of the errors it's throwing up is making it become a really thankless and un-enjoyable task. I used to rate my work by how turned on it made me feel to do.. at the moment I'm suffering a serious flop-on! Or.. alternatively let writers (not developers, not people who care about the intricacies of the programme per se) know when it's safe to start work.

I've spent days upon days trying to make Spicy viable (I love you genome.. but she's seriously broken still!) I had her to the point where she would run smoothly 80% of the time and now she'll make a successful run-through maybe 1 in 10 times and is totally un-publishable. I feel like I'm fighting a tide but at the same time time I don't want to be another passive member of the community. For me, success is about creating a stable tease, with enough kink and 100% continuity from day to day that actually turns people on.

I know this sounds like a QQ and it's not meant to be.. I love all of the new possibilities and 1885, I'm so happy that you're back, but at the moment I'm resorting to using alternative means for actual stimulation.. doesn't this defeat the entire purpose? I'm sure I'm not the only one who feels this way.

I'm sorry to hear that you're having trouble mea. I know that's really frustrating, and not the kind of frustrating we're looking for here.

That being said, any changes I'm making are very mindful of stuff that currently exists now. I'm just adding things, but not in a way that affects the functionality of anything before. Even if something's getting replaced, I leave the old version in as legacy code so old scripts still work. That doesn't change the fact that something is very wrong here, but I just want to assure you that past and future updates won't break anything to the degree you're describing.

I have to believe that the problems you're having are one of three things:

1. Your Tease AI folders are not set up correctly: A lot of times I've had people tell me things weren't working right, and for some reason windows just didn't extract all the folders when they set it up. Compare your folder setup to the Tease AI Open Beta rar fle and make sure everything is accounted for

2. The scripts you're using have errors: I would need to look over some of the scripts you're using to tell for certain

3. The scripts are using Commands in some arrangement that should be working but isn't due to a bug in my code. Also possible, and that's the case I would definitely like the scripts you're using to do some stress testing.

If you could send me some of the error messages you're getting, that would be very helpful in isolating what the problem is. The more information you have, the easier it will be to help you out. Let me know, because I do want to get you up and running again

Harry2stroke wrote:hmmm
thats what i get when i just try to open Tease AI with Patch 51

Thanks for reporting this, this will be sorted for Patch 52. In the meantime, SensEx's fix will work. Sorry about that

avatarbr wrote:- when you use @MultipleEdges with a Glitter contact (like @Contact3 #Edge @EdgeNoHold @MultipleEdges(8, 5, 100)), TeaseAI use Domme images. Its possible to change that?
- when TeaseAI dont find a Vocabulary file, instead of a popup message, would be possible to just show the #File in the chat? Maybe in other color. Its a little distract to get that popup in the middle of the session.
- Not sure if something with my configuration, but ShowBoobsImage shows Butt images
- When using @FollowUpXX() command, I got this:

Thanks, I've got these fixed for Patch 52

Mat wrote:Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?

Normally it's not a problem but sometimes it randomly selects a set with only a few images in.

Done, added the option in Patch 52 as a Slideshow Option setting

SkyHimeros · Post by **SkyHimeros** » Sun Apr 17, 2016 1:29 pm

First of all thanks a lot for the update and especially for making multiple @RandomText's possible. That is awesome.

I don't know if this is already being fixed, but I also have problems with FollowUpXX, although it looks slightly different, for example:

03:17 Domme Name: Repeat that a few times let the message sink in
03:17 Domme Name: And let the message sink in

This is how the command looks: ... @FollowUp40(@RandomText(and let the inherent truth of these words seep in, and don't forget it, and let the message seep in, and let the message sink in, and let it sink in, and learn it, and say it passionately))
Putting a RandomText inside a FollowUp seems to work in principle, however sometimes the line that is being randomly selected is shown in the previous line (without the first word however) and then again in the next line.
(To be clear what the problem is: "let the message sink in" should not be shown in the first line.)

Tease AI General Discussion

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51

Re: Tease AI Open Beta - Updated to Patch 51