Hacking WiiFlow Lite

  • Thread starter Thread starter fledge68
  • Start date Start date
  • Views Views 1,030,954
  • Replies Replies 4,832
  • Likes Likes 66
Ok, just to be clear.

You want to launch WiiWare title that requires neek2o through WFL, then when you exit, you want to return to WiiFlow Lite.


Answer:
neek2o NK2O_1 .wad... must be installed using WFL NAND Emulation Settings.

WFL Settings - Page 1/14
NAND Emulation Settings --- Set
Page 2/3 --- Install Wad --- Go
Find neek2o NK2O_1 .wad --- Install

When running neek2o environment game, after exiting, you'll return to Wii System Menu. I don't believe it is possible to return to loader after playing neek2o game. If you cannot find said .wad file, PM me.

Hope this helps you out.
 
Last edited by RunningSnakes,
Ok, just to be clear.

You want to launch WiiWare title that requires neek2o through WFL, then when you exit, you want to return to WiiFlow Lite.


Answer:
neek2o NK2O_1 .wad... must be installed using WFL NAND Emulation Settings.

WFL Settings - Page 1/14
NAND Emulation Settings --- Set
Page 2/3 --- Install Wad --- Go
Find neek2o NK2O_1 .wad --- Install

When running neek2o environment game, after exiting, you'll return to Wii System Menu. I don't believe it is possible to return to loader after playing neek2o game. If you cannot find said .wad file, PM me.

Hope this helps you out.
the only way to return to wiiflow is have priiloader installed and setup to launch wiiflow on bootup. you have to have the forwarder channel installed and have priiloader launch a special dol i have mentioned on here before that will be on the root of your SD card.
 
the only way to return to wiiflow is have priiloader installed and setup to launch wiiflow on bootup. you have to have the forwarder channel installed and have priiloader launch a special dol i have mentioned on here before that will be on the root of your SD card.

@fledge68 Thanks. I have already setup priiloader to autoboot into WiiFlowLite using a special priiloader forwarding DOL (all of that on my real NAND). Is that the special DOL you are talking about? Or are you talking about an even more special DOL which enables a [neek2o EmuNAND Game] ---> [WiiFlowLite Real NAND] return route?

As I say, if upon exiting a neek2o hosted game something can make the system genuinely reboot, priiloader should get me back to WiiFlow. What does the wad that @RunningSnakes mentioned actually do in layman's terms? Imagine these wads (that people kindly make) were actually named based on what they do. "neek2o NK2O_1.wad" - crazy! I think ModMii even generates that WAD with that name. Purposeful obfuscation? Probably not.

@RunningSnakes Thank you, Sir. As I say, I don't understand what that wad is or does, but I can certainly blindly install it on my EmuNAND risk free and see if there is any change.

BTW guys, presumably uninstalling a wad on an EmuNAND requires booting into it and using a wad manager, or using ShowMiiWads on a PC.
 
[Note: I haven't done anything related to the above post yet. I'm just using CIOS EmuNAND.]

TL;DR: What is the most logical sequence of steps to try to resolve a WiiFlow boot loop? Delete the "cache" folder on USB? Delete the save game file (I don't know what it stores)? Disable the EmuNAND?

GOTO: "End"

My WiiFlowLite install gets stuck in a boot loop any time I try and run it. The last thing I did before hitting the first boot loop was exit an EmuNAND game which required the classic controller (which was not plugged in). It said "press 1 to exit" or something after telling me I needed the CC. The thing I did before that was hide one of the buttons in one of the plugin tiers using WiiFlow's built-in show/hide feature. I'm using Shima's theme, but not using sourceflow.

GOTO "TL;DR"

End: Cheers!
 
  • Like
Reactions: RunningSnakes
Where do you have WiiFlow installed? SD or USB? Whatever the case, try going to apps/wiiflow/wiiflow_lite.ini <<< Rename this file for backup purpose ^^^^^^

Boot back into WFL and all should be default with hopefully no loop.

You can uninstall game.wad through WFL, select the game, then press X button right side box, permanently delete press go.

The neek2o NK2O_1.wad should bring you back to WiiFlow Lite Real NAND after exiting neek2o emuNAND game.
 
@fledge68 Thanks. I have already setup priiloader to autoboot into WiiFlowLite using a special priiloader forwarding DOL (all of that on my real NAND). Is that the special DOL you are talking about? Or are you talking about an even more special DOL which enables a [neek2o EmuNAND Game] ---> [WiiFlowLite Real NAND] return route?

As I say, if upon exiting a neek2o hosted game something can make the system genuinely reboot, priiloader should get me back to WiiFlow. What does the wad that @RunningSnakes mentioned actually do in layman's terms? Imagine these wads (that people kindly make) were actually named based on what they do. "neek2o NK2O_1.wad" - crazy! I think ModMii even generates that WAD with that name. Purposeful obfuscation? Probably not.

@RunningSnakes Thank you, Sir. As I say, I don't understand what that wad is or does, but I can certainly blindly install it on my EmuNAND risk free and see if there is any change.

BTW guys, presumably uninstalling a wad on an EmuNAND requires booting into it and using a wad manager, or using ShowMiiWads on a PC.
yes that is the dol i am talking about.

"neek2o NK2O_1.wad" is a channel installed on your emunand that when launched switches you from the neek2o emunand back to the wii's real nand or it basically reboots the wii to use realnand. i believe its sometimes referred to as nswitch (neek switch) channel. I believe its the same channel you install to real nand that when launched will reboot the wii to use the emunand you have setup for neek2o.

if i recall, you said when you exit a neek2o game the screen just goes black. but you should see the neek2o emunand system menu with channels you have installed on it. i'm not sure whats wrong. i am not an expert at using neek2o. I tried to avoid it. @Cyan seems to know quite a bit about it. but he is very busy with real life.

If I launch a WiiWare game in neek2o mode, play it for a bit (optional) and then finally exit the game normally by pressing Home and then System Menu, the screen goes black and the DVD drive starts flashing. Any ideas why?
have you ever launched neek2o from real nand? not via wiiflow? this black screen and drive light flashing is what happens when you launch neek2o and can take a long time especially on first boot depending on how many games/channels you have installed on the neek2o emunand. maybe this is your problem.

"Update on how things work: Using Wiiflow rev 712+ and neek2o rev93+
1. Start Wiiflow from real nand > Start any Wiiware in normal mode > Exit game > back to Wiiflow on real nand
2. Start Wiiflow from real nand > Start any Wiiware in neek2o mode > Exit game > back to Wiiflow on neek2o nand
3. Start Wiiflow from Neek2o nand > Start any Wiiware in any mode > Exit game > back to Wiiflow on neek2o nand
4. To go back to real nand select "Exit to real nand" from Wiiflow exit menu"
by the way 3 and 4 no longer work in wiiflow lite. only the old wiiflow 4 could do 3 and 4 but not very good. there were issues so i removed those options to clean things up.
 
Last edited by fledge68,
neek2o NK2O_1.wad

What is it :
these are (old) Nswitch homebrew compiled and injected into a channel.
There are different channels nicknamed "Neek2o" or "nswitch" with TitleID "NK2O" which are only different themed "animated banner", all the WAD are exactly the same content, except the banner color and animation.
You just pick the one you prefer based on its look and whether you want it to fit your theme'd sysMenu.


What it actually does:
(Old !!) Nswitch was created to act as a "switch" like its name implies.
If you install that channel on sysNAND and launch it, it's used to launch Neek.
If you install that channel on Neek's emuNAND, and launch it, it just exits Neek (actually, it's just rebooting the console)

I'm only talking about the old nswitch, injected in all the channels with titleID "NK2O" which you can find here : https://code.google.com/archive/p/custom-di/downloads

