On this page
Which Windows or Linux version do I need?
| Platform | Operating system | CPU | Graphics |
|---|---|---|---|
| Windows | Windows 10 version 1903 or newer, or Windows 11; 64-bit | x86-64 with AVX | Vulkan 1.3 and a current driver |
| Linux and Steam Deck | x86-64 Linux with glibc 2.39 or newer | x86-64 with AVX | Vulkan 1.3 driver |
Linux and Steam Deck use the experimental AppImage. On Deck, a first start selects 1280 × 800; a saved resolution takes priority.
How do I check my system version?
On Windows, run winver to see the Windows version. Open Settings → System → About to check the system type and exact processor name.
On Linux, run:
uname -m
ldd --version
The machine type must be x86_64. Read the glibc version on the first line of ldd --version and compare it with 2.39. Use a distribution that meets that requirement for the AppImage.
Does my CPU need AVX or AVX2?
AVX and AVX2 are CPU instruction features. SpartanPort requires AVX. Check the exact CPU model's instruction set in its manufacturer's specifications. The loader substitutes several other missing instructions on older AVX processors; AVX remains the starting requirement.
On Windows 11, Coreinfo 4.02 can show instruction support. From its extracted folder, run Coreinfo64.exe -f and find AVX; * means supported. Check AVX2 separately if you are considering eltutz. Use the manufacturer's model specifications on Windows 10.
If the game exits with STOP: this CPU lacks, include the complete message and CPU model in your problem report.
How do I check Vulkan and choose the right GPU?
Vulkan is the graphics interface used by the port. Update the driver for the GPU you intend to use. With the Vulkan SDK's Vulkaninfo utility, inspect that GPU's device apiVersion and check for 1.3 or newer. Check the device entry as well as the installed Vulkan software.
On a laptop with two GPUs, open Performance → GPU data → Graphics card in the launcher, select the dedicated GPU, click Save and start the game again. That setting selects the card the game runs on.
Can I use Intel integrated graphics or an HD 630?
Intel integrated graphics have specific outstanding rendering and loading problems:
- HD 630: the real-time 3D image can be black or blue while videos and the interface remain visible.
- Iris Xe: startup and level-loading crashes, black screens and hangs.
- Intel UHD:
Device lost during submitduring area loads or longer sessions. - Iris Plus and Iris Xe: excessive lighting, white areas or flashing colours on some setups.
If the computer also has a dedicated GPU, select it using the steps above. For an integrated-only computer with one of these symptoms, use the GPU troubleshooting entry and keep its log for the matching report.
How much RAM or VRAM do I need, and what should I lower first?
The project publishes no minimum RAM or VRAM capacity. Start at Native render resolution on a desktop or laptop, or 1280 × 800 on Steam Deck. Higher resolutions reserve more memory. When the launcher warns about a larger request, lower Render resolution before trying again.
On a lower-end GPU, choose a lower rendering size through Settings. On a CPU with four threads or fewer, use the current release for its worker-scheduling changes.
A Windows error 1450 calls for the virtual-memory steps.
Will my computer hold 60 FPS?
A mid-range dedicated GPU such as the RX 6700 XT, paired with a Ryzen 5 5600X, averages well above 60 FPS at 1080p: the reference run averaged 144 FPS. The older i5-7500 + GTX 1660 Ti averaged about 59 FPS in SpartanPort 2.7.0. If FPS falls short, lower Render resolution first.
| Hardware and conditions | Result |
|---|---|
| Ryzen 5 5600X, RX 6700 XT and 32 GB RAM; 1080p, 240 FPS engine | 144 FPS average, ranging from 55 to 240 FPS |
| i5-7500 and GTX 1660 Ti; worker-scheduling update comparison | 59.0 FPS average, up from 36.0 FPS |
For low FPS on a slower GPU, lower Performance → Render resolution to 900p or 720p first. On a CPU with four threads or fewer, use the current release for its worker-scheduling improvement. Settings gives reference frame rates and lower-resolution options; CPU troubleshooting gives the per-thread log and performance display; PC port vs RPCS3 explains how to choose a route.
Does the eltutz alternative need a different CPU?
Yes. eltutz v3 needs Windows 10/11 64-bit, AVX2 and current Vulkan drivers. Check AVX2 explicitly before choosing it. Ports compares the separate launcher, emulator and patch components.
How much free disk space should I leave?
Allow space for each part separately: the program download, extracted Windows program, existing game directory, prepared game image, shader and pipeline caches, and saves. Keep a separate copy of existing saves before an update.
Shader and pipeline caches grow as new scenes compile shaders. Older versions could exceed 20 GB because they stored duplicate pipeline binaries. The current release stores identical binaries once and converts existing files in the background. Open Performance → Shaders → Delete shader cache to see the actual size and folder before confirming a deletion; the next launch compiles those shaders again.
After checking the system and game build, continue to Windows installation or Linux & Steam Deck. If launch fails, keep the displayed error and use Troubleshooting.