feat: check system requirements above the tools download #25
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/ui
area/updates
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!25
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:feat/system-requirements"
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?
Players should see whether their PC meets the published requirements while the builder downloads, before spending time building the game. Add a status card above the download progress. The status caption and System requirements link share the first line; a visible second line shows detected RAM, Vulkan support, VRAM and mesh-shader availability, along with any limitations or unknown checks. Details wrap across the card as needed and remain available as accessibility help text.
The native Vulkan probe reads API support, device-local memory and the meshShader feature directly from the installed loader. It evaluates one GPU at a time, without combining different cards' capabilities. CPU-model performance and physical core count are not verified; the linked requirements page covers them. GPU shared memory can be reported differently, storage uses the initial build destination, and RAM reflects the runtime's available-memory limit. No frame-rate guarantee is implied.
Validation: .NET 10 build with warnings as errors; 597 core checks passed, including 22 requirements cases for thresholds, unknown results, mesh shaders, precedence, multiple GPUs and accurate descriptions of detected hardware; all 28 release tests passed. Native Vulkan/mesh-shader probe exercised on Linux. Actual Avalonia screens rendered headlessly at 960×600 and visually reviewed with authored status fixtures. No game files or saves used. Windows native probing remains untested on Windows.
2b6c2e3f4b61a453e39361a453e393a04a3e81ea