Hacking WiiFlow Lite

[fledge68]

Obviously put <cmath> back to <math.h>
It must not work.

I tried ppc r31-2
It didnt give me any powf error
The nanosleep error was conflicting in libogc and ppc. Not wfl code. I commented it out i libogc system.h and added the null.

Remember i believe when you update devkit pro now. You have to do a clean install. But copy old devkitpro folder first in case of issues

 

[GreyWolf]

You can't use <cmath> for C. You have to use <math.h>.

The "c" headers (<cmath>, <cstdio>, etc.) are C++.

 

[kaisersozeh]

Obviously...

 

[einsteinx2]

try r1149!

http://www.mediafire.com/file/y1bf3657eba45im/boot.dol

-added flash screen image to appear before wiiflow wait animation. i hope the image isn't too big to cause problems with wfl.
-added 'noflash' arg for meta.xml if you don't want the flash screen image to appear. and no i can't make it load a image from a folder. it must be compiled in the code.
-added 'sdonly' arg for meta.xml for those of you that have everything on SD and hate the 20 second wait for wiiflow to search for usb devices. thanks einsteinx2!
-added meta.xml args support when wiiflow boots homebrew. meaning when a homebrew boot.dol or elf is launched the meta.xml (if exist) will be read for arguments and those args sent when the app is launched. this fixes the issue of custom wait images when changing themes.
-added spanish translation file 'spanish.ini'. thanks to ravmn for sending it to me!
-other minor changes, mainly remarks added for myself.

i take no credit for the flash screen image. credit goes to jiiwah or benjay or one of those theme makers.
add your args to meta.xml between <app> and </app> like this:

<arguments>
<arg>noflash</arg>
<arg>sdonly</arg>
</arguments>

Hey sorry haven't really been keeping up with this thread lately, been super busy. Regarding the load time fix, I had implemented it in a way to specifically remove the need for a separate config file entry. Basically it first checks to see if the Wiiflow files are on SD, then if so, it checks all configs to see if anything uses the HDD. If nothing does, it automatically skips mounting HDD. So hypothetically, anyone using an SD only setup would not have paths set to HDD and so it should do the right thing. The check is really fast so it shouldn't impact boot time.

I'm just wondering your reasoning for adding a flag? Did you find the checks to be too hacky or otherwise unreliable? My goal was to make it work automagically so people using HDD or SD would get the same load time without having to know to do anything, but maybe I missed something in my checks?

 

[fledge68]

Hey sorry haven't really been keeping up with this thread lately, been super busy. Regarding the load time fix, I had implemented it in a way to specifically remove the need for a separate config file entry. Basically it first checks to see if the Wiiflow files are on SD, then if so, it checks all configs to see if anything uses the HDD. If nothing does, it automatically skips mounting HDD. So hypothetically, anyone using an SD only setup would not have paths set to HDD and so it should do the right thing. The check is really fast so it shouldn't impact boot time.

I'm just wondering your reasoning for adding a flag? Did you find the checks to be too hacky or otherwise unreliable? My goal was to make it work automagically so people using HDD or SD would get the same load time without having to know to do anything, but maybe I missed something in my checks?

I understand and like that you did it automatic but i didnt like that you had to load the config early and do all the same checks that are done in menu.cpp. so basically doing those things twice. Plus i had just added args for wait images why not add one for sd only users who only account for maybe 2% of wiiflow users.

 

[kaisersozeh]

I understand and like that you did it automatic but i didnt like that you had to load the config early and do all the same checks that are done in menu.cpp. so basically doing those things twice. Plus i had just added args for wait images why not add one for sd only users who only account for maybe 2% of wiiflow users.

I like having support for arguments in the meta generally. But that 2% is way off. If that's what is informing your decision, I'd reconsider.
Edit. I couldn't help but come up with some further considerations:
- magnetic hard drives are going to start failing, and more often, as they age.
- SD(HC) cards are only going to get bigger and cheaper (how big can they get?)
- Wii support for flash memory over USB is ...patchy
EDIT:- @fledge68 - please excuse the tag and the bold, but this point is worth hammering home - there are any number of reasons why a user might be using wiiflow without wiiflow needing access to media on a hard drive.

Just a thought, but if you'd prefer to avoid duplicating the work done in menu.cpp, is it not possible to use the result of einstein's code directly in the menu.cpp?
Because if not, that isn't exactly duplicating the work done in menu.cpp.

 

[rogerioronin]

I like having support for arguments in the meta generally. But that 2% is way off. If that's what is informing your decision, I'd reconsider.
Edit. I couldn't help but come up with some further considerations:
- magnetic hard drives are going to start failing, and more often, as they age.
- SD(HC) cards are only going to get bigger and cheaper (how big can they get?)
- Wii support for flash memory over USB is ...patchy
- there are any number of reasons why a user might be using wiiflow without wiiflow needing access to media on a hard drive.

