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
Summary:
There are three (3) Exits in Level 1. Using any exit (to Level 2, To Level 4 or to Level 8) results in impossible game boards.
FinalBurn Neo Version Tested*
v0.2.94.44 (commit 706d8ae)
*Note: tested version does not suggest issue was introduced with this version.
Current Behavior
When taking the Level 2 Exit, player will be placed in between solid walls with no way out, no timer to remove walls and a voice over "try to find a way out". Play cannot advance.
When taking the Level 4 Exit, world will scroll and player is not visible. Play cannot advance.
When taking the Level 8 Exit, player is placed into a corrupt world. Navigating will eventually result in a freeze.
Expected Behavior
(Reference MAME 0.220 for correct behavior)
Levels 2, 4 and 8 should load properly.
The text was updated successfully, but these errors were encountered:
Amazing team you guys have. I'll specify device in future reports to avoid confusion. I expect to exclusively be testing on Raspberry Pi 4B, but will make note.
Summary:
There are three (3) Exits in Level 1. Using any exit (to Level 2, To Level 4 or to Level 8) results in impossible game boards.
FinalBurn Neo Version Tested*
v0.2.94.44 (commit 706d8ae)
*Note: tested version does not suggest issue was introduced with this version.
Current Behavior
When taking the Level 2 Exit, player will be placed in between solid walls with no way out, no timer to remove walls and a voice over "try to find a way out". Play cannot advance.
When taking the Level 4 Exit, world will scroll and player is not visible. Play cannot advance.
When taking the Level 8 Exit, player is placed into a corrupt world. Navigating will eventually result in a freeze.
Expected Behavior
(Reference MAME 0.220 for correct behavior)
Levels 2, 4 and 8 should load properly.
The text was updated successfully, but these errors were encountered: