Discuss how to use the Ren'Py engine to create visual novels and story-based games. New releases are announced in this section.
Forum rules
This is the right place for Ren'Py help. Please ask one question per thread, use a descriptive subject like 'NotFound error in option.rpy' , and include all the relevant information - especially any relevant code and traceback messages. Use the code tag to format scripts.
Hi all. I am trying to speed up an image sequence faster than 0.1. Is this possible?
This is the current code I use:
Also, removing the dissolve doesn't really speed it up, sadly...
image b_animated:
"0.png" with Dissolve(0.5)
0.1
"1.png" with Dissolve(0.5)
0.1
"2.png" with Dissolve(0.5)
0.1
"3.png" with Dissolve(0.5)
0.1
"4.png" with Dissolve(0.5)
0.1
"5.png" with Dissolve(0.5)
0.1
"6.png" with Dissolve(0.5)
0.1
"7.png" with Dissolve(0.5)
0.1
"8.png" with Dissolve(0.5)
0.1
"9.png" with Dissolve(0.5)
0.1
"10.png" with Dissolve(0.5)
0.1
"11.png" with Dissolve(0.5)
0.1
"12.png" with Dissolve(0.5)
0.1
"13.png" with Dissolve(0.5)
0.1
"14.png" with Dissolve(0.5)
0.1
"15.png" with Dissolve(0.5)
0.1
repeat
I tried putting a minus in front of 0.1 to speed it up but then it says "ATL appears to be in an infinite loop" It's worth to note that I also use
Ooooh nevermind! I just tested 0.01 and it worked great! I just thought that it wouldn't do it as fast as I thought since changing from 0.5 to 0.1 didn't do a huge change.
This absolutely did the job. Thank you a ton Remix!
Although not an issue, I would avoid 0.01 and instead use 0.0599400599 or 0.06 (which is about 16ms) because it is the absolute fastest an older 60Hz monitor can display at. (newer models do exactly 60Hz, but older tech was usually 59.940)
60/1.001 = absolute frames per second
Anything faster than this won't be seen and may introduce rounding errors, resulting in screen tearing.
Warning: May contain trace amounts of gratuitous plot.
pro·gram·mer (noun) An organism capable of converting caffeine into code.
Imperf3kt wrote: ↑Wed Dec 20, 2017 4:02 pm
Although not an issue, I would avoid 0.01 and instead use 0.0599400599 or 0.06 (which is about 16ms) because it is the absolute fastest an older 60Hz monitor can display at. (newer models do exactly 60Hz, but older tech was usually 59.940)
60/1.001 = absolute frames per second
Anything faster than this won't be seen and may introduce rounding errors, resulting in screen tearing.
That's a really good point. Thanks, I will do that!