Been messing with this the past couple of days. I have a massive collection of gay content lined up that I plan on posting here, but I'm still doing some testing to make sure I didn't fuck anything up.
To anyone else working on these things, here's the common issues you'll see and how to avoid them:
1. Image fails to load. Simply put, the game ran out of memory. However, there is no "magic number" your files need to be under in order to avoid this. Since the game has to keep multiple files in memory (the file currently playing and the one next up) a file can load fine in one instance, but if a larger file comes after another large file it may fail to load because the first file is taking up more memory.
2. Sped up gifs. This is strictly an issue with how many frames you have. Putting [@#@] at the end of the file name where you replace # with the number of thrusts or downbeat scenes, since by default it will speed up playback to return to frame 1 on the downbeats. However, keep in mind that this should only be used if there are variances within the scenes (e.g. the second thrust goes deeper than the first thrust, and it loops back from there) and if possible you should delete all extra frames to both avoid having to use this function, and to shrink the final file size.
3. Flickering. This is actually caused by disposal frames. The game really doesn't like them, and will cause seizures if any are left in. Load up the file and make sure all frames are set to "Do Not Dispose" the save it again, voila, no more strobe effect in your porn.
It's a neat little program, and it's not really that hard to make content for once you understand how it works. Sucks that the creator stopped working on it years ago, but that's life.
|