Moderator: 1885
yep
initialy i do it
try another clean install, take few inmages and tag tham with all tags and still crashes after 3 lines.PtheV wrote: Mon Mar 15, 2021 11:41 pm Also, make sure you've got everything setup in Tease AI, including tags and all 3 Glitter contacts.
I forgot to tag lesbians kissing. It works now. Sorry for being a dingus haha. Thank you for the help :) [SOLVED]PtheV wrote: Mon Mar 15, 2021 11:41 pmI can't think of any reason why those lines would throw an error, sorry. Have you tried it with the metronome turned off? Maybe try a completely fresh install of Tease AI? Also, make sure you've got everything setup in Tease AI, including tags and all 3 Glitter contacts.fean wrote: Mon Mar 15, 2021 6:18 pm yep 2 times does clean install but when metronome starts it's cause a crash. And all teases starts with same phrases
That last line calls a picture tagged SoloF, could you check if you have at least one of those? See the first post for a list of required image tags. Yes it will go through that script again until the flag is set.Bambi143 wrote: Mon Mar 15, 2021 10:15 pm I did a fresh T.A.I and Miss blue install. I've done 2 sessions and it works fine except for one issue. When she wants to restrict porn outside sessions it always goes to error message and freezes completely. I can work around it with safeword after she asks but I think she's going to ask it every session until the the flag is installed no? Amazing work otherwize!
nope. Errorlogs folder is empty
unless 1885 changed something in the callreturn routine that i made, theorically speaking there should be endless possible callreturnsPtheV wrote: Wed Mar 17, 2021 5:11 pm This was something I worried about so I've tested it quite extensively and it never seemed to cause any problems. After I read your comment I did a quick test with the exact scenario you described and it worked fine with 3 layers of @CallReturn. Could you post the chat log so I can take a closer look the scripts that were called when it happened?
There is a line where she said it's time to finish, but still didn't got the end script.PtheV wrote: Wed Mar 17, 2021 5:11 pm This was something I worried about so I've tested it quite extensively and it never seemed to cause any problems. After I read your comment I did a quick test with the exact scenario you described and it worked fine with 3 layers of @CallReturn. Could you post the chat log so I can take a closer look the scripts that were called when it happened?
Out of my mind, not remembering precisely how i wrote the callreturn routine back then, it is pretty probable that this is a problem with callreturns called AFTER you used the @decideorgasm command.PtheV wrote: Thu Mar 18, 2021 12:05 pm Alright, this i definitely not a @CallReturn issue. I wanted to make the ending a little more unpredictable, so I created a buffer script that is called when the end script is reached. One of the options is that you get one more round of stroking, as happened here and the Domme indictated as much (" but making you ache and squirm is just so much fun"). The problem seems to be that once in the @CallReturn script you triggered by asking to edge, the @End caused the session to end, instead of going back to where the @CallReturn was triggered.
I had actually noticed this happening when @CallReturns were triggered in Taunts and that's why I prevented those Taunts from being called in the last cycle. But I forgot about the ones in Responses.
I'll have to take a closer look. Either the @CallReturns have to be blocked in the last cycle or I get rid of the last cycle altogether. And I'm wondering if the same thing is true for Interrupts.
Isnt it possible to just use this without Fury? Like with the original with sweet patch?PtheV wrote: Thu Mar 18, 2021 12:05 pmDaragorn wrote: Wed Mar 17, 2021 7:38 pm unless 1885 changed something in the callreturn routine that i made, theorically speaking there should be endless possible callreturnsAlright, this i definitely not a @CallReturn issue. I wanted to make the ending a little more unpredictable, so I created a buffer script that is called when the end script is reached. One of the options is that you get one more round of stroking, as happened here and the Domme indictated as much (" but making you ache and squirm is just so much fun"). The problem seems to be that once in the @CallReturn script you triggered by asking to edge, the @End caused the session to end, instead of going back to where the @CallReturn was triggered.avatarbr wrote: Thu Mar 18, 2021 3:02 am There is a line where she said it's time to finish, but still didn't got the end script.
The log ends here.
I had actually noticed this happening when @CallReturns were triggered in Taunts and that's why I prevented those Taunts from being called in the last cycle. But I forgot about the ones in Responses.
I'll have to take a closer look. Either the @CallReturns have to be blocked in the last cycle or I get rid of the last cycle altogether. And I'm wondering if the same thing is true for Interrupts.That's a Tease AI issue, not caused by Miss Blue. I'm sorry I can't be more helpful.Bhurk wrote: Thu Mar 18, 2021 12:16 am Hello, I tried using the latest version with TAI Fury but I keep getting "Out of memory" errors when displaying images, it looks like its only happening to high resolution images and gifs which is weird because the non fury version works fine.
Not that I know of. But it reminds me that I forgot to mention that Domme tags Ass and Boobs are required, so I'll add that to the main post.Never say never, I guess. There will definitely be a 3.1 though, for bug fixes and small additions.bob0bob wrote: Wed Mar 17, 2021 8:15 pm Maybe when the summer comes you'll miss us and start thinking about version 3 point 1. One can hope!
I think it's to do with the module counter, if you're in chastity then Miss Blue only allows one module to play before shutting down. Just need to tweak line 8 in the ModuleMain_CHASTITY script.PtheV wrote: Fri Mar 19, 2021 12:57 pmWeird. There aren't any RemoveTeaseTime commands in MB. There's a couple of specific circumstances where the session is cut shirt, but in those cases it should be clear why that is happening.Daragorn wrote: Thu Mar 18, 2021 7:21 pm P.s: BTW i had the same issue reported by another user of sessions lasting very little, around 20-25 minutes only in the few tries i made so far with her
