Hacking USB Loader GX

[forza11]

I recently updated both USB Loader GX and Nintendont, but ever since the updates I can't directly load Nintendont games via USB Loader, instead it just opens Nintendont where i have to select the game from the list. All games are being indexed by GX so that works fine, it just doenst load games directly. Before the latests versions everything worked fine. Any idea how to solve this?

All apps and games are running on the SD card.

ps: if this was answered already, i've read a couple of pages but couldnt find this issue

 

[OriginalHamster]

I don't think it's fair to call it "my own fault". No one told me about this.

Really, getting on a guy's case for "being an idiot" really is no way to answer an honest question.

Also is this really true?

We need more details about your nintendont/ULGX versions, your partitions/file system, USB 2.0 or USB 3.0, self powered HDD?, cIOS running on, ULGX settings, etc...

 

[Dharengo]

Uhm, off the top of my head, I think the HDD is 3.0, and it's self powered, no spindown. It's Fat32 formatted, single partition. The file system is just the default one since I use GX to install the games anyway.

As for version. For GX, in the credits page it says "Rev1233"
cIOS is d2x v10beta52-vWii
For Nintendont it says v2.277 (Wii U)

 

[OriginalHamster]

Uhm, off the top of my head, I think the HDD is 3.0, and it's self powered, no spindown. It's Fat32 formatted, single partition. The file system is just the default one since I use GX to install the games anyway.

As for version. For GX, in the credits page it says "Rev1233"
cIOS is d2x v10beta52-vWii
For Nintendont it says v2.277 (Wii U)

Could be GX version, I remember GX getting updates to work with nintendont, you always can try some of the test that cyan posted, v12 looks to be stable.

USBLoaderGX download repository

beta test

 

[Dharengo]

I think I'll wait with that until the testing for the latest version is done.

 

[Acidflare]

I don't think it's fair to call it "my own fault". No one told me about this.

Really, getting on a guy's case for "being an idiot" really is no way to answer an honest question.

Also is this really true?

it's kinda obvious and it says it on the main project page
you also need to have autoboot enabled in the USBLGX loader settings

 

[Cyan]

Dharengo :
Which version of the loader are you using? r1235 is having issues. don't use the released 1235 (either go back to 1233 or update to beta11. I'll release 1238 probably today)

