789
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Oct 2024
789 points (98.1% liked)
Games
32161 readers
1237 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
An FPGA seems like a lot of effort, but an SNES emulator running on a Raspberry Pi seems like it may have been a better option IMO.
I am sure that Nintendo is using FPGA for internal R&D, so they have people capable of writing cores for FPGA. Add to that the fact that Nintendo has all the schematics and detailed information about the original hardware and designs.
Yes, a FPGA would have been work, but not lots of work for them. And we are speaking of 8 and 16 bit hardware, that is very small and limited hardware.
Besides that: Windows can run on a Raspberry PI, so maybe the emulator on Windows used by Nintendo is already using that. Who knows?
Making an FPGA for all of this is far more work than pulling an open source emulator and sticking it on a machine...
Yes, but Nintendo did neither the one nor the other.
This looks a whole lot like it's probably some random emulator they grabbed and full screened?
Why should they do that? They already have their own SNES emulator with Canoe (used for example on the SNES Classic Mini). It is much more logical to assume that they compiled Canoe to run on Windows for this exhibition.
I take it you've never ported an application to a different platform running on a different hardware architecture before.
I have and if the code is well written and prepared then such a port can be done with just a recompilation for the different platform. Yes, often it is not that easy but the developers at Nintendo are neither dumb nor incompetent.
You're making my point for me though. Each of the other things you've suggested is more work than requires more expertise. Popping up an emulator on an existing box and dumping a ROM in there is something an intern can do.
All of these other things can be done, but they're not as quick and simple, and that's why we're seeing this in the first case - Nintendo went with a quick and simple solution, and someone found a bug (it still plays Windows noises).
You have your view at the world, a view where everyone is lazy on every level, and I have mine. Thank you for the nice conversation and have a great day!