In SpikerSoft Stacker, the Performance Settings panel fails to detect or utilize the GPU correctly. Despite having a compatible GPU installed, the system reports “none (CPU only)” under the hardware overview. This prevents users from leveraging GPU acceleration for image processing and stacking tasks, resulting in slower performance.
Issue Description
When accessing the Settings → Performance tab, the hardware overview lists the CPU and memory correctly but shows GPU: none (CPU only) even when a GPU is available. The Warp Engine and GPU resident options remain inactive or default to Auto (0.0 GiB). This indicates that the GPU detection or initialization logic is not functioning as intended.
Environment
Property
Value
Application
SpikerSoft Stacker
Module
Settings → Performance
Environment
Production
Operating System
Windows 11
Version
v2026.10.10e
Device
Desktop
Hardware
AMD64 Family 25 Model 80 (12 cores, AVX2)
Memory
15.4 GiB total, 6.3 GiB available
GPU
Detected as “none (CPU only)”
Preconditions
User has a GPU installed and drivers properly configured.
Steps to Reproduce
Launch SpikerSoft Stacker.
Open Settings → Performance.
Observe the Hardware Overview section.
Note that GPU is listed as “none (CPU only)” even when a GPU is present.
Attempt to switch to GPU mode under Warp Engine — no change occurs.
Expected Result
The GPU should be detected automatically and listed under Hardware Overview.
The Warp Engine and GPU resident options should activate and allocate memory accordingly.
Image processing should leverage GPU acceleration when selected.
Actual Result
GPU is not detected or utilized.
All GPU-related options remain inactive or default to Auto (0.0 GiB).
Image processing runs exclusively on CPU, reducing performance.
Evidence
Screenshot shows GPU: none (CPU only) and GPU resident: Auto 0.0 GiB (auto) despite available hardware.
The Warp Engine section defaults to CPU mode.
Impact
Prevents users from using GPU acceleration.
Slower image stacking and processing times.
Reduces efficiency for high-resolution workflows.
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
Review GPU detection logic during app initialization.
Ensure compatibility with major GPU APIs (CUDA, OpenCL, DirectX).
Implement fallback detection for integrated GPUs.
Add diagnostic logging for GPU initialization errors.
Provide user feedback if GPU drivers or permissions are missing.
## Summary
In **SpikerSoft Stacker**, the **Performance Settings** panel fails to detect or utilize the GPU correctly. Despite having a compatible GPU installed, the system reports **“none (CPU only)”** under the hardware overview. This prevents users from leveraging GPU acceleration for image processing and stacking tasks, resulting in slower performance.
## Issue Description
When accessing the **Settings → Performance** tab, the hardware overview lists the CPU and memory correctly but shows **GPU: none (CPU only)** even when a GPU is available. The **Warp Engine** and **GPU resident** options remain inactive or default to **Auto (0.0 GiB)**. This indicates that the GPU detection or initialization logic is not functioning as intended.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Stacker |
| Module | Settings → Performance |
| Environment | Production |
| Operating System | Windows 11 |
| Version | v2026.10.10e |
| Device | Desktop |
| Hardware | AMD64 Family 25 Model 80 (12 cores, AVX2) |
| Memory | 15.4 GiB total, 6.3 GiB available |
| GPU | Detected as “none (CPU only)” |
## Preconditions
User has a GPU installed and drivers properly configured.
## Steps to Reproduce
1. Launch **SpikerSoft Stacker**.
2. Open **Settings → Performance**.
3. Observe the **Hardware Overview** section.
4. Note that GPU is listed as “none (CPU only)” even when a GPU is present.
5. Attempt to switch to **GPU mode** under **Warp Engine** — no change occurs.
## Expected Result
- The GPU should be detected automatically and listed under **Hardware Overview**.
- The **Warp Engine** and **GPU resident** options should activate and allocate memory accordingly.
- Image processing should leverage GPU acceleration when selected.
## Actual Result
- GPU is not detected or utilized.
- All GPU-related options remain inactive or default to **Auto (0.0 GiB)**.
- Image processing runs exclusively on CPU, reducing performance.
## Evidence
- Screenshot shows **GPU: none (CPU only)** and **GPU resident: Auto 0.0 GiB (auto)** despite available hardware.
- The **Warp Engine** section defaults to CPU mode.
## Impact
- Prevents users from using GPU acceleration.
- Slower image stacking and processing times.
- Reduces efficiency for high-resolution workflows.
## Frequency
Always
## Reproducibility
100%
## Severity
High
## Suggested Fix
- Review GPU detection logic during app initialization.
- Ensure compatibility with major GPU APIs (CUDA, OpenCL, DirectX).
- Implement fallback detection for integrated GPUs.
- Add diagnostic logging for GPU initialization errors.
- Provide user feedback if GPU drivers or permissions are missing.
Thanks for the report and the screenshot. Two things are going on:
Stacker only looks for the GPU when the first alignment runs, so with no images imported (as in the screenshot) the overview says "none (CPU only)" on every machine, and "GPU resident 0.0 GiB" follows from that. The caption was wrong to say "what Stacker found when it started". That is fixed in spikerj/spikersoft-stacker#1015: the GPU is looked for at startup and the line says "looking…" until it has answered.
Whether your Ryzen's GPU is genuinely usable is a separate question. Could you attach stacker.log (Help › Reveal log) after importing a stack and running Align once? If the adapter was found it will show GPU warp available; if not, the line GPU: no adapter (…) or GPU: … found but no device (…) says why, and that is what we need to see.
Thanks for the report and the screenshot. Two things are going on:
1. Stacker only looks for the GPU when the first alignment runs, so with no images imported (as in the screenshot) the overview says "none (CPU only)" on every machine, and "GPU resident 0.0 GiB" follows from that. The caption was wrong to say "what Stacker found when it started". That is fixed in spikerj/spikersoft-stacker#1015: the GPU is looked for at startup and the line says "looking…" until it has answered.
2. Whether your Ryzen's GPU is genuinely usable is a separate question. Could you attach `stacker.log` (Help › Reveal log) after importing a stack and running Align once? If the adapter was found it will show `GPU warp available`; if not, the line `GPU: no adapter (…)` or `GPU: … found but no device (…)` says why, and that is what we need to see.
Tracked in spikerj/spikersoft-stacker#1014.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In SpikerSoft Stacker, the Performance Settings panel fails to detect or utilize the GPU correctly. Despite having a compatible GPU installed, the system reports “none (CPU only)” under the hardware overview. This prevents users from leveraging GPU acceleration for image processing and stacking tasks, resulting in slower performance.
Issue Description
When accessing the Settings → Performance tab, the hardware overview lists the CPU and memory correctly but shows GPU: none (CPU only) even when a GPU is available. The Warp Engine and GPU resident options remain inactive or default to Auto (0.0 GiB). This indicates that the GPU detection or initialization logic is not functioning as intended.
Environment
Preconditions
User has a GPU installed and drivers properly configured.
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
High
Suggested Fix
Thanks for the report and the screenshot. Two things are going on:
Stacker only looks for the GPU when the first alignment runs, so with no images imported (as in the screenshot) the overview says "none (CPU only)" on every machine, and "GPU resident 0.0 GiB" follows from that. The caption was wrong to say "what Stacker found when it started". That is fixed in spikerj/spikersoft-stacker#1015: the GPU is looked for at startup and the line says "looking…" until it has answered.
Whether your Ryzen's GPU is genuinely usable is a separate question. Could you attach
stacker.log(Help › Reveal log) after importing a stack and running Align once? If the adapter was found it will showGPU warp available; if not, the lineGPU: no adapter (…)orGPU: … found but no device (…)says why, and that is what we need to see.Tracked in spikerj/spikersoft-stacker#1014.