Just a thought, but if you'd prefer to avoid duplicating the work done in menu.cpp, is it not possible to use the result of einstein's code directly in the menu.cpp? Because if not, that isn't exactly duplicating the work done in menu.cpp.

You can be sure that it is not only 2% of users that use games by SD Card, in poorer countries this percentage is much higher.

 

[fledge68]

Well it isnt that hard to add the arg to meta.xml. and maybe for future users i can add a readme to the download so they know about the different args.

 

[kaisersozeh]

Well it isnt that hard to add the arg to meta.xml. and maybe for future users i can add a readme to the download so they know about the different args.

I hate to say this, and I say it as a friend and as a 'lite user. That attitude is why wiiflow gets 650 downloads a week and USBLoader gets 6,500.
USBLoader has a beautiful interface, but beyond the graphics, the functionality of the UI is astoundingly good - because the people who supported it also wrote it, and listened to their users.
You are in exactly as fortunate a position - a user base who care enough to comment.
I can't encourage you enough to use that resource.
WiiFlow is a gem, listen to the folks who use it. You can scroll back just a few pages through this thread and find multiple references to people finding use for it and extolling your virtue for doing it.
Thanks for doing anything at all, but understand that the people who use WiiFlow might have something intelligent to add.
No disrespect intended, only encouragement.
p.s. a GUI that needs a readme is a bad GUI, right?

 

[fledge68]

I hate to say this, and I say it as a friend and as a 'lite user. That attitude is why wiiflow gets 650 downloads a week and USBLoader gets 6,500.
USBLoader has a beautiful interface, but beyond the graphics, the functionality of the UI is astoundingly good - because the people who supported it also wrote it, and listened to their users.
You are in exactly as fortunate a position - a user base who care enough to comment.
I can't encourage you enough to use that resource.
WiiFlow is a gem, listen to the folks who use it. You can scroll back just a few pages through this thread and find multiple references to people finding use for it and extolling your virtue for doing it.
Thanks for doing anything at all, but understand that the people who use WiiFlow might have something intelligent to add.
No disrespect intended, only encouragement.
p.s. a GUI that needs a readme is a bad GUI, right?

To keep this short. I do listen to the people. If you scroll back thru this thread you will see i have fixed and added stuff requested by users and they have been pleased.

You guys are just upset because i didnt add einsteins patch the way he coded it.

 

[kaisersozeh]

To keep this short. I do listen to the people. If you scroll back thru this thread you will see i have fixed and added stuff requested by users and they have been pleased.

You guys are just upset because i didnt add einsteins patch the way he coded it.

Honestly, mate, that's not how it is. There's a real lesson to be learned here - no one cares about who's code gets used, it's about listening to the people who love and use your work
EDIT-I'm pleased - everyone's pleased, and you absolutely should be proud - I'm not suggesting it's not good enough, I mean your decision was misplaced because you're not hearing your users

 

[kaisersozeh]

WiiFlow Poll https://gbatemp.net/threads/now-the...w-without-a-usb-hard-drive-plugged-in.510392/
Please vote
@fledge68 - step back, feel the love - please try to see the point

 

[einsteinx2]

I understand and like that you did it automatic but i didnt like that you had to load the config early and do all the same checks that are done in menu.cpp. so basically doing those things twice. Plus i had just added args for wait images why not add one for sd only users who only account for maybe 2% of wiiflow users.

No worries, was just interested in your reasoning. I personally use an HDD, so this fix was entirely for other people.

If I find the time, maybe I could rewrite it to share the config check code, but unfortunately the config file would always have to be loaded early for it to work at all. Anyway as long as it's available as an option for those that need it, that's great.

 

[fledge68]

No worries, was just interested in your reasoning. I personally use an HDD, so this fix was entirely for other people.

If I find the time, maybe I could rewrite it to share the config check code, but unfortunately the config file would always have to be loaded early for it to work at all. Anyway as long as it's available as an option for those that need it, that's great.

fyi in the next release its a good chance the sd only setting will be added to the wiiflow save and removed as a arg in meta.xml

 

[fledge68]

@einsteinx2
After re reviewing his code for sd only i have decided to reconsider my decision to not use. Which means i will include his code for sd only in the next revision.

 

[aphirst]

I've just noticed a strange bug which I think lies in wiiflow-lite's jurisdiction.

My Wii U (and vWii) system menus both report the correct time and date. Wiiflow-Lite and all other homebrew also report the correct time and date.

Games loaded through Wiiflow-Lite seem to think it's 7 days in the future, but with the correct time (i.e. today on the 7th, games think it's the 14th). I get this for all games I tested (including the Wii Fit Plus initial setup which asks you to confirm the date; and Skyward Sword's save file timestamp).

Games loaded through CFG USBLoader Mod (which I only really keep around for a laugh) do not seem to experience this discrepancy (Wii Fit Plus reports the correct time during initial setup, and games saved in Skyward Sword use the correct date, though of course the previous save before overwriting reported a date in the future).

It doesn't seem to matter whether I load WiiFlow-Lite through the HBC or via the Loader Channel I have (on my vWii Home Page). Very weird!

Edit: I'm using WiiFlow Lite 4.4.0 (r1149), the first version after I found out about the "SD only" option being implemented.
Edit 2: I can confirm the same behaviour in 4.4.0 (r1135).
Edit 3: The issue even persists (in both tested versions) after deleting the Wiiflow save.

 

[fledge68]

I've just noticed a strange bug which I think lies in wiiflow-lite's jurisdiction.

My Wii U (and vWii) system menus both report the correct time and date. Wiiflow-Lite and all other homebrew also report the correct time and date.

Games loaded through Wiiflow-Lite seem to think it's 7 days in the future, but with the correct time (i.e. today on the 7th, games think it's the 14th). I get this for all games I tested (including the Wii Fit Plus initial setup which asks you to confirm the date; and Skyward Sword's save file timestamp).

Games loaded through CFG USBLoader Mod (which I only really keep around for a laugh) do not seem to experience this discrepancy (Wii Fit Plus reports the correct time during initial setup, and games saved in Skyward Sword use the correct date, though of course the previous save before overwriting reported a date in the future).

It doesn't seem to matter whether I load WiiFlow-Lite through the HBC or via the Loader Channel I have (on my vWii Home Page). Very weird!

Edit: I'm using WiiFlow Lite 4.4.0 (r1149), the first version after I found out about the "SD only" option being implemented.
Edit 2: I can confirm the same behaviour in 4.4.0 (r1135).

thanks for the info.

@Cyan @GreyWolf apparently in both wiiflow and usb loader gx the code to launch a game includes the following set time line

settime(secs_to_ticks( time( NULL ) - 946684800 ));

why is this done before launching a game?
and would this have anything to do with what aphrist is talking about?

i also noticed in wiiflow main code its done but then wiiflow boots external loader which boots the wiiflow game booter which finally launches the game. but the settime() is not used in wiiflow game booter. i'm wondering if maybe it should be called in wiiflow game booter instead of back in the main wiiflow code?

 

[GreyWolf]

946684800 is Saturday 1st January 2000 12:00:00 AM. Maybe it's something the system menu normally does?

It looks like that code has been in there since v1.0 of USB Loader GX so there's no telling.

 

[fledge68]

946684800 is Saturday 1st January 2000 12:00:00 AM. Maybe it's something the system menu normally does?

It looks like that code has been in there since v1.0 of USB Loader GX so there's no telling.

would it have something to do with the y2k fix? jan 1st 2000? not sure why the wii would need that?

 

[fledge68]

I've just noticed a strange bug which I think lies in wiiflow-lite's jurisdiction.

My Wii U (and vWii) system menus both report the correct time and date. Wiiflow-Lite and all other homebrew also report the correct time and date.

Games loaded through Wiiflow-Lite seem to think it's 7 days in the future, but with the correct time (i.e. today on the 7th, games think it's the 14th). I get this for all games I tested (including the Wii Fit Plus initial setup which asks you to confirm the date; and Skyward Sword's save file timestamp).

Games loaded through CFG USBLoader Mod (which I only really keep around for a laugh) do not seem to experience this discrepancy (Wii Fit Plus reports the correct time during initial setup, and games saved in Skyward Sword use the correct date, though of course the previous save before overwriting reported a date in the future).

It doesn't seem to matter whether I load WiiFlow-Lite through the HBC or via the Loader Channel I have (on my vWii Home Page). Very weird!

Edit: I'm using WiiFlow Lite 4.4.0 (r1149), the first version after I found out about the "SD only" option being implemented.
Edit 2: I can confirm the same behaviour in 4.4.0 (r1135).
Edit 3: The issue even persists (in both tested versions) after deleting the Wiiflow save.

LOL! I know why its doing that!

i made a change to that line i mentioned but didnt commit it. yet when i compile wiiflow it includes that change which just happens to be 7 days. thanks for finding this. i will fix in next revision.

 

[WesMods]

Just wondering if Wiiflow Lite supports WiiU Gamepad like @FIX94 did with FCEUGX, SNES9XGX etc. I would love to create a WiiU menu icon for WiiFlow Lite and be able to run/control it with the WiiU gamepad