Skip to content

build(release): the RTX 5090 fork list's note says what its build changed (#2143 follow-up) - #2703

Open
Brett-D wants to merge 1 commit into
NotRexed:mainfrom
Brett-D:docs/pipeline-note-2143
Open

Brett-D wants to merge 1 commit into
NotRexed:mainfrom
Brett-D:docs/pipeline-note-2143

Conversation

@Brett-D

@Brett-D Brett-D commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #2143, which merged before I could answer Joey-Magnus's and hckrman101's question about brett-d-rtx-5090-fork-fg-2x. This changes only that list's note, to say what its build was.

The "fork" was local builds of main at 0828863 (9 Nov), plus changes that don't touch what goes into a record: DLSS-NR and an FXAA option in the window-scaling pass, a sampler cache and its descriptor-reuse check, a texture budget, menu rows and a voice feature. There are no changes to shader translation, program variants, target formats or draw state.

python -I nx2/pipeline_states.py check passes. The list itself is unchanged.

Refs #2034, #2143

…ord holds)

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

@Joey-Magnus Joey-Magnus left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this answers the question I asked on #2143. The list was recorded on local builds of main at 0828863 (9 Nov, which I can see on main), and the local changes are host-side only: DLSS-NR, FXAA in the window-scaling pass, the sampler/descriptor caching, the texture budget, menu and voice. None of those touches shader translation, program variants, target formats or draw state, so the records describe pipelines main makes. Records from the older-main sessions can at worst name pipelines that are never hit, which costs nothing. I merged this into current main and ran python -I nx2/pipeline_states.py check: it passes, and only the note changed. The one failing job, Python source checks part 1/2, is test_release_scripts.py's test_nightly_two_runs_at_once_end_at_the_newer_commit. That test is flaky and unrelated to this file, and a re-run should clear 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.

2 participants