There are different thing which need to be clarified:
- Nintendont application CAN be installed either SD or USB, regardless of the game's location! Nintendont on SD can load games on USB just fine. (this is what I'm using).
- If the screen shrink to 4:3 when launching nintendont, you are probably not using r1235 (I fixed this) and not using latest nintendont either (because it wouldn't work if you don't have 1235 and games on USB. I don't know about SD).
- since 1235, There's a setting to choose nintendont aspect ratio (16:9 or 4:3). Note that majority of gamecube games were produced to be in 4:3 and picture is better in this mode (with black bars on the sides).

it's kinda obvious and it says it on the main project page

No, it doesn't.

OriginalHamster:
so for you, v12 is working fine?
that's a contradictory report
You are the one who had the less compatibility with r1235 (it code dump), and now you are the one with best compatibility lol
I really don't know what to think of my current situation
I'll probably remove PS3 support because I don't want to create issues for unknown users (not everyone comes on gbatemp).

But if you are free, I'll be happy to make more tests to find the real issue.

- Pointer speed is an issue with calibration. I'll see how to fix this, but it's not urgent.

Forza:
users reported the same issue. I don't know what's the cause yet. I'll look into it later.

 

[Dharengo]

Are the black bars JUST on the sides? Because when it's "forced", there are also black bars top and bottom which makes the image even smaller.

it's kinda obvious and it says it on the main project page

you also need to have autoboot enabled in the USBLGX loader settings

Not only does it in fact, not say that, Beanzy also mentioned not knowing what you were on about. Not to mention the above post which appeared just before I made this post.

And autoboot IS enabled in the settings. -_-

 

[Cyan]

I think the settings are not passed to nintendont because they are incomplete with r1233.
nintendont detects the settings size being less than expected one, and doesn't use them at all.
so it stops at select drive.

if you use 1235 (beta v10 or v11) it should work fine.

I'll release next revision soon.
hoping today.
I would like more users to test v12 and tell me if there's issues with text and game listing.

 

[Dharengo]

...Which is also the version I shouldn't be using right now, right?

I'll just wait for the next version.

 

[Acidflare]

I think the settings are not passed to nintendont because they are incomplete with r1233.
nintendont detects the settings size being less than expected one, and doesn't use them at all.
so it stops at select drive.

if you use 1235 (beta v10 or v11) it should work fine.

I'll release next revision soon.
hoping today.
I would like more users to test v12 and tell me if there's issues with text and game listing.

So it's no longer corrupting drives? just giving display error's?

 

[Cyan]

I don't know.
one user had a corrupted drive while using 1235, I don't know if the loader is at fault or his HDD had a bad sector/cluster/bad shutdown while writing file table/etc.

Don't use officially released 1235.
if you want, you can use v11 which doesn't have PS3 support.

v12 have PS3 support, but I removed an unneeded header. one user had issue, hamster didn't.
so I don't know what's the current situation.
I'll try to officially release v11 as new revision today as quick fix for nintendont compatibility.

But, I don't like quick fixes without proper tests.
I hope it won't have issues.

 

[Acidflare]

If my computer will stay on so I can copy some wbfs files to that blank drive I have, I can do some tests I have 145 games I don't want to lose them
If I get a code dump at any given point During/After after this testing phase would you like me to post pictures of them?

 

[Plunt]

I don't know.
one user had a corrupted drive while using 1235, I don't know if the loader is at fault or his HDD had a bad sector/cluster/bad shutdown while writing file table/etc.

Don't use officially released 1235.
if you want, you can use v11 which doesn't have PS3 support.

v12 have PS3 support, but I removed an unneeded header. one user had issue, hamster didn't.
so I don't know what's the current situation.
I'll try to officially release v11 as new revision today as quick fix for nintendont compatibility.

But, I don't like quick fixes without proper tests.
I hope it won't have issues.

I'm willng to test more builds if you want, I've got lots of spare time in the winter months.

I'll try to elaborate a bit more on how my HDD got corrupted. It happened twice last week both times I was running gx 1235 (official). The first time I was updating wiitdb it downloaded the zip correctly, during the extraction process it stopped around 50% the time remaning jumped to -200 and counting up (or less because its a negative number) and the percent complete started counting down. After a few seconds it slowed to halt and wouldn't let me cancel, the only thing I could do was power down resulting in a corrupted HDD. So I formatted transferred everything back (luckily I had a backup). The second time was the next day after everything was transferred back, I tried to update a cover for a game that was missing, it appeared to work correctly, so I just turned the console off. When I turned it back on no games showed up, plugged the HDD to my computer and sure enough all the content was replaced by random characters and folders. (The whole time I was using 1235 I was getting the corrupted text/hdd info/game count but didn't think anything of it)
At this point I figured my HDD was to blame and nearly went out and bought a new one. Deciding to wait until my next pay day. I happened to stumble upon this thread and realised that others were having corruption issues and maybe my HDD wasn't to blame.

My setup:
Original Wii w/ GC ports
WD 2tb My Book
Gx on SD, but all settings saved to USB

My HDD could very well have bad sectors causing the total corruption, but using v10 and v11 I'm not able to repeat the problem

 

[OriginalHamster]

Yeah, the last I test was v12 and it is working fine on my end, didn't know it was the one with PS3 controller support so it was a clean-blind-unbiased test lol
Problably will stick with v11.

I'm starting to think that the half of the problems reported are hardware based, Wii U not being able to feed HDDs through 1 USB port creates different configurations, for example I use a hub to power my HDD, and it behaves strange, sometimes it's off and the HDD still works with only the cable data, other times it start to click if the hub is not turned on. So in my test we should take in account my hub , for the record I suffered similar problems with WiiXplorer, where it crashed when creating new folders, moving/copy/paste files, never could isolate the problem because like I just said it's very random. Sooooo, I'm keeping the hub turned on forever, just in case xD

 

[AbdallahTerro]

DS3Sicksaxis is now deprecated: http://playstationhax.it/forums/top...between-dualshock4-and-wii-through-bluetooth/

it won't be that long before having DS3 and DS4 BT support in libogc!
If there is a wrapper for those 2 libs I could add them both fairly easily now

 

[xombiemp]

I've reported this before but wanted to reiterate: I'm on vWii running USBLoader GX from a hard drive that's plugged in with a Ycable to both the back ports. My wbfs partition is also on the hard drive, which contains less than 70 games total. I've been running 1235 since it was release and have not seen any weird characters, any crashing or instability in any way. That's just my experience. Which I could help debug more, but at the same time I'm glad I'm not seeing any of the problems other people are.

 

[CheatFreak47]

If my computer will stay on so I can copy some wbfs files to that blank drive I have, I can do some tests I have 145 games I don't want to lose them
If I get a code dump at any given point During/After after this testing phase would you like me to post pictures of them?

I think you might have misunderstood the bugs we're talking about. We're talking about memory corruption- not hard drive corruption.
Memory meaning- the Wii's RAM is getting too full and sections of memory are overwriting themselves with other parts of the loader- like DS3 support overwriting part of the memory with font images and library information- if you backup your ULGX configs- you should have nothing to worry about. The worst I could see happening here is with the corrupt memory- the loader might write to the config files incorrectly or just general loader crashes.

 

[Cyan]

well, the memory issue could be the cause too if it affects libfat.
Without testing his hardware (testing on another drive, or testing his defective drive on computer chkdsk) we won't know.
I'm very sorry that you had this issue with your drive, it wasn't deliberate and never had memory issues on my Wii so I didn't notice any issue before releasing it.

I will now release r1238 r1239 .. I really shouldn't haste things.
I won't push it to internal update before enough good reports.



abdallah: I saw he was working on a DS4 and bluetooth support lib on his git few weeks ago.
adding it would be good, if it doesn't make it instable again. maybe bte takes less memory than usb?


acidflare:
if you use v12 and get a code dump, that will be interested.
unfortunately, I didn't keep the boot.elf from other beta version required for debugging. reporting a dump with beta1-11 are not useful for me.
so, either v12 or r1235 or I'll make new version especially for debug/code dump purpose.


Edit:

USBLoaderGX r1239
Please tell me if there are any issues.
if everything is good I will put it on internal update tomorrow.
Thank you for your help.

surprisingly, r1239 without PS3 support has a bigger filesize than r1235 with PS3.

 

[AbdallahTerro]

abdallah: I saw he was working on a DS4 and bluetooth support lib on his git few weeks ago.
adding it would be good, if it doesn't make it instable again. maybe bte takes less memory than usb?

surprisingly, r1239 without PS3 support has a bigger filesize than r1235 with PS3.

no idea how much it would take the .o is roughly 20k for each
you still need to init while the usb cord is plugged
I would say it should be the same
I just need a good wrapper to make adding the code easy and clean