Having been a web dev for 10 years and now Deep Learning / ML, I've never even dabbled in emulators or even read their code, and I find it inspiring that there's entire fields of programming that I know little about and can explore later.
Our field is truly amazing!
As a 15-year web dev- was that transition a natural one? Relatively easy? Profitable?
I was able to transition from web dev to aerospace software while taking care of a family.
Boy I want to read that article
> In basic terms, Disney Infinity and Cars 2 do a very specific amount of writes to lower MEM1, where a lot of really important data is stored. But, it writes just enough that the CPU doesn't flush it to MEM1; it remains in the CPU L1/L2 caches. It then tells the CPU, nevermind and invalidates the CPU cache. Thus, even on a hacked Wii this would do exactly nothing; it's specifically targeting a weakness in emulators.
> Emulating the CPU cache in Dolphin would likely slow-down Dolphin by a factor of ten or more. While we prefer not using hacks to "fix" games, we found it to be permissable in this case due to how specialized of an issue it is. Even if the L1/L2 caches are implemented in the future (which is definitely a possibility,) it will likely be something only used for testing, and thus this hack would remain so that people could actually play these two games. It's a compromise, one that no one is entirely happy with, but the game behavior necessitated it in this case.
Honestly a Wii really is an upclocked GC with a coprocessor stapled on the side handling new (and a lot of old) I/O.
For a chip made in 1999, they certainly got their mileage out of it.
You could even run GabeCube games on the Wii, and it didn't require Nintendo to ship almost an entire GameCube on the board like Sony did with PS2 emulation on the PS3.
Although reading this article I wonder how Nintendo handled the ARAM situation and the like on the Wii when playing GameCube games?
The hardware could choose to use the bottom 16MB of MEM3 as an ARAM equivalent. That was actually the source of one of the first attacks. That is putting tweezers on that RAM chip, shorting the address lines and accessing the high part if that RAM while in GameCube mode.
I guess it's just a byproduct of too much WhatsApp / IM in general, which introduces bad practices for long form writing, and also a lack of editing review.
That's a minor, minuscule annoyance in an otherwise very interesting article :)