There are new version of Nswitch which I don't know, but I guess their purpose are still the same : just a switch realNAND <-> NeekNAND based on where you launch it.

How it can be useful :
If you have that "NK2O" channel installed on your Neek's emuNAND, and use neek2o Autoboot feature + "return to" feature, you can tell Neek2o to return to "NK2O" when you exit the launched game in order to reboot the console at game exit.
real NAND -> game launcher (USBGX, wiiflow?) -> Game on neek launched with autoboot -> back to realNAND.
you don't see the Neek's system menu at all. Only the game you want to play launches, using the benefit of neek's better compatibility (but slower to boot, feature missings like cheats, patches, etc.); and exits back to real NAND where you can tell Priiloader to load Wiiflow by default at console's (re)boot.



BTW guys, presumably uninstalling a wad on an EmuNAND requires booting into it and using a wad manager, or using ShowMiiWads on a PC.
Nope, you better use a Wad manager "outside" the emuNAND, without first booting into it.
Not that you can't or shouldn't do it while inside neek, but just because it's faster and easier to not boot into neek. WARNING: homebrew inside NEEK is REALLY HARD to setup and use.

a few wad managers homebrew are compatible with emuNAND's "additional" folders. not booting into it using neek and faking to manage "real NAND" while being on neek.

USBLoaderGX (no advertising intended, just fact to be useful) is one of them. but probably not the most complete feature wise. just the bare minimum (install/uninstall from single wad or folders).
there are others too, you just have to look into your favorite manager if it's compatible with emuNAND (it usually mean managing folders instead of current console's storage)

Note: You can also use Savegame Manager GX to manage you emuNAND's savegames without booting into your emuNAND!
 
Last edited by Cyan,
Where do you have WiiFlow installed? SD or USB? Whatever the case, try going to apps/wiiflow/wiiflow_lite.ini <<< Rename this file for backup purpose ^^^^^^

Boot back into WFL and all should be default with hopefully no loop.

You can uninstall game.wad through WFL, select the game, then press X button right side box, permanently delete press go.

The neek2o NK2O_1.wad should bring you back to WiiFlow Lite Real NAND after exiting neek2o emuNAND game.

Thanks Snakes. In the end I deleted the cache folder and I think that is what fixed it. From now on I'm simply going to backup the entire USB wiiflow folder periodically. Simple. I don't think the ini was at fault, and if I get wiiflow to generate a new one it sets all the paths to SD again.

yes that is the dol i am talking about.

"neek2o NK2O_1.wad" is a channel installed on your emunand that when launched switches you from the neek2o emunand back to the wii's real nand or it basically reboots the wii to use realnand. i believe its sometimes referred to as nswitch (neek switch) channel. I believe its the same channel you install to real nand that when launched will reboot the wii to use the emunand you have setup for neek2o.

if i recall, you said when you exit a neek2o game the screen just goes black. but you should see the neek2o emunand system menu with channels you have installed on it. i'm not sure whats wrong. i am not an expert at using neek2o. I tried to avoid it. @Cyan seems to know quite a bit about it. but he is very busy with real life.


have you ever launched neek2o from real nand? not via wiiflow? this black screen and drive light flashing is what happens when you launch neek2o and can take a long time especially on first boot depending on how many games/channels you have installed on the neek2o emunand. maybe this is your problem.


by the way 3 and 4 no longer work in wiiflow lite. only the old wiiflow 4 could do 3 and 4 but not very good. there were issues so i removed those options to clean things up.

Cheers. Well that switch channel WAD was definitely not on my EmuNAND because I used your WiiFlow WAD injector to just install a couple of game WADs. So that would make sense I guess. I might try it again at some point but I've realised that neek2o seems almost never needed, although I could see the benefit of basically autobooting into it and never using the System NAND ever again. But presumably there is some kind of performance hit of running the whole system off a USB2 HDD rather than flash memory. Either way, it's good to understand neek2o in case you want to use it.

