[Tease AI] Personality AliceMerged / AliceAwaked

[dark0512]

How do you install Leezer's patch?

[jred]

Thank you for the fixes and updates - they work great!

One thing I've noticed - there is an entire folder of pre-decision scripts \Custom\End\BeforeDecision\ , but my domme never plays them - the way it goes for me, every time, is that after domme asks me, after a module finishes, if I can handle anything more, if I say yes, she starts a module, and if I say no, then the session ends within ten seconds, and I feel like this is where scripts from that folder were intended to be played and also perhaps some varied-endings scripts.

I mean, my typical endings looks like this, it's pretty much the same every time, and I'm not sure if it's intentional or a bug:

Code: Select all

06:47 AM Crystal: Can you bare more teasing?
06:47 AM X: no
06:47 AM Crystal: Seems like I did a good job this morning then
06:47 AM Crystal: I've already told you before, no spurting for you this morning, ...
06:47 AM Crystal: Maybe you was hoping I could forget that, I didn't stroker!
06:47 AM Crystal: Good bye for now ^_^
Mistress Crystal has logged off

[markus]

Hi again!

Someone pointed out before that the slowing/freezes problem could be on the unofficial patches, so i went and download the previous TAI Fury version and, well, no more freezing or slowing until now. I couldn't even finish the first introduction talk with the domme before, now i just finished my first session (btw, i loved it! Thanks for your work, markus!). Only problem i faced was that the @ShowBoobs or any other show something @ wasn't working, but the program itself ran without a hitch. It's worth taking a look specifically in the changes made in the newest TAI updates, perhaps?

You should try leezer3's latest patch and see if that work for you.
I didn't tested the fury patch much, but it would surprise me if '@ShowBoobsImage' wouldn't work with it,... maybe you don't have set a URL file and local path in the Tease AI Settings -> Genre Images?

Well, all the scripts of AliceMerged will work with the fury patch, ... that is because how TAI works,... if there is a command in a script which is unknown, it will simply ignore that command.
But in AliceMerged there are new commands used, so it could happen that she types something, but nothing according happens.
The new commands are not heavily used, so it wouldn't happen that much, ... yeah, if you don't mind such glitches, you can use the fury patch, ... but I would recommend to give leezer3's latest patch a try.

How do you install Leezer's patch?

Unzip the package, in it you'll find a folder:
\Source\Tease AI\obj\Release
In it there is a Tease AI.exe, just copy it into your TAI installation, overwriting the existing Tease AI.exe.
(Before that, you might want to copy & paste the old Tease AI.exe as a backup).

I mean, my typical endings looks like this, it's pretty much the same every time, and I'm not sure if it's intentional or a bug:

As the old saying goes: It's not a bug, it's a feature.
It's intended to have a quick ending script, ... the ending scripts of Miss Blue and HoT are great,... as long as you don't know them already.
One thing I wanted with AliceMerged is a higher replayability, for my taste these original ending scripts are too long and getting old too soon.
Edit: But the old endings are there but only with a little chance to get to them.

Best greetings,
Markus

[47dahc]

dark0512 wrote: ↑Wed Oct 14, 2020 9:30 pm
How do you install Leezer's patch?

Unzip the package, in it you'll find a folder:
\Source\Tease AI\obj\Release
In it there is a Tease AI.exe, just copy it into your TAI installation, overwriting the existing Tease AI.exe.
(Before that, you might want to copy & paste the old Tease AI.exe as a backup).

Did that and TAI goes unresponsive and just hangs when I do a greeting. No issues with 55.7.2c

[leezer3]

dark0512 wrote: ↑Wed Oct 14, 2020 9:30 pm
How do you install Leezer's patch?

Unzip the package, in it you'll find a folder:
\Source\Tease AI\obj\Release
In it there is a Tease AI.exe, just copy it into your TAI installation, overwriting the existing Tease AI.exe.
(Before that, you might want to copy & paste the old Tease AI.exe as a backup).

Did that and TAI goes unresponsive and just hangs when I do a greeting. No issues with 55.7.2c

You'll probably find it unsticks after a little while, try waiting. (Unfortunately, it'll likely be un-usuable for you at the minute)

------

So, I've been digging into what's going on today, and it's not pretty.
The primary issue is that the threading in this thing is non-existant, and Markus' changes have made things rather worse on anything but fast computers.

