rich_is_bored@Posted: Tue Aug 26, 2008 3:06 am : http://code.google.com/p/wiidoom/Installation for use with Homebrew Channel...
- Download zip from link above
- Extract zip to desktop
- Copy apps folder to SD card
- Copy prboom folder to SD card
- Open prboom folder on SD card and delete freedoom.wad
- In the same folder place a copy of doom.wad or doom2.wad
This project is in it's infancy but it's playable.
Some things I've noticed that need fixed...
- No aiming at the screen. Aiming is controlled via left and right on the dpad.
- Player movement occasionally stalls. Just release the joystick and resume play.
- During start up sometimes you have to unplug and reinsert the nunchuck.
- The brightness is way too high.
- Sounds are being played at the wrong sample rate. Everything is high pitched.
- There is no music.
- The menus and dialogs need to be remapped. At present some parts of the menu are inaccessible or cannot be closed.
I've played through a few levels in the retail version of Doom. I'm going to test out some other wads with the port and post and update. From what I understand Doom 2 also works but I'd like to see if the same holds true with Heretic and Hexen.
rich_is_bored@Posted: Tue Aug 26, 2008 6:28 am : I tried out using heretic.wad. No joy.
Out of curiosity I've been looking over the source and I've run across the code that checks wad files so here are the ones that will work...
Code:
"doom2f.wad",
"doom2.wad",
"plutonia.wad",
"tnt.wad",
"doom.wad",
"doom1.wad",
"doomu.wad",
"freedoom.wad"
Deadite4@Posted: Tue Aug 26, 2008 1:00 pm : Interesting. As for the Homebrew Channel, has it ever been broken by any of the firmware updates? Thats usually what has prevented me from trying it out.
goliathvt@Posted: Tue Aug 26, 2008 1:08 pm : The upkeep of Homebrew is quite solid and "if" a Wii update breaks anything, they usually have a fix out within hours or days.
rich_is_bored@Posted: Fri Aug 29, 2008 11:17 am : I found a fix for the brightness problem.
Doom had a gamma adjustment that still exists in this port but it set to a high level by default hence the reason why everything is washed out. Now it's possible to lower this value by modifying the key/bindings in the options but given the way controls have been hacked in (I'll comment more on that in a moment), it's a pain in the ass.
You have to bind the key to a button that's responsive, then cycle through the various levels until your satisfied, then reassign the button to what it was before. Just don't use the 1, 2, or left/right dpad buttons as they are used to navigate the menus.
The worst part about doing it this way is that the settings aren't saved so you'll have to repeat this process every time you launch the game.
I've got a better solution but you have to be willing to setup a tool chain to compile the source code. And given the technical nature of that I'm not going to elaborate on it much other than to say everything is documented at
http://www.wiibrew.org.
Once you have a tool chain setup properly all you have to do is edit line 336 of m_misc.c from ...
Code:
{"usegamma",{&usegamma},{3},0,4, //jff 3/6/98 fix erroneous upper limit in range
... to ...
Code:
{"usegamma",{&usegamma},{0},0,4, //jff 3/6/98 fix erroneous upper limit in range
You can also uncap the framerate by editing line 338 from ...
Code:
{"uncapped_framerate", {&movement_smooth}, {0},0,1,
... to ...
Code:
{"uncapped_framerate", {&movement_smooth}, {1},0,1,
I've emailed the author so he's aware of the fixes and they'll be implemented in the next release. But that may be awhile as he's working on getting IR support working.
As for the way controls are implemented right now, from what I've seen in the source code it looks like all the Wii controls are being mapped to keyboard events. It's playable that way but given the port already has code to manage joystick control, that would seem to me to be the better place to make changes.
I may have a go at that later. It might be a good learning exercise.
rich_is_bored@Posted: Tue Sep 02, 2008 1:12 pm : Small update. I've been tinkering with the source code and I've resolved pretty much everything. I'm not proud of the way I fixed some things but it works and serves my needs.
I've remapped the Wii controls to the proper joystick input. Movement doesn't seem to stall anymore. I also extended it to handle more buttons and analog input. The strafe toggle button is inverted so that strafe is on by default.
IR is also now half-implemented. It controls turning but I've done nothing about aiming. It's a little wonky because I'm only dealing with the IR directly. I'm not doing any prediction so if the remote looses sight of the sensor bar it's assumed that you want to keep turning.
I've fixed the menu navigation. Controls are standardized now. A to select, B to back out, ect... One interesting thing I found was that the home button is detected as the esc key but nowhere in the code is this evident. I assume one of the libraries is responsible.
I've forced all sounds to play at 11025hz. This seems to fix the chipmunk audio problem although I don't know if all the sounds in Doom are 11025hz.
And the fixes I talked about earlier are implemented. Brightness has been adjusted and the framerate has been uncapped. I'll upload the source when the author gives me permissions to the project on Google Code.
Download
rich_is_bored@Posted: Wed Sep 03, 2008 6:12 am : I've committed my changes to the repository. Everything should make it into the next build.
rich_is_bored@Posted: Wed Sep 10, 2008 10:15 pm :
rich_is_bored@Posted: Tue Aug 26, 2008 3:06 am : http://code.google.com/p/wiidoom/Installation for use with Homebrew Channel...
- Download zip from link above
- Extract zip to desktop
- Copy apps folder to SD card
- Copy prboom folder to SD card
- Open prboom folder on SD card and delete freedoom.wad
- In the same folder place a copy of doom.wad or doom2.wad
This project is in it's infancy but it's playable.
Some things I've noticed that need fixed...
- No aiming at the screen. Aiming is controlled via left and right on the dpad.
- Player movement occasionally stalls. Just release the joystick and resume play.
- During start up sometimes you have to unplug and reinsert the nunchuck.
- The brightness is way too high.
- Sounds are being played at the wrong sample rate. Everything is high pitched.
- There is no music.
- The menus and dialogs need to be remapped. At present some parts of the menu are inaccessible or cannot be closed.
I've played through a few levels in the retail version of Doom. I'm going to test out some other wads with the port and post and update. From what I understand Doom 2 also works but I'd like to see if the same holds true with Heretic and Hexen.
rich_is_bored@Posted: Tue Aug 26, 2008 6:28 am : I tried out using heretic.wad. No joy.
Out of curiosity I've been looking over the source and I've run across the code that checks wad files so here are the ones that will work...
Code:
"doom2f.wad",
"doom2.wad",
"plutonia.wad",
"tnt.wad",
"doom.wad",
"doom1.wad",
"doomu.wad",
"freedoom.wad"
Deadite4@Posted: Tue Aug 26, 2008 1:00 pm : Interesting. As for the Homebrew Channel, has it ever been broken by any of the firmware updates? Thats usually what has prevented me from trying it out.
goliathvt@Posted: Tue Aug 26, 2008 1:08 pm : The upkeep of Homebrew is quite solid and "if" a Wii update breaks anything, they usually have a fix out within hours or days.
rich_is_bored@Posted: Fri Aug 29, 2008 11:17 am : I found a fix for the brightness problem.
Doom had a gamma adjustment that still exists in this port but it set to a high level by default hence the reason why everything is washed out. Now it's possible to lower this value by modifying the key/bindings in the options but given the way controls have been hacked in (I'll comment more on that in a moment), it's a pain in the ass.
You have to bind the key to a button that's responsive, then cycle through the various levels until your satisfied, then reassign the button to what it was before. Just don't use the 1, 2, or left/right dpad buttons as they are used to navigate the menus.
The worst part about doing it this way is that the settings aren't saved so you'll have to repeat this process every time you launch the game.
I've got a better solution but you have to be willing to setup a tool chain to compile the source code. And given the technical nature of that I'm not going to elaborate on it much other than to say everything is documented at
http://www.wiibrew.org.
Once you have a tool chain setup properly all you have to do is edit line 336 of m_misc.c from ...
Code:
{"usegamma",{&usegamma},{3},0,4, //jff 3/6/98 fix erroneous upper limit in range
... to ...
Code:
{"usegamma",{&usegamma},{0},0,4, //jff 3/6/98 fix erroneous upper limit in range
You can also uncap the framerate by editing line 338 from ...
Code:
{"uncapped_framerate", {&movement_smooth}, {0},0,1,
... to ...
Code:
{"uncapped_framerate", {&movement_smooth}, {1},0,1,
I've emailed the author so he's aware of the fixes and they'll be implemented in the next release. But that may be awhile as he's working on getting IR support working.
As for the way controls are implemented right now, from what I've seen in the source code it looks like all the Wii controls are being mapped to keyboard events. It's playable that way but given the port already has code to manage joystick control, that would seem to me to be the better place to make changes.
I may have a go at that later. It might be a good learning exercise.
rich_is_bored@Posted: Tue Sep 02, 2008 1:12 pm : Small update. I've been tinkering with the source code and I've resolved pretty much everything. I'm not proud of the way I fixed some things but it works and serves my needs.
I've remapped the Wii controls to the proper joystick input. Movement doesn't seem to stall anymore. I also extended it to handle more buttons and analog input. The strafe toggle button is inverted so that strafe is on by default.
IR is also now half-implemented. It controls turning but I've done nothing about aiming. It's a little wonky because I'm only dealing with the IR directly. I'm not doing any prediction so if the remote looses sight of the sensor bar it's assumed that you want to keep turning.
I've fixed the menu navigation. Controls are standardized now. A to select, B to back out, ect... One interesting thing I found was that the home button is detected as the esc key but nowhere in the code is this evident. I assume one of the libraries is responsible.
I've forced all sounds to play at 11025hz. This seems to fix the chipmunk audio problem although I don't know if all the sounds in Doom are 11025hz.
And the fixes I talked about earlier are implemented. Brightness has been adjusted and the framerate has been uncapped. I'll upload the source when the author gives me permissions to the project on Google Code.
Download
rich_is_bored@Posted: Wed Sep 03, 2008 6:12 am : I've committed my changes to the repository. Everything should make it into the next build.
rich_is_bored@Posted: Wed Sep 10, 2008 10:15 pm :