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
Version: 0.8.3 - 683ba98
Running on: RetroArch 1.8.8 in RetroPie
Also present in the same build running on LibRetro on Windows 10.
Description:
When playing Final Fantasy 1 and talking to any NPC, small graphic glitches will sometimes flash in the screen as the text window opens or closes. Those graphical glitches are, for the most part, temporary and will stay on the screen for only some frames. Sometimes, however, those graphic glitches may stay on the screen until it is refreshed (talking again to someone to open a new text window, opening the menu or transitioning from one map to another).
It's very difficult to capture the version o the glitch that is temporary because it happens too fast. Here I include a picture of the glitched screen in the permanent version of this glitch.
The text was updated successfully, but these errors were encountered:
Duplicate of #1711. It's going to be fixed in the upcoming 0.9, which will release at...some point in the future. It won't be fixed in 0.8.4, but you can work around it using an official BIOS.
Version: 0.8.3 - 683ba98
Running on: RetroArch 1.8.8 in RetroPie
Also present in the same build running on LibRetro on Windows 10.
Description:
When playing Final Fantasy 1 and talking to any NPC, small graphic glitches will sometimes flash in the screen as the text window opens or closes. Those graphical glitches are, for the most part, temporary and will stay on the screen for only some frames. Sometimes, however, those graphic glitches may stay on the screen until it is refreshed (talking again to someone to open a new text window, opening the menu or transitioning from one map to another).
It's very difficult to capture the version o the glitch that is temporary because it happens too fast. Here I include a picture of the glitched screen in the permanent version of this glitch.
The text was updated successfully, but these errors were encountered: