Odd behavior of overlay_functions since 10.1 [hotfix?]

[Halen]

Hello,
I use overlay_functions for a while now, but since I updated from Renpy 10.0e to 10.1d the displayables in the overlay functions are drawn multiple times.

I wrote a short test script to demonstrate the problem:

Code: Select all

init:  
  $ e = Character('Narrator', color="#c8ffc8")
  
  image eliza one = "Eliza_FM_001.png"
  image bg        = "AlienCrashsite.jpg"
    
  python:    
    # my overlay function
    def global_ui_frame():
      ui.text("{color=#FF0000B0}{size=46}Test{/size}{/color}", xalign=renpy.random.random(),yalign=renpy.random.random(), drop_shadow=[(2,2),(0,0),(2,-2),(0,0)])
      
    # add my overlay function to the overlay_function list
    config.overlay_functions.append(global_ui_frame)

label start:

    show bg with dissolve
    show eliza one at center with moveinleft

    e "The overlay function places ONE >Test< at a random place on the screen."
    show eliza one at left with move
    e "..."
    show eliza one at right with move
    e "..."
    e "Multiple >Test< outputs are shown every transition."

I define a simple overlay funcion which writes the word "Test" at a random screen location ONCE.
Using Renpy 10.0e there is only one "Test" visible on screen which jumps around while the script is executed.
In version 10.1d I see multiple "Test"s on the screen, even after a transition is finished.

Is this a bug or is there a new way to handle overlays??

And BTW, hello all, this is my first posting.

[PyTom]

This was a behavior change. I need to look at your program and see if the behavior that's going on is reasonable.

[JinzouTamashii]

Was there a new release of Ren'Py recently?

[Halen]

I observed something, that may help to solve the issue:

While comparing the Renpy source code of 10.0 and 10.1 (/renpy/display/core.py) I noticed that the "compute_overlay" was only executed within the "interact_core" function in version 10.0.
In 10.1 the function is also called from "with_none". By removing the line "self.compute_overlay()" from this function the behavior is, what I consider correct again.

Edit: Behaves not 100% normal. The overlay dissolves in and out with every image which is shown or removed by dissolve.