User:Wiibrewfan4
|
I'm an anonymous wii user. From this page you may read about my recent findings, conserning especially valuable information that didn't exist the interewebs before. (F.e Taiko drum & glovepie.. Trust me, i have very 31337 googlor skillzor... The golden sun emulator thingie was found on some anciet tehskeen thread..)
Wiibrewfan4's mystique findings
Wii constantly freezing in Xenoblade - DVD or USB
Is your Wii freezing on some games in a way, that the picture freezes but audio keeps playing and controller wont work? Is this a problem that occurs in only of handful of games? You have done a factory reset and even tried installing fresh nand-image or system menu? Tried every IOS but didn't make a difference? You have the original dvd AND a backup on external HDD which you have triplechecked, that it wont go to autosleep during game-play? Using the DVD or HDD get's the same result, the game freezes at some point? You might have even bought a wii disc cleaner and cleaned the lense several times.. I did all this because of Rune Factory: Tides of Destiny and Xenoblade and one other game I can't remember right now. I spent 6 months of debugging and googling and writing a troubleshooting diary about it till I almost lost my mind.
You propably want to know how I managed to get these games to work? I deattached the Official Nintendo USB-Lan adapter from my Wii, that's right.. The game has not been frozen ever since - this is a bug either in the game or a bug that is caused by the way Wii handles this interface during gameplay, who knows? I really hope that someone else who might have the same problem will find this page.
Update: the problem came back, fffffuuuuck, will write more if I'll ever find the real cause.
keywords: wii freezes, xenoblade, rune factory tides of destiny, picture freezes but audio continues, freeze
Glovepie & Wii Taiko Drum Controller
Around 10-20 of August, I've figured out how to read all necessary incoming data from the Wii Taiko Drum controller using glovepie. It seems that Taiko No Tatsujin isn't using the full potential of the controller, as it turned out that there were a possibility of 16 different key presses... (15 if you don't count the state when none of the 'buttons' are pressed ;)) When i'm done with the investigations i'll post the script somewhere around teh internets. WID..
Update: Here's a little something... I've managed to lost the original script file during normal format operation, and i've also temporarily lost interest in redoing the script. Anyway, even if you have little experience for glovepie scripting, this should be a no-brainer for you. ;p ... I will however redo this script in near future, but for now this is all that i have the energy to write..--Wiibrewfan4 17:57, 24 September 2009 (UTC)
Update2: The code below should be working with the latest Glovepie (0.43)
//This short script checks if taiko drum is inserted into wiimote
//and shows the incoming decimal numbers in the debug field.
//So if you touch the right side of the inner ring of the drum, you should get
//value of 239, try all the 16 combinations and do what you want
//It also plays fierce snarefills when touched to either left or right side
//of the center part of the taiko drum
Wiimote1.Leds = 9 //If 2 leds are lit up your wiimote is working
if (Wiimote.expansion == 195) then //if taikodrum is inserted
var.tmp = wiimote1.inByte18
debug = var.tmp
var.d_nohit = var.tmp=255
var.dr = var.tmp=239
var.dl = var.tmp=191
midi.AcousticSnare=var.dl
midi.AcousticSnare=var.dr
end ifOvercoming the very annoying lag in Golden Sun: The lost age when using wii port of VBA.
13 of September I found out that if you have been trying to play Golden sun: The Lost Age with more recent versions of Visual Boy Advance, the framerate is terrible, but the version 1.01 runs it allmost perfectly! :o
Recent struggles with bootmii, mikep4-kernel and upgraded debian-lenny
The 'latest' cvs-version of nuvalo's x11 cube-module has to be compiled in order to get Xorg working after dist-upgrading debian from etch to lenny. I have 42" wide-screen TV connected to wii with YPbPr-cabel. With my hardware setup the compiled cube-driver fucks up the visibility of screen borders. In order to lower my y-resolution I had to modify several lines from the cube-driver.c and recompile it. All in all this required several hours of investigation & testing, and even google turned me down. So in near future expect to see a short tutorial how to get, hack, compile and install cube-driver.c with the resolution of your choice! This manual will allow you to change the values of x and y without odd crashes. The precompiled xwhiite cube-driver let's you do so, but if you have to compile the driver these changes are needed. NOTE: I did not compile the cube-driver in xwhiite release, i do not know who did.
Install cvs-client in order to get the lastest build of nuvalo's cube xorg driver
apt-get install cvsget the source:
cvs -d:pserver:anonymous@gc-linux.cvs.sourceforge.net:/cvsroot/gc-linux login
cvs -z3 -d:pserver:anonymous@gc-linux.cvs.sourceforge.net:/cvsroot/gc-linux co -P xf86-video-cubeBefore compiling Nuvalo's cube_driver for Xorg, please install the following packages:
apt-get install module-init-tools pkg-config xserver-xorg-dev x11proto-randr-dev libxrandr-dev x11proto-video-dev x11proto-fonts-devEdit xf86-video-cube/src/cubedriver.c with your favourite editor and change the following lines:
Here are the needed changes, I'm using height value 460, so change this if the screen is still stretched... bwahahah, fuck that. I admit that I do not know why this works as it works, but it works. So just chnage the following lines will you:
//part1: in line number 951, change FALSE to TRUE
if (width == 640 && ((height == 480)||(height == 576)))
{
match = TRUE;
}
if (!match)
{
xf86DrvMsg(pScrn->scrnIndex, X_ERROR,
"Selected width = %d and height = %d is not supported by cube/wii
\n", width, height);
//first we allow the Xorg to start up no matter what resolution is given...
return TRUE; //* CHANGE THIS!
}
//part2: the last lines of cube_driver.c (lines starting from 1162 -> 1170)
//by doing the changes above, you are not limited to hardcoded resolutions!
static void
CUBERefreshAll(ScrnInfoPtr pScrn)
{
BoxRec box;
box.x1 = 0;
box.x2 = pScrn->currentMode->HDisplay; //* CHANGE THIS!
box.y1 = 0;
box.y2 = pScrn->currentMode->VDisplay; //* CHANGE THIS!
CUBERefreshArea(pScrn, 1, &box);
}After this, compile the driver:
cd to xf86-video-cube/ and type:
./configure && make && make installThe driver installs itself to wrong location, so:
cp /usr/local/lib/xorg/modules/drivers/cube_driver.* /usr/lib/xorg/modules/change xorg-conf to match your new height value (460 in this example) in my setup, i used the following modeline:
##modeline from /etc/X11/xorg.conf
Modeline "pal_50" 23.72 640 656 720 800 460 577 580 593 -HSync +VsyncAfter all this, i got it working.
Misc.
Completed Giddy 3 16.02.2008 on one session with 6 lives left.