feat(settings): Free up space says what it deletes, and can clear shader caches #178
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!178
Loading…
Reference in a new issue
No description provided.
Delete branch "dyst/LongshotLauncher:feat/free-space-details"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Free up space deleted gigabytes without saying what, and players having trouble had no way to clear their shader caches. Now it asks first: it lists what it deletes, how big each part is and what it was kept for, and it can clear the shader caches too.
What changed
Free up space asks first. A confirmation lists each part of the build files folder that holds something, in plain words, with its size and what it was kept for (
Disk.WorkGroups):Then it gives the total and what the next build costs (it makes them again, up to as long as a first build).
Clearing shader caches, unticked by default. The dialog shows their total size and how many versions they belong to (
ShaderCaches.Clear):cache/files the game reads back, plus.partleftovers from an interrupted copy. Nothing else incache/or the game folder is touched (saves, settings, mods).longshot_pipelines.bin: it holds the pipeline list the build shipped, and only a build writes it again.Clearrefuses too.Settings say what's kept and why, with the shader caches' size beside the build files'.
Disk.WorkBytesis split into a size per part (GroupBytes).ShaderCaches.Keepreuses the new running check.README's Free up space note describes all of this.
Screenshots
New
free-spacescene intools/screenshots, and the updatedlauncher-settingsscene: attached in the first comment. Before and after, againstmain: #178 (comment)Tested
python -I tests/test_launcher_core.py: 1541 checks passed.WorkPartsentry is in exactly one group, and each group's size (the object store less what is hard-linked with objcache).cache/not followed (needs symlinks: always on Linux).python -I tests/test_release.py: 37 tests OK.dotnet build App -c Release: 0 warnings, 0 errors.Not done
main, and the check only lists them; they need translators.mise run ci:smoke: mise isn't installed on this PC.Disk.BuildBytes, which this doesn't change.The completely cold build is the next PR, stacked on this one.
Screenshots (tools/screenshots: free-space, launcher-settings): the confirmation, and the settings' new line about what is kept and why.
Screenshots: before and after
Drawn with
tools/screenshots(headless, the same scene and window on both sides): before frommain@321a9e1, after from this branch.Settings: the build files line and Free up space
Before
After
The Free up space confirmation
New: no before. On
main, Free up space deletes at once, without a confirmation.After
Before and after screenshots added.
WIP: feat(settings): Free up space says what it deletes, and can clear shader cachesto feat(settings): Free up space says what it deletes, and can clear shader caches