Toggle sidebar

Hacking Homebrew Browser Bricked my vWii?

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 waffleman1230
Start date Nov 22, 2014
Views 1,931
Replies 3

waffleman1230

New Member

Newbie

Level 1

Nov 22, 2014

I tried running Homebrew Browser on my vWii, and it might have been bricked. It has a screen with a crash, and an "Exception (DSI) occurred!". Is there anyway to restore/get back my vWii or Wii U? Or am I SOL?

Hiccup

Well-Known Member

Member

Level 10

Nov 22, 2014

Is this on boot-up of the vWii, or has this just happened to you and you haven't restarted?

The Real Jdbye

Le derg

Member

Level 26

Nov 22, 2014

Hiccup said:
Is this on boot-up of the vWii, or has this just happened to you and you haven't restarted?

I'm thinking the latter. There's no way Homebrew Browser could brick his Wii, but it does tend to be a bit unstable and I've seen that crash lots of times in that one and other apps.

Hiccup

Well-Known Member

Member

Level 10

Nov 22, 2014

It certainly does crash a bit. But not so much that it is unusable. Just try not to press too many buttons at the same time, especially when it is loading. You may have to start it a few times until it starts to work properly though.