Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iridion 3d - Glitches Logo and game over #77

Open
wwark opened this issue Nov 28, 2020 · 3 comments
Open

Iridion 3d - Glitches Logo and game over #77

wwark opened this issue Nov 28, 2020 · 3 comments

Comments

@wwark
Copy link
Contributor

wwark commented Nov 28, 2020

Save states - Glitches at the game over screen
https://github.com/MiSTer-devel/GBA_MiSTer/files/4130122/Iridion.3D.USA.Europe.zip

From @M-Walrus
"I see Iridion 3D was already reported. I was just about to report it but checked here first.
Here are two places where you can see the glitchy line in Iridion 3D. First is actually right at the beginning (Developer Logo) and seems the same as the "game over" screen example. Top row of pixels in each example is shifted far to the left:
Logo: https://youtu.be/WWyJugZctRY?t=45
Game Over: https://youtu.be/WWyJugZctRY?t=1500"

Thanks.

@fleroviux
Copy link

I had the same issue in NanoBoyAdvance. The issue is that mid-frame writes to BGX/Y don't get copied into the internal registers immediately like GBATEK says. They're copied at the start of the next scanline instead.

I have a test ROM here that might help to solve the issue:
https://github.com/nba-emu/hw-test/tree/master/ppu/bgx

@wwark
Copy link
Contributor Author

wwark commented Oct 26, 2022

thank you @fleroviux for all those HW tests you write.
Some tests are OK with the current core.
Maybe others not OK could help to improve accuracy of the core.

@RobertPeip
Copy link
Member

Thanks a lot for the hint!

I didn't know you have written such tests. I should take some time and look at them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants