Hacking USB Loader GX

  • Thread starter Thread starter blackb0x
  • Start date Start date
  • Views Views 8,066,382
  • Replies Replies 30,226
  • Likes Likes 74
I preferred the PS2 version (for the game pad and smashing button lag issue on Wii).
it's not blurry, it's a pencil and paper effect applied on screen.
I didn't notice that Wii version had less visual effect.


About the Wiimote vibration, it sometime happen even when not launching nintendont.
Maybe it doesn't get properly de-init before exiting the loader.
But you say that it's your Gamecube controller which is vibrating? it's a real/retail/official controller on a compatible Wii?
I have an official controller and never had that issue.

I don't know if third party controllers could be the cause.
You could try exiting to HBC or exiting to system menu, or exiting to another homebrew (from the homebrew browser menu in the loader) as it's using the same function to launch nintendont and other homebrew.
 
I preferred the PS2 version (for the game pad and smashing button lag issue on Wii).
it's not blurry, it's a pencil and paper effect applied on screen.
I didn't notice that Wii version had less visual effect.


About the Wiimote vibration, it sometime happen even when not launching nintendont.
Maybe it doesn't get properly de-init before exiting the loader.
But you say that it's your Gamecube controller which is vibrating? it's a real/retail/official controller on a compatible Wii?
I have an official controller and never had that issue.

I don't know if third party controllers could be the cause.
You could try exiting to HBC or exiting to system menu, or exiting to another homebrew (from the homebrew browser menu in the loader) as it's using the same function to launch nintendont and other homebrew.


Yup, its an official one, going back to homebrew from Loader GX to open Nintendont from there still makes the problem appear. The bug is no where to be seen only if i open Nintendont without opening Loader GX at all. Which is a bit annoying if i consider playing some Wii games first before going to Gamecube. I cant figure out why really, i followed the guides properly but still...eh.. I wonder if going back to an older version of Loader GX will work. Do you have any other recommendation maybe?

Are you by any chance working on this project? Thanks a lot if you do
 
Yes, I'm the project's active developer (well, not very active lol).
I'm not releasing very often, but I'm working on it.

I had vibration issue when exiting the loader with PS3 controller connected on USB.
But only r1235 had PS3 support, and that version was found unstable.
If you are using 1235, please update quickly to prevent data loss.

If you are on 1239 or 1244, then I don't know why you have this issue. You are the first one reporting it.
A lot of users are launching nintendont from USBLoaderGX, I suppose they would have reported it if they had the same issue too.


