You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is timed by scanlines. But I think this is wrong.
The keyword here is "normally" suggesting that it can take more or less, and in Mode 1, it only takes a few cycles.
And the Realboy Blog Post states: "Because the Game Boy’s CPU is clocked at 4194304hz (that is, 4194304 cycles per second)". 4194304 / 60 = 69905.06666666667 cycles per frame.
Which matches up with codeslinger's reasoning: "According to game pan docs site the amount of clock cycles the gameboy can exectue every second is 4194304 which means that if each frame we update the emulator 60 times a second the each frame will execute 69905(4194304/60) clock cycles. This will ensure the emulator is run at the correct speed".
The text was updated successfully, but these errors were encountered:
https://github.com/torch2424/wasmBoy/blob/master/wasm/cpu/cpu.ts#L63
Currently it is timed by scanlines. But I think this is wrong.
The keyword here is "normally" suggesting that it can take more or less, and in Mode 1, it only takes a few cycles.
And the Realboy Blog Post states: "Because the Game Boy’s CPU is clocked at 4194304hz (that is, 4194304 cycles per second)". 4194304 / 60 = 69905.06666666667 cycles per frame.
Which matches up with codeslinger's reasoning: "According to game pan docs site the amount of clock cycles the gameboy can exectue every second is 4194304 which means that if each frame we update the emulator 60 times a second the each frame will execute 69905(4194304/60) clock cycles. This will ensure the emulator is run at the correct speed".
The text was updated successfully, but these errors were encountered: