feat(tools): the launcher's screens drawn without a display into PNGs, for pull requests and the README #85
No reviewers
Labels
No labels
area/build
area/install
area/saves
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
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!85
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:feat/screenshot-tool"
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?
Pull requests that change a screen should include screenshots, but the only way to get them was to run the launcher by hand on a real desktop: a real home, real saves, real paths, and a real game build to reach the build page. This adds a tool that draws the screens without a display, the same way every time, with nothing from the PC that draws them.
What changed
tools/screenshots(new):dotnet run --project tools/screenshots -- <out folder> [scene ...]renders the 960x600 window through Avalonia.Headless and Skia into one PNG per scene:homesettings-linux(AMD GPU)settings-windows(NVIDIA GPU)fsr-linux-noticebuild(reading the game files)build-log(Show details at Debug, from a replayed make_game transcript)/home/player/...,C:\Users\Player\...);SetNewest), so nothing goes over the network;Disk.ShownDrive. Without it, a Windows path on Linux resolved against the current folder and showed this PC's mount point.Directory.Packages.propspinsAvalonia.Headless12.1.6 (the Avalonia version in use). The tool has its ownpackages.lock.json, and it's inLongshotLauncher.slnx, so CI compiles it and it keeps up with the views. It isn't part of the release programs (package.shpublishesApponly).Testing
Tested on Linux:
python -I tests/test_launcher_core.py: 1058 checks passed.python -I tests/test_release.py: OK.Not tested: running the tool on Windows.
Screenshots
What the tool draws, from this branch:
home
settings-linux
settings-windows
fsr-linux-notice
build
build-log