Hey everyone, Patch 54.0.2 is here and hopefully this should clear up some of the problems that got introduced with Patch 54. The main point of this patch is to address the performance issues and image freezing problems, especially with gifs. Those fixes here are thanks to Stefaf, and I can't thank him enough for how much work he's put into this
Patch 54.0.2
Here:
https://mega.nz/#!fJ01AQ4R!uRI4SVZ0wRGT ... rgsOtIT79M
Patch Notes:
BugFixes -
The code to parse
@CheckDate() in the last patch contained syntax errors. It should now work correctly according to the usage established by the Command Guide
Legacy Command
@CheckBnB reinstated by checking for available Boobs and Butt pictures rather than the defunct "Enabled BnB Games" checkbox
Fixes added from Community Members:
Stefaf: Bugfix freezing imageDownload caused by not serverside closed connection. Now the Connection is closed on clientside, if no data is received anymore.
Stefaf: Added automated ImageAnimation disabling, when a gif is displayed and the UI-Thread is not reponding.
Stefaf: Improvement IO.Access
Removed all My.Settings.Save() except after loading the application. Increased My.Settings autosavetime to 60 seconds. Now the application does not create the "ösldkflkm".newcfg files that much. Settings are still saved on regular application close.
Stefaf: Metronome is now loading the wav file into a memory-stream and plays it using a Media.Soundplayer. This way the file is not loaded again after startup unless an exception occurs. If so it will try to recover 120 times with a delay of a second in between. Positive side effect: now the metronome volume is adjustable with Tease-AI application and not System-Sounds any more.
Stefaf: BugFix: Exceptions on Closing
Stefaf: Added new ToolStripMenuitem to PictureStrip, to stop the current ImageAnimation
Stefaf: Reworked PictureStrip The checks now on opening what type if image is displayed and shows Informations according the Image.
Stefaf: Reworked Button behaviour Dislike and Like Image. Their check-state indicate now if an image is in a certain list. If they are checked and clicked, the current image will removed from the file.
If you were having issues before, please let us know how things are working for you after this patch. As always, if you have any questions, comments or new bugs to report, please let us know and we'll address them as soon as we can.
avatarbr wrote:It's possible create a "Autosave" option for the session? Like in games.
Thus, in case of a crash or freeze, we can continue the session, because losing the progress in a session is the most frustation part of the problems with a beta version.
We already have the "suspend session", I think could be this with the automatic option, maybe per time or scripts loaded.
Overhauling the Suspend/Restore feature is on my Roadmap for Patch 55, so I'll keep this in mind as I'm working on it and see if it's feasible to put something like this in
meowww wrote:Because at somepoint she showed me a Slideshow to "calm down" after she decided it would been enough and i should get back to the edge, the Slideshow did not stopped, when i told her i was on the edge, usually a Picture of the Domme would show up or if she trys to show me a Picture of something the Picture would show up, but instead the Slideshow still was there and i thought to myself fuck it, she still was able to tell me to Edge, so i kept on going with the neverending Slideshow running and then close towards the end she did not respoded to me anymore...the only think that worked was to use the safeword, that was the only way to get her to respons again, but as i then wrote on the edge, she didn´t knew anmyore that i had to owe her this Edges, but atleast using the Safeword finally stopped the Slideshow...
Thanks for reporting this bug, I'll look into it
meowww wrote:By the way is it even right to write Bugs down here or is there some other Place where i should write them down and can see if this Bug already was posted?
The official Bug Report thread is here:
viewtopic.php?f=2&t=16203 , but some people report them here because activity dwindled a bit there. I'll see them either way, but "officially" the bug report thread is over there
milo7 wrote:Is it possible to expand the "restrict orgasm" functionality to be for a specified (or random) number of days?
You can do this already with
@RestrictOrgasm()
@RestrictOrgasm(2 Weeks) will only run _RESTRICTED End scripts for 2 weeks from the moment the @RestrictOrgasm() Command is used. You can also use a comma to set a random range. For example, @RestrictOrgasm(2 weeks, 3 months) would restrict an orgasm anywhere between 2 and 3 months.