The original source uses Application.DoEvents() heavily.
What this does (well, I'm simplifiying considerably) is to force the main UI thread to process a refresh, and to process all the pending messages in the window pump.
Markus' patch removes these, and replaces these with an Async tag on several functions. Unfortunately, this is broken; Just adding an Async tag to something doesn't mean it'll execute in this manner; You've gotta spawn it's own thread and run it in there. What this essentially means is that *everything* done in these functions is now blocking. Those of us with faster computers and SSDs are OK, but anything slower is a mess.

Unfortunately, it's not as simple as just stuffing a Task.Run() onto the functions in question, as I've discoverred today.
For unknown reasons, all settings key off the state of the controls on the settings form, which we cannot access from outside the main UI thread.

Short-term, the solution to the freezing is to revert the Async / Application.DoEvents changes.
Longer term, it wants the Async fixing properly.
At the minute, I've got it to not crash, but it won't give me a response either; I'm looking into this, but there might well be something else that the async changes broke somehow....

[markus]

Hi again!

New peronality update:
Personality - AliceMergedScripts_2020_10_16.zip - leezer3's fixes V8 included
https://mega.nz/file/rF5SwDaT#Bxvapm4FS ... h1G03-O3PM
--->
For any updates: Best way to install them would be to go to the folder:
TAI/Scripts/AliceMerged
Delete every folder EXCEPT the folder 'System' (this contains your progression), copy the zip file of the new version into the TAI main folder and then unzip the update 'here'.

New audio update:
Audio - Update (you will need both, the main Audios from the first post and this update):
AliceMergedAudioUpdate02.zip (Update 2 contains everything from Update 1, it's the whole Spicy Audio Folder now):
https://mega.nz/file/jBpWkBTJ#oSYm0-cwL ... E3lJH5DaPo

ERROR: Can't locate the file: "C:\aiopen\Scripts\AliceMerged\Stroke\End\Extended_End.txt" :::: Error loading TextFile:
::: TYPO :::
::: FileText = C:\aiopen\Scripts\AliceMerged\Stroke\End\Extended_End.txt ::: LineVal = 120
::: TauntText = C:\aiopen\Scripts\AliceMerged\\Stroke\StrokeTaunts_1.txt ::: LineVal = 1887
::: ResponseFile = ::: LineVal = 9

Should be repaired with the personality update from above, thanks for reporting!

but there might well be something else that the async changes broke somehow....

I've reversed that async change in Public Sub ChatReadyState() 2 days ago, ... as I've reported, there was a problem that the domme pictures will not move to the next pixture after using @NewDommeSlideshow,... not 100% sure,... but I've got that problem every day before, after taking this change back, I didn't encountered that problem anymore.

Best greetings,
Markus

[leezer3]

Good, hopefully that'll sort it for most users then

I'm still working on the multi-threading issues in my copy of the source.
Might have something fully finished by next week some time.
This is my current source code (no binaries):
https://mega.nz/file/a8wlHCTD#BRDfof6LQ ... jSMBgBzBl8

This is *most* of the way there, in that personalities, scripts etc. load and start to work, and the main threading issues have been resolved, although I keep finding more....
No lag / freezing on lower end machines either.

However, it's nowhere near usable at the minute.

Known todo / glitches:

• Media player controls need to be moved into new functions & invoked properly from the UI thread.
• Random crash when it attempts to clone an image.
• Videos not tested / debugged yet (see first issue)
• Settings need to be verified. I think we're all OK, but there's been a *lot* of changes to where stuff is accessed.

[markus]

Hey there!

However, it's nowhere near usable at the minute.

Take all the time you need, ... awesome job you did already!

In the meantime:

Recommended patch version:
Tease AI 0.55.7.2d__2020_10_17_leezer3 patch 4 + Async ChatReadyState reversed.zip:
https://mega.nz/file/DV4EAIhC#orlrDxBLj ... 53EE5skIfQ
Hint:
There is a file in it called '\Images\System\_LocalImageTags.txt'
If you already have tagged local images, then this patch doesn't overwrite your file, ... but if you install this patch to a new TAI installation folder where you don't have tagged local pictures, then you will have to rename:
_LocalImageTags.txt
to
LocalImageTags.txt
(... Or, if you have tagged local pictures with another personality/TAI installation, of course you could just copy & paste that file into the " '\Images\System\ " folder).

(The patch is still under development, see leezer3's posts in this thread, but this version should already run much better than my original patch did, .... THX a thousand times and big credits to leezer3 for all those technical-/performance- fixes! )

You still will need the beatmeters from here:

You will need the Unofficial Patch 55.7.2 and at least one set of beatmeters which are linked for download in that patch-release thread:
viewtopic.php?f=26&t=23259&sid=75ba1550 ... cbd2b1a3f3

(It's recommend to download all beatmeter-sets, but it's a lot to download, so you could get started with only one of those sets)

Best greetings,
Markus

[leezer3]

Hm....

At the minute, I'm still thinking about the last issue.
The only real issue left (other than testing) is the video / animated GIF player.

Backing this is an ActiveX control, which can *only* be accessed from the main UI thread (including properties etc. etc.)
Now our workers are actually running in independant threads, almost every time we access this it throws a wobbly.
Having fixed the threading on everything else, this is what I can only describe as a problem (at least realtively speaking)

There are two options to deal with the problem I suspect; Either write a wrapper around the thing that invokes it's way out of trouble (ugh- Nasty horrible mess and very much likely to go badly wrong), or mirror the video properties as variables (so we can access them thread independant) & then add a loop in the main thread to update the video player from these as necessary.
Neither is pretty, and both rely heavily on hacks.

TLDR:
This thing was *never* designed with proper threading in mind in the first place.
Ce'st la vie

[leezer3]

Further updates to the multi-threaded source:
https://mega.nz/file/bsZmkBKQ#LjcY51AGu ... hhTT-UsnOg

Still not ready for 'real' use, build / test at your own risk.
The basic concept now works though.

Changes:

• Proxy class implemented for the main media player.
• Found *more* crashes which were being masked by the original setup.
• Split more of the main form into partial files (No actual changes, but Visual Studio with a bunch of extensions is not happy with oversized files. Completely un-readable too).

TODO before ready for real use:

• Add proxy for the beatmeter & Risky Pick WMP instances. (Anything using these will likely crash at the minute)
• Work on Risky Pick & the games to stop them accessing the form variables.
• Test (???!!!)

[jred]

A few things I've noticed that have begun to irk me:

1) edging during a stroking interval (when not allowed) leads extremely often to the script IWouldCallThatABargain being called, which becomes extremely annoying after a time

2) Domme doesn't count ruined orgasms as orgasms (might be a feature)

3) There is a relatively high chance of the session being extremely low on action - long timers of slow stroking, then a super-long pause, then more intervals of slow stroking, and then the end. The slow stroking modules are fun when they come after some edging, but all by themselves, they make for an extremely dull session, especailly with the domme usually ignoring me asking her to speed up

[markus]

A few things I've noticed that have begun to irk me:

Hi!

Well, the things you point out (THX for the feedback btw ) can be explained with the fact that it was never be intended to be published, like I said in the first post, ... it all started with some small changes I made, then more and more changes, ... all to fit my own idea of a personality rather than having in mind that it could be published.
That's why I only focused on how I play, leaving out how other could play with her.

1) edging during a stroking interval (when not allowed) leads extremely often to the script IWouldCallThatABargain being called, which becomes extremely annoying after a time

This is a good example how I play different,... I never tell her that I am on the edge in a stroke cycle,... I just pause if it's needed.
That's not how it is intended of course,... but that's why I never encountered that problem.

2) Domme doesn't count ruined orgasms as orgasms (might be a feature)

Same as above, ... ruined orgasm is not included at all (except with a very low chance to get to an old ending script).

3) [...] especailly with the domme usually ignoring me asking her to speed up

And again that's something I didn't worked on because how I play,... I don't try to 'chat' with her, ... I usualy just let the scripts run without 'saying' anything.

Anyway, THX for the feedback, but right now I paused on working on her, so don't expect updates on your points too soon, sorry.... but feedback will not be forgotten, so please keep reporting issues or problems or such!

(With all that pandemic issues all around us I am not in the right mood and motivation to work on it right now, ... hopefully this change soon!)

Best greetings,
Markus

... and: Stay healthy!

[dark0512]

Just let me know if you want me to test anything out!

[Kirishima]

Hey, I followed your steps and I was able to get past the inital setup, but the program crashed in the middle of the "first session" and when I type "Hi" to restart/start the personality the program will lag and crash again, any ideas? The Log doesn't seem to show any errors either.

Update! I've noticed it does this behavious when I type and it seems like the tease did not expect me to type anything and as a result it start freezing and after like 1-2 minutes it unfreezes and continues

[markus]

Hey, I followed your steps and I was able to get past the inital setup, but the program crashed in the middle of the "first session" and when I type "Hi" to restart/start the personality the program will lag and crash again, any ideas? The Log doesn't seem to show any errors either.

Update! I've noticed it does this behavious when I type and it seems like the tease did not expect me to type anything and as a result it start freezing and after like 1-2 minutes it unfreezes and continues

Hi!
There are some people who has some problems with such freezes, it's maybe because of a weak PC, ... my computer isn't a up-to-date-gaming-monster-machine, it's OK but nothing special, ... for me those freezes are only for some seconds - tolerable.

If you haven't already installed, then try this patch-version:

Tease AI 0.55.7.2d__2020_10_17_leezer3 patch 4 + Async ChatReadyState reversed.zip:
https://mega.nz/file/DV4EAIhC#orlrDxBLj ... 53EE5skIfQ

(See the first post for some more info)

In general if you use google chrome browser, there is a problem which has slow down my system a lot,... try to google for:
'chrome software reporter tool' and deactivate it, could give you a better performance of your system in general.

Best greetings,
Markus