Toggle sidebar

Homebrew Wii U wii menu less redundant

Quake 3 is being ported to Wii U

Mayo1990 · 2026-07-10T11:02:29+00:00

I spent my last few months porting Quake 3 Arena to most consoles that didn't have a port yet (Wii, PS3, PS4, Xbox One), but my main roadblock was always the Wii U. Thanks to all the experience I gained from my previous ports as well as a new toy I'll release later I decided to give it another shot and I got much farther this time. The port is far from playable at the moment, but I lifted most of the roadblocks I ran into last time, which made all this very promising. Since this is my most important project so far, I'd like the first release to be very, very polished. However, I'm still unsure about which name I should pick this time around, so I'll pick the one with most votes the moment I have to do the release. Main features Crossplay with other Quake 3 clients, either via LAN or online Gamepad + Pro Controller support as well as other controllers through Bloopair Mod support Open Arena, Team Arena and CLASSIC (specific build to crossplay with Dreamcast clients) support. Installation This homebrew can only run under Aroma. Place ioquake3_wiiu.wuhb for Quake III Arena, ioquake3_ta_wiiu.wuhb for Team Arena, ioquake3_oa_wiiu.wuhb for Open Arena and ioquake3_classic_wiiu.wuhb for Classic inside wiiu/apps/, then follow the instructions below where to place the required files. Quake III Arena Place pak0-8 in /quake3/baseq3/ from your own Quake III Arena copy. Open Arena Place all the pak files in /quake3/baseoa/ from your own Open Arena copy. Team Arena Place pak0-3 in /quake3/missionpack/ from your own Team Arena copy. Quake 3 Classic Place pak0-8 in /quake3/baseq3/ from your own Quake III Arena copy, as well as dc-mappack.pk3 inside quake3/baseq3/ Latest release Pro and Cons compared with each of my ports: Wii + More stable framerate + Mods can load more reliably + Higher resolution, higher quality models and textures + Team Arena support + Automatically sets Player name based off User's Mii (with limits, due to characters limitations) + XInput support thanks to Bloopair - No mouse and keyboard support - No additional video modes PS3 + More stable framerate + higher quality models and textures, but not as noticeable as Wii's + XInput support thanks to Bloopair - No native OSK (for now) for text inputs - No mouse and keyboard support PS4 + Faster boot times + XInput support thanks to Bloopair - No native OSK (for now) for text inputs

Thread starter Dominator211
Start date Nov 23, 2016
Views 1,354
Replies 3

Dominator211

JFK's Jelly Donut

Member

Level 13

Nov 23, 2016

As I am typing this I am transferring my data from the wii to the Wii U and I've heard a few rumors that the V wii on the Wii U is very less redundant then the NAND on the Wii is this true

Irastris

Well-Known Member

Member

Level 6

Nov 23, 2016

Dominator211 said:
As I am typing this I am transferring my data from the wii to the Wii U and I've heard a few rumors that the V wii on the Wii U is very less redundant then the NAND on the Wii is this true

You're gonna need to better define what you mean by "redundant".

If by redundant you mean unnecessary, then no it's not. You need it in order to boot original Wii games.

Dominator211

JFK's Jelly Donut

Member

Level 13

Nov 23, 2016

what i meant was is it more likely to brick than the actual wii nand

GerbilSoft

Well-Known Member

Member

Level 14

Nov 23, 2016

That has less to do with "redundancy" and more to do with installing non-vWii CIOSes in slots lower than 200. Non-vWii CIOSes can brick Wii mode due to hardware differences (though this might be fixable with wuphax now).