I know that the Wii U cant run 3DS games, but what exactly is preventing it?
In theory you would think that the Wii U would be more than capable of running the games, but since that isn't the case does anyone here know why not?
Posted Sep 15, 2020, 8:09 PM UTC
[deleted]
as someone who knows little about how emulation works it seems hard to believe, but yeah im sure people have put hours into trying it before. thx for taking the time to spell it out for me
edit: thx to everyone who responded, it helped me a lot with understanding exactly how emulation works
N64 still isn't emulated perfectly on many systems.
[deleted]
Not really, I remember, if I am correct, desert strike wasn't 100% emulated correctly and had an issue with the shadows. I know it is rom to rom basis, but 100% emulation in the SNES wasn´t perfected in 20 years.
Think of it like this: The 3DS is like a small car. The Wii U is like a pickup truck.
Imagine trying to put the car - and its passengers - into the bed of the pickup truck and THEN trying to drive it to your destination. You'd be lucky if you could even get the pickup to move! It doesn't matter that the truck is so much more powerful than the car; it wasn't made to carry the entirety of the car itself while doing its job.
That's the kind of performance problem software emulation faces, to oversimplify it a bit.
When a CPU does an operation, ideally it happens as fast as the CPU can manage. When there's an emulator involved, the CPU is working to recreate the emulated hardware's behavior, so it has a workload that is several orders of magnitude higher than the original system. Multiple operations are being done on the real CPU to produce a single operation on the emulated CPU. It's never just a matter of one machine being more powerful than the other; you need several orders of magnitude more power to do it well.
There's certain situations where there's exceptions to this (e.g. PSone Classics on PSP/Vita) but in general, emulation is a hefty workload for a CPU to take on.
What about if you had the source code?
you could port the game to run natively, which needs a lot less resources, but it's way more complicated. The Wii U and the 3DS have very different hardware
Think about it like this- in order to run 3DS games on a Wii U, the Wii U processor needs to create a virtual 3DS processor capable of running 3DS CPU instructions, which takes a lot of work.
One way of looking at it is . Look at emulation as 2 different things, one is translation where the software has to read the instructions on the binary and translate into something that can be executed on that machine and the other is execution itself..... its like asking someone to read a book in english while telling tje story to someone in japanese at the same time, taking in consideration linguistic expressions and jokes . Not all emulators goes for perfect emulation speed, but they get so close that you cant tell . Also emulators bot only translate the code, but also music, trxtures and model files... most complex consoles, like the 3ds, even need system calls (like open files) to be emulated to some degree. Emulators are some of the most complex type of softwares out there (sure, it depends on what you are emulating)
When you emulate you need more power than the system youre emulating. Youre essentially running a computer within a computer. At the same time it still needs to run the Switch hardware
The processor itself would be powerful enough but as the 3DS is on ARM and the Wii U on PowerPC, it makes emulating the first one on the second much more difficult.
hmmmmmm, that makes me wonder because I know that it was discovered that Wii u had a arm processor responsible for system stuff, I might be wrong tho