Random note: I have two SATA-USB enclosures and only one works with neek2o. The one that doesn't work is a newer 2.5" USB3 one with a single USB cable (not a Y splitter) and the other is an old 3.5" one with a PSU. Personally I think the power supply difference is the deciding factor. It's a bit baffling that neek is so fussy about USB drives, when all other homebrew doesn't seem to be.

What is it :
these are (old) Nswitch homebrew compiled and injected into a channel.
There are different channels nicknamed "Neek2o" or "nswitch" with TitleID "NK2O" which are only different themed "animated banner", all the WAD are exactly the same content, except the banner color and animation.
You just pick the one you prefer based on its look and whether you want it to fit your theme'd sysMenu.


What it actually does:
(Old !!) Nswitch was created to act as a "switch" like its name implies.
If you install that channel on sysNAND and launch it, it's used to launch Neek.
If you install that channel on Neek's emuNAND, and launch it, it just exits Neek (actually, it's just rebooting the console)

I'm only talking about the old nswitch, injected in all the channels with titleID "NK2O" which you can find here : https://code.google.com/archive/p/custom-di/downloads

There are new version of Nswitch which I don't know, but I guess their purpose are still the same : just a switch realNAND <-> NeekNAND based on where you launch it.

How it can be useful :
If you have that "NK2O" channel installed on your Neek's emuNAND, and use neek2o Autoboot feature + "return to" feature, you can tell Neek2o to return to "NK2O" when you exit the launched game in order to reboot the console at game exit.
real NAND -> game launcher (USBGX, wiiflow?) -> Game on neek launched with autoboot -> back to realNAND.
you don't see the Neek's system menu at all. Only the game you want to play launches, using the benefit of neek's better compatibility (but slower to boot, feature missings like cheats, patches, etc.); and exits back to real NAND where you can tell Priiloader to load Wiiflow by default at console's (re)boot.




Nope, you better use a Wad manager "outside" the emuNAND, without first booting into it.
Not that you can't or shouldn't do it while inside neek, but just because it's faster and easier to not boot into neek. WARNING: homebrew inside NEEK is REALLY HARD to setup and use.

a few wad managers homebrew are compatible with emuNAND's "additional" folders. not booting into it using neek and faking to manage "real NAND" while being on neek.

USBLoaderGX (no advertising intended, just fact to be useful) is one of them. but probably not the most complete feature wise. just the bare minimum (install/uninstall from single wad or folders).
there are others too, you just have to look into your favorite manager if it's compatible with emuNAND (it usually mean managing folders instead of current console's storage)

Note: You can also use Savegame Manager GX to manage you emuNAND's savegames without booting into your emuNAND!

Very informative and should be stickied or in a guide somewhere. The only thing missing is how to tell neek where you want it to return to.

I've realised that WiiFlow can effectively remove at least game WADs from an EmuNAND, by deleting the game in the normal way. But a second option below "Install WAD" for removing WADs would be good and presumably quite trivial to implement. All the wad managers out there are probably using the same lines of code for the actual (un)installation process. Note: I realise you don't develop WiiFlow.

I briefly tried your loader but I just decided I couldn't face setting up and learning another loader. Maybe it looked a bit less kid friendly too, but I really didn't get that far. I did want to ask you though, would it be easy to install it just for the disc ripping feature? Is there a way I can effectively tell it to not look for games or anything else? Just load up blank and let me use the disc ripper. Finally, does the disc ripper rip to WBFS in a way which WiiBackupManager would understand and accept? Are the filesize splits the same etc.? I can always check this myself, of course.

Thanks to all three of you. :bow:
 
The only thing missing is how to tell neek where you want it to return to.
This is done by the launcher (USBLoaderGX, or wiiflow ? I don't know how compatible Wiiflow is with neek2o)
At game launch, USBGX run neek with passed arguments : Game's ID to launch and return_to channel's ID. Neek2o catches these arguments at boot to check if you want to either run sysMenu normally, or autoboot a game. it also checks if there is the "return to" TitleID information, and patches the launched game with that information.
When you exit the game, it sees "run NK2O title" instead of "run sysMenu title", loads that channel instead of "exiting to sysMenu" (actually, it doesn't exit, but loads another channel by their TitleID)

Note: USBLoaderGX doesn't let you choose the "return_to" ID. It's forced to "NK2O" on Wii, and to "return to WiiU" channel on vWii. You can, if you want, enable or disable that feature, but not choose a different TitleID. (unless Blackb0x made it editable on his mod).

So, if Wiiflow didn't implement the full neek2o integration yet, you can't autoboot a game or apply the "return to" information.

I briefly tried your loader but I just decided I couldn't face setting up and learning another loader. Maybe it looked a bit less kid friendly too, but I really didn't get that far. I did want to ask you though, would it be easy to install it just for the disc ripping feature? Is there a way I can effectively tell it to not look for games or anything else? Just load up blank and let me use the disc ripper. Finally, does the disc ripper rip to WBFS in a way which WiiBackupManager would understand and accept? Are the filesize splits the same etc.? I can always check this myself, of course.
Ohh, lot of questions here. You are talking about USBloaderGX, right?

- Less kid friendly :
I don't know. I never really used wiiflow to compare. But USBGX has the same "wii menu" feeling, and the menus are easy to access and change. By default most settings are (should be) already properly set up for "usb loading".
If you want additional things like channels or emuNAND, or gamecube, it effectively requires 2 or 3 settings to enable.

- would it be easy to install it just for the disc ripping feature?
Extremly !!!
Insert the disc, select "install" from the popup menu asking you want to do with that disc.
Wait .... Done !
you can eject the disc, insert another one, etc.

- Is there a way I can effectively tell it to not look for games or anything else?
Not sure to understand.
You want the loader to "not look for games" ?
whether it does or not shouldn't bother you. just let it "look for USB games", it will just list them in the main interface, just don't launch any if you don't want to launch them.

- Just load up blank and let me use the disc ripper.
Yep, just do that. launch USBGX, insert disc to rip them, exit USBLoaderGX when finished.

- does the disc ripper rip to WBFS in a way which WiiBackupManager would understand and accept?
It rips to WBFS format. it splits at 4GB (by default, can be changed) to fit any FAT32 partition.
It's of course fully compatible with WiiBackupManager

- Are the filesize splits the same etc?
It can be changed if needed.... The same way WiiBackupManager can change the size if needed too !



Ultimately, all loader's features are almost identical. users mostly choose the one they prefer based on the interface. There are no competition or fight among each developers, we just want users to be happy :D
 
Last edited by Cyan,
This is done by the launcher (USBLoaderGX, or wiiflow ? I don't know how compatible Wiiflow is with neek2o)
At game launch, USBGX run neek with passed arguments : Game's ID to launch and return_to channel's ID. Neek2o catches these arguments at boot to check if you want to either run sysMenu normally, or autoboot a game. it also checks if there is the "return to" TitleID information, and patches the launched game with that information.
When you exit the game, it sees "run NK2O title" instead of "run sysMenu title", loads that channel instead of "exiting to sysMenu" (actually, it doesn't exit, but loads another channel by their TitleID)

Note: USBLoaderGX doesn't let you choose the "return_to" ID. It's forced to "NK2O" on Wii, and to "return to WiiU" channel on vWii. You can, if you want, enable or disable that feature, but not choose a different TitleID. (unless Blackb0x made it editable on his mod).

So, if Wiiflow didn't implement the full neek2o integration yet, you can't autoboot a game or apply the "return to" information.


Ohh, lot of questions here. You are talking about USBloaderGX, right?

- Less kid friendly :
I don't know. I never really used wiiflow to compare. But USBGX has the same "wii menu" feeling, and the menus are easy to access and change. By default most settings are (should be) already properly set up for "usb loading".
If you want additional things like channels or emuNAND, or gamecube, it effectively requires 2 or 3 settings to enable.

- would it be easy to install it just for the disc ripping feature?
Extremly !!!
Insert the disc, select "install" from the popup menu asking you want to do with that disc.
Wait .... Done !
you can eject the disc, insert another one, etc.

- Is there a way I can effectively tell it to not look for games or anything else?
Not sure to understand.
You want the loader to "not look for games" ?
whether it does or not shouldn't bother you. just let it "look for USB games", it will just list them in the main interface, just don't launch any if you don't want to launch them.

- Just load up blank and let me use the disc ripper.
Yep, just do that. launch USBGX, insert disc to rip them, exit USBLoaderGX when finished.

- does the disc ripper rip to WBFS in a way which WiiBackupManager would understand and accept?
It rips to WBFS format. it splits at 4GB (by default, can be changed) to fit any FAT32 partition.
It's of course fully compatible with WiiBackupManager

- Are the filesize splits the same etc?
It can be changed if needed.... The same way WiiBackupManager can change the size if needed too !



Ultimately, all loader's features are almost identical. users mostly choose the one they prefer based on the interface. There are no competition or fight among each developers, we just want users to be happy :D

I'm pretty sure WiiFlow sends the return argument. So somebody could edit any WAD by setting its name to NK20 and then via USBLoader's passed argument that's the channel that would be launched on exit. Interesting. It is right that installing a WAD with a TitleID that matches the TitleID of an already installed WAD causes that installed WAD to be overwritten?

Regarding patching a launched game's exit command, is this something that the stock Wii System Menu does all the time when it launches disc games? Or is the Exit To System Menu command already on the disc?

I agree all you guys' loaders are great and fully-featured these days. An amazing achievement. Thanks.

I didn't realise you were French. Bonjour! Je m'appelle Michel. J'habite en anglettere. Quelquefois j'achetes des pommes a la supermarket. Etc. :D I studied French quite intensively for a few years in 2009. I watched a hell of a lot of Smallville and X-Files episodes with French audio. I still hear Mulder and Scully as French people in my head. Their American voices sound so weird now! I've forgotten a lot of my French, but I know it i still in the back of my mind somewhere, waiting to be refreshed.
 
Last edited by NormalMisha,
It is right that installing a WAD with a TitleID that matches the TitleID of an already installed WAD causes that installed WAD to be overwritten?
yes.
all content is managed by its TitleID. If you install something with the same titleID of an already installed content, it'll be overwritten ... or mixed and messed up.

Regarding patching a launched game's exit command, is this something that the stock Wii System Menu does all the time when it launches disc games?
The patch is done by Neek2o (or by USBLoaders for launches games from USB).
By default, all games have hardcoded values of the System menu to load when the user choose home>exit.
The loaders just replace that hardcoded values to another titleID.

I watched a hell of a lot of Smallville and X-Files episodes with French audio
Ahah, I do the contrary ! I watch all TV series in english :p (I just watched superman&Lois, and Debris, funny that they are the new "version" of the two you mentioned) Let's continue offtopic in private if you want ;)
 
Last edited by Cyan,
So recently, I had to redo my whole setup. I've spent the last couple days getting everything back up to speed, and testing everything. I've got almost everything ironed out and working, but I have a question. My wiiware/vc will only launch with the setting "app loader" set to on. Is there a way in the settings to turn this on universally, without having to turn it on for every game? I looked through the menu and the wiiflow_lite.ini but didn't see anything.

Besides that, the only other issue i'm having is with vecxwii as a plugin. It launches the app, but doesn't load the rom, i've tried on both SD & USB with the same results. It code dumps when you get to the emulator main screen where it says "push a button". and you then push a button. All games are working fine via hbc. I was thinking it was possibly the arguments, but I don't know. I'm currently using arguments={device}:/{path}|{name}. Can anyone verify if this plugin is or isn't working?
 
  • Like
Reactions: biggzsizzle
Besides that, the only other issue i'm having is with vecxwii as a plugin. It launches the app, but doesn't load the rom, i've tried on both SD & USB with the same results. It code dumps when you get to the emulator main screen where it says "push a button". and you then push a button. All games are working fine via hbc. I was thinking it was possibly the arguments, but I don't know. I'm currently using arguments={device}:/{path}|{name}. Can anyone verify if this plugin is or isn't working?
Vectrex Wii is working for me. Your arguments line is not correct, use this:
arguments={device}:/{path}/{name}
You can use my Plugins Pack if you want to spare you some headaches.
I've updated it just today, all plugins tested and working;)
 
Vectrex Wii is working for me. Your arguments line is not correct, use this:
arguments={device}:/{path}/{name}
You can use my Plugins Pack if you want to spare you some headaches.
I've updated it just today, all plugins tested and working;)

Thanks bud, I do use your plugin pack for reference, when i viewed your .ini to compare i didn't catch the "/" instead of "|" in the arguments line. Anyway, I just tried with your setup, and am having the same problem. Damn you vectrex! Code dumping at the emulator main screen, when i assume i should be autobooted into the game and not even see the main screen (unless vectrex is wierd like that, i don't remember.) I'll keep trying.
 
Thanks bud, I do use your plugin pack for reference, when i viewed your .ini to compare i didn't catch the "/" instead of "|" in the arguments line. Anyway, I just tried with your setup, and am having the same problem. Damn you vectrex! Code dumping at the emulator main screen, when i assume i should be autobooted into the game and not even see the main screen (unless vectrex is wierd like that, i don't remember.) I'll keep trying.
The emulator auto loads the rom correctly, but you still have to press + to enter into the game. That's the way it works.
 
So recently, I had to redo my whole setup. I've spent the last couple days getting everything back up to speed, and testing everything. I've got almost everything ironed out and working, but I have a question. My wiiware/vc will only launch with the setting "app loader" set to on. Is there a way in the settings to turn this on universally, without having to turn it on for every game? I looked through the menu and the wiiflow_lite.ini but didn't see anything.

Besides that, the only other issue i'm having is with vecxwii as a plugin. It launches the app, but doesn't load the rom, i've tried on both SD & USB with the same results. It code dumps when you get to the emulator main screen where it says "push a button". and you then push a button. All games are working fine via hbc. I was thinking it was possibly the arguments, but I don't know. I'm currently using arguments={device}:/{path}|{name}. Can anyone verify if this plugin is or isn't working?
about your app loader issue:

do you have the 480p pixel fix in main settings set to ON or YES?
if so that is why you have to set app loader to ON. sorry my bad. i made it so the 480p fix works for wiiware/vc games but it only works if app loader is ON. so you either set app loader ON for each game or set 480p pixel patch from DEFAULT to OFF for each wiiware/vc game or set the 480p in main settings to OFF but that will effect all games.
 
  • Like
Reactions: mastershoes
How do I load wbfs backups with the latest WiiFlow Lite from SD in vWii? The game is picked up by a loader but freezes during after wiiflow loading bar is completed. Custom IOS 236, 249 & 250 were installed as per guidelines.

Which basic checks shall I do?
 
about your app loader issue:

do you have the 480p pixel fix in main settings set to ON or YES?
if so that is why you have to set app loader to ON. sorry my bad. i made it so the 480p fix works for wiiware/vc games but it only works if app loader is ON. so you either set app loader ON for each game or set 480p pixel patch from DEFAULT to OFF for each wiiware/vc game or set the 480p in main settings to OFF but that will effect all games.

Does that apply to normal Wii games too? Where are the individual game settings stored?
 
Two random questions:

What does Boot Apploader actually do?

Why does pressing HOME while playing a game and then selecting the "Reset" button cause a black screen in all games except 8 and 16-bit VC games when launched via WiiFlow?
 
Last edited by NormalMisha,

Site & Scene News

Popular threads in this forum