DevkitPro CVS is no longer updated. DevkitPro SVN is now used.by Tantric - Coding
Umm...did you check on DevkitPro SVN? rodries has finished the devoptab, and he and I submitted a new TinySMB, which is now there. It has write support, amongst other things.by Tantric - Coding
Quotetico1177QuoteTantricHit your controller. Yes, I'm serious. Believe it or not, this is the actual solution. I had the same problem before and searched it out online. I was led to Nintendo's Support site where they tell you to firmly hit the controller onto the palm of your hand. That will fix it. I think there might be mercury inside and it gets stuck... But yet for some reasoby Tantric - Homebrew General
Someone else would know better, but I think these three functions would help: GX_Flush(); GX_DrawDone(); GX_WaitDrawDone(); I think calling these after GX_End() is sufficient?by Tantric - Coding
assert does in fact call exit(), that is the defined behavior of assert(). Basically...that means assert isn't as valuable to you on the Wii - if you're wanted to see the error. But, considering all that assert does is check if what you passed it is true (and terminate the program if it's not), you could easily write your own "assert".by Tantric - Coding
What koopa said. Follow the directions on Google Code. Also see under GUI and IDE Access.by Tantric - Homebrew General
You'll also need to make sure you're setup to read that additional Wiimote. In your init line, make sure you have WPAD_SetDataFormat(WPAD_CHAN_ALL,WPAD_FMT_BTNS_ACC_IR);by Tantric - Coding
libfat changed. Now the code you're compiling needs to. It's really simple. Init libfat - fatInitDefault(); Using sd - sd:/thefolder/thefile Using usb - usb:/thefolder/thefile (sd: and usb: replace fat3: and fat4:) Anything else, you can delete - eg: fatSetDefaultInterfaceby Tantric - Coding
Probably your SD card is corrupted or failing. It happened to me. Try running chkdsk on it in Windows.by Tantric - Homebrew General
It's even more trivial to just use snprintf. I would recommend this over itoa.by Tantric - Coding
It's not a "bug". The format just changed, that's all, and I didn't write something to "convert" to the new format.by Tantric - Homebrew Applications
Go here, click to download the cheat file. Copy the .cht file into the /snes9x/cheats folder. Rename the file to be the same as whatever your ROM is (eg: Final Fantary II (U).cht) Load the game, press the Home button. A cheat menu option will appear if you did this all correctly.by Tantric - Homebrew Applications
They're already on SVN, you can download them yourself, or just wait for the next release. The next release will be whenever shagkur and wintermute feel it's appropriate, I guess.by Tantric - Coding
Snapshots from older VBA's (eg: 1.0.2) don't work anymore. Don't remember when they were invalidated. You can try a save file, or try loading the snapshot on VBA-M, and seeing if you can resave it there. Then try it again on the Wii. Good luck!by Tantric - Homebrew Applications
Possible, but hasn't been done yet.by Tantric - Homebrew Applications
From the Wiibrew Snes9x GX page: By default, cheats are loaded from "/snes9x/cheats/". Cheat files must be placed in the cheats folder and named identically to the ROM name, except with a CHT extension. After putting the cheat file in the proper place and naming it correctly, you can access cheats in-game by pressing 'Home' after loading a game. A Cheats menu option should be availabby Tantric - Homebrew Applications
It should download the update (1.07) to the sd card, sd:/apps/vbagx/. If you have your old copy stored somewhere else (eg: sd:/apps/vba) and you keep loading that old copy, of course it's going to keep asking you to update to 1.07.by Tantric - Homebrew Applications
Of course he could but: a) there's no point for him to b) the comment above suggested there already was a .a file and he just needed to find it.by Tantric - Coding
WRONG. GRRLIB is not in a .a file - just find grrlib.c and grrlib.h and put them in with the rest of your code.by Tantric - Coding
Ok, great. That's looking better. But, still some mistakes. Why don't you just do this instead: in Save function: fwrite(brickx, 1, sizeof(brickx)*30, pattern); fwrite(bricky, 1, sizeof(bricky)*30, pattern); in Load function: fread(brickx, 1, sizeof(brickx)*30, pattern); fread(bricky, 1, sizeof(bricky)*30, pattern); Keep in mind the definitions of functions. fread reby Tantric - Coding
What you should do is lookup the fopen function. It says: "w" Create an empty file for writing. If a file with the same name already exists its content is erased and the file is treated as a new empty file.by Tantric - Coding
It's always a good idea to check ALL return values. It'll help the users if something goes wrong, and you to know exactly what went wrong. That means checking the return value of putc and getc too. Also, although they're almost equivalent, you should use fputc and fgetc instead. putc and getc are meant more for macros.by Tantric - Coding
What version of libfat are you using? If you're using the newest, it's sd:/ now, not fat:/. Another thing this is you should check the return value of fopen. When you're saving a file, you shouldn't be using "rb", use "wb" to open the file for writing.by Tantric - Coding
Why don't you use TCP? Am I missing something here?by Tantric - Coding
Yes, HBC is prepending the fat:/ on there :(by Tantric - Coding
I'm already in contact with the Snes9x team, thanks =)by Tantric - Homebrew Applications
That's just overscan. Your TV is cropping more of the picture than it should.by Tantric - Homebrew General
GRRLIB works with C++. Just include the GRRLIB.h like so: extern "C" { #include "GRRLIB.h" }by Tantric - Coding
Take a peek at libogc's source - specifically - usb.c for low-level USB access, and usbstorage.c for an implementation of USB MSD support. They may help you in figuring out how to do what you want.by Tantric - Coding