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.

Sign up for GitHub

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

Jump to bottom

Inaccurate emulation: mooneye-gb general tests #13

Open
10 of 16 tasks
akatsuki105 opened this issue May 11, 2020 · 0 comments
Open
10 of 16 tasks

Inaccurate emulation: mooneye-gb general tests #13

akatsuki105 opened this issue May 11, 2020 · 0 comments
Assignees
@akatsuki105
Labels
accuracy This issue is about emulator accuracy

Comments

@akatsuki105
Copy link
Owner

akatsuki105 commented May 11, 2020 •
edited
Loading

related to #4

  • call_cc_timing2
  • call_timing2
  • di_timing-GS.gb (note: this test is expected to pass only when ran on a DMG or SGB, and fail when ran on a CGB or AGB. This is because the name ends in -GS, as explained here)
  • ei_sequence
  • ei_timing
  • halt_ime0_ei
  • halt_ime0_nointr_timing
  • halt_ime1_timing
  • halt_ime1_timing2-GS (-GS, so the note above also applies)
  • if_ie_registers
  • interrupts/ie_push
  • oam_dma/sources-GS (this CRASHES the emulator itself)
  • oam_dma_start
  • pop_timing
  • rapid_di_ei
  • ../manual-only/sprite_priority.gb (here's how it should look)
@akatsuki105 akatsuki105 added the accuracy This issue is about emulator accuracy label May 11, 2020
@akatsuki105 akatsuki105 self-assigned this May 11, 2020
akatsuki105 added a commit that referenced this issue May 30, 2020
@akatsuki105
#13 pass halt_ime0_nointr_timing test
7adfd40
@akatsuki105 akatsuki105 changed the title Inaccurate emulation: mooneye-gb tests Inaccurate emulation: mooneye-gb general tests Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akatsuki105 akatsuki105

Labels
accuracy This issue is about emulator accuracy
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akatsuki105