Wii U to vWii forwarder channels -AC

[mrmagicm]

I have not had any problems with fceugx or fceutx, all the buttons work and load the roms like any other emulator, I don't know what problem you have, but make sure you have the latest versions of each emulator

I use FCEUXTX 1.1.7 (the latest), on TIRAMISU, with forwarder from THIS forum: FCE Ultra TX 0005000206212000/apps/fceutx/boot.dol
And for me the CROSS (directionnal below the joystick) on the WIIU gamepad doesn't work for me for donkey kong Nes ou Fist of the North Star 1 and 2. Does it work for you Elru please?
It's weird, as PABLOLUNAJESUS as the same kind of problem, but with genesis plus gx that works for me on every button or directionnals. At the moment, I'm redownloading both emus and reinstalling forwarder to "Recheck"....
Also, what WAD channel do you use in Vwii Mode? Mine is FCEUXTX-Channel-1.5-vWii.wad

 

[Elru]

I use FCEUXTX 1.1.7 (the latest), on TIRAMISU, with forwarder from THIS forum: FCE Ultra TX 0005000206212000/apps/fceutx/boot.dol
And for me the CROSS (directionnal below the joystick) on the WIIU gamepad doesn't work for me for donkey kong Nes ou Fist of the North Star 1 and 2. Does it work for you Elru please?
It's weird, as PABLOLUNAJESUS as the same kind of problem, but with genesis plus gx that works for me on every button or directionnals. At the moment, I'm redownloading both emus and reinstalling forwarder to "Recheck"....
Also, what WAD channel do you use in Vwii Mode? Mine is FCEUXTX-Channel-1.5-vWii.wad

As I said, it works perfect, I tried each one you mentioned.
I don't use any wad in vWii there's no need, the forwarders are to directly execute the dol files, maybe that's your problem

 

[mrmagicm]

Ok...Found out the problem! The thing, even on wiiU, the FCE Ultra TX is set to work on a "wiimote" by default (maybe), so I had to go in parameter menu of FCEDTX then select wiiU "WIIU gamepad" as controller.....Noone gaved me the answers ^^ Strange thing, is that is was working with wiiu gamepad but without the "directionnal keys", that thing was misleading me, anyway, it's solved. ​

PABLOLUNAJESUS Maybe your problem is the same as I had but in your emu.​

