I'll check this out. Are you sure it happened too soon? I can see it happening too late, but too soon seems odd to me. Well, we'll see..monele wrote: First one, it seems renpy.pause has somewhat changed (unless it's the way you deal with the framerate) because previously synced parts (sound+animation) are now out of sync (by about 0.1 or 0.2 seconds but that's enough to have some sounds be out of place). It even happened with very short scenes along the lines of :
The show happened too late or too soon.Code: Select all
$ renpy.play("sound.wav") $ renpy.pause(1.7) show something
Oh, can you try replacing the call to renpy.play with:
Code: Select all
$ renpy,music.play("sound.wav", loop=False, synchro_start=True)
Also, realize that timing is a best-effort sort of thing on Ren'Py. I'd make sure you don't have any other programs running, that would slow things down, making the pause start later.
I see my obvious error, will fix it when I get home.The other new bug :
Not directly. I factored the various display_say functions out into a new file, that's what caused the problem.That's when I use my shift+> shortcut that skips to the next choice. Seems there's a problem with the implicit "with None" *gut feeling*.
Even the one that uses your own MoveTransition? That should probably break, since I changed the data structure MoveTransition depends on. You can replace it with providing a factory argument to MoveTransition, which is the new preferred way of customizing things.Surprisingly, my animations routines are intact XD... That's what I thought would break ^^;
Let me know what you think. Right now, my thoughts are that I'll cut a bug-fix 5.6.2 release on the weekend, and slip the new demo to 5.6.2.still have to try out all the new stuff (layers and shift+R). Already looks like a nice version though ^.^