"say" statement hangs game after renpy.jump() [SOLVED]

[Milkymalk]

I have a problem with this. Let me first tell you what works:

Code: Select all

label rhythm_minigame:
    $ game = Rhythmgame([x+1 for x in range(8)], 5, 6, 90, 3.0, "gewonnen")
    show expression game.notemanager as rhythmusspiel
    show screen note_score(game)
    $ wait = ui.interact() 
    return
    
label gewonnen:
    hide screen note_score
    scene black with fade
    "gewonnen"
    $ del game
    return

And inside the spritemanager update function:

Code: Select all

renpy.jump(self.returnlabel) # self.returnlabel is "gewonnen"

So far, so good.

But when I do this (triggering a "say" statement first), the game hangs itself instead of doing anything:

Code: Select all

label gewonnen:
    "gewonnen"
    hide screen note_score
    scene black with fade
    $ del game
    return

What is the reason for this? Can I prevent that from happening so I can show dialogie before the game screen disappears?

EDIT:
I have a different minigame where it works, no problems:

Code: Select all

    $ game = Slider(0, "c2_slidertutorial_finished")
    show rahmen at topleft
    show expression game.tilemanager as schiebespiel
    show expression game.glowmanager as leuchten
    $ wait = ui.interact()
    
label c2_slidertutorial_finished:
    "test"
    scene bg corridor with fade         # "scene" hides all spritemanagers too
    $ del game

With the same "renpy.jump(self.returnlabel)" to jump to the label.

What other things could cause this behaviour? I did no other jumps or calls inside the loop.

[paktek123]

do you get same results if you use

Code: Select all

renpy.say

instead?

[PyTom]

Without replications, there's zero chance anyone can solve this. If I had to guess, the problem is likely that the spritemanager is going into some sort of loop during image prediction.

[Milkymalk]

I solved the problem: I paused the minigame before the say statement so the update function is not called any more (more excatly, it returns immediately). That fixed it. Maybe the "say" statement just can't be the first thing to happen after the jump, I didn't try it.