Homebrew Anybody have a guide on making wii u homebrew apps?

[QuarkTheAwesome]

I have not been on the website for a while so thanks for the help. And about all that school stuff. I just started year 7. Evrybody is asking me to hacks stuff lol

I've been there - being known as a techie is both a blessing and a curse. Be sure to make friends with the IT guys! :3

 

[BullyWiiPlaza]

Nice topic, it really seems like some people are trying to get others up and running. I'm already proficient in many languages but I just don't feel like developing Wii U apps because there is really nothing I'm particularly excited about doing and it's pretty tedious to run code and when it crashes it's time to reboot, reload the exploit(s) and such so it's tiring

I've been there - being known as a techie is both a blessing and a curse. Be sure to make friends with the IT guys! :3

Once a lonely nerd loser then the coolest person around haha. That's the evolution of IT guys

 

[QuarkTheAwesome]

Nice topic, it really seems like some people are trying to get others up and running. I'm already proficient in many languages but I just don't feel like developing Wii U apps because there is really nothing I'm particularly excited about doing and it's pretty tedious to run code and when it crashes it's time to reboot, reload the exploit(s) and such so it's tiring

I've managed to convince the Wii U's exception handler to return execution to the main thread; turns out the OSContext you get passed is the actual one for the thread that crashed. Thus, you can just set the program counter to wherever you'd like. You just return 1 and away it goes. The problem I've found is that moving too far from the crash location absolutely destroys the stack so you can't return to HBL or anything; although since you're on the main thread you could make yourself an interactive exception handler (for instance).

Once a lonely nerd loser then the coolest person around haha. That's the evolution of IT guys

So very true

 

[BullyWiiPlaza]

I've managed to convince the Wii U's exception handler to return execution to the main thread

That's cool. While you're at it, you might as well make a debugger/breakpoints because it would be really useful to step through certain functions called by RPC for instance to better see what's going on/why it's not working how it should. Thank you for considering it

 

[enderzombie15]

I've been there - being known as a techie is both a blessing and a curse. Be sure to make friends with the IT guys! :3

:-) Of course I will. But the people are usually skaing for black ops mod menus and im like "i only do nintendo stuff but ill try" lol

 

[QuarkTheAwesome]

But the people are usually skaing for black ops mod menus and im like "i only do nintendo stuff but ill try" lol

@BullyWiiPlaza knows a lot about Black Ops (2) mod menus... on Nintendo consoles!

 

[enderzombie15]

@BullyWiiPlaza knows a lot about Black Ops (2) mod menus... on Nintendo consoles!

Thats cool!! I might get bo2 now

 

[JFalcon]

Think having some prior knowledge in a programming language would be wise. " Guides " aren't something that can just be whipped up and would require prior knowledge like I said, in order to be used.

 

[BullyWiiPlaza]

Thats cool!! I might get bo2 now

Not necessarily I'm going to share anything so don't get your hopes up (just as a disclaimer)

 

[enderzombie15]

Not necessarily I'm going to share anything so don't get your hopes up (just as a disclaimer)

Ok

 

[depaul]

You can learn C in 3 months or less. Just do some basic examples and you'll be fine. C++ is like C it just has some extra OOP functionalities (which aren't needed in the context of Wii U hacking).

 

[enderzombie15]

You can learn C in 3 months or less. Just do some basic examples and you'll be fine. C++ is like C it just has some extra OOP functionalities (which aren't needed in the context of Wii U hacking).

Ok. Ill probably do C then.

 

[YugamiSekai]

I think you should wait for the IOSU before developing for the Wii U...







But what do I know, I'm a 3DS dev.

 

[depaul]

Ok. Ill probably do C then.

But that doesn't mean that you will understand every C function. Even expert programmers know 10% or less about their programming language. They learn every time new thing: "learn it by doing it".

I think you should wait for the IOSU before developing for the Wii U...

@QuarkTheAwesome says there is no reason to wait everything is already possible with kernel exploit, except USB/permanent hack.

 

[enderzombie15]

I think you should wait for the IOSU before developing for the Wii U...


But what do I know, I'm a 3DS dev.

Maybe? I might try to do some simple stuff before IOSU (now) and try more advanced stuff later on when IOSU has been released.

Also, If i was to write something like print "Hello world" (probably not that easy to code it) how would i get it onto the wii u.

--------------------- MERGED ---------------------------

@QuarkTheAwesome says there is no reason to wait everything is already possible with kernel exploit, except USB/permanent hack.

Maybe I wont wait then. Yeah I wont wait.

 

[rw-r-r_0644]

You may be interested in that: https://github.com/rw-r-r-0644/WiiU-HelloWorld-Easy

You may want to look here: https://github.com/rw-r-r-0644/WiiU-HelloWorld-Easy
I did this yesterday for some reason (maybe just because it was fun to make ); basically (it's a W.I.P.) it tries to provide a library to make homebrew as easy as a windows constole application. Many things do not work yet, but this is the main.c file:

uprintf("Hello World!");
while(1) {
    updatePressedButtons(); //Update buttons state
    if(isPressed(VPAD_BUTTON_HOME)) break; //Check if home is pressed
}
uprintf("Exiting...");
return 0;

It's quite easy. Anyway, as I said, it's still a W.I.P. and probably would need to be implemented as proper libraries (and moved to WUT for future wii u develops).
Also '\n' (new line) seems to still be not working (I'm trying to fix that, it's just because OSScreenPutFontEx doesn't seem to care about new line) - Fixed (in a bad, hacky way)
You can call any wii u function without find_export and a super-commented example will be available soon(tm?) - Now available at: https://github.com/rw-r-r-0644/lib_easy_example__UClick. As of now I'm still trying to fix things and adding more functions

 

[QuarkTheAwesome]

I've said this several times, and I'll say it again:

An IOSU exploit is completely unnecessary for developing homebrew.

While the methods of loading homebrew will change, from a programming standpoint it'll be identical: The absolute worst that could happen is you need to change your Makefile a bit, or (optionally) add USB support. The kernel exploit already gives us all the power of a retail game and the Wii U doesn't have much more to offer than that. I've explained this a bit more over here, but to sum it up IOSU total control isn't worth waiting for.

 

[BullyWiiPlaza]

Yeah, those kiddies are clueless and clutter the forum with this stupid "IOSU will change everything" mentality:

1 w1ll b3 4bl3 70 d3v3l0p 1n54n3 7h1n65 0nc3 105u 15 0u7. n0 n33d 70 574r7 n0w wh1l3 17'5 h4rd

Not really but you'll learn your lesson eventually when suddenly it's still all the same and you still can't or won't develop anything

 

[QuarkTheAwesome]

Yeah, those kiddies are clueless and clutter the forum with this stupid "IOSU will change everything" mentality:

1 w1ll b3 4bl3 70 d3v3l0p 1n54n3 7h1n65 0nc3 105u 15 0u7. n0 n33d 70 574r7 n0w wh1l3 17'5 h4rd

Not really but you'll learn your lesson eventually when suddenly it's still all the same and you still can't or won't develop anything

I like to think that they're simply misinformed from the hype machine and overall glorification of the IOSU exploit.
We just witnessed it happen, too: remember that enderzombie probably didn't know a huge amount about how the Wii U was put together before starting this thread; and here's the whole userbase excited about IOSU and some developers talking about its power (still no idea where you all got that idea from ;D ) while the other developers don't really mention it: what would you conclude? I'd certainly think twice; it's like if someone pitched you browserhax homebrew during the lead-up to kernel.
For this reason, I reckon the best solution is to provide the correct information to the best of my ability. Everyone has the potential to become a great developer given the resources they need, which is why I have an issue with disregarding people who are really just misinformed. I still hope we can find a way to be excited aboit exploits without having developers as our collateral damage.