Skip to content

Check the Drift Zone curve in the running game for builds outside the table - #229

Draft
Views2k wants to merge 2 commits into
mainfrom
feat/drift-zone-curve-check
Draft

Views2k wants to merge 2 commits into
mainfrom
feat/drift-zone-curve-check

Conversation

@Views2k

@Views2k Views2k commented Nov 20, 2026

Copy link
Copy Markdown
Owner

First step of #220: Drift Zone guidance no longer depends on a table entry for every Forza build.

What changes

  • Curve check. A build that is accepted but not in DriftZoneProfileCatalog gets the bonus guide after Wisp has read the running game and found the known curve. DriftZoneCurveScan looks 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.
  • Service. DriftZoneCurveCheck answers 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 in drift-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.
  • Builds in the table keep their guidance from the table and are read once as well, so the check is exercised on today's builds before a game update depends on it.
  • Reporting. One drift check observation per result and run: success, unsupported, unknown, timeout or failure.
  • Pause control. New controlled feature drift-zone-check. While paused, nothing is read and a build outside the table stays on ANGLE ONLY.
  • Memory access. NativeHudProcessMemory.TryQueryRegion (VirtualQueryEx) on the existing handle. RequiredProcessAccess is unchanged at 0x1010, and nothing is written.

Checked

  • App and test projects compile.
  • DriftZoneCurveScanTests (12) and DriftZoneCurveCheckTests (19) pass locally against the same sources; the build key tests run in CI.
  • The same algorithm ran against both live builds on November 19 from a standalone tool: 20 of 20 entries, about 1.1 s unpaced for 5 to 7.5 GiB.

Not checked

  • The in-app path has not run against the game on either platform.
  • Because the handle keeps only the limited query right, the read cannot skip pages that are not in memory. On the test PC about 5% of the scanned memory was not resident.
  • A single zone with a different curve is not detected, and scoring code is not compared.

Decisions before merging

  • Whether the check may open a second read-only handle with PROCESS_QUERY_INFORMATION so it can skip non-resident pages. ProcessRightsRemainReadOnlyAndLimitedQuery forbids that right today, so this change does not use it.
  • Builds in the table are read once per player after the release that carries this.

… 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.
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.

1 participant