Masturbatrix - Tease-AI Awakening - V1.25B

[Rar1197]

-re slide03 issue - I did not have matching flags files as noted in vocabulary file. I copied the only one slide flag i had, renamed it and have no issues since. (No idea what is supposed to be in the flag files though nor how to edit them)

-re crash at video end: I found advice somewhere in Tease-Ai awakening forum, can't find the same again to post here, but basically @Rar1197 : you described it here as well:
viewtopic.php?p=351876#p351876
I've put the end of line after @stopvideo to new line and have no issues since.

You should have exactly one out of the following flags set:
SlideShowSystem_01
SlideShowSystem_02
SlideShowSystem_03

During installation it defaults to settings SlideShowSystem_01 , but this can be changed by typing 'settings' at the initial menu screen and then typing 'slideshow' to choose which slideshow mode you want.

Because of the way #Slide.txt is setup , there should in theory always be a valid line , even if none of the flags has been set. If for some reason the flags are missing , the 5th line will end up creating the SlideShowSystem_01 flag.

Which is why my only guess as to what could have gone wrong was down to an unlucky timing issue with a video stopping at exactly the wrong point.

(I wasn't actually aware that you had a video crash , I was just guessing that it might have reached the end naturally).

As a side note , I don't think 'slideshow mode 3' currently works as advertised, since none of the 'domme mod' flags (DMod1 etc) ever get set. I happen to be using it anyway , since I've modified my #Slide_03.txt to use images based on my tastes instead.

[Rar1197]

it is conceivable that it was just bad luck with the video stopping playing in between evaluating the 3rd and 4th line of #Slide.txt. I don't know enough about how TeaseAI works internally to say whether that is a possibility or not.

Possible, yes, but that the video stopped right in that fraction of a second would be very unlikely.
Noted down, ... will take a look at that the next days.

I just encountered the error message myself , and it turns out that there is a simpler explanation.

If a video has been paused then it is neither playing nor not playing.

Eg :

Code: Select all

@NullResponse @PermaRapidCodeOn
@NullResponse @PlayVideoNoWait(all)
@NullResponse @Wait(1)
@NullResponse @PauseVideo()
(Loop)
@VideoIsNotPlaying Video is not playing @Goto(Loop)
@VideoIsPlaying Video is playing @Goto(Loop)
Video is neither playing nor not playing @Goto(Loop)

Oh , I just noticed that there is an @VideoIsPaused condition available. So I guess if a paused video is considered to be not playing by design , then the original script needs to have an extra line with @VideoIsPaused check.

[Rar1197]

The edging section in Custom\Session\Video\Session_Video_Stop.Go.txt suffers from similar errors to Edges.txt and Edges_Hold.txt , in that it never stops (because Edges_Total is increased each look) , and the counter on the censorbar doesn't get updated.

Code: Select all

This section :
(Edging)
@NullResponse @SetVar[Edges_Total]=[#Random(2,5)]
@NullResponse @SetVar[Edge_Count]=[0]
Get ready to edge! #Slide @Wait(10) @Censorbar2On(85,90,15,10,Edges #Var[Edge_Count]:#Var[Edges_Total])
(Edging2)
@Variable[Edge_Count]>=[Edges_Total] @NullResponse @Goto(Edging3)
#Edge @EdgeNoHold #Slide
#LetTheEdgeFade #Slide
@NullResponse @ChangeVar[Edges_Total]=[Edges_Total]+[1]
@NullResponse @ChangeVar[Edge_Count]=[Edge_Count]+[1]
@NullResponse @Wait(10) @ShowWait
@NullResponse @Goto(Edging2)
(Edging3)
@NullResponse @CensorbarAllOff
@NullResponse @SetVar[Edges_Total]=[0]
@NullResponse @Goto(Return)

Should look something like this I think :

Code: Select all

(Edging)
@NullResponse @SetVar[Edges_Total]=[#Random(2,5)]
@NullResponse @SetVar[Edge_Count]=[0]
Get ready to edge! #Slide @Wait(10) @Censorbar2On(85,90,15,10,Edges #Var[Edge_Count]:#Var[Edges_Total])
(Edging2)
@Variable[Edge_Count]>=[Edges_Total] @NullResponse @Goto(Edging3)
#Edge @EdgeNoHold #Slide
#LetTheEdgeFade #Slide
@NullResponse @ChangeVar[Edge_Count]=[Edge_Count]+[1]
@NullResponse @Censorbar2On(85,90,15,10,Edges #Var[Edge_Count]:#Var[Edges_Total])
@NullResponse @Wait(10) @ShowWait
@NullResponse @Goto(Edging2)
(Edging3)
@NullResponse @CensorbarAllOff
@NullResponse @SetVar[Edges_Total]=[0]
@NullResponse @Goto(Return)

[genome231]

Hi all

As per usual a big thank you!
Think I got it all.
Version 1.23 should be there.

Regarding the fast typing bug.
I tried something which might help, let me know how it goes
Otherwise I will have to spend more time on it - because obviously it is not acceptable, it has to be fixed!

Cheers
Genome

[Rar1197]

Regarding the fast typing bug.
I tried something which might help, let me know how it goes
Otherwise I will have to spend more time on it - because obviously it is not acceptable, it has to be fixed!

Markus added a fix for this in the latest version of Tease AI Awakening (0.3.75). The @NullLine command was causing extremely rapid text.

[StellaRack]

I am not sure if this is intended

I was near the end of a session playing Supreme.
Domme picked the Curfew Card
I was then send back to the who to call page
And was asked why the session stop suddenly

The chat log

Spoiler: show

Domme: There is the element of remembering what cards are left
Domme: And playing the odds
Domme: Don't worry if you don't understand the game right away
Domme: You will learn one way or another *grin*
Domme: I call this game "Supreme"
Domme: Are you happy with your hand or would you like to reshuffle?
Me: Happy
Domme: From top left you have card 1, 2 andd 3, 4 - from top right you have card 5, 6 and 7
Domme: I think I want to pick a card for you now!
Domme: What card to pick .. *wicked grin*
Domme: Card 7! :p
Domme: Lucky me!
Domme: That ends our game and you go straight into a 24h curfew!
Domme: You have earned yourself a no-stroking curfew
Me: Domme
Dialing ..
Domme: Hello slave
Me: Hello
Domme: I see that our last session ended suddenly?
Me: Yes
Domme: Did you exit prematurely or was it a bug?
Me: Bug
Domme: Remember to report it!
Me: Exit
Domme: Ciao Name

Looking into the script
Custom\Session\Release\Generic\Instant\Gamble\Gamble_02.txt Line 428

Code: Select all

(CurfewCard)
@NullResponse @ImageBarAllOff
(Curfew)
That ends our game and you go straight into a 24h curfew! #DT
#Curfew #DT
@NullResponse @Interrupt(Restart)

@NullResponse @Interrupt(Restart) was the course.

My guess of the code flow that lead up to this

Spoiler: show

ShowCards
DeclareOrder
P1PlayCard
DommeDecide
Card7B
Card7C
CurfewCard
Restart

[Rar1197]

Hi all

As per usual a big thank you!
Think I got it all.
Version 1.23 should be there.

Thanks for all those fixes! I believe that covers all the things I had reported.

There were a few minor things I noticed in the changes :

--------------------------------------------------------------------------------------------------------


In your fix for #Slide.txt , I think you may have it the wrong way round.

Instead of

Code: Select all

@VideoIsPaused @Flag(SlideShowSystem_01) #Slide_01
@VideoIsPaused @Flag(SlideShowSystem_02) #Slide_02
@VideoIsPaused @Flag(SlideShowSystem_03) #Slide_03

I think you want

Code: Select all

@VideoIsPaused @NullLine

(Ie , a paused video should behave the same as an actively playing video).

--------------------------------------------------------------------------------------------------------

In your change to #DT.txt , I think you need an @NullLine for the NoTagSystem case to work without displaying error messages.
Ie. :

Code: Select all

@Flag(NoTagSystem) @NullLine
@NotFlag(NoTagSystem) #DT_Fix

--------------------------------------------------------------------------------------------------------

I see that you've changed Commitment_Period and Commitment_Period_Set to Commitment_Period_Set_Date and Commitment_Period_Var. However people that were already on Version 122 won't get updated automatically by Update.txt and so may need to manually fix things. It may all sort itself out well enough on its own though.

[TanyaHumble]

Ran a session with 1.23 and had zero issues but I'll keep an eye out and report any if I find one.

Keep up the good work!

[sirveillance]

Hi,
i just set up TAI Awa with the provided Media and after starting it for the first time, every line the Domme is saying ends with "NO_POSSIBLE_LINES: Scripts\Masturbatrix_2_0\Vocabulary\#DT.txt"

The text looks fine, but at the end of every single line is the Error. Any Ideas on how to fix this? Thanks!

[sirveillance]

--------------------------------------------------------------------------------------------------------

In your change to #DT.txt , I think you need an @NullLine for the NoTagSystem case to work without displaying error messages.
Ie. :

Code: Select all

@Flag(NoTagSystem) @NullLine
@NotFlag(NoTagSystem) #DT_Fix

--------------------------------------------------------------------------------------------------------

This fixes my problem above after a restart. Thanks @Rar1197

[Rar1197]

A couple of minor bugs I've noticed...

In Custom\Start_And_Misc\Base.txt the (NoSessionYet) section is showing an error message based on commitment time, but it should be doing it based on SessionDelay.

So this section :

Code: Select all

(NoSessionYet)
@Variable[Commitment_Remaining_Var]>=[#DateDifference(Commitment_Period_Date,Days)] @NullResponse @SetVar[Commitment_Remaining_Var]=[#DateDifference(Commitment_Period_Date,Hours)]
@Variable[Commitment_Remaining_Var]>[48] @NullResponse @Goto(NoSessionYet_Days)
You still have to wait #DateDifference(Commitment_Period_Date,Hours) hours before you can have a session #DT @Goto(Base)
(NoSessionYet_Days)
You still have to wait #DateDifference(Commitment_Period_Date,Days) days before you can have a session #DT @Goto(Base)

Should look something like this :

Code: Select all

(NoSessionYet)
@NullResponse @ChangeVar[SessionDelayRemaining]=[SessionDelay]-[#DateDifference(LastSession,Hours)]
@Variable[SessionDelayRemaining]>[48] @NullResponse @Goto(NoSessionYet_Days)
You still have to wait #Var[SessionDelayRemaining] hours before you can have a session #DT @Goto(Base)
(NoSessionYet_Days)
@NullResponse @ChangeVar[SessionDelayRemaining]=[SessionDelayRemaining]/[24]
You still have to wait #Var[SessionDelayRemaining] days before you can have a session #DT @Goto(Base)

-------------------------------------------------------------

In Custom\Session\Release\Base.txt the wrong chance variable is being updated in the (Gamble) section

This :

Code: Select all

(Gamble)
@NullResponse @ChangeVar[Chance_Denial]=[Chance_Denial]/[2]

Should probably be this:

Code: Select all

(Gamble)
@NullResponse @ChangeVar[Chance_Gamble]=[Chance_Gamble]/[2]

-------------------------------------------------------------

And some random thoughts...

At the moment it seems that the chance of release at the end is high. A side effect of this is that Merits drop fairly drastically since they get halved after every succesful release, and so you'll never really have a good chance at recovering them.

Not sure what the best solution for that is. Maybe the Merit reduction for authorised release should be lowered, or it should prevent the Merits from dropping below a certain value in that case.

A somewhat related thing is that DenialLVL is currently always set to 1 (since there is no option to change it). As a result Chance_Denial and Chance_Hard always get set to 0.

[genome231]

Hi all,

New version!

@rar1197
Random thoughts / feedback is the best!

I changed the merits related to orgasm and ruined orgasm.
Good catch!
If you have more comments/feedback, Please!

Cheers
Genome

[Rar1197]

Hi all,

New version!

Looks like some good changes/fixes.

I think there may be a minor copy/paste error with your change to Insert\Sub_Ruin.txt. It now updates LastOrgasm and Orgasm_Count , instead of LastRuined and Ruin_Count. I'm guessing that isn't intentional since the Ruined variables are still being used elsewhere.

[Rar1197]

Regarding the Merit changes for ruined/orgasm , it looks like there are still a fair number of places that use the formula @ChangeVar[Merits]=[Merits]/[2] directly , instead of making use of Sub_Ruin or Sub_Orgasm.

It appears to affect the following files :
Custom\Session\Chastity\Stop_Go_Chastity.txt (2 hits)
Custom\Session\Release\Delayed_Release.txt (3 hits)
Custom\Session\Release\Generic\Instant\Hard\2.txt (2 hits)
Custom\Session\Release\Generic\Instant\Hard\3.txt (2 hits)
Custom\Session\Release\Generic\Instant\Milking\1.txt (2 hits)
Custom\Session\Release\Generic\Instant\Ruined\1.txt (2 hits)
Custom\Session\Release\Generic\Instant\Ruined\2.txt (2 hits)
Custom\Session\Release\Generic\Instant\Swing\3.txt (2 hits)
Custom\Session\Release\Release_Orgasm.txt (1 hit)
Custom\Session\Release\Release_Ruin.txt (1 hit)
Custom\Session\Release\Specific\Generic\Orgasm.txt (2 hits)
Custom\Session\Release\Specific\Generic\Ruined.txt (2 hits)
Custom\Session\Release\Specific\Instant\Boss.txt (1 hit)
Custom\Session\Release\Specific\Instant\Goddess.txt (2 hits)
Custom\Session\Release\Specific\Instant\HeadMistress.txt (1 hit)
Custom\Session\Release\Specific\Instant\Humiliatrix.txt (2 hits)
Custom\Session\Release\Specific\Instant\Lesbian.txt (1 hit)
Custom\Session\Release\Specific\Instant\Mistress.txt (1 hit)
Custom\Session\Release\Specific\Instant\Nurse.txt (1 hit)
Custom\Session\Release\Specific\Instant\Princess.txt (1 hit)
Custom\Session\Release\Specific\Instant\Secretary.txt (1 hit)
Custom\Session\Release\Specific\Instant\Seductress.txt (1 hit)
Custom\Session\Video\Session_Video_StopGo.txt (2 hits)
Custom\Task\Tease\Maid\Maid.txt (1 hit)


There are a few cases of dividing by 3 as well , which may or may not be intentional.

[wowpeterpaulson]

Hi All,

Is the counting punishment working for you? I'm always getting shown a smaller number of slides than is on the counter making it impossible to tell correctly number of slides. Some slides probably fail to load in time or sometimes are shown for a very small fraction of a second. Like if it's very lagy. I'd guess this may be caused by my PC, but it's quite a good one. I'm not having any memory issues or so.
Any suggestions are welcome.
Thanks for the great work as always!