d2x-v10beta52-vWii with bases 56, 57, and 58. I also added the fat library to enable emuNAND while using ustealth.
d2x-v10beta52-vWii with bases 56, 57, and 58. I also added the fat library to enable emuNAND while using ustealth.
btw, I know this controller isn't a fake. I once bought a fake and the box was a different size. however, the dead giveaway with that controller was the dpad. it didn't feel right.
Are you willing to try beta53-alt-vWii base 58?
That's the one I use, used to have problems with WUPC too with beta52.
can I do that and keep beta 52? I remember having issues with emuNAND on beta 53.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
just don't install anything to slot 254 or above.
254 is historically used for bootmii.
255 is now used for WiiU fw.img when injected in WiiVC. (see how nice is Nintendo, not overwriting our slot numbering
)
256/257 are BC and MIOS on a Wii.
220'th were used for Hermes. instead of detecting Hermes IOS, USBGX bases it on the slot number, so 202;222-224 are reserved for hermes.
anything from 225-253 are free. a lot of users prefer using 248 instead of 252. As long as you remember your own setup, anything is fine.
Oh, some info :
DJ_skual helped me and made a WiiVC forwarder for USBGX.
I can now test the gamepad support.
1269_mod1 is bad! the buttons are all out of mapping (Home=Y, Right=Up, etc.), but I now have a working base to fix that for the next release (not before january now, sorry)
No idea if I'll find how to fix the NAND access to fix channel's listing and banner layout mode.
254 is historically used for bootmii.
255 is now used for WiiU fw.img when injected in WiiVC. (see how nice is Nintendo, not overwriting our slot numbering
)256/257 are BC and MIOS on a Wii.
220'th were used for Hermes. instead of detecting Hermes IOS, USBGX bases it on the slot number, so 202;222-224 are reserved for hermes.
anything from 225-253 are free. a lot of users prefer using 248 instead of 252. As long as you remember your own setup, anything is fine.
Oh, some info :
DJ_skual helped me and made a WiiVC forwarder for USBGX.
I can now test the gamepad support.
1269_mod1 is bad! the buttons are all out of mapping (Home=Y, Right=Up, etc.), but I now have a working base to fix that for the next release (not before january now, sorry)
No idea if I'll find how to fix the NAND access to fix channel's listing and banner layout mode.
Last edited by Cyan,
how does the system know to use beta 53 instead of 52? and, does using a lower slot mean what's in that slot takes priority? I'm wanting to keep a fully-functional emuNAND if possible.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
USBGX doesn't know it should use it, you need to tell the loader to do it.
there's no slot priority, it's all manual.
Wiiflow uses a scan/autodetect/autochoose mode based on the "IOS base",
wiiflow auto-load a "cIOS base56" if you launch a game which officially require "IOS56", etc.
but not USBGX
So, you need to choose :
settings > Loader's settings > Loader's IOS : this one is the IOS slot used when inside the loader's interface (accessing channel's list, extracting Wii menu theme files, etc.). implicitely used to init the drive too.
settings > Loader's settings > game's IOS : this one is the global/default IOS slot used by Wii games (Wii, NAND, emuNAND)
Game > option > Game settings > IOS : individual setting for this game only, to bypass the default/global game's IOS setting. useful if only one game need a different IOS version or base.
there's an optional location :
meta.xml > arguments list > -ios=xxxx : this one is used to initialize the HDD at loader's launch, used to mount SD/USB to be able to load the user's setting file. This meta.xml is now automatically edited when you edit the loader's settings. but it can be set manually for testing purposes if you understand why/what to do.
to speed the mount/launch process, maybe this one is good :
loader's IOS and game's IOS : same cIOS (249, or 250, etc.)
meta.xml : 58 (manually edited, or else the loader would change it)
it uses 58 to init the drive, then load the settings, see you want cIOS for the loader so it reloads it. the cIOS already have the needed access so you skip the IOS58 patching time. when you launch a game, there's no IOS reload as it's already using the one you need.
I'm trying to change the boot process for 1269.
there's no slot priority, it's all manual.
Wiiflow uses a scan/autodetect/autochoose mode based on the "IOS base",
wiiflow auto-load a "cIOS base56" if you launch a game which officially require "IOS56", etc.
but not USBGX
So, you need to choose :
settings > Loader's settings > Loader's IOS : this one is the IOS slot used when inside the loader's interface (accessing channel's list, extracting Wii menu theme files, etc.). implicitely used to init the drive too.
settings > Loader's settings > game's IOS : this one is the global/default IOS slot used by Wii games (Wii, NAND, emuNAND)
Game > option > Game settings > IOS : individual setting for this game only, to bypass the default/global game's IOS setting. useful if only one game need a different IOS version or base.
there's an optional location :
meta.xml > arguments list > -ios=xxxx : this one is used to initialize the HDD at loader's launch, used to mount SD/USB to be able to load the user's setting file. This meta.xml is now automatically edited when you edit the loader's settings. but it can be set manually for testing purposes if you understand why/what to do.
to speed the mount/launch process, maybe this one is good :
loader's IOS and game's IOS : same cIOS (249, or 250, etc.)
meta.xml : 58 (manually edited, or else the loader would change it)
it uses 58 to init the drive, then load the settings, see you want cIOS for the loader so it reloads it. the cIOS already have the needed access so you skip the IOS58 patching time. when you launch a game, there's no IOS reload as it's already using the one you need.
I'm trying to change the boot process for 1269.
Last edited by Cyan,
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
yes, it's planned. I'll update all the home menu when on vWii or WiiVC.
Nintendont uses IOS58 and you don't even need to install any cIOS if you only want to play gamecube games.
like I said, cIOS is only for Wii games, not gamecube games.
Nintendont uses IOS58 and you don't even need to install any cIOS if you only want to play gamecube games.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
wait, let me re-read what's your problem and why you would need r53 (which is bad).
emuNAND often doesn't work with r53, you need r52 !
edit: ok I understood what you meant. you think too ahead of the problem here.
r53 was suggested only because another user who is currently using r53 doesn't have the vWii unsync issue, and you wanted to test r53 too.
but other users who use r52 don't have sync issue either.
r52 and r53 shouldn't affect the controller differently. you have another issue, but you can try r53 before thinking about needing to set back emuNAND to r52 like if you already found the fix to your problem.
if you have unsync in emuNAND, that's another problem or issue (and might be normal if you created a new NAND).
if you use emuNAND in vWii (to load channels installed to emuNAND, or neek) you need to dump your system file to that emuNAND copy. the SYSCONF file contains the controller sync information.
if you lose sync when resyncing in emuNAND, that's probably caused by this file's conflict.
if you only want to test r53, don't install it in a new empty slot !
don't install it like you will need to keep multiple version at the same time for whatever reason and imagining a way to get used to switch slots every time you play something different.
just replace for example the slot249 with r53 ! do your tests, if it doesn't fix or improve (it should even be worse), then revert back and reinstall r52 in slot 249.
if it helps, then, keep r53 and you don't need r52 anymore.
r53 is not always bad. some HDD don't work with r53+emuNAND, some work. you'll need to test to know if r53 is good or bad for you, but it has no relation to the WiiUPro.
Edit :
Surprise! I didn't expect it before 2018.
1269_mod2 with WiiU gamepad support
http://www.mediafire.com/?74jbrzozleqnk
It has some issue :
1. Stick's diagonals are not working.I don't know why ok I do, calibration range is different than gamecube sticks. but at least, it works, you can move the cursor and press the buttons. I'll try to fix it later.
2. cursor speed is very slow, you can change the speed from 0.18 to 0.5 in the GUI Settings. I'll made an automatic WiiVC detection to do speed x5 without needing to change the setting manually.
3. still no channel mode. didn't had time to debug it. (it finds how many channel is on NAND, but can't read the title from it. Maybe ES_ is working, but ISFS is not in IOS255? network is also not in IOS255?)
improvement: it should boot even faster.
emuNAND often doesn't work with r53, you need r52 !
edit: ok I understood what you meant. you think too ahead of the problem here.
r53 was suggested only because another user who is currently using r53 doesn't have the vWii unsync issue, and you wanted to test r53 too.
but other users who use r52 don't have sync issue either.
r52 and r53 shouldn't affect the controller differently. you have another issue, but you can try r53 before thinking about needing to set back emuNAND to r52 like if you already found the fix to your problem.
if you have unsync in emuNAND, that's another problem or issue (and might be normal if you created a new NAND).
if you use emuNAND in vWii (to load channels installed to emuNAND, or neek) you need to dump your system file to that emuNAND copy. the SYSCONF file contains the controller sync information.
if you lose sync when resyncing in emuNAND, that's probably caused by this file's conflict.
if you only want to test r53, don't install it in a new empty slot !
don't install it like you will need to keep multiple version at the same time for whatever reason and imagining a way to get used to switch slots every time you play something different.
just replace for example the slot249 with r53 ! do your tests, if it doesn't fix or improve (it should even be worse), then revert back and reinstall r52 in slot 249.
if it helps, then, keep r53 and you don't need r52 anymore.
r53 is not always bad. some HDD don't work with r53+emuNAND, some work. you'll need to test to know if r53 is good or bad for you, but it has no relation to the WiiUPro.
Edit :
Surprise! I didn't expect it before 2018.
1269_mod2 with WiiU gamepad support
http://www.mediafire.com/?74jbrzozleqnk
It has some issue :
1. Stick's diagonals are not working.
2. cursor speed is very slow, you can change the speed from 0.18 to 0.5 in the GUI Settings. I'll made an automatic WiiVC detection to do speed x5 without needing to change the setting manually.
3. still no channel mode. didn't had time to debug it. (it finds how many channel is on NAND, but can't read the title from it. Maybe ES_ is working, but ISFS is not in IOS255? network is also not in IOS255?)
improvement: it should boot even faster.
Last edited by Cyan,
well, I tested just going into usb loader gx, and I didn't have a sync issue. I was going to test a wii game, but my hdd died. it was less than a year old too. I'm getting a replacement for it. I found a replacement drive, and I Have two backups of my wii hdd. I'm transferring the content now. could this issue be the result of using a theme? I noticed it doesn't happen when using a wii vc game. I'm assuming it uses the some of the same files as the virtual wii since the system restarts whenever you go from the wii vc game back to the wii u menu. I'm basing this on the fact that both wii vc and the wii reset the system when returning to the wii u menu. what I mean is that the cbhc autobooting screen appears with both in that case.
I found a replacement drive, and I Have two backups of my wii hdd. I'm transferring the content now. could this issue be the result of using a theme? I noticed it doesn't happen when using a wii vc game. I'm assuming it uses the some of the same files as the virtual wii since the system restarts whenever you go from the wii vc game back to the wii u menu. I'm basing this on the fact that both wii vc and the wii reset the system when returning to the wii u menu. what I mean is that the cbhc autobooting screen appears with both in that case.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
I'm not familiar with theming the menu, but I'd imagine it only affects the design (replacing pictures or font), so it shouldn't affect the controller's data.
sorry, I don't have a lot of suggestions.
I'd only recommend trying to reinstall the cIOS (same base/version). Sometime a bad installed cIOS can cause SYSCONF issues. seeing it affects the controller only when you use USBGX, it's related to cIOS.
ah, another idea:
did you try to set USBGX with IOS58, exit (to be sure it uses 58 next time)
sync the pad (if unsync)
boot USBGX and exit without launching a game, so it never load the cIOS in memory.
see if it affects the syncing. (it shouldn't, the loader itself shouldn't do any modification to sysconf file)
that will narrow the issue, and leave out the possibility of being the loader's fault.
sorry, I don't have a lot of suggestions.
I'd only recommend trying to reinstall the cIOS (same base/version). Sometime a bad installed cIOS can cause SYSCONF issues. seeing it affects the controller only when you use USBGX, it's related to cIOS.
ah, another idea:
did you try to set USBGX with IOS58, exit (to be sure it uses 58 next time)
sync the pad (if unsync)
boot USBGX and exit without launching a game, so it never load the cIOS in memory.
see if it affects the syncing. (it shouldn't, the loader itself shouldn't do any modification to sysconf file)
that will narrow the issue, and leave out the possibility of being the loader's fault.
Last edited by Cyan,
I remember trying that ios before for some reason, and the loader could no longer find any games on the usb drive. I have my gc games on an sd card. should the pad sync while in virtual wii mode?
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
no, the pad can't sync on the vWii system menu.
well, you can register it by pressing the red button, but it will unsync right away (meaning it worked!)
the system menu shutdown the sync WiiUPro controller if found, but then homebrew can use it.
PS: your signature doesn't have the link to PS3 1 of 2
well, you can register it by pressing the red button, but it will unsync right away (meaning it worked!)
the system menu shutdown the sync WiiUPro controller if found, but then homebrew can use it.
PS: your signature doesn't have the link to PS3 1 of 2
should I try a different cios or would they all behave the same with beta 52 being used for all three?
oh, yeah, I fixed the problem. I recently redid part 1 of my tutorials to add coloring since you can't do that in CODE bb code.
btw, I'm having a weird issue with saving. if I save, then place the content into a word document. it won't be double-spaced when I transfer it back. this doesn't happen on psx-place. also, whenever I save a large post, it creates all these extra bb codes in the post. it doesn't mess up the content, but you can no longer find what you want to edit. because of these two issues, I have to edit in word, transfer the content to psx-place, then copy and paste that on to here. it's frustrating. :-/
oh, yeah, I fixed the problem. I recently redid part 1 of my tutorials to add coloring since you can't do that in CODE bb code.
btw, I'm having a weird issue with saving. if I save, then place the content into a word document. it won't be double-spaced when I transfer it back. this doesn't happen on psx-place. also, whenever I save a large post, it creates all these extra bb codes in the post. it doesn't mess up the content, but you can no longer find what you want to edit. because of these two issues, I have to edit in word, transfer the content to psx-place, then copy and paste that on to here. it's frustrating. :-/
Similar threads
-
@
Psionic Roshambo:
@Veho, didn't need any news. Just going to the store and buying groceries is a constant reminder. -
-
-
@
Veho:
Reminded that every single price gouging law was blocked by republicans because "muh gubmint overreach"? -
-
@
Psionic Roshambo:
The problem with X party blocked X bill that would have prevented X is that yes the bill probably would have worked great, buuuttt they put XYZDCBG in said bill as an attempt to sneak things in that tend to be completely unrelated to the original bills intent. It sucks because if they would just do a single thing they could probably get something done...
-
@
Psionic Roshambo:
But congressman X needs to have government funding for his cousins unicycle business
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Rotflmao 