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 save / load system seems to be malfunctioning.
The New game / continue script at the beginning results in kernel panic if there is no saved game data.
the load command anywhere just does the same.
IF you have a saved slot then it works, but if you don't have one, it will kernel panic. Also using the "if game data saved" event to handle this (as in the sample project) seems to not work and the result is always fail if you try to load when no saves are present (instead of displaying a message).
To Reproduce
Steps to reproduce the behavior:
Reuse the New game / Continue script from sample project GBS 2, or
Use the save / load function in the game
Expected behavior
The game is able to continue from the last save from the title screen or inform the player there is no saved game state
the game is able to continue from the last save or inform the player there is no saved game state
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
OS: Win 7, Retroflag
App version 3.0.2
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The save / load system seems to be malfunctioning.
IF you have a saved slot then it works, but if you don't have one, it will kernel panic. Also using the "if game data saved" event to handle this (as in the sample project) seems to not work and the result is always fail if you try to load when no saves are present (instead of displaying a message).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: