Using a move transition while a Zoom is running restarts the Zoom
Bug #354805 reported by
delta
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ren'Py |
Invalid
|
Undecided
|
Tom Rothamel | ||
Bug Description
From the "Zoom crashes on rollback" issue: https:/
Just doing a "show eileen happy with move" while it's running should trigger it.
Revision history for this message
| Tom Rothamel (renpytom) wrote | #1 |
| Changed in renpy: | |
| assignee: | nobody → pytom |
| milestone: | none → 6.9.1 |
| status: | New → Invalid |
| milestone: | 6.9.1 → none |
To post a comment you must log in.
This is one of those really odd interactions that you seem to run across regularly.
Basically, when MoveTransition sees a displayable that's in both the new and old scenes, it calls a factory function on that displayable. Normally, the factory produces a Move, which doesn't do anything when the object hasn't moved.
I don't want to not call the factory when the object remains stationary, because the factory could do other things... I remember using it with Revolve in the past.
The problem is, the result of the factory is considered to be a new displayable, which gets its show timebase set to 0. That's what's causing the problem you're seeing.
The solution is to give anim_timebase=True to the Zoom. That will make it count up from when it (or an image with the same tag) was last shown.
And I believe that resolves the problem.