You can try older version of the loader (but you will have to revert nintendont version to old ones too or it will not work correctly)
You can start by downgrading nintendont only (it's strange that it affects only the pad when you launch nintendont, not other homebrew)

You tested launching other homebrew from the loader?

Does TinTin work now?
Tintin works only on Neek (sneek/uneek/uneek2o)
it will work when I add n2o support.

I hope to work on it next month, I'll have few holidays.
 
I'm trying to figure out how to use my Wiiu Pro controller when launching Nintendont from GX. The controller is recognized and works fine when running Nintendont and to navigate the GX menu, but cuts out as soon as the loader boots up Nintendont. I've played around with a few of the controller settings in the Nintendont section of GX, but nothing has worked. What am I missing?
 
Cyan will you add libwupc ? : http://gbatemp.net/threads/libwupc-...library-for-wii-homebrew-applications.371574/
To use Wii U Pro controller with USB Loader GX :)
yeahh, for once I did something before a request ! lol
I even added more than the library, I added a patch to support L3/R3 (press both to shutdown the controller) which is not in the official release.
There are still problem with some menus (the cursor speed is different than other controllers, and you can't grab the 3D cover in game info window).


I'm trying to figure out how to use my Wiiu Pro controller when launching Nintendont from GX. The controller is recognized and works fine when running Nintendont and to navigate the GX menu, but cuts out as soon as the loader boots up Nintendont. I've played around with a few of the controller settings in the Nintendont section of GX, but nothing has worked. What am I missing?

now that I think about it, I didn't try to launch nintendont with that controller synced. I tested it in the loader only.
It's possible the controller is shutdown at launch because it's reloading to IOS58 (unless you are already using IOS58 as Loader's IOS), and because the loader is shutting down controllers and USB so it will force a disconnection for all devices.
But once in nintendont, like you said, the controller should reconnect by pressing any button while in nintendont. Maybe the console is not auto-reconnecting it as it's not part of the officially synced devices on Wii. it's registered but can't synch.

No setting in USBLoaderGX is required to enable WiiUPro in nintendont.
maybe the MaxPad, set it to 4, but that's all.
the "USB HID" is for USB controllers only, and now always enabled since r3.304 even if you set the option to OFF in the loader.
 
  • Like
Reactions: OuahOuah
you go to system menu (Wii or vWii, both are working), press the red button to register the controller.
It will start blinking and quickly stop because the console will try to synch the controller by reading a missing area of the chipset (it things it's a Wiimote+classic controller, but it's only half of it).

Go to a compatible Homebrew and press any button on the controller and it will synch... in the homebrew.
You can't "play Wii games with it" as the console will always try to access unavailable memory and shutdown the controller.
Only homebrew using the WiiUPC library will work because it's using its own function to access only the area where the buttons info are stored.

It works in USBGX, in nintendont (and games), in Devolution (and games), and few recompiled homebrew emulators.
 
yes, ciso is compatible, and should work in all partition format. (even fat32, as ciso is a recompiled iso after scrubbing dummy files so it will often be less than 4GB)
ciso is like a wbfs file but without the wbfs encapsulation.

if the ciso is bigger than 4GB, there's no real interest in using this format, using ISO is the same, except maybe for dual layers games.


You can find all working format and path checked by the loader here:
https://gbatemp.net/threads/usb-loa...ck-to-hbc-for-some-games.386627/#post-5455832
 
  • Like
Reactions: kimotori
Tnx, for your support and patient :)

this format (ciso) is good for reduced space, iso is too big, wbfs is inconsistent (like fat32 :)) ne c'est pa?
 
wbfs is an ISO data encapsulated in a WBFS partition.

when the loaders were created, it used the WBFS partition format to store up to 500 games on it.
later, when FAT32 was possible, instead of reading ISO directly from partition file's system, the loader continued to use WBFS for its internal structure by loading multiple virtual wbfs partitions with one single game on each.
The .wbfs file is in fact 1 virtual partition with 1 game installed on it.

The .wbfs file is the native format used by the loaders, while the ciso is loaded directly without the wbfs header happened to it.
Using .wbfs files or cIOS has not differences in compatibility, read speed or size. (only few kb added when using wbfs file, or few MB depending on the HDD sector size)

The wbfs files has the advantage that it can be split in multiple files to fit on FAT32 partition, while ISO and cIOS bigger than 4GB will work only on NTFS/ext.
The only difference is on the computer side, the wbfs requires a manager to convert/split/extract files, while cIOS is a clean ISO with scrubbed dummy files but still need a manager to edit the game (extract files, apply patches etc.).

edit:
Ahhh, just an important thing to note:
cISO used by Wii are NOT THE SAME as PSP cISO !!!
don't use PSP ISO compressor to compress the Wii ISO.
the cIOS PSP format is compressing files inside the ISO and the PSP is processing it in realtime to unpack the files. But the Wii will not understand this format. there's no OS behind the game to extract the data.

The Wii's cISO is a normal uncompressed ISO data.
cISO name is more like the cIOS name. A "custom ISO", like in "cIOS for custom IOS", not a compressed ISO.
the custom ISO for Wii contains the full uncompressed game data, and only removes the dummy files used to fill the 4GB disc.


Wiiscrubber : replace dummy data with repetitive pattern to compress better in .rar
cISO : delete dummy data and re-create the ISO without them.
wbfs : delete dummy data and re-create the iso without them, and write wbfs header for split info.
 
  • Like
Reactions: kimotori

Site & Scene News

Popular threads in this forum