Test Environment (required)
You can use MEGAINFO from within FREEZER to obtain this information
(long press RESTORE to enter FREEZER, then press HELP to start MEGAINFO)
- Platform: MEGA65 R3, xemu
- ROM Release: 920413
- Core Commit: aaf4542
Describe the bug
If a Basic program performs "COLLISION 2,1000" at the start, this works initially, but at some point during execution, it stops working - the subroutine is never called, despite there being further sprite collisions.
To Reproduce
I wish I had a clean, simple test program that would reproduce this quickly. What I do have is a test program, and when I run it, it always stops detecting the sprite collisions after a while, typically within 40-80 minutes. I get the same results on real hardware and on xemu, using the same ROM version.
Steps to reproduce the behavior:
- Run the program "collision" on the disk image held in this Zip archive: collision.zip
- The program shows a yellow raster bar and plays a sound effect every time a sprite to background collision is detected.
- Let the program run for some time, probably about 45 minutes, but it could take hours. At some point, it just stops showing the yellow bar and stops playing the sound effect.
Expected behavior
Sprite collision detection should just keep working for as long as the program is running.
Screenshots
Additional context
I had this problem with Rocket Delivery Service, Release 3. It usually happened quite quickly there. I have no idea what makes this problem occur more or less often. In Rocket Delivery Service Release 4 I execute "collision 2,1000" every frame, and this seems to make the problem go away (at a cost in performance, of course).
Test Environment (required)
You can use MEGAINFO from within FREEZER to obtain this information
(long press RESTORE to enter FREEZER, then press HELP to start MEGAINFO)
Describe the bug
If a Basic program performs "COLLISION 2,1000" at the start, this works initially, but at some point during execution, it stops working - the subroutine is never called, despite there being further sprite collisions.
To Reproduce
I wish I had a clean, simple test program that would reproduce this quickly. What I do have is a test program, and when I run it, it always stops detecting the sprite collisions after a while, typically within 40-80 minutes. I get the same results on real hardware and on xemu, using the same ROM version.
Steps to reproduce the behavior:
Expected behavior
Sprite collision detection should just keep working for as long as the program is running.
Screenshots
Additional context
I had this problem with Rocket Delivery Service, Release 3. It usually happened quite quickly there. I have no idea what makes this problem occur more or less often. In Rocket Delivery Service Release 4 I execute "collision 2,1000" every frame, and this seems to make the problem go away (at a cost in performance, of course).