- Joined
- Aug 21, 2019
Kirkzz apparently has the Everdrive working on Analouge 3D already. If you order a new one, it will ship with the new firmware, but existing carts will require an actual N64 to upgrade it.
The newest versions of the Everdrive 64 have an FPGA in them themselves, and Kirkzz developed a super accurate NES core for it. I wonder if that will work on the Analogue 3D. Then you'd have an FPGA NES running on an FPGA N64.
I only notice it on games I know really well. Like, I cannot play Mario World in a shitty emulator. Whenever I do Yoshi's Island 1 for example, I always hang onto the shell you can boot up to get the 1-up, jump between the boxes a screen or two over, kick the shell upwards as I jump between them to get the fire flower out, grab the fire flower, boot the shell and then shoot the shell and get a coin when it ricochets back. I can do that 100% of the time on an actual SNES or GBA or a really accurate emulator like bsnes, but it's hit or miss on the emulator in the SNES classic.
If I was playing Glover or Iggy's Wrecking Balls for N64, I probably wouldn't know the difference if there was input delay, but if I was playing something I've played to death on an actual N64 like one of the AKI wrestling titles, Mario Kart or Mario 64, I bet I'd notice the lag. Especially with the wrestling games requiring perfect timing for reversals and stuff.
*Edit* The Ganondorf and Phantom Ganondorf fights in Ocarina of Time where you hit the magic balls back and fourth is another good example of something that gets harder to do when the emulator has a lot of input lag.
The newest versions of the Everdrive 64 have an FPGA in them themselves, and Kirkzz developed a super accurate NES core for it. I wonder if that will work on the Analogue 3D. Then you'd have an FPGA NES running on an FPGA N64.
Trigger Warning: AutismIt would be interesting to know how FPGA stands up to emulation, because that was another piece of curiosity that led me towards wanting a 3D. If you've had any time testing that out yet, I'd love to know.
I was a very young child when I owned my N64 initially and it's kinda difficult for me to tell where the accuracy ends and emulation issues begin, especially as some of the emulation issues have been smoothed out over recent years. If you do end up testing it out at all, I'd like to know how the Ares emulator stacks up, considering its whole premise is high accuracy.
I only notice it on games I know really well. Like, I cannot play Mario World in a shitty emulator. Whenever I do Yoshi's Island 1 for example, I always hang onto the shell you can boot up to get the 1-up, jump between the boxes a screen or two over, kick the shell upwards as I jump between them to get the fire flower out, grab the fire flower, boot the shell and then shoot the shell and get a coin when it ricochets back. I can do that 100% of the time on an actual SNES or GBA or a really accurate emulator like bsnes, but it's hit or miss on the emulator in the SNES classic.
If I was playing Glover or Iggy's Wrecking Balls for N64, I probably wouldn't know the difference if there was input delay, but if I was playing something I've played to death on an actual N64 like one of the AKI wrestling titles, Mario Kart or Mario 64, I bet I'd notice the lag. Especially with the wrestling games requiring perfect timing for reversals and stuff.
*Edit* The Ganondorf and Phantom Ganondorf fights in Ocarina of Time where you hit the magic balls back and fourth is another good example of something that gets harder to do when the emulator has a lot of input lag.
Last edited:






