Just wanted to give a quick update on the status of all the reported bugs so far:
sexybastardo wrote: Wed Mar 22, 2017 9:33 pm
I noticed a problem with @CallReturn / @MiniScript:
Thank you for the detailed info on this. I'm going to set aside some time in the next day or two to take a deep look at it as you suggested in the other thread
closetwanker wrote: Wed Mar 22, 2017 4:26 pm
I like to use the Maximize Media Window interface, with the side bar chat. Sometimes, during a session, the side chat locks up and I have to revert to the Default Window and continue the chat underneath the media window.
I have an issue where a line in side chat gets eaten every now and then (you can still see it if you highlight it), but I've never had it lock up completely. I'll ask around the team and see if anyone has any ideas
avatarbr wrote: Sun Mar 19, 2017 3:13 am
If a taunt with 2 or 3 lines have some image call on the first line, the image will change back to the domme on the second line.
Even without calling a image, now everyline change the domme pic in each line, what did not happens in the old versions. That its not a big problem, but when is a specific image (lesbian, online, etc), its strange.
Fixed in the next patch
genome231 wrote: Thu Mar 16, 2017 1:16 pm
In situations where Tease-AI asks you to input something.
Right after you make the input. NO MATTER WHAT
The domme writes a line even though no one exists
Fixed in the next patch
genome231 wrote: Thu Mar 16, 2017 1:16 pm
So when I call images I usually use --> @ShowImage[\Path\Path\Name.jpg]
This used to work even though the file ending was PNG or Gif.
I guess the command is more strict now?
As far as I know, @ShowImage[] always required the correct extension, I don't know why it would have worked the other way before
thatwilldoit2 wrote: Tue Mar 14, 2017 4:50 pm
If one Domme image is tagged with more than tree tags all the tags get ignored.
Even worse: If you tick the tag GarmentCovering it gets tagged twice with it if you don't rename the garment in the text field on the bottom.
Can give me a specific example? I've tried using an ImageTags.txt where there were more than three tags for each picture, but it didn't affect anything. Do you mean more than three tags in the @DommeTag() Command itself? (For example, @DommeTag(Smiling, Boobs, Pussy, HalfDressed) ) @DommeTag() has only ever supported three tags, but the code for handling all Tags has been changed extensively and way above my knowledge level during my last hiatus. To the point where I can't even make sense of it really, so getting Tags untangled is going to be an undertaking. As far as I can tell though, all @DommeTag() tests I've run have worked, so any further information you can give me will be helpful
wolfet wrote: Sun Mar 12, 2017 6:57 am
Is it normal that TAI doesn't save either chat logs, error logs, session images, I don't even see saved up variables etc... Any idea why and how to fix it? after puch update I hade to create fake files because during start up TAI wanted some gif file in session images folder and txt file ...
I had that session images thing happen to me one time, but I was able to click through the error and everything worked fine. I keep wanting to take a deeper look at it, but it hasn't happened to me again since. I'll take a deeper look at all the startup code when I get the chance
As far as nothing saving, are the folders read-only by any chance? Is the first question off the top of my head I can think of to ask
SkyHimeros wrote: Fri Mar 10, 2017 2:12 pm
First of all, it's great that this program is still being worked on and thank you to anyone who is putting their time and energy into this.
In playing with the new functionally to use a douple comma ",," in @RT()-commands I think I found a pretty significant bug. When you start TeaseAI it automatically changes any ",," inside a @RT()-command into a simple "," thereby ruining the lines. It doesn't just show it wrong, it actually changes the scripting in the txt-file. I assume this is because of the "Auditing Scripts"-part whenever you start TeaseAI. It seems to think ",," inside a command must be a mistake and changes it to ",".
Fixed in the next patch, it was Audit Scripts causing it as you suggested. It's been changed to leave commas alone
holaba_be wrote: Wed Mar 08, 2017 7:34 pm
I've removed the brackets, slash and exlamation mark from the file now, to see if that's the cause
pepsifreak fixed the timeout issue for the next patch
Bluelow wrote: Wed Mar 08, 2017 4:10 pm
I'm using version 0.54.7. Just tested with only one picture for the Domme (named 01.jpg), with a tag:
01.jpg TagFullyDressed
As I mentioned above, the code for ImageTags has been changed so drastically I don't even know where to start. Please bear with me, they'll be high on the list but I'm going to have to seek help for it. I also want to isolate any problems with @DommeTags() and get those fixed as well, but Daragorn helped me narrow a couple things down on that front, so progress is being made
Qybixxx wrote: Sun Mar 05, 2017 9:55 pm
Great job so far, just two things I'd like to bring to your attention. One might be more to do with the scripts and the other is more of a feature request.
1) I've been noticing that after tits/ass slideshows, the screen isn't staying on the selected image but going back to the Domme pix. Is that a script thing, or a script engine thing?
2) Since updating, I've notice that there are a lot of broken images that do not display any information. If the information would show even when the image didn't; you could figure out what is broken on your machine and fix it. Because I think more likely than not it's my settings here.... But which ones!?
Trusfrated wrote: Tue Mar 07, 2017 4:52 am
Even though I did the rebuild, there are still hundreds of links to the offline servers in my URL files. I'm not sure if this is a temporary Tumblr issue, or something wrong with how TeaseAI builds its URL files.
1. Fixed in the next patch
2. The next patch has a new feature that lets you fix all broken images across all URL Files quickly and easily so that they display correctly
Trusfrated wrote: Tue Mar 07, 2017 4:52 am
Also, last night I tried using custom lines for Lazy Sub. (Apparently this option is only available at higher vertical resolutions. It might be helpful to toggle with Avatar window to allow for more room for apps?) I had a lot of difficulty with this. My fourth custom line kept getting over-written by the other lines. For instance, if I clicked the first line, the fourth one would change to a duplicate of the first. If I clicked the 2nd line, its text would copy the 4th. And so on. So I couldn't get the 4th line to stay the way I wanted it. A few times, after editing the customs, I was unable to get the focus back to the chat input and could no longer carry on the conversation with the domme no matter what I tried.
What resolution are you using?
Trusfrated wrote: Thu Mar 02, 2017 5:39 am
However, I'm still only seeing the default Microsoft Anna. Does anyone else see their other installed voices as an option with the current patch?
Fixed in next patch
avatarbr wrote: Thu Mar 02, 2017 1:21 am
Another really small thing. Sometimes, I copy a text to put in a script, and the text use
` instead of
' .
Like this: Don`t and Don't
TeaseAI dont recognizes this and put a ? in the place. Not sure if its something just here.
I think whatever font you're using doesn't have a character for `. I tried it with Cambria and it displayed okay
holaba_be wrote: Wed Mar 01, 2017 7:34 pm
Error I had today:
Date/Time: 2017-03-01 20:22:12
Version: 0.54.7.0
Title: Exception occured finding GotoLabel "(AV_NoPosi)" in file "[TEASE AI DIR]\Scripts\House of Tease\Stroke\Link\LinksRamdom11.txt"
Message: Index was out of range. Must be non-negative and less than the size of the collection.
Afther the error, all interaction stopped. Asking to go faster/slower/stop had the AI tell me I wasn't supposed to be doing anything, everything else just got no response.
It's probably something in the script, but I hope it helps everyone involved.
This has been one of the most persistent reasons for crashes in Tease AI, but @Goto() and @Interrupt() handling in these cases have been improved in the next patch, and hopefully should bring an end to these kind of crashes altogether
