WiiSX RX - A new fork.

you can just use a regular installer and rename the file.

i have the channel for the original wiisx and that installer just boot the bootdol placed in wiisx/boot.dol so you can just replace that boot dol and leavue wiisx name intact on the apps folder and it will work

 

after some testing, this issues ive run into so far are (and if im not supposed to do this here plz lemme know): rugrats search for reptar: runs great but some (not all) of the fmv's dont play (are they hard to emulate?), toy story 2 (emu code dumps after clicking on the folder (not even the bin file, just entering the directory makes the emu go kaplooie), and crash 3 erformance is even better, tho still has the same gfx issues as wiisxr

— Posts automatically merged - Please don't double post! —

ignore the emoji, that was a typo

 

That worked! God knows what was going on with the installer. Thanks!

 

basicaly any installer just points to a boot.dol on the apps folder for isntance i cloned wii64 installer and one points to wii64 and another to wii64rice and another to not64 and so on, as long as the filename matches its what they boot.

 

wait how do u do this exactly? I just keep switching from Wii64 Rice and Not64 due to performance differences if there's a way to make the games be recognized from both ends without having to rename the folder of where the games are, I would love to know

 

i have several injects on my wiiu menu all pointing to a specific path.

one points to apps/wii64/boot.dol another to apps/wii64rice/boot.dol and another to apps/not64/boot.dol

 

yes, i love it

 

Hi, quick question. I can't make the Wii U pro controller to work. Do I have to edit something in settings or how do I make it work?

I have a 3rd party Wii U pro controller l. Can this be the reason? Could a 3rd party controller work?

Thank you very much for your response, I really want to play this with the generic controller

Regards

 

probably is because its third party/fake, the code only works with originals, same way most fake wiimotes/CC dont work in most homebrew apps.

 

how come?

 

3rd party controllers dont use the same code protocols, some of them just do random shit, they work in real games and wii menu becuase the code is full of checks so it doesnt let them get away too much and ignores most signals that arent well standard on homebrew we use codes that read every singnals and protocols and if a controller just throws random data around obviously its not very usefull on homebrew, some controllers even crash some hb aplications due to the codes they send out.

 

Thank you very much everyone for the comments and recommendations. I really was expecting to play with the 3rd party controller but oh well.

Unfortunately, the original controller in Mexico still costs (used) around 60 USD, so I'll keep playing the WiiSX with the gamepad.

 

jesus, guess i should be lucky stuff got pretty cheap here in the US, been eyeing a black wii classic controller thats $17 from walmart (need it for the wii chocolate doom ports)

 

Really happy to see a PSX emulator still being worked on.

I just installed the latest build on my Wii U with the proper channel loaders as well.
Do we still need to run sigpatcher for the speedup before running the Wii U loader or nah?

 

It would be cool if they merged the overclock to the WUP Fowarder..

 

Yeah if doable, that would be awesome.
But yeah I ran some tests and it does look like the overclock is needed for the most part.

Keep up the great work!

 

Phew, it's been a while. But the classic controller problem is still irritating me. Looking through @Wiimpathy 's autoboot commit on github, I've noticed that they added a message box as a sort of workaround for input not responding. My question for Wiimpathy is:
Did wiisxrx not respond to any controllers at all before adding this message box?

 

It didn't respond at all. It's a quick 'n nasty hack. The controller is automatically detected when we access the menu at startup. I haven't investigated more about the auto input routine. You have to dig into that part of code to improve it.