Lag when using image heavy screens?

[Heiden]

Hello~!

I've run into a problem where my game will slow down pretty significantly when I'm using screens with 5 or 6 different items you can click on.

I've made a point and click game based on screens where you click on imagebuttons to send you to different labels.

I've been looking through previous thread posts looking to see if anyone else has run into this issue (I found a few) and if anyone was able to find a solution for this.
I've tried increasing image cache size as well as forcing Renpy to dump its memory cache every so often, but neither have worked. Also using shift + d and forcing the game into Direct X also doesn't help the lag.

I'm using Renpy 6.99.

(And I'm sorry I don't have much experience with programming (never the less programming dealing with performance issues) so I don't really know... how to approach this.)

[Remix]

The functions you likely want to look at are:

Code: Select all

renpy.exports.get_image_load_log(age=None):
    """
    :doc: other

    A generator that yields a log of image loading activity. For the last 100
    image loads, this returns:

    * The time the image was loaded (in seconds since the epoch).
    * The filename of the image that was loaded.
    * A boolean that is true if the image was preloaded, and false if the
      game stalled to load it.

    The entries are ordered from newest to oldest.

    `age`
        If not None, only images that have been loaded in the past `age`
        seconds are included.

    The image load log is only kept if config.developer = True.
    """
# As a generator, you should be calling:
for i in renpy.exports.get_image_load_log():
    renpy.say("", "[i]") 
# or somesuch after the screen shows

# a line or two before call/show screen... use above to test result
renpy.start_predict_screen( "your screen name in quotes" )

# just after (or during is better)
if renpy.has_screen( "your screen name in quotes" ):
    renpy.stop_predict_screen( "your screen name in quotes" )

# and possibly... before
renpy.exports.start_predict( list of the images used in the screen )
# after
renpy.exports.stop_predict( list of the images used in the screen )

[Imperf3kt]

According to the documentation, screens without () are slower than screens with ()

For best performance, all screens should be defined with a parameter list. When a screen doesn't take parameters, it should be define with an empty parameter list. The screen:

Code: Select all

screen test():
    vbox:
        for i in range(10):
            text "[i]"

is faster than:

Code: Select all

screen test:
    vbox:
        for i in range(10):
            text "[i]"

When a screen is defined without a parameter list, any name used in that screen can be redefined when the screen is show. This requires Ren'Py to be more conservative when analyzing the screen, which can limit the optimization it performs.