Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,066,806
  • Replies Replies 30,226
  • Likes Likes 74
@TalalQ8 But did you delete the usbloader_gx folders from both your SD card and HDD before reinstalling the loader?

And could you please get a new picture of the crash, since the one that you originally uploaded and reposted 2-3 times was from Cyan's SourceForge version of the loader. My version should have different addresses for the "STACK DUMP".



https://gbatemp.net/posts/9552316



Ah, so you're launching it via a channel forwarder. I was launching it via the loaders built in homebrew browser, which does work.

For years the loader wasn't able to patch WiiWare and VC games, but I fixed that in the new update. I think that fix is what causes this issue though, so I'll need to try to make it handle both games and channel forwarders.
How do i delete the hdd?
 
But i don’t have a usbloader_gx apps folder in my hard drive
In that case don't worry about it. As long as you removed it from your SD card it should of reset everything.

At this point I can only suggest copying the contents of your SD card to your computer, formatting it and then only installing the loader to it.
 
In that case don't worry about it. As long as you removed it from your SD card it should of reset everything.

At this point I can only suggest copying the contents of your SD card to your computer, formatting it and then only installing the loader to it.
Ooh..well that’s sketchy and scary in my opinion…
 
That's the only way to debug the issue, unless you've got another SD card that you can format and use.
But i mean as i said, WiiFlow and CFG are great and it never happened like what usb loader gx, i still use cfg and wiiflow till jow but usb loader gx used to be okay but now it’s crashing a lot
 
But i mean as i said, WiiFlow and CFG are great and it never happened like what usb loader gx, i still use cfg and wiiflow till jow but usb loader gx used to be okay but now it’s crashing a lot
And it started crashing for an unknown reason. So it could be caused by something on the SD card, but you don't know until you format the SD card.

It should only take a few minutes to backup the SD card contents and format.
 
  • Like
Reactions: XFlak
And it started crashing for an unknown reason. So it could be caused by something on the SD card, but you don't know until you format the SD card.

It should only take a few minutes to backup the SD card contents and format.
Ooh i see
 
Ah, so you're launching it via a channel forwarder. I was launching it via the loaders built in homebrew browser, which does work.

For years the loader wasn't able to patch WiiWare and VC games, but I fixed that in the new update. I think that fix is what causes this issue though, so I'll need to try to make it handle both games and channel forwarders.

EDIT: I've fixed it for the next release.

Hi blackb0x,

Thanks for the follow-up and quick fix!
I'll keep my eyes open for when the 8th release becomes available.
 
[*]Added deflicker filter options (the safe option is recommended)

Maybe this is a bit niche, but I don't suppose there'd be a way to make two separate settings, one used with progressive scan output and the other used with interlaced output?

My thinking here is that you generally want to use the deflicker filter on CRT TVs, but don't want it on flat-panel displays. And since the Wii is the newest console capable of true 240p output with a ton of homebrew capability as well, the Wii is also likely to be the most commonly-used system that would see active use on both types of displays rather than just one or the other (especially since the Wii is even smart enough to automatically switch to interlaced if you boot with composite cables when the console is set to 480p output, and it will even automatically switch back to 480p if subsequently you boot with component cables connected)
 
Last edited by Nintendo Maniac,
Maybe this is a bit niche, but I don't suppose there'd be a way to make two separate settings, one used with progressive scan output and the other used with interlaced output?
You're right, that is niche. I mean how many people are moving the same Wii between a CRT and a modern display often enough that changing the deflicker setting would become a problem?

I could add a new setting that controls if your deflicker settings are applied, depending on if you're using a component cable. Although I'm trying to avoid adding too many new settings because the settings menus are already cluttered :unsure:
 
Last edited by blackb0x,
BTW while you're here, I normally use the "play count" sort order, and I'm wondering if there's a way to make USB Loader GX always default to the beginning of your game list / first channel page without just setting "GXGlobal.cfg" to read-only (which is what I've been doing for the last... I dunno, half decade or something?)

I could add a new setting that controls if your deflicker settings are applied, depending on if you're using a component cable.
That's better than nothing, but there are games that don't use deflicker by default even with composite cables (Quantum of Solace being one that comes to mind), meaning that such games would effectively need inverted settings.

Also, being a new additional setting, wouldn't you'd still end up with two deflicker settings in total? I don't understand how my suggestion of two settings, one for 480p and one for interlaced, wouldn't end up being the exact same amount of settings in total (two) while allowing for much more flexibility.
 
Last edited by Nintendo Maniac,
BTW while you're here, I normally use the "play count" sort order, and I'm wondering if there's a way to make USB Loader GX always default to the beginning of your game list / first channel page without just setting "GXGlobal.cfg" to read-only (which is what I've been doing for the last... I dunno, half decade or something?)
I should be able to add a setting to handle that.

Also, being a new additional setting, wouldn't you'd still end up with two deflicker settings in total?
Two settings, but each setting would have 6 options. And there's also the custom game settings. So it's not ideal and it would just look messy.

I assume that you play specific games on a CRT, since I don't know why else you'd switch between screens so often. So couldn't you use custom game settings for anything you play on a CRT and then leave the global deflicker setting set to the safe or extended option?
 
Last edited by blackb0x,
I have a bad habit of making multiple after-the-fact edits so, since I'm not sure if you saw them due to you posting soon after my edits, I've removed the edits from my previous post and am copy-and-pasting them above the quote-box; this should be my final post asking things so don't worry about me bothering you any longer:

EDIT: Quick note about the deflicker naming - rather than "enhanced" (which implies that's it's somehow better than "safe"), wouldn't it be clearer to the user what the difference is if it instead was named something like "aggressive" or "forced"?

EDIT 2: Oh and I don't suppose you know if this deflicker setting exists in Wiiflow Lite? While I don't use Wiiflow Lite and have always preferred USB Loader GX, I have a friend that does use Wiiflow Lite as he prefers having loaders separated into a per-console basis (so he uses USB Loader GX for GameCube and Wiiflow Lite for Wii).


So couldn't you use custom game settings for anything you play on a CRT and then leave the global deflicker setting set to the safe or extended option?
Mostly, but at least having the option to be able to play other games on either display without needing to manually change the deflicker setting was kind of what I was hoping for, but TBH I'm really not even sure if I'd really even do that now that I think of it outside of some testing stuff where it wouldn't even be that important if the deflicker is set incorrectly.

So... maybe let's just don't worry about it? If I get desperate I can always just use separate SD cards with different configurations since I store the games on the USB drive due to my use of a 2GB non-HC SD card.


Speaking of which, just to confirm, Excite Truck and Endless Ocean's limitation of only being able to read non-HC SD cards is not something that a USB loader could fix, correct? It'd require at the very least a gecko code or straight-up a patch for the ISO itself? (like the gecko code that exists for Smash Bros Brawl which also was limited to non-HC SD cards by default)

Which also reminds me, on the subject of ISOs, just how (un)realistic would it be to support the RVZ format introduced by Dolphin and to be adopted by Nkit (if it hasn't already)? According to Dolphin devs, the main bottleneck would likely be memory rather than CPU (especially if one could take advantage of the extra CPU cores/clockrate on the Wii U... though I'm using an actual Wii console).
 
Last edited by Nintendo Maniac,
EDIT: Quick note about the deflicker naming - rather than "enhanced" (which implies that's it's somehow better than "safe"), wouldn't it be clearer to the user what the difference is if it instead was named something like "aggressive" or "forced"?
It's extended, not enhanced. Maybe you read enhanced from my GitHub branch name or my signature and got things mixed up?

It'd require at the very least a gecko code or straight-up a patch for the ISO itself?
Correct.

Which also reminds me, on the subject of ISOs, just how (un)realistic would it be to support the RVZ format introduced by Dolphin and to be adopted by Nkit (if it hasn't already)? According to Dolphin devs, the main bottleneck would likely be memory rather than CPU (especially if one could take advantage of the extra CPU cores/clockrate on the Wii U... though I'm using an actual Wii console).
Other than the hardware limitations it'd also require some (major?) cIOS and loader changes. So you're more likely to win the lottery than to ever see RVZ support on real hardware.
 
It's extended, not enhanced. Maybe you read enhanced from my GitHub branch name or my signature and got things mixed up?

Ah, yeah, probably. TBH I looked at the deflicker settings a whole one time before making that post as I hadn't yet gotten around to testing a few things.

I still like a my idea of aggressive or forced though since I personally find the word "extended" to not be "safe"-sounding enough to imply that it may actually break things, but whatever. It's your mod, not mine.


As for the things I was testing, I just realized that the GXGlobal.cfg also controls whether the settings GUI is locked or not, meaning it also lets one only temporarily lock or unlock the settings GUI and, the next time you load USB Loader GX, it'll be back to whatever unlock/lock state is saved in the file. I find this too is quite useful to make sure I don't forget to re-lock it if/when I need to change a setting.

So uh, I don't suppose a setting that goes something like "Default lock state" with the three options being 'none', 'unlocked', and 'locked' would asking for too much? 'None' would be the current behavior when GXGlobal.cfg is not set to read-only, 'unlocked' would mean that USB Loader GX will always launch unlocked, and 'locked' would mean that USB Loader GX will always launch locked.
 
Last edited by Nintendo Maniac,
I still like a my idea of aggressive or forced though since I personally find the word "extended" to not be "safe"-sounding enough to imply that it may actually break things, but whatever. It's your mod, not mine.
The extended option is literally an extended version of the safe option, since it does exactly what the safe option does while also patching a function that enables filters. But when that function is patched it might break fade and brightness effects in some games.

I've mentioned it in a few posts now, but to avoid any potential issues you should use the safe option and only apply the extended one if a filter still seems to be enabled.

Oh and I don't suppose you know if this deflicker setting exists in Wiiflow Lite?
I'll most likely eventually copy it over, but not yet. Right now I'm busy working on other things.

So uh, I don't suppose a setting that goes something like "Default lock state" with the three options being 'none', 'unlocked', and 'locked' would asking for too much? 'None' would be the current behavior when GXGlobal.cfg is not set to read-only, 'unlocked' would mean that USB Loader GX will always launch unlocked, and 'locked' would mean that USB Loader GX will always launch locked.
Wouldn't a setting like the one that you're suggesting defeat the actual purpose of the lock though? Like it's a parental feature, so you shouldn't ever want the loader to be unlocked by restarting it :unsure:

Blocking write access to your config file will result in some unintended behaviour, but is there any reason to block write access if game sorting worked the way you want it to?
 
Last edited by blackb0x,

Site & Scene News

Popular threads in this forum