Skip to content

refactor(builder): name the DLSS license flag apart from the dialog text, and finish its comment - #2565

Open
LNDF wants to merge 1 commit into
NotRexed:mainfrom
LNDF:windows-dlss-license-nits
Open

LNDF wants to merge 1 commit into
NotRexed:mainfrom
LNDF:windows-dlss-license-nits

Conversation

@LNDF

@LNDF LNDF commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

The two nits from the review of #2528, which merged before I could address them.

  • The field dlssLicense sat beside the existing DlssLicense constant (the license dialog's text) in MainWindow.xaml.cs. It is dlssLicenseAccepted now.
  • Its comment read as cut off ("…and its runtime went"). It now says in full that the update built the folder without DLSS and removed its DLSS runtime.

No change in behaviour. The UpdateBuild fixture (tests/builder_dlss_update_test.cs, run on .NET 10 here) still passes its 63 checks; python -I -B tests/run_all.py on Linux: nothing new fails.

🤖 Generated with Claude Code

…ext, and finish its comment

Review nits on NotRexed#2528: the field dlssLicense sat beside the DlssLicense
constant (the license dialog's text) in MainWindow, and its comment read as
cut off. The field is dlssLicenseAccepted now, and the comment says what the
old record did in full. No change in behaviour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.

I merged this into current main. Nothing else in builder/ or tests/ refers to dlssLicense by name: I grepped main and the open #2591 branch, so the rename breaks no source-reading check. tests/test_ffx_sdk.py passes. The .NET fixture (tests/builder_dlss_update_test.cs) needs the SDK, which I don't have here, so for that I'm relying on your run and the Builder package job, which is green. I also merged it on top of #2591 and #2553 and it applies cleanly with both, so the three can land in any order.

The red Python shards fail only test_env_on (HOS_FPS_LOG in host/oot_high_fps.c, fixed on main since), test_psychov35 and test_pcache_header_read on Windows. None of them come from this change, and a re-run should clear them.

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