it was probably a category filter issue, or a favorite issue.
the category can have different checkbox type : the "check" type is the one you use by default to display ALL games.
even if you have other checks on other category, it doesn't have any effect if "all" is enabled, because it means that you want to see all of them.
the "X" type is used as a blacklist mode. if "all" is set to "X" is means it will display ALL games except the one with a cross.
and finally, if "all" is not checked at all, it's displaying only the game which contains the category marked with "check" type, and will hide all games with category marked with "X".
if you need more help, I will search a better tutorial and example for the category menu.
The MD5 is not really important. what's important is to have proper settings, and check that the ISO is correct. to check that, you use the "sha1" option in WiiBackupManager.
MD5 is only a way to check if two files are identical. it doesn't tell you if the ISO is good. if you have a WBFS file, the md5 will be different than the ISO, etc.
sha1 is using the internal file system of the game to compare if the game is good or corrupted.
How did you learn how to code, Cyan? I have free time 99% of the time, so I want to learn how to code so I can help you!
try and analyze.
I always learned how to code by trying to change existing source codes and see the result.
I learned basic, html, PHP like that, and knowing PHP helped a lot with learning C/C++ as it's all based on the same logic : the keyword are the same, the while/for/condition etc. all are working the same way.
If you already know a language (compiled like C or just processed like PHP or only read like html) it will help you. you will already have the rigor and the logic for ordering your program correctly.
if you want to do things yourself:
Start by being able to compile the homebrew so you can make changes and see the result by yourself.
try to do very simple changes for a start, don't think about doing a new menu, or adding new settings. instead you could for example there's this bug :
" progress bar to starts at 100% (0/0) instead of 0% (0/100) (issue 2185)"
this is a bug where the initial values are not initiated yet when the window is displayed. then it reads the start and end for the progress bar %
you could decide to fix that bug doing two different method :
- be sure the GUI doesn't display the window before the init is done
or
- ensure that the "end" value of the default state is always bigger than the "start".
Guess which is the easier one, and try to fix it. doing try and error is how you learn.
let me know if you fixed it
Well, there's also "read C/C++ books or tutorial".
But if you want to help, even without programming knowledge, what would be useful are users who understand ALL the setting's function, their use, their effect on the loader, etc.
understanding and knowing all the loader's possibility will help me when I need a beta tester. someone who understand that if I change something, it can affect something else and that he can try and check if it still work as intended. Understanding the loader is needed to do proper bug report !
A lot of user's bug report are hard to understand, confused or even conflicting with current loader's logic.
understanding how the loader works lets you report a bug properly, not "it doesn't work" but "in revision xxx it worked, in revision yyy it doesn't with that option" is already a lot more useful.
Example of wrong bug report :
Smash Bros Brawl is not dumped correctly! there's an issue ! please fix the dump function !
that's not a bug, it's only the user's fault for not using the proper setting to dump the additional partitions...