Commit Graph

5 Commits

Author SHA1 Message Date
chrg6
d6b4eab004 Describe the Linux changes, the event wakes and the log thread in the 0.7.0 notes, and thank their authors.
The Linux section says plainly that none of it was run here. The AppImage is described as built and attached by an
automated job after the release is published.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 07:40:20 -05:00
chrg6
c2a51a334a Merge GitHub main into the 0.7.0 release line: uniform blocks copied at the submit call with the replay on its own thread, the overlay's frame times measured where the pictures go out, and early pictures kept back.
The two commits main gained since the last merge. docs/releases/v0.6.2.md stays removed; the two notes they added to
it are in docs/releases/v0.7.0.md. Checked on a dev build of the merged tree: the settings, self-test, graphics ABI,
input and kernel probes pass, and a scripted run with six DLSS mode changes presents no dark or black frame, makes the
area's textures in one frame at the load and ends without a fatal error.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 07:17:01 -05:00
chrg6
9dbfed207f Turn the lazy write-back off by default and offer it in the settings menu as Experimental FPS boost.
With it on, single frames come out with the whole scene lit differently (brighter, shadows off). The flight recorder's
thumbnails of 1,800 presents standing in Hyrule Field show none with it off in every run, and with it on 43 to 181
while four other threads keep the CPU busy (10 to 97 in earlier runs, 0 on an idle machine); the cause is not found.
Two candidate fixes (arming only against a sync whose copies were handed over, and snapshots waiting for GPU writes in
flight) did not change the count, and fetching at every release made it far worse.

So wb_lazy is 0 unless set, on every platform (mem_init loses its special case), and the Screen tab has the row
Experimental FPS boost for it on Windows, with its text in the four menu languages; like every setting read at the
start it notes "after restart". The 0.7.0 notes describe it as experimental and off, say about 1.6 GiB for the video
memory a full shader cache no longer holds (2,484 to 846 MiB at the title screen in the measured run), and list the
two fixes before this one.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 07:12:23 -05:00
chrg6
9ecfdf1543 Merge GitHub main into the 0.7.0 release line: frames that lack draws are held back, and the overlay shows the game's own video memory.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 05:37:45 -05:00
chrg6
c5478866cf Set the version to 0.7.0 and write its release notes.
The notes take over the draft kept for the release after 0.6.1 and add what the test line gained since: the open-area
and town frame rate work, the memory fixes, DLSS Multi Frame Generation, the settings that apply while the game runs,
and the fixes from the testers' reports and pull requests.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-10 05:37:02 -05:00