Skip to content
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

Remove POLY_KAL and restore POLY_OPA for kaleido #5041

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

Archez
Copy link
Contributor

@Archez Archez commented Feb 11, 2025

POLY_KAL was a custom buffer we originally added on the launch of the port to handle rendering kaleido and the game world at the same time, such that kaleido was over the game world (OPA & XLU) but under the OVERLAY.

Now that the game world is no longer rendered and a framebuffer capture is used for kaleido, we can finally revert kaleido back to using POLY_OPA like the original source code and remove all port additions around polyKal.

The changes largely consist of renames from POLY_KAL_DISP -> POLY_OPA_DISP and then removing any specific graphics setup code around polyKal.

Build Artifacts

Comment on lines -195 to -198
// #region SOH [General]
// Upstream TODO: Document reasoning for these only existing in SoH
#define POLY_KAL_DISP __gfxCtx->polyKal.p
// #endregion
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very happy to be able to finally get rid of all the added buffers from launch 🎉

@leggettc18
Copy link
Contributor

Still need to review the actual code, but from a brief playtest on linux so far it all works fantastically. Even the custom Kaleido menu I added. I figured if anything would have an issue it'd be that but it seems to behave exactly as before.

@aMannus aMannus merged commit 135c2e8 into HarbourMasters:develop Feb 12, 2025
5 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.

3 participants