Hi everyone,
I'm currently working on pokediamond and I've run into a strange graphical glitch after making some modifications to trainer_data.c.
The Issue:
When fighting a Gym Leader, the VS screen (the brief cutscene showing the leader's sprite with the blue stripe before the battle starts) displays black horizontal stripes over it, making it look glitched. This does not freeze or block the game in any way; it is purely a visual bug.
Steps to Reproduce:
The glitch seems strictly tied to the memory of previous encounters:
- Boot the game.
- Encounter and finish a battle with at least one wild Pokémon.
- Talk to a Gym Leader to initiate a battle.
- Result: The VS screen is glitched with black stripes.
However, if I reset the game and go directly to the Gym Leader as the very first thing I do (without fighting any wild Pokémon beforehand), the VS screen renders perfectly.
Context & Question:
Since this only started happening after my edits to trainer_data.c, I suspect it might be an OAM/VRAM clearing issue, where the wild battle leaves garbage data in the memory that the VS screen fails to overwrite or clear properly.
Has anyone encountered something similar, or could someone point me to the specific function/file responsible for clearing the VRAM before the VS screen initialization?
It happens both on an emulator and on a bootstrap.
Thanks in advance for your help!
Hi everyone,
I'm currently working on pokediamond and I've run into a strange graphical glitch after making some modifications to trainer_data.c.
The Issue:
When fighting a Gym Leader, the VS screen (the brief cutscene showing the leader's sprite with the blue stripe before the battle starts) displays black horizontal stripes over it, making it look glitched. This does not freeze or block the game in any way; it is purely a visual bug.
Steps to Reproduce:
The glitch seems strictly tied to the memory of previous encounters:
However, if I reset the game and go directly to the Gym Leader as the very first thing I do (without fighting any wild Pokémon beforehand), the VS screen renders perfectly.
Context & Question:
Since this only started happening after my edits to trainer_data.c, I suspect it might be an OAM/VRAM clearing issue, where the wild battle leaves garbage data in the memory that the VS screen fails to overwrite or clear properly.
Has anyone encountered something similar, or could someone point me to the specific function/file responsible for clearing the VRAM before the VS screen initialization?
It happens both on an emulator and on a bootstrap.
Thanks in advance for your help!