- memory issue (try to delete lot of games from xml to make it smaller)
- malformed xml (need to find which game breaks the xml, and fix it on the gametdb website)
as for the 'memory issue'... I assume it might be tricky to delete things properly from the xml? ; like is there any specific way you got to delete entries so things work properly? ; but even if I do get that stuff deleted right to remove say a few MB or so, I don't think it's going to help any given my answer below (see my text quote my quote of you below).
as for the 'malformed xml'... I assume finding which game breaks the xml file is going to be quite difficult? ; because even though I was saying things were working months ago, as I know it was okay back in November (and might have been okay a fair amount after that), it might be difficult to find out at exactly which point the issue appeared where it does not show any info when you highlight a game and press 2 on the Wii remote.
Ahh, you have backup with smaller size? did you try it?
Well I deleted the 'wiitdb.xml' and 'wiitdb_offsets.bin' from the general 'usbloader_gx' folder on the Wii's SD card and replaced it with the wiitdb.xml I have from Nov 2018 and it does show info when highlighting a game and pressing the 2 button on the Wii remote. but... the parental controls don't filter properly, or much at all, as I think off the top of my head from messing with it last night, it might have only filtered one game out of the total amount of games I have when I locked and unlocked the USBLoaderGX. so the automatic parental controls are pretty much shot even though this does display the stuff when highlighting a game and pressing 2 on the Wii remote.
EDIT: I figured I would update this post as I updated the wiitdb a moment ago on my main Wii (on May 8th 2019) and it's fixed as the parental controls now work as expected. did someone fix something on the wiitdb side? ; because pressing the 2 button on Wii remote now shows the correct info again and adjusting parental controls now filters the games correctly for each setting as I tested it quickly and all seems to work again as expected.
Last edited by ThaCrip,