Wiiflow Lite + Wii Fit Plus Calendar Date?

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
Hello helpful community!

I am having a problem with the latest release of Wiiflow Lite v5.5.3:

The date in all my games on my Wii displays as the year 10/05/2159.

This is a particular problem for Wii Fit Plus, which makes the game difficult to enjoy as the game is centered around a calendar system. I found 5 minor problems with the latest release of Wiiflow Lite v5.5.3, which as far as my efforts can take me, are unavoidable and unfixable as far as I can tell:

1. GAMES SHOW DATE AS 10/05/2159. On Wii Fit Plus, when launched from the latest Wiiflow Lite v5.5.3 release, the date and time displays as 10/05/2159. Despite both the Wii's System Menu time and the neek2o Emunand time being correctly set. Wii Fit plus displays the correct date when launched from USB Loader GX and when lauched from the disc on the System Menu. But not with Wiiflow Lite v5.5.3. Changing all settings in Wiiflow Lite (running it within my neek2o emunand, custom IOS 248, 249, 250 has no change). This is nothing to do with the Wii's internal battery, as the System Menu retains the correct date after being unplugged for many hours.

2. [SOLVED] Back to the Future: The Game does not work on the latest Wiiflow Lite despite working on the old Wiiflow.

3. GAMES FREEZE AND SCREETCH WHEN EMUNAND SAVES ARE TURNED ON. I am limited to 512mb of space for save files on my Wii. This is because in about 50% of games, (WALL-E, Cook Wars) the entire game freezes and makes a screeching noise when it is about to load saved data, when Emunand saves are enabled. Therefore I need to use the NAND Saves to avoid this problem, which means I am limited to just 512mb. I am using the pre-built neek2o emunand found on "Noob Friendly Neek2o Guide" and the latest release of Wiiflow Lite.

4. [SOLVED] I have replaced the custom loading animation in Wiiflow Lite, this displays fine when launching the Wii, however, Wiiflow Lite ignores the "wait_imgs" whenever exiting out of a game other than a Wii game.

5. WII MOTION PLUS CONTROLLERS UNSTABLE IN WIIFLOW. Wii Motion Plus controllers do not work on Wiiflow Lite, only normal controllers. This is because I have my sensor bar is in the same room as a window, and some minor light coming in. When I use a non-Wii Motion Plus controller, I set the sensitivity on the System Menu settings to the lowest setting and it ignores the areas of light from the window, and works perfectly in all games and Wiiflow Lite. However, when I use a Wii Motion Plus controller, it has an increased ability to pick up light, and with the same setting set to the lowest, it still picks up a little bit of light around it. However, this isn't a problem because when on the official System Menu, the Wii Motion Plus controller is still perfectly still and secure, despite the Wii Motion Plus's increased ability to pick up light. However, as soon as you enter into Wiiflow Lite, it is suddenly flickering and teleporting all over the screen. When I enter into a game on Wiiflow, it's smooth and secure, then back to the Wiiflow menu, it is flickering and teleporting everywhere. My only explanation to why this is, is that the Wii System Menu uses the Wii Motion Plus's Extra Technology to calculate the cursor position, wheras Wiiflow Lite ignores it and only uses the light data, which is why it shakes and teleports everywhere. To clarify: A normal Wiimote works perfectly fine in Wiiflow Lite. A Wii Motion Plus flickers and teleports everywhere in Wiiflow Lite (but the same Motion Plus controller in System Menu or Wiiflow-launched game is perfectly fine.)

If you've had any past experience or encountered any of these problems, I would be extremely grateful if you could share your knowledge.

Thank you so much for reading this post.



This is my syscheck:

SysCheck ME v2.5.0 by blackb0x, JoostinOnline, Double_A, R2-D2199 and Nano

...runs on IOS58 (rev 6176).



Region: PAL (original region: AUS)

System Menu 4.3E (v514)

Priiloader installed

Drive date: 02.13.2007

Homebrew Channel 1.1.3 running on IOS58



Hollywood v0x11

Console ID: 76266196

Console Type: Wii

Shop Channel Country: Australia (65)

Boot2 v4

Found 102 titles.

Found 51 IOS on this console. 7 of them are stubs.



IOS4 (rev 65280): Stub

IOS9 (rev 54321): Trucha Bug

IOS10 (rev 768): Stub

IOS11 (rev 54321): Trucha Bug

IOS12 (rev 526): No Patches

IOS13 (rev 1032): No Patches

IOS14 (rev 1032): No Patches

IOS15 (rev 1032): No Patches

IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access

IOS17 (rev 1032): No Patches

IOS20 (rev 54321): Trucha Bug

IOS21 (rev 1039): No Patches

IOS22 (rev 1294): No Patches

IOS28 (rev 1807): No Patches

IOS30 (rev 54321): Trucha Bug

IOS31 (rev 3608): No Patches

IOS33 (rev 3608): No Patches

IOS34 (rev 3608): No Patches

IOS35 (rev 3608): No Patches

IOS36 (rev 65535): No Patches

IOS37 (rev 5663): No Patches

IOS38 (rev 4124): No Patches

IOS40 (rev 3072): Stub

IOS41 (rev 3607): No Patches

IOS43 (rev 3607): No Patches

IOS45 (rev 3607): No Patches

IOS46 (rev 3607): No Patches

IOS48 (rev 4124): No Patches

IOS50 (rev 54321): Trucha Bug

IOS51 (rev 4864): Stub

IOS52 (rev 5888): Stub

IOS53 (rev 5663): No Patches

IOS55 (rev 5663): No Patches

IOS56 (rev 5662): No Patches

IOS57 (rev 5919): No Patches

IOS58 (rev 6176): USB 2.0

IOS60 (rev 54321): Trucha Bug

IOS61 (rev 5662): No Patches

IOS70 (rev 54321): Trucha Bug

IOS80 (rev 6944): Trucha Bug

IOS90 (rev 54321): Trucha Bug

IOS222 (rev 65280): Stub

IOS223 (rev 65280): Stub

IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access

IOS240 (rev 65535): No Patches

IOS241 (rev 65535): No Patches

IOS248[38] (rev 65535, Info: d2x-v11beta1): Trucha Bug, ES Identify, NAND Access

IOS249[56] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS250[57] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS251[58] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS254 (rev 65281): BootMii

BC v6

MIOS v10 (DIOS MIOS 2.10)

Report generated on 05/07/2159.
 
Last edited by guitarburger,

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
This is a picture from Wii Fit Plus:
 

Attachments

  • 2023-04-02-203359.jpg
    2023-04-02-203359.jpg
    55.6 KB · Views: 78
Last edited by guitarburger,

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
UPDATE:

I've just noticed something which is in my syscheck, my syscheck also gets the incorrect year. If you see in my Syscheck, on the last line it says: Report generated on 05/07/2159.

So, it is not just Wiiflow but also the SyscheckMe Homebrew App that retrieves an incorrect date and time, since neither my System Settings nor neek2o have anything close to this date and time.

To clarify:

Wiiflow Lite (Latest version) launching Wii Fit Plus - Incorrect Date (No matter the setting)

USBLoaderGX Launching the Same Wii Fit Plus - Correct Date

System Menu Launching Wii Fit Plus - Correct Date

SyscheckMe Homebrew App - Incorrect Date

My other update is that after giving it some thought, I think my initial theory that Wiiflow cannot utilise the Wii Motion Plus's extra technology is incorrect, and that actually, the entire Wiiflow app is utilising a seperate System Configuration in which the entire cursor sensitivity setting is set differently, and the time is different.

I found another source here describing Wiiflow accessing an entirely different set of Shared2 settings in which this person's controllers aren't even synced: https://gbatemp.net/threads/wiiflow-motion-plus-controller-issues.628254/

What are these System Settings that give this incorrect date? And where do homebrew apps like Wiiflow Lite and SyscheckMe retrieve their date and time information from? I've gone into my neek2o in case it is somehow getting the settings from there, but they are configured identically to my System Settings. I should note that my Wiiflow Lite is NOT running from within an Emunand.

Is it possible that by taking the Homebrew Channel WAD off from my System Menu, I've erased some kind of copy of System Setting information that the Homebrew Channel holds that Homebrew Apps retrieve from?

I've also done a ModMii recommended update of my system IOS's, hoping that it might update some old IOS that was causing this issue, but to no avail, so here is my new SysCheck:

SysCheck ME v2.5.0 by blackb0x, JoostinOnline, Double_A, R2-D2199 and Nano

...runs on IOS58 (rev 6176).



Region: PAL (original region: AUS)

System Menu 4.3E (v514)

Priiloader installed

Drive date: 02.13.2007

Homebrew Channel 1.1.3 running on IOS58



Hollywood v0x11

Console ID: 76266196

Console Type: Wii

Shop Channel Country: Australia (65)

Boot2 v4

Found 107 titles.

Found 52 IOS on this console. 7 of them are stubs.



IOS4 (rev 404): Stub

IOS9 (rev 1034): No Patches

IOS10 (rev 404): Stub

IOS11[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS12 (rev 526): No Patches

IOS13 (rev 1032): No Patches

IOS14 (rev 1032): No Patches

IOS15 (rev 1032): No Patches

IOS16 (rev 404): Stub

IOS17 (rev 1032): No Patches

IOS20[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS21 (rev 1039): No Patches

IOS22 (rev 1294): No Patches

IOS28 (rev 1807): No Patches

IOS30[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS31 (rev 3608): No Patches

IOS33 (rev 3608): No Patches

IOS34 (rev 3608): No Patches

IOS35 (rev 3608): No Patches

IOS36 (rev 3608): No Patches

IOS37 (rev 5663): No Patches

IOS38 (rev 4124): No Patches

IOS40[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS41 (rev 3607): No Patches

IOS43 (rev 3607): No Patches

IOS45 (rev 3607): No Patches

IOS46 (rev 3607): No Patches

IOS48 (rev 4124): No Patches

IOS50[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS51 (rev 404): Stub

IOS52[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS53 (rev 5663): No Patches

IOS55 (rev 5663): No Patches

IOS56 (rev 5662): No Patches

IOS57 (rev 5919): No Patches

IOS58 (rev 6176): USB 2.0

IOS60 (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS61 (rev 5662): No Patches

IOS62 (rev 6430): No Patches

IOS70[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS80[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS90 (rev 404): Stub

IOS222 (rev 65280): Stub

IOS223 (rev 65280): Stub

IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access

IOS240 (rev 65535): No Patches

IOS241 (rev 65535): No Patches

IOS248[38] (rev 65535, Info: d2x-v11beta1): Trucha Bug, ES Identify, NAND Access

IOS249[56] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS250[57] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS251[58] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS254 (rev 65281): BootMii

BC v6

MIOS v10 (DIOS MIOS 2.10)

Report generated on 05/09/2159.
 

gZa

Well-Known Member
Newcomer
Joined
May 4, 2021
Messages
81
Trophies
0
Age
48
XP
789
Country
United Kingdom
Have you got the nand saves set to Full or Partial in Wiiflow.

Also what does your Date / Time say in System Menu Settings?

Maybe your Wii battery is done so the date it not being stored after Shutdown.
 

fledge68

Well-Known Member
Member
Joined
Jan 30, 2012
Messages
2,440
Trophies
2
XP
4,998
Country
United States
first, i use a wiimotion plus controller all the time. i have the white and red with a blue bottom and on top is a toad icon. i have no problem using it in wiiflow even if it turns off after no use i can just turn it back on again.

plus i just ran a syscheck using syscheck hacksden edition and it shows the correct date. i don't have wiifit plus to check it.

i'm wondering how you are starting wiiflow lite? via priiloader? what version of priiloader? and what dol are you telling it to load and run?
 

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
Have you got the nand saves set to Full or Partial in Wiiflow.

Also what does your Date / Time say in System Menu Settings?

Maybe your Wii battery is done so the date it not being stored after Shutdown.
Hey I appreciate the input and help, you just reminded me so I double checked the partial or full saves settings, and ran through four configurations:



NAND Emulation - Partial

Saves NAND Emulation - Game Save

Result: WALL-E Freezes on Start Menu



NAND Emulation - Partial

Saves NAND Emulation - Full

Result: WALL-E Freezes on Start Menu



NAND Emulation - Full

Saves NAND Emulation - Game Save

Result: WALL-E Freezes on Start Menu



NAND Emulation - Full

Saves NAND Emulation - Full

Result: WALL-E Freezes on Start Menu



NAND Emulation - Full

Saves NAND Emulation - OFF

Result: WALL-E Runs Fine



Attatched is my System Settings Date configuration. I have never in all memory ever needed to change the System Settings Date or even had it reset itself, and I almost always unplug and move the Wii between two TVs. Launching Wii Fit Plus with USBLoaderGX displays the correct date.
Post automatically merged:

first, i use a wiimotion plus controller all the time. i have the white and red with a blue bottom and on top is a toad icon. i have no problem using it in wiiflow even if it turns off after no use i can just turn it back on again.

plus i just ran a syscheck using syscheck hacksden edition and it shows the correct date. i don't have wiifit plus to check it.

i'm wondering how you are starting wiiflow lite? via priiloader? what version of priiloader? and what dol are you telling it to load and run?
Hello fledge68, huge fan of your continuation of Wiiflow which is in my opinion the most impressive and customizable homebrew on any console ever.

Many great improvements over the original Wiiflow especially the ability to use a boot animation from images on the hard drive, something you could only do on the original by reverse engineering and recompiling files, which never worked for me, so I could never use that feature until Wiiflow Lite.

With regards to this Wii Motion Plus problem, I wanted to clarify exactly what the circumstance is. I am using the standard white, Nintendo "Wii MotionPlus INSIDE" controller, and it's 110% a legitimate Nintendo one.

The issue only comes when there are MORE THAN TWO DOTS on the Sensitivity setting on the Wii's System Menu Settings.

When I set the Sensitivity to the lowest setting "1", my non-Wii Motion Plus controller displays only two dots in the Sensitivity page when set to "1", and works fine both in the regular System Menu and in Wiiflow.

However, when I use a Wii Motion Plus controller, it has some increased ability to pick up the light of the sensor bar, and, when also set to the lowest setting "1", there are now Two Main Dots on the Sensitivity page, but it is also picking up a bit more light around it.

Despite there being more than two dots, the Wii Motion Plus controller is still completely stable, solid and perfectly usable, in the System Menu and in Wiiflow Lite-launched Games. However, in Wiiflow Lite, these extra light areas still cause the controller to teleport and flicker everywhere over the screen.

That was my issue regarding Wii Motion Plus.

I did some digging into the time display being incorrect, and the best I could find was this thread:

https://gbatemp.net/threads/vwii-has-a-completely-random-date-and-time.366336/

From there, I downloaded a homebrew application called InspectMii, and was able to find my 'Counter Bias' attatched below. With no clue how to change the counter bias or what that is.

I am running Wiiflow Lite v5.5.3, double checked at the top of the System Settings, and I am indeed autobooting the dol through Priiloader v0.10.0 (beta 2). I assure you this is an untouched, standard Wiiflow Lite 5.5.3 boot.dol.

Thanks for all your work.
Post automatically merged:

To clarify:

Non-Wii Motion Plus Controller:

In games: Perfectly Fine

In Wiiflow: Perfectly Fine

In System Menu: Perfectly Fine



Wii Motion Plus Controller:

In games: Perfectly Fine

In Wiiflow: Teleporting everywhere

In System Menu: Perfectly Fine



My only possible theory or idea as to why that is, is possibly because the System Menu incorporates both the Wii Motion Plus’s LIGHT DATA (1) and it’s MOTION PLUS TECHNOLOGY (2) in calculating the cursor’s position, which is why despite the Wii Motion Plus picking up more light dots on the sensitivity page than a non-Wii Motion Plus controller, it’s still able to be completely solid and secure. Whereas Wiiflow only uses the LIGHT DATA (1) to calculate the cursor’s position. That’s just a totally random theory though.
 

Attachments

  • 4.png
    4.png
    383.2 KB · Views: 51
  • 1.png
    1.png
    481.6 KB · Views: 63
  • 2.png
    2.png
    404.7 KB · Views: 66
  • 3.png
    3.png
    624.9 KB · Views: 62
Last edited by guitarburger,

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
Update: I tried two things today in regards to resolving the 10/5/2159 date issue.

The first was I reinstalled the Homebrew Channel WAD to my System Menu on the chance that Wiiflow and Syscheck (since they're both homebrew) are retrieving this random date from a unified source it expects to find in the Homebrew Channel.

I used "hbc1.1.4-unpatched.wad" and ModMii's YAMM to install it.

There was no change to the date problem.

The second thing I attempted was loading Wiiflow Lite directly from the .dol on the harddrive, rather than having the .dol installed on the NAND and autobooting it.

The date still displayed as the year 2159.
 
Last edited by guitarburger,

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
UPDATE:

I found two more instances of people having problems with their Wii games displaying the date 10/05/2159.

The first says the date in games was set to 5/20/2157, but that they fixed it by "changing nothing":
https://gbatemp.net/threads/usb-loader-gx-wrong-time-and-date.586753/

What was interesting to me is that it went away after changing nothing, so I left my Wii unplugged all night to see if it might resolve some internal battery issue of some kind, as that's the only thing I could think of that would involve doing nothing, but my System Menu date was still correct and my Wiiflow date was still the year 2159.

The only other interesting thing is that their Wii is from the region AUS which is the same as my system.

The second had a date problem on USBLoaderGX which resolved by updating USBLoaderGX to a later version:
https://gbatemp.net/threads/date-problems-with-usb-loader.145056/
 

fledge68

Well-Known Member
Member
Joined
Jan 30, 2012
Messages
2,440
Trophies
2
XP
4,998
Country
United States
2. Back to the Future: The Game does not work on the latest Wiiflow Lite despite working on the old Wiiflow. There was absolutely nothing I could do to overcome this, this is because Back to the Future: The Game contains multiple "games" within a single game, and needs "Block IOS Reload". On Back to the Future, when you press one of the five episodes on the opening screen, the game crashes and exits back to Wiiflow on the latest Wiiflow Lite v5.5.3 release. There's nothing I could do to get around this.
check these posts in another thread for a fix - https://gbatemp.net/threads/the-gre...m-a-call-for-adventurers.563575/post-10129456
4. I have replaced the custom loading animation in Wiiflow Lite, using the "wait_imgs" folder in apps/Wiiflow with my own animation. This displays fine when launching the Wii, however, Wiiflow Lite ignores the "wait_imgs" whenever exiting out of a game other than a Wii game, such as Gameboy games or Gamecube games, at which point it will always play the stock Wiiflow splash image and the stock Wiiflow wait animation when retuning back from a game. The only "return from" that retains the custom wait animation is when returning from Wii Games or Emunand Channels. I am using the plugins from ABZ's Masterpiece Pack.
read these 4 posts for a fix to this issue - https://gbatemp.net/threads/wiiflow-lite.422685/post-10037802
 

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
  • Like
Reactions: fledge68

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
UPDATE:

Have tested and can confirm both points 2. and 4. have been resolved fully in their entirety.

This update is regarding point 3. where the majority of games freeze at the moment of Save or Load when Emunand saves are Enabled.

Yesterday I discovered that the Wiiware title The Legend of Zelda: Ocarina of Time also freezes at the moment of attempting to save, with the Wii's disc tray flashing blue on a frozen frame of the game.
I tried all combination of Emunand Saves On/Off/Game Save and Emunand set to Full/Partial and "Use Real NAND Config" and sat through the Ocarina of Time opening to attempt each combination of settings.

Universally, Ocarina of Time freezes on Save attempt no matter the setting. This is launched from Emunand through Wiiflow with the WAD installed inside the pre-made Emunand found here: https://ccabz.wordpress.com/2013/01/16/neek2o-emunand-setup-for-noobs/

I'm not sure what exactly this says about Wii Game freezing when Emunand saves are on, but think maybe it might explain some detail as to what's causing it.
 

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
UPDATE:
Have tested and can confirm both points 2. and 4. have been resolved fully in their entirety.
This update is regarding point 3. where the majority of games freeze at the moment of Save or Load when Emunand saves are Enabled.
Yesterday I discovered that the Wiiware title The Legend of Zelda: Ocarina of Time also freezes at the moment of attempting to save, with the Wii's disc tray flashing blue on a frozen frame of the game.
I tried all combination of Emunand Saves On/Off/Game Save and Emunand set to Full/Partial and "Use Real NAND Config" and sat through the Ocarina of Time opening to attempt each combination of settings.
Universally, Ocarina of Time freezes on Save attempt no matter the setting. This is launched from Emunand through Wiiflow with the WAD installed inside the pre-made Emunand found here: https://ccabz.wordpress.com/2013/01/16/neek2o-emunand-setup-for-noobs/
I'm not sure what exactly this says about Wii Game freezing when Emunand saves are on, but think maybe it might explain some detail as to what's causing it.
Attached below:

- Nintendont Launched Wiiflow games retrieve the correct system date

- Wii Fit Plus launched with USB Loader GX retrieves the correct system date
 

Attachments

  • 2023-04-23-120627.jpg
    2023-04-23-120627.jpg
    60 KB · Views: 39
  • 2023-04-23-121432.jpg
    2023-04-23-121432.jpg
    51.9 KB · Views: 73
Last edited by guitarburger,

fledge68

Well-Known Member
Member
Joined
Jan 30, 2012
Messages
2,440
Trophies
2
XP
4,998
Country
United States
2023-04-25-170005.jpg

i moved it back to this thread.
"A Light turns on, the camera zooms up on a wii balance board character" does not happen for me. I get a static screen with images and text wanting me to sync my wii balance board. which i don't have. so either you have synced your wii balance board some time in the past or you have a PAL version which runs different.

don't worry I'm still trying to figure out the issue. i googled it and see there's others with the same problem. I see in libogc there's a time issue commit. maybe i'll try it and see if it fixes your problem. but then why does usblgx work fine. ive looked at its code and can't see any difference. at least none that would make the time work and not work in wiiflow.

@blackb0x any thoughts?

EDIT: curious what version of usblgx? because i just saw syscheck modmii edition and it is compiled with the latest devkitppc which might be why wiiflow v5.5.3 has time issues and if your using an older version of usblgx that would be why it works on it.
 
Last edited by fledge68,

blackb0x

Well-Known Member
Member
Joined
Apr 22, 2019
Messages
788
Trophies
1
XP
3,547
Country
United Kingdom
@blackb0x any thoughts?
Try compiling WiiFlow's external booter with libogc 2.4.0 to see if their time fix resolves the issue. If it doesn't then you could apply this patch instead, which fixed this exact issue for someones Wii in 2021.

i just saw syscheck modmii edition and it is compiled with the latest devkitppc
It's actually a release behind now, since the latest devkitPPC and libogc update is just a week old. So SysCheck ModMii Edition doesn't include the time fixes.

You might need to make a few changes to get WiiFlow compiling with the latest version of devkitPPC and libogc. For example, the new SHA code from DacoTaco creates a conflict with wolfSSL because he defined SHA_BLOCK_SIZE within his code.
 
Last edited by blackb0x,
  • Like
Reactions: fledge68

fledge68

Well-Known Member
Member
Joined
Jan 30, 2012
Messages
2,440
Trophies
2
XP
4,998
Country
United States
Try compiling WiiFlow's external booter with libogc 2.4.0 to see if their time fix resolves the issue. If it doesn't then you could apply this patch instead, which fixed this exact issue for someones Wii in 2021.


It's actually a release behind now, since the latest devkitPPC and libogc update is just a week old. So SysCheck ModMii Edition doesn't include the time fixes.

You might need to make a few changes to get WiiFlow compiling with the latest version of devkitPPC and libogc. For example, the new SHA code from DacoTaco creates a conflict with wolfSSL because he defined SHA_BLOCK_SIZE within his code.
i assume i just slightly alter SHA_BLOCK_SIZE in wolf ssl to SHA_BLOCK_SZ maybe?
 

blackb0x

Well-Known Member
Member
Joined
Apr 22, 2019
Messages
788
Trophies
1
XP
3,547
Country
United Kingdom
i assume i just slightly alter SHA_BLOCK_SIZE in wolf ssl to SHA_BLOCK_SZ maybe?
Yeah. You can rename the 2-3 lines in that file to anything and it'll get rid of that warning. I just used "SHA_BLOCK_SIZE_WOLF".

Ideally it should be changed within libogc, since wolfSSL supports devkitPPC and it's been around for much longer than the new libogc code. But I doubt the devkitPro team care to fix it since it's not a library that they distribute.
 
Last edited by blackb0x,
  • Like
Reactions: fledge68

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
i moved it back to this thread.
"A Light turns on, the camera zooms up on a wii balance board character" does not happen for me. I get a static screen with images and text wanting me to sync my wii balance board. which i don't have. so either you have synced your wii balance board some time in the past or you have a PAL version which runs different.

don't worry I'm still trying to figure out the issue. i googled it and see there's others with the same problem. I see in libogc there's a time issue commit. maybe i'll try it and see if it fixes your problem. but then why does usblgx work fine. ive looked at its code and can't see any difference. at least none that would make the time work and not work in wiiflow.

@blackb0x any thoughts?

EDIT: curious what version of usblgx? because i just saw syscheck modmii edition and it is compiled with the latest devkitppc which might be why wiiflow v5.5.3 has time issues and if your using an older version of usblgx that would be why it works on it.
Got it. So, although it doesn't require you to connect or have a balance board to get to that screen, you still need to have a previously synced balance board somewhere in the system. I wonder if I could help you add it to your shared2 just for the sake of testing.

Amazing to hear your working on a solution. Was mainly updating to get some visibility in case someone else had this problem and fixed it. But definitely cool to have the two best devs on here looking into it as I didn't expect that.

The USBLoaderGX version pictured above was a couple revisions behind, USBLoaderGX 3.0 r1272, however I just updated to the latest, USBLoaderGX 3.0 r1281, and still got the correct date.

The only thing I really want to fix is the date problem, the others on my list were just small cosmetic problems like the boot animation (which you fixed) and a single game (Back to the Future). Which you now also fixed. However the date problem is something I'd really like to overcome, as well as perhaps the emunand saves. The Motion Plus is really a non-issue as I can just switch to a different controller to resolve that.
 
Joined
Sep 19, 2020
Messages
121
Trophies
0
XP
431
UPDATE:

I've just noticed something which is in my syscheck, my syscheck also gets the incorrect year. If you see in my Syscheck, on the last line it says: Report generated on 05/07/2159.

So, it is not just Wiiflow but also the SyscheckMe Homebrew App that retrieves an incorrect date and time, since neither my System Settings nor neek2o have anything close to this date and time.

To clarify:

Wiiflow Lite (Latest version) launching Wii Fit Plus - Incorrect Date (No matter the setting)

USBLoaderGX Launching the Same Wii Fit Plus - Correct Date

System Menu Launching Wii Fit Plus - Correct Date

SyscheckMe Homebrew App - Incorrect Date

My other update is that after giving it some thought, I think my initial theory that Wiiflow cannot utilise the Wii Motion Plus's extra technology is incorrect, and that actually, the entire Wiiflow app is utilising a seperate System Configuration in which the entire cursor sensitivity setting is set differently, and the time is different.

I found another source here describing Wiiflow accessing an entirely different set of Shared2 settings in which this person's controllers aren't even synced: https://gbatemp.net/threads/wiiflow-motion-plus-controller-issues.628254/

What are these System Settings that give this incorrect date? And where do homebrew apps like Wiiflow Lite and SyscheckMe retrieve their date and time information from? I've gone into my neek2o in case it is somehow getting the settings from there, but they are configured identically to my System Settings. I should note that my Wiiflow Lite is NOT running from within an Emunand.

Is it possible that by taking the Homebrew Channel WAD off from my System Menu, I've erased some kind of copy of System Setting information that the Homebrew Channel holds that Homebrew Apps retrieve from?

I've also done a ModMii recommended update of my system IOS's, hoping that it might update some old IOS that was causing this issue, but to no avail, so here is my new SysCheck:

SysCheck ME v2.5.0 by blackb0x, JoostinOnline, Double_A, R2-D2199 and Nano

...runs on IOS58 (rev 6176).



Region: PAL (original region: AUS)

System Menu 4.3E (v514)

Priiloader installed

Drive date: 02.13.2007

Homebrew Channel 1.1.3 running on IOS58



Hollywood v0x11

Console ID: 76266196

Console Type: Wii

Shop Channel Country: Australia (65)

Boot2 v4

Found 107 titles.

Found 52 IOS on this console. 7 of them are stubs.



IOS4 (rev 404): Stub

IOS9 (rev 1034): No Patches

IOS10 (rev 404): Stub

IOS11[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS12 (rev 526): No Patches

IOS13 (rev 1032): No Patches

IOS14 (rev 1032): No Patches

IOS15 (rev 1032): No Patches

IOS16 (rev 404): Stub

IOS17 (rev 1032): No Patches

IOS20[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS21 (rev 1039): No Patches

IOS22 (rev 1294): No Patches

IOS28 (rev 1807): No Patches

IOS30[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS31 (rev 3608): No Patches

IOS33 (rev 3608): No Patches

IOS34 (rev 3608): No Patches

IOS35 (rev 3608): No Patches

IOS36 (rev 3608): No Patches

IOS37 (rev 5663): No Patches

IOS38 (rev 4124): No Patches

IOS40[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS41 (rev 3607): No Patches

IOS43 (rev 3607): No Patches

IOS45 (rev 3607): No Patches

IOS46 (rev 3607): No Patches

IOS48 (rev 4124): No Patches

IOS50[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS51 (rev 404): Stub

IOS52[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS53 (rev 5663): No Patches

IOS55 (rev 5663): No Patches

IOS56 (rev 5662): No Patches

IOS57 (rev 5919): No Patches

IOS58 (rev 6176): USB 2.0

IOS60 (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS61 (rev 5662): No Patches

IOS62 (rev 6430): No Patches

IOS70[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS80[60] (rev 65535, Info: ModMii-IOS60-v6174): Trucha Bug, NAND Access

IOS90 (rev 404): Stub

IOS222 (rev 65280): Stub

IOS223 (rev 65280): Stub

IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access

IOS240 (rev 65535): No Patches

IOS241 (rev 65535): No Patches

IOS248[38] (rev 65535, Info: d2x-v11beta1): Trucha Bug, ES Identify, NAND Access

IOS249[56] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS250[57] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS251[58] (rev 65535, Info: d2x-v11beta1): Trucha Bug, NAND Access, USB 2.0

IOS254 (rev 65281): BootMii

BC v6

MIOS v10 (DIOS MIOS 2.10)

Report generated on 05/09/2159.
I am NOT an professional with this but, I believe your Homebrew's date is absolutely screwed.
I believe that Wii Fit Plus and your other games take the time from the WiiFlow menu as I believe the games take the time from the loader.
That probably means that WiiFlow has something wrong with it. Try reinstall the newest version or install an older version.
Just my advice; Sorry if I got something wrong.
 

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
Hey @fledge68, I've just noticed that both Kororinpa 1 and Kororinpa 2: Marble Saga both behave identically to Wii Fit Plus with displaying the date, if that's an easier game to access or test with as it doesn't require a balance board:
 

Attachments

  • koro1.png
    koro1.png
    1 MB · Views: 37
  • koro2.png
    koro2.png
    1 MB · Views: 38

guitarburger

Active Member
OP
Newcomer
Joined
Mar 31, 2023
Messages
27
Trophies
0
Age
33
XP
63
Country
Australia
I am NOT an professional with this but, I believe your Homebrew's date is absolutely screwed.
I believe that Wii Fit Plus and your other games take the time from the WiiFlow menu as I believe the games take the time from the loader.
That probably means that WiiFlow has something wrong with it. Try reinstall the newest version or install an older version.
Just my advice; Sorry if I got something wrong.
Appreciate it brother.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://youtu.be/IXlMFWPzjH4?si=g3HamowQcr950zrt lmao IT CHANGED MY LIFE