Repository navigation
Conversation
… table A build without a table entry gets angle-bonus guidance after Wisp has read the known scoring curve from the game: the saturation angle with the other four values beside it, in one arrangement, at least eight times, unchanged on a second read. The read runs once per build per PC in the background and its result is stored. The drift-zone-check control pauses it.
This file contains hidden or 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
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.
First step of #220: Drift Zone guidance no longer depends on a table entry for every Forza build.
What changes
DriftZoneProfileCataloggets the bonus guide after Wisp has read the running game and found the known curve.DriftZoneCurveScanlooks for the float32 saturation angle with the minimum and maximum angles and both multipliers beside it, in one arrangement, at least eight times, unchanged on a second read. Both checked builds hold 20 such entries.DriftZoneCurveCheckanswers the renderer from stored results and never blocks. The read starts when the gauge needs a profile in Drift Zone mode while driving, runs once per exact build per PC on a lowest-priority thread, is paced, and is kept indrift-zone-checks.json. A verified build is read again after 14 days; a build without the curve is retried after 2 minutes, 10 minutes and then hourly.driftcheckobservation per result and run:success,unsupported,unknown,timeoutorfailure.drift-zone-check. While paused, nothing is read and a build outside the table stays onANGLE ONLY.NativeHudProcessMemory.TryQueryRegion(VirtualQueryEx) on the existing handle.RequiredProcessAccessis unchanged at0x1010, and nothing is written.Checked
DriftZoneCurveScanTests(12) andDriftZoneCurveCheckTests(19) pass locally against the same sources; the build key tests run in CI.Not checked
Decisions before merging
PROCESS_QUERY_INFORMATIONso it can skip non-resident pages.ProcessRightsRemainReadOnlyAndLimitedQueryforbids that right today, so this change does not use it.