https://www.youtube.com/watch?v=U34vUdSIBtE
This guy is playing PAL games on NTSC systems, and I can understand most of the glitches, but why is the HUD showing up on top of the BG? Is this some kind of CRT problem?
Explain this glitch in Battle Toads?
Moderator: Moderators
-
- Posts: 3140
- Joined: Wed May 19, 2010 6:12 pm
Re: Explain this glitch in Battle Toads?
HUD is sprites and unaffected by PAL/NTSC timings. Black bar is cycle-timed and affected by PAL's longer VBLANK.
Re: Explain this glitch in Battle Toads?
That HUD is way too big to be made out of sprites.
-
- Posts: 3140
- Joined: Wed May 19, 2010 6:12 pm
Re: Explain this glitch in Battle Toads?
I'm guessing that Battle Toads might be flickering between showing the gameplay, and showing just the HUD and a black screen, and the camera doesn't pick up the brightness difference.
Re: Explain this glitch in Battle Toads?
Quickly loading the PAL ROM in FCEU-0.98 and emulating as NTSC shows that's exactly what's going on.psycopathicteen wrote:I'm guessing that Battle Toads might be flickering between showing the gameplay, and showing just the HUD and a black screen, and the camera doesn't pick up the brightness difference.
The PAL build seems to spend enough time that the game logic is only evaluated every other vblank when run at 30kcy/vblank instead of 33kcy/vblank. And relatedly, after it misses a real vblank, the status bar is is delayed by an extra 16 scanlines.
-
- Posts: 3140
- Joined: Wed May 19, 2010 6:12 pm
Re: Explain this glitch in Battle Toads?
So does that mean it is flickering?lidnariq wrote:Quickly loading the PAL ROM in FCEU-0.98 and emulating as NTSC shows that's exactly what's going on.psycopathicteen wrote:I'm guessing that Battle Toads might be flickering between showing the gameplay, and showing just the HUD and a black screen, and the camera doesn't pick up the brightness difference.
The PAL build seems to spend enough time that the game logic is only evaluated every other vblank when run at 30kcy/vblank instead of 33kcy/vblank. And relatedly, after it misses a real vblank, the status bar is is delayed by an extra 16 scanlines.