PPTC Profiles #370
Merged
PPTC Profiles #370
+299
−28
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
github-actions
bot
added
cpu
|
Download the artifacts for this pull request: |
LotP1
force-pushed
the
PPTC-profiles
branch
4 times, most recently
from
ebc9441 to
e0acefe
Compare
GreemDev
force-pushed
the
PPTC-profiles
branch
from
523be83 to
176ce06
Compare
this is currently broken with Exlaunch mods that use hooks
The stream hadn't been reset causing all hashes to be the same in most cases
- Added blacklist status to FunctionProfile - Added PPTC Info file updater from v5518 and updated old updater logic to allow multiple update passes - Added blacklist check to PPTC Cache loading - Added marking functions as blacklisted if they do not yet exist at PPTC translation time - Logger now shows how many functions were blacklisted when translating new functions to PPTC cache
SomeoneIsWorking
pushed a commit
to SomeoneIsWorking/Greem
that referenced
this pull request
Feb 1, 2025
Added functionality that allows ExeFS mods to compile to their own PPTC Profile and therefore store PTC data between sessions. The feature calculates the hash of the currently loaded ExeFS mods and stores the PPTC data in a profile that matches said hash, so you can have multiple ExeFS loadouts without causing issues. This includes different versions of the same mod as their hashes will be different. Using this PR should be seamless as the JIT Sparse PR already laid the groundwork for PPTC Profiles and this PR just allows ExeFS mods to load and store their own profiles besides the `default` profile. ❗❗❗ **WARNING!** ❗❗❗ **This will update your PPTC profile version, which means the PPTC profile will be invalidated if you try to run a PR/Build/Branch that does not include this change!** **This is only relevant for the default PPTC Profile, as any other profiles do not exist to older versions!**
Closed
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.
Added functionality that allows ExeFS mods to compile to their own PPTC Profile and therefore store PTC data between sessions.
The feature calculates the hash of the currently loaded ExeFS mods and stores the PPTC data in a profile that matches said hash, so you can have multiple ExeFS loadouts without causing issues. This includes different versions of the same mod as their hashes will be different.
Using this PR should be seamless as the JIT Sparse PR already laid the groundwork for PPTC Profiles and this PR just allows ExeFS mods to load and store their own profiles besides the
defaultprofile.❗❗❗ WARNING! ❗❗❗
Using this fork will update your PPTC profile version, which means the PPTC profile will be invalidated if you try to run a PR/Build/Branch that does not include this PR!
This is only relevant for the default PPTC Profile and because of that i don't recommend running this PR without ExeFS mods!