Skip to content

Use correct VRAM transfer mode for savestates #203

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

Closed
wants to merge 1 commit into from

Conversation

NobodyNada
Copy link
Collaborator

We set the high bit of $2115 to 0, which instructs the PPU to increment the VRAM word address after writing the low data byte. However, the DMA transfer writes low bytes first, then high bytes. This means the high byte of the first word of a transfer was being skipped, leading to an occasional glitchy tile. Setting the mode bit to 1 instead fixes the issue.

We set the high bit of $2115 to 0, which instructs the PPU to increment
the VRAM word address after writing the low data byte. However, the DMA
transfer writes low bytes first, then high bytes. This means the high
byte of the first word of a transfer was being skipped, leading to an
occasional glitchy tile. Setting the mode bit to 1 instead fixes the
issue.
@InsaneFirebat
Copy link
Collaborator

InsaneFirebat commented Mar 3, 2024

Nice. That's probably the bug total mentioned a long time ago but I couldn't make any sense of it at the time.
image

@InsaneFirebat InsaneFirebat added the bug Something isn't working label Mar 3, 2024
@InsaneFirebat
Copy link
Collaborator

Merged with #202

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants