Skip to content

Fix boss key kaleido text for NTSC #5389

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

Merged
merged 1 commit into from
Apr 11, 2025

Conversation

Archez
Copy link
Contributor

@Archez Archez commented Apr 11, 2025

The texture name for the boss key item name text in kaleido is named gBigKeyItemNameENGTex in the NTSC versions, but named gUnusedBigKeyItemNameENGTex in the PAL versions. The code is using gUnusedBigKeyItemNameENGTex to for rendering, causing NTSC to crash when hovering over the boss key.

I think gBigKeyItemNameENGTex would be the better name overall, but for a develop-blair bugfix, I'd rather have the NTSC OTRs require regen instead of the PAL ones. We can always rename and change the code later for a 9.1.0 release in the future.

Build Artifacts

@leggettc18
Copy link
Contributor

So the texture for the BigKeyItemNameTex doesn't visibly appear anywhere but the game tries to load it anyway? Am I understanding that right?

@Archez
Copy link
Contributor Author

Archez commented Apr 11, 2025

The game was crashing, as it tries to load the resource by that name, but it didn't exist

@leggettc18
Copy link
Contributor

OK, since this one is fixing a crash should we make it actually require an OTR regen? Or is there not a way to do that for only the NTSC versions?

@Archez
Copy link
Contributor Author

Archez commented Apr 11, 2025

There is not a way currently to selectively do a regen. We can just call it out again in the changelog.
The crash would only occur for anyone that strictly had NTCS versions. If someone had a combo of PAL and NTSC for mq non-mq, then it wouldn't crash).

@leggettc18
Copy link
Contributor

Alright, figured I'd ask. Would be nice if we could trigger rebuilds for only NTSC, but at this point by the time we could implement it we probably wouldn't need it anymore.

@leggettc18
Copy link
Contributor

Confirmed I could repeat the crash pre-regen and no crash post-regen. Merging now.

@leggettc18 leggettc18 merged commit 86e1e8e into HarbourMasters:develop-blair Apr 11, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants