apply XPARAM directly on RAM #1277
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
israpps
force-pushed
the
patch-24
branch
4 times, most recently
from
e0c4dce
to
68afb2f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request checklist
Note: these are not necessarily requirements
Pull Request description
summoning @qnox32 here in case I did something wrong.
The idea behind this PR is taking benefit of the fact that XPARAM table is accesible in RAM, allowing us to apply manual params quickly. specially for the reset params function. uploading XPARAM to the IOP 12 times doesnt sound right XD. we still use XPARAM, but only because it has a database of the games needing one, saving us the trouble of copying that DB around