Search found 9 matches

by PeterM
Sat Mar 01, 2008 12:09 pm
Forum: Bug Reports
Topic: libogc: Pads unusable if unplugged then plugged back in
Replies: 8
Views: 7812

Re: libogc: Pads unusable if unplugged then plugged back in

I mentioned that to WinterMute recently, who said the PAD_ScanPads call should be moved to your update/main loop and not done in the retrace callback any more.
by PeterM
Mon Feb 11, 2008 8:05 pm
Forum: Gamecube/Wii Development
Topic: Any SD card fixes in the next version?
Replies: 2
Views: 4376

Any SD card fixes in the next version?

Hello, Currently I access the SD card via SoftDev's TinyFAT FS library instead of the SD card lib built into libOGC. This adds a couple of layers of code to my file handling which I'd like to ditch when libOGC's SD card library works well enough. I was wondering if any of the SD bugs are fixed in th...
by PeterM
Mon Feb 11, 2008 7:32 pm
Forum: Bug Reports
Topic: libogc: Pads unusable if unplugged then plugged back in
Replies: 8
Views: 7812

Re: libogc: Pads unusable if unplugged then plugged back in

Even though I was calling PAD_Read myself, I was checking for all the error codes and acting (as far as I could tell) accordingly. I switched my code over to use PAD_ScanPads as the post-retrace callback, but still no dice. Once the pad is unplugged, the buttons are always zero. The code is a lot si...
by PeterM
Sat Feb 09, 2008 5:35 pm
Forum: Bug Reports
Topic: libogc: Pads unusable if unplugged then plugged back in
Replies: 8
Views: 7812

Re: libogc: Pads unusable if unplugged then plugged back in

Thanks for looking into it. I had a quick look through CVS and it's possible that there were fixes: http://devkitpro.cvs.sourceforge.net/devkitpro/libogc/libogc/pad.c?r1=1.19&r2=1.20 (Note new variable "connected" in PAD_ScanPads). I don't use PAD_ScanPads though, I just call PAD_Read in Quake's inp...
by PeterM
Sat Feb 09, 2008 1:07 am
Forum: Gamecube/Wii Development
Topic: Specify per project stack size?
Replies: 1
Views: 3710

Specify per project stack size?

To cater for Quake's hefty stack requirements I've had to increase the stack from 128K to 256K. It used to be 512, but I did some optimisation in R_RecursiveWorldNode to take the usage down. I was wondering if there is a way to do this on a per .elf basis instead of modifying the global ogc.ld links...
by PeterM
Fri Feb 08, 2008 9:58 pm
Forum: Bug Reports
Topic: libogc: malloc hangs instead of returning NULL on failure.
Replies: 2
Views: 4411

libogc: malloc hangs instead of returning NULL on failure.

It seems that malloc locks up instead of returning NULL when it can't allocate a block big enough.

I don't *think* it's my bug (I've increased the stack size in ogc.ld from 128K to 256K), but it could be.
by PeterM
Fri Feb 08, 2008 9:52 pm
Forum: Bug Reports
Topic: libogc: Pads unusable if unplugged then plugged back in
Replies: 8
Views: 7812

libogc: Pads unusable if unplugged then plugged back in

I've tried calling PAD_Init again, but it doesn't seem to help.
by PeterM
Fri Feb 08, 2008 9:50 pm
Forum: Bug Reports
Topic: libogc: <ogc/lwp_watchdog.h> #includes <lwp_queue.h>
Replies: 1
Views: 3167

libogc: <ogc/lwp_watchdog.h> #includes <lwp_queue.h>

Sorry if this is in the wrong board, I didn't know whether to put it in bug reports or libogc. The (minor) bug is as in the subject. The ogc folder isn't on the include path, so it should probably be referred to as <ogc/lwp_queue.h> or "lwp_queue.h" in lwp_watchdog.h. There are probably other instan...