You dont know TAS (Tool Assisted Speedrun) ?Uh... "frame advance features"? Can you elaborate?
You dont know TAS (Tool Assisted Speedrun) ?Uh... "frame advance features"? Can you elaborate?
I think you are asking way too much for GameYob.You dont know TAS (Tool Assisted Speedrun) ?
I know pc-based emulator, and im not asking to want, i only want to know if is possible or not on 3dsI think you are asking way too much for GameYob.
If you want to do TAS, you should use PC-based emulators, don't expect a console emu to implement those kind of features.
Not sure about that. If we consider he only want a frame advance feature (non for tas use) it is litterally slowing down a 60fps emulated output to a frame by frame randerer. Only useful for tas presision tricks ingame, but useless for end user experience.Everything is possible, but it wouldn't run at fullspeed so it would be pretty useless (not to mention it would probably require a cycle-accurate version of the emulator).
I have a request: while playing Pokemon Crystal, the time and date got messed up somehow; I was wondering if there's a way to sync the game clock to the 3DS clock.
All emulators I've ever tried do this because the actual cartridges have batteries in them that make the clock inside the cart run even when you're not playing, the clock keeps ticking even if you take the cart out of your GameBoy. Of course a rom file couldn't do the same thing as they're a file and not a physical thing.
Technically, this could be worked around with game-specific code in the emulator, but I don't know if anyone actually ever bothered to do so.
Actually, it should be syncing to the 3DS clock already. The clock is accessed through the MBC (cartridge specific hardware for managing ROM/RAM banks, etc.), which the emulator gets data from the 3DS clock for.
To the poster of the issue: Can you elaborate on exactly how it got messed up? Reset to a certain value, off from actual time, etc.?
The game's clock skipped ahead about two days, as well as about 12 hours ahead in time. I wasn't sure what happened, since I made sure it was correct when I first started the save file.Actually, it should be syncing to the 3DS clock already. The clock is accessed through the MBC (cartridge specific hardware for managing ROM/RAM banks, etc.), which the emulator gets data from the 3DS clock for.
To the poster of the issue: Can you elaborate on exactly how it got messed up? Reset to a certain value, off from actual time, etc.?
Do we know how frequently the download for the compiled build is updated? According to Github there has been updates as soon as 11 hours ago at the time of writing but there's no clue as to how old the compiled builds are.
I ran it ninjahax first with Super Mario Bros DX to trade, but the game became in responsive a just flashing a red x over and over. I had to reset.If anyone has two 3DS's and wants to test IR support, I uploaded a test build. It should work like normal GBC IR, requiring you to line up the IR ports on both 3DS's. May or may not actually work, but I can't test it myself as I only have a single 3DS.
https://www.dropbox.com/s/f19ns16z08g42v9/GameYob_test.zip?dl=0
I assume the red X is part of the actual game? And, GameYob cannot use sound from Ninjhax while in emuNAND due to the libkhax errors mentioned. Not on a N3DS, anyway.I ran it ninjahax first with Super Mario Bros DX to trade, but the game became in responsive a just flashing a red x over and over. I had to reset.
On my New 3ds in gateway mode 9.0.0.20U I get a a khaxinit error saying unknown kernel version k=02310000 f=02310000 n=1, also sound didn't work and the error message spammed out continuously.
No error on my old 3ds in gateway mode 9.0.0.20U.
I also tried it as a cia. The Cia did not emit any khaxinit error, but otherwise was the same.
Did I need a gbc bios or anything?