Hacking Question about Wii U Emulation
- Thread starter Noctosphere
- Start date
- Views 57,837
- Replies 127
- Likes 1
Sounds like a job for the community once the emulator is released. For now I would prefer to focus my time on actual development.What games in its current build, runs at least the intro? besides you can post more videos of other games? (New Mario Bros U, DK Tropical Freeze for example, in the current build). With fraps showing the fps in realtime. Would be quite interesting and exciting, in addition to increasing your credibility.
There isn't really anything worth sharing. Some register documentation stuff, but thats hardly relevant to homebrew developers.
So, just out of curiosity, are you actually a dev or just a well read tester? I got the vibe of the latter before but that doesn't seem to be the case?...
If you have a spare minute and wouldn't mind, I would much appreciate such information being published (on wiiubrew, I suppose) regardless
I am a dev. Read my response to NWPlayer123 here.
Of course. I'll publish some stuff over at wiiubrew in the coming days.If you have a spare minute and wouldn't mind, I would much appreciate such information being published (on wiiubrew, I suppose) regardless
The syscalls you posted on wiiubrew are accurate, so you certainly know what you're doing.
However, that poses a completely new problem. You claimed to have started this project 2 years ago, which would be late 2013.
Back then, there was no public way to decrypt games, system applications or even the CafeOS kernel.
This means one of the following things:
a) You got the keys or decrypted binaries from fail0verflow and started from there;
b) You reached out to some ODE team and asked them for decrypted game dumps (VENOM began distributing game dumps as early as May 2013);
c) You have your own set of exploits and already dumped any binary or key needed.
I'm not trying to accuse you of anything, I'm just interested in knowing how much access you have inside the Wii U system.
he may have started with writing the basic PPC interpretor and other low level stuff.citra started the same way.
During the first year development was stagnant most of the time due to the reasons you mentioned. We were able to dump memory via the browser which allowed us to look at the userspace memory layout and the system libraries. It ended with us loading the dumps 1:1 into flat memory and trying to execute code from random modules. Eventually we gave up and took a break until somewhere mid-2014 when the first leak relevant for emulation appeared. But even then we didn't really make much progress. Development speed increased significantly once the common key was leaked. (We had code to read Wii U images already earlier but we lacked the common key and weren't able to dump it)
Last edited by Exzap,
Have you considered going open source? Rather than splitting the effort like whats going on now, what about trying to work together? Personally I'd be greatly interested in offering my skills for writing code, especially since I feel I could learn a great deal about the architecture in doing so.
-palantine
-palantine
Last edited by palantine,
Just to add my 2-cents to this, I believe emulators are extremely important in terms of preserving the history of the games medium. It's awful when a closed-source emulator is discontinued by it's author, and all the work that went into understanding and preserving that system goes to waste and has to be redone by others. So if you choose to remain closed, you should at the very least give serious consideration to opening your code when the day comes that you are ready to step away from it.
That's actually a plausible explanation. Thank you for clarifying.
Another Wii U emulator? That's great, i'll wait until it can run Smash Wii U (1-3 years maybe?)
It does work yet, it just doesn't do graphics
Similar threads
