RetroGaming

19908 readers

673 users here now

Vintage gaming community.

Rules:

Be kind.
No spam or soliciting for money.
No racism or other bigotry allowed.
Obviously nothing illegal.

If you see these please report them.

founded 2 years ago

MODERATORS

Xylinna@lemmy.world

Tenthrow@lemmy.world

gts@lemmy.world

177

VIDEO: Why is Nintendo 64 emulation still a broken mess in 2025? (www.youtube.com)

submitted 2 days ago* (last edited 2 days ago) by lIlIllIlIIIllIlIlII@lemmy.zip to c/retrogaming@lemmy.world

87 comments fedilink hide all child comments

The Nintendo 64 has always been a difficult machine to emulate correctly. But in 2025 - we should be well and truly past all of it right? Not exactly. Issues with Plugins, performance, graphical glitches, stutters. Unless you have a very powerful machine, these are common things many of us will run into when emulating the Nintendo 64. But why? And Is there any hope for fast, accurate N64 emulation in 2025 and beyond?

you are viewing a single comment's thread
view the rest of the comments

[–] kadup@lemmy.world 1 points 4 hours ago

on the accuracy of the core on the FPGA.

Or in other words, FPGAs aren't miracle hardware clones and depend on the quality of their programming. Exactly as I said, got it.

Your comparison of GBA on dsi is kinda like saying “my dos games didn’t work well on my windows 2000 computer” same cpu sure, but OS and hardware ‘locations’ aren’t necessarily the same.

Which is why I mentioned it's an hypervisor, not running as if it were natively supported. It's more analogous to original hardware than a FPGA, though. Your analogy to DOS and Windows 2000 however shows you really do not understand how GBA2Runner or FPGAs work in general.

Your comment is got any point or it's just these two incoherent sentences?