Line 100:
Line 100:
: No, it can't be a memory issue - everything is effectively wiped upon return to HBC. It sounds like some sort of video mode misconfiguration that libogc does not know how to correct, so HBC inherits the bad setting from VBA. See if you can find a way of reproducing it reliably and we can have a look at it. [[User:Marcan|Marcan]] 14:44, 9 June 2008 (CEST)
: No, it can't be a memory issue - everything is effectively wiped upon return to HBC. It sounds like some sort of video mode misconfiguration that libogc does not know how to correct, so HBC inherits the bad setting from VBA. See if you can find a way of reproducing it reliably and we can have a look at it. [[User:Marcan|Marcan]] 14:44, 9 June 2008 (CEST)
: Sounds like the frame buffer got misaligned somehow. A bad memory allocator in VBA? [[User:ector|ector]]
: Sounds like the frame buffer got misaligned somehow. A bad memory allocator in VBA? [[User:ector|ector]]
+
:: This has also happened to me twice. Ive noticed it only happens when you enter the homebrew channel. The first time was when I entered the HBC from System Menu, and the second time was when I exited a homebrew program (forgot what it was). I think it might be a 480p issue, because I too have component cables. [[User:Oops ur dead|oops_ur_dead]] 23:40, 3 September 2008 (UTC)
== Wireless WEP unsupported? ==
== Wireless WEP unsupported? ==