Re: [Tease AI Awakening] - A Sharp Awakening - Release: Remote Toy Control v0.3.40 (Buttplug.IO) - Latest Update: 26.09.
Posted: Sat Nov 04, 2023 11:59 am
Hi!
I've looked up those log-files, unfortunately like in most of the cases, it's hard to tell if a problem is not reproducible for me.
What's left then is that a log file gives away a good hint or that something comes to my mind.
To make it short, I don't really know, just a few guesses/thoughts:
When I let it run and play a video with it in Visual Studio (Debug), it is the VLClib (or the plugins of it) which (sometimes, depends on the played video) spits out tons of error-messages/hints/infos, while the videos plays just fine, that's probably what the VLClib does/how it is made to give as much info as possible.This could be Wine issue as there are some errors in the logs relating to video playback (although Wine errors are actually fairly normal and the video plays back fine).
The only thing which looks suspicious:
direct3d9 vout display error: Can't create HD device (not Windows 7+)
---> Which seems related to the h264-codec.
This maybe/could (Note: Just a guess!!!) a problem with one specific video, ... h264 is quite common, so I think if that would be a general problem with the codec/plugin itself, you'd have such problems more often.
Correct, it saves that only on normal exit, that is because the protocol (just take a look at one and it's timestamps) is getting filled all the time, which means that if you write it immediately the harddisk would be accessed all the time, but one idea of Awakening right from the start was to reduce harddisk access to the absolutely necessary.Unfortunately, I don't have the chat log as it seems that only gets saved on normal exit?
Still, there is an option in the menu: 'Debug' -> 'Write Protocol Immediately', but I wouldn't recommend to switch it on all the time, that was for reproducible errors which leading to a crash, so those could be tracked down.
If the crash is caused by NAudio then it should be reproducible, -> it would crash always on the same audiofile.It looks like an issue with an NAudio buffer that I caught with the console capture:
Problems could be a corrupt audio file or an audio file which is not pure wave or mp3 (maybe a different audio-codec with the wrong file extension).
This audio player plays mp3 and wave-files only.
To be honest, the VLClib is still a mystery to me.The last script in the logs,16.txt
is video related and doesn't seem to have much to do with audio files.
I've got most of the problems sorted out, but still, in 1 out of 1000 tries it might freeze.
If that's the case for you (one freeze in a 1000 tries), then I have no idea how to solve that at the moment, sorry, ... I am not happy with that, but out of ideas.
But if it's happens more often and it's somehow reproducible, let me know!
This whole answer probably doesn't help you much, but maybe brings some insight.
That's good to hear, thanks, much appreciated!Apart from that, it's been running flawlessly. I especially like the full-screen mode and prompts for missing image tags. Thanks again for this!
Best greetings,
Markus