Thanks for you help (so the forwarders in Vwii weren't the pb)

 

[chaxho]

I've recently been doing this same method and releases will be hopefully soon I fully scrapped all my previous Emulators and fully redesigned them New Banners. Logo, Icon, DRC and boot sounds With a full minimalistic look And honestly turned out better than i had thought.

https://mega.nz/folder/8x1RDQQS#IPmetNrsXLNik9bItp7ZnA
This version in this folder is a experimental build which I don't think got pushed out btw Blackb0x had sent me so for latest features use the .dol also

Post automatically merged: May 2, 2023

Issue with Not64 is no Gamepad support as far as im aware

Post automatically merged: May 2, 2023

I have Wii flow with Gamepad support if you want it?

Hello
can you send me the wii flow channel wirh gamepad support for aroma?

 

[L0w]

Thank you for the great work @AdamCatalyst!
I did build my own forwarder as well for WiiSX. If someone needs it, I did put a link in the WiiSX thread.
The forwarders make our Wii U lives so much easier!

I do have one question about the N64 forwarders though: Do they all support the Wii U overclock (sign c2w patcher via homebrew) option?
It is not totally clear to me, so I need to be sure

 

[Auxxann]

i have done usb loader gx but when i start it it goes to the vwii but after it goes back to the wii u menu i will try again but if someone already made it send me the download pls

Post automatically merged: Jan 27, 2024

 

[blue-spirit]

Is it possible to autoload to a specific rom with this method? I was playing with this idea for some time and I found some tutorials for single rom loaders but I don't know if these are still up to date.

 

[spookini]

I'm trying to use this for Project + but it just reboots the console instead of loading the boot.elf, the game works if you load from hbc but I want to use the gamepad support.

 

[Sowden]

I'm trying to use this for Project + but it just reboots the console instead of loading the boot.elf, the game works if you load from hbc but I want to use the gamepad support.

From my understanding Aroma doesn't load elf files. It only loads rpx or wuhb files.

 

[spookini]

But this is loading it in the vwii and should be the same as the homebrew channel right?

 

[Sowden]

But this is loading it in the vwii and should be the same as the homebrew channel right?

Oh I see what your saying now. For vWii if you want Gamepad support, you need to use a forwarder as opposed to boot2vwii. Boot2vwii will never let you have Gamepad, but a forwarder will never let you use USB storage. That's the trade off.

 

[spookini]

yeah so I'm using the method from this post to make a forwarder to apps/projplus/boot.elf
which worked when I made one that goes to apps/ridersnintendont/boot.dol
and when I use it for project + it loads into vWii and reboots the console back to the wii u menu
Is this method just not capable of reading the disk in the drive? Would there be a way to pack the iso into the forwarder?

 

[jul16ares]

but a forwarder will never let you use USB storage. That's the trade off.

Hbl2hbc or do that trick, but it's an elf, and therefore works only with titamisu, that's the big reason why tiramisu, keep my preferences

 

[AVissie]

Hi, so i just go the genesis plus gx forwarder. it says that gamepad is supported but when I use the forwarder and the emulator launches the gamepad is not detected and I did go into the input settings to check, not there

 

[HomeStarRunnerTron]

To anyone who still needs Nintendont, here's my own try at the forwarders I needed. Thank you so much, AdamCatalyst, for making such an incredible tutorial.

Things to mention about Nintendont: No rumble on Wii U Gamepad. Which is weird, because I really thought I'd successfully had rumble before. Must just be a false memory I created while playing with a GameCube controller while looking AT the gamepad, because it just doesn't seem like anyone ever got that working, in my searches. I also think you can only successfully read from SD? MAYBE front USB slot, but you'd have to hide it from the actual Wii U, otherwise it's gonna try to format it. Not worth it to use the USB slot, even if it IS possible, I think.

FCE Ultra TX
0005000206212000
/apps/fceutx/boot.dol

Genesis Plus GX (redid, was broken before)
0005000207160700
/apps/genplusgx/boot.dol

mGBA
0005000213020100 (Er, well, in redoing this, I accidentally made it 0005000213070200 instead. But it actually worked this time! 'Cause my last go didn't work. Dees' one does.)
/apps/mGBA/boot.dol
/apps/mgba/boot.dol

Nintendont
0005000214142000
/apps/Nintendont/boot.dol

SNES9x RX
0005000219182400
/apps/Snes9xRX/boot.dol

Visual Boy Advance GX
0005000222022400
/apps/vbagx/boot.dol

Wii64 Rice
0005000223180500
/apps/wii64 Rice/boot.dol

 

[ShadowOS]

Okay at this point I'm convinced no one has actually made a proper Wii64 OC forwarder, and neither have I. Judging from Wii64 compatibility page, someone must have been successful in the past but I haven't seen any recent forwarders that actually enable the OC.

(1) First I tried all the forwarders I could find online and within GBATemp, including this thread. I tested Golden Eye, Conkers, and Diddy kong Racing. For each forwarder, the performance was the exact same as when I launched from vWii manually.

Goldene Eye - From frontend to level load everything is 60fps until the damn scene renders, then it's at 15fps. Start of gameplay bounces between 15 and 30fps. Immediately turning around and facing the garage/shutter FPS goes to 40. Running up to the watch tower is about 20-25fps, sometimes 30, sometimes sub 20. Standing about half way through the tunnel is 25-30ish, sometimes 40 frames depending where you stand. Exiting the tunnel the next area will make the FPS dip to 10-15 during the firefight.

Conkers - 30fps during the splash screens, about 15-18fps when Conker starts chainsawing the N64 logo. The tavern is 25-30fps depending on how quickly you scroll through the options. The opening sequence is a solid 30fps.

Diddy Kong Racing - Loading into the world is about 25-30fps. FPS remains stable throughout the first race, pretty much locked at 30fps with a rare dip here and there.

(2) I confirmed manually launching vWii does not trigger any sort of OC by comparing Saulfabreg's WiiStation forwarder. Launching manually through vWii gives 700-something mhz, which is expected. Using Saulfabreg's WiiStation forwarder produced the OC of 1.25ghz.

(3) I confirmed the performance of the above three games were identical on my physical Wii when compared to the existing Wii64 forwarders on Wii U.

(4) Given the above, I made my own Wii64 forwarders for glide and rice. Exact same results for Wii64, no FPS improvements in the three aforementioned games. Maybe I made them wrong? Nope! Since WiiStation has a confirmed working case I decided to make my own WiiStation forwarder; I successfully made a forwarder with OC enabled.

This leads me to believe there is a problem with Wii64 BUT as previously mentioned, apparently at one point someone was successful otherwise there wouldn't be notes about overclocking in the Wii64 Compatibility wiki.

For programs and assets, I used these:
- wii64_wiivc and wii64 Rice_wiivc as found in the latest Wii64 release package.
- A modified TeconMoon's injector (the latest official release of TeconMoon's injector spits out an empty directory when you try to enable OC. The modified version I linked has its own small bugs but produces working injects, a la the WiiStation one I created).

So, has anyone successfully created a working Wii64 OC forwarder or has any clue what the problem could be? Note that the forwarder simply launching Wii64 DOES NOT MEAN OC IS WORKING (tons of people have made this mistake from what I can see).

OR maybe I've wasted a bunch of time and the three games I used to test don't benefit from OC? Any leads here would be appreciated.

 

[V10lator]

@ShadowOS Are you patching the Wii VC loader to load the patched file enabling the overclock from the inject instead of NAND before starting the inject containing it? For Aroma this would be doable with https://hb-app.store/wiiu/C2WPatcher , for example

 

[ShadowOS]

@ShadowOS Are you patching the Wii VC loader to load the patched file enabling the overclock from the inject instead of NAND before starting the inject containing it? For Aroma this would be doable with https://hb-app.store/wiiu/C2WPatcher , for example

Yes.

SD:\wiiu\environments\aroma\plugins\c2w_patcher.wps
SD:\wiiu\environments\aroma\modules\setup\01_sigpatches.rpx

I am using the vWii versions of Wii64-glN64 and Wii64-Rice, provided in the latest Wii64 1.3 github release.

There is nothing wrong with my Wii U's setup as evidenced by the fact WiiStation receives the expected CPU Unlock.

There is nothing wrong with how I've created the Wii64 forwarders as evidenced by the fact I made my own WiiStation forwarders: one that unlocks the CPU and one that does not unlock the CPU, confirmed within the emulator.

What I have not seen anywhere is someone confirm/validate that Wii64 actually benefits from the CPU unlock, or if the CPU unlock feature is actually working. On the compatibility Wiki I see ambiguous notes like "might run better with overclock" or "needs vWii overclock for better performance". I see youtubers saying "WHOA LOOK AT HOW SMOOTH IT IS" even though performance is identical to that of a physical Wii. I see people on various forums saying "The forwarder works now!" with no confirmation that the unlock CPU has actually taken effect. I see performance identical between a supposedly "unlocked" Wii64 and a physical Wii and a standard vWii application.

What I'd like to see is someone, anyone name a game that for sure demonstrates a performance boost with an unlocked CPU, and actually demonstrate the difference. What'd be even better is a visual indicator for Wii64 that the CPU unlock has taken effect similar to how WiiStation does it, but that's a feature request I'll make in the appropriate threads, not here.

The only things I can think of for why this isn't working are (1) Unlocked CPU simply does not work for Wii64 1.3; (2) Unlocked CPU has no measurable difference for Wii64; (3) There's an undocumented 'special configuration' for Wii64 that needs to be applied.

Later tonight I'm going to try Wii64 1.2 based off a comment from the compatibility Wiki. I don't know if the feature exists for that version, but supposedly it does based off this Smash Bros comment "...but on not64 you can fix this by turning cpu clock devider to ON and using vwii overclock for perfect full speed and gfx with glide pluggin."

Still, seems like I'm grasping at straws.

 

[V10lator]

on not64 you can fix this by turning cpu clock devider to ON

Not sure what this means and never used Wii64/Not64 but I would assume it's an option somewhere inside of the emulator.

No need to waste time to reply in case I'm wrong or you already confirmed but did you check it is enabled?

//EDIT: BTW, IIRC Wii software not supporting the overclock should just blackscreen when overclocking is enabled in the inject + c2w patches applied (the Aroma plugin does not apply the patchset in case of option not choosen while injecting to prevent this), so in case you're right and it doesn't work while Wii U side is set up correctly that sounds like a bug of the emulator to me.

//EDIT2: Also IIRC I never confirmed what happens when the software doesn't support the overclock but tested loading c2w patches with titles not having the correct file to load (overclocking option not enabled in the injector or Wii software from Wii U eShop) only, so take it with a grain of salt.

 

[ShadowOS]

FOUND THE PROBLEM. It was "(3) There's an undocumented 'special configuration' for Wii64 that needs to be applied."

I went through many more forum posts but ultimately found the answers in old github threads, right on the Wii64 github page. Smart place to look, right? There are a number of posts talking about the clock divider and it needing to be set to 1 to take advantage of the overclock. Here are just a few examples:

https://github.com/emukidid/Wii64/issues/38#issuecomment-758165052
https://github.com/emukidid/Wii64/issues/28#issuecomment-699703561
https://github.com/emukidid/Wii64/issues/17#issue-312644268

CPU Divider Settings:
1 = Unlocked Wii64 (A.K.A. WiiVC)
2 = Wii CPU speeds (A.K.A vWii)
3 = GCN CPU speeds

Now, due to the following request, the CPU Clock Divider was defaulted to 2:

https://github.com/emukidid/Wii64/issues/39#issuecomment-900210179

It's not a bad idea since some games do run good enough or surprisingly are just more playable when using vWii CPU speed*. However, since there's no documentation stating CPU Clock Divider needs to be set to 1 for overclock speeds, most people will probably be playing with placebo (a la the many youtube videos I've seen). What really bugs me though is that I did change the clock divider setting, but I must have been doing it on vWii and my physical Wii, and not with the overclocked forwarder.

It also doesn't help that the documentation is inconsistent**.

Regarding the Wii64 forwarders on the main post of this thread, I can confirm they are NOT CPU UNLOCKED***.

* Tomorrow I will post my thoughts on unlocked CPU WiiVC vs vWii based off gameplay experiences with a few games.
** Tomorrow I'll post some problems with the documentation and make a quick numbered guide on how to set things up correctly.
*** Tomorrow I'll post some PROPERLY UNLOCKED FORWARDERS for Wii64 regular/glide and rice.