You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The setting for sprites for destroy on wall does not trigger destruction when a sprite goes of screen on a tilemap-less screen. bounce on wall does bounce on the edge of the screen suggesting an implicit wall. This is inconsistent.
I've seen this in beta beta, 0.14.45 / 5.30.6, but I think it's like this in all versions.
If you run the code in #1505 the cyan duck at the bottom will eventually come back on screen very briefly. This is not shown in the short animated gifs as they don't cover enough time.
To Reproduce
Steps to reproduce the behavior:
Set a sprite to destroy on wall
Set velocity or acceleration to set it moving
Watch it go off screen.
Set reverse direction to make it come back.
Observe it re-appearing.
Expected behavior
I'd expect consistent behaviour between bounce on wall and destroy on wall here.
Screenshots
Desktop (please complete the following information):
n/a
Smartphone (please complete the following information):
Describe the bug
The setting for sprites for
destroy on wall
does not trigger destruction when a sprite goes of screen on a tilemap-less screen.bounce on wall
does bounce on the edge of the screen suggesting an implicit wall. This is inconsistent.I've seen this in beta beta,
0.14.45 / 5.30.6
, but I think it's like this in all versions.If you run the code in #1505 the cyan duck at the bottom will eventually come back on screen very briefly. This is not shown in the short animated gifs as they don't cover enough time.
To Reproduce
Steps to reproduce the behavior:
destroy on wall
Expected behavior
I'd expect consistent behaviour between
bounce on wall
anddestroy on wall
here.Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Discussed in #1505 (comment)
The text was updated successfully, but these errors were encountered: