Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some fixes: avoid black banners / minimize one usb related dsi exceptions / get custom banners / install shared content #2
base: enhanced
Are you sure you want to change the base?
some fixes: avoid black banners / minimize one usb related dsi exceptions / get custom banners / install shared content #2
Changes from 7 commits
bc177f4
2d8980e
66194a4
e90a9b0
92a412f
d507ba5
9be48c9
73f97bd
35aac59
e0fbe07
b19f469
5dd6e85
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is breaking up the
Wad::CheckContentMap
function in to two separate functions (which is probably a good thing), I think you will need to update all existing invocations ofCheckContentMap
to useUpdateContentMap
, since those old calls expectCheckContentMap
to do both pieces.Not 💯 on this yet, but I'm pretty sure. Still learning my way around here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Jacoby6000!
No, in fact the original problem was that despite its name, checkContenMap checked and always updated the content.map file without installing the shared content. The updateContentMap process should only be called once, after the shared content has been succesfully installed. The other invocations of checkContentMap only need the check stuff. The flow is explained here with a little more of detail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahhh I see. I didn't fully understand what was going on. This makes sense! I'll test it this week and get it merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any examples of wads with shared content so that I can validate this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think any title will do.
If you want to see the bug in action, you can prepare the following lab.
Take a working emunand and delete all but one shared content:
Install any title with the old build. Check the shared1 folder. You will find no new file. But notice that the
content.map
file has increased in size::USBGLX have added the hash of the shared contents included in the wad to the
content.map
file. The title won't load for sure. And from now on, this emunand is doomed. Any tool that checkscontent.map
will assume that the shared content is already installed and will skip its installation.Recreate the minimal
content.map
again:and install the same content with the new build.
content.map
will have the same size (and content) than with the old build, but now shared1 folder will contain some0000000x.app
files. If you try, the installed title will (probably) load (if not, well ... we have deleted ~ 70 files or so, some unexpected behavior can happens...).If you have access to a (physical) Wii , the real case scenario is to create a minimal emunand using modMii and then install any title with USBGLX. You will will succeed only with the new build (with the old build, installation apparently works, but the title won't load).
Or in a wii/vWii, only if you have never installed any title in the real NAND: if you export it to create and emunand, title installation will only succeed with the new build.
It's a subtle bug, which is why it has gone unnoticed for years. And I think mainly affects to new modders.
By the way, when testing this with the previous version, the DSI exception error hit me twice :D