D
Deleted User
Guest
someone ported it to a printer...exactly, because the Doom1 engine is the single most well understood gaming engine in videogaming, i think someone even managed to port a really low res version to the NES.
someone ported it to a printer...exactly, because the Doom1 engine is the single most well understood gaming engine in videogaming, i think someone even managed to port a really low res version to the NES.
Unfortunately, it is the driving factor. There's more games to pirate than there is homebrew developed. Anyways, I know that an unofficial SDK is probably in the works and is partially working, but it's very convoluted to set up and get running. The best way is to use the Wii U's SDK if you have access to it and the compilers, otherwise, you're gonna have to be real patient. After all, ctrulib (3DS) is still being actively worked on, and when the 4.X MSET exploit was discovered, people had very limited homebrew that wasn't at all optimized and was written mostly in assembly.Piracy should be the cherry on top of the Homebrew sundae, not the driving factor.

I hate to be a ungrateful party pooper, but after we got @NWPlayer123 's exploit what most devs where afraid of is exactly what happened, it was used to pirate and cheat, nothing else. where's the next big mari0 port? what happened to playing Super Mario War on every console we could port it to? why hasn't someone done DOOM yet? It'd be awesome to be able to switch weapons to exactly what i want using the sides of the touchscreen with a big ole map dead in the center. where did that GBATemp spirit go? is it hiding, scared away by a early release leak?
I could care less about piracy, i want to get the most out of my wii u with emulators, and homebrew.
waiting on that fateful retroarch wii u day
I'm waiting hopefully for KODI or any media player to access my NAS library and enjoy some TV shows on the GamePad in my bed.
....Emulators are Piracy lol

Does your pi have a gamepad? XDAt this point in time with how inexpensive and readily available Raspberry Pis, Banana Pis, Ardunios, and other SoC boards are it really doesn't make any sense what-so-ever to wait around for something like the Wii U to get these apps as homebrew other than the simple fact of saying that you have it.
I'm completely aware of what I could do. I'm already running a Rasp with KODI but having it on the Wii U is some kind of "next stage" for me as it lowers the amount of devices that I need on my TV plus I can view stuff on the Gamepad.You could do both of these things today by going down to your local hobby store, Fry's, Amazon, or checking Craigslist and picking up a Raspberry Pi. The Raspberry Pi Zero, which sold for $4USD, was more than capable of running KODI and RetroArch/EmulationStation better than your Wii U ever will. At this point in time with how inexpensive and readily available Raspberry Pis, Banana Pis, Ardunios, and other SoC boards are it really doesn't make any sense what-so-ever to wait around for something like the Wii U to get these apps as homebrew other than the simple fact of saying that you have it.
What about the Virtual Boy?There's more games to pirate than there is homebrew developed.
the first public was released 2 months from being LAST YEAR, the Vita had more going on within the first day than the entire Wii U's hacked lifespan.The exploit has been out for barely a little more than a week. I get the impression you are not a developer/engineer or you would understand that even building simple apps can take time. Especially when it is in a closed ecosystem that you have to create an exploit to even get access to because you do not own a proper devkit.
-MEGA SNIP-.
the first public was released 2 months from being LAST YEAR, the Vita had more going on within the first day than the entire Wii U's hacked lifespan.
the exploitability of 5.3.x was announced almost a solid month before Nintendo patched it and the DNS tools to prevent updates where released roughly the same week it was patched, nice try though.Released for non-current versions of the Wii U firmware. With the Wii U's auto updating feature the amount of developers and users that would have had an exploitable version at the time were a lot less than they are now that an exploit is available up to 5.5.1. Not everyone knew how to block updates or that it was even advised to block updates. Logic would dictate that since the previous exploit was released for non-current versions of the firmware at the time that all new users/developers that would have learned about it would have learned about it after their machine auto updated. Things will come, though just like the release of the current exploit, they might not come as fast as many would like.
The good news is that now that a kernel exploit is released for the current firmware, if you don't want to wait around for someone else to bring homebrew to the Wii U, you have more tools available to develop something yourself - which is way more productive than complaining about it.![]()

While I totally agree that "couldn't" makes a lot more sense than "could", in UK English people say "I couldn't care less" whereas in US English it's perfectly normal to say "I could care less" even though when you think about it, what they're saying doesn't make any sense at all since it implies they care.You couldn't care less

Sure it is, I could port Yeti3D just as easily with the Homebrew launcher as I could from app boot from the home menu, you still have access to all the same resourcesBecause "kernel" is not enough to develop such great things, that's why @smealum used IOSU to develop on Wii U.



