sky_line/Slipstream

Fork 1

Startup check: warn when Slipstream runs on a Vulkan translation layer / software renderer / wrong GPU instead of the real graphics driver #950

New issue

Closed

opened 2026-10-23 00:24:18 +00:00 by sky_line · 2 comments

sky_line commented

2026-10-23 00:24:18 +00:00

Owner

Some users end up running Slipstream on a Vulkan device that isn't their real GPU driver, and see broken rendering (for example every texture white) with no explanation. Typical causes:

the GPU vendor's driver isn't installed (Windows' generic Microsoft display driver has no Vulkan), and something else answers instead: Microsoft's Vulkan-on-Direct3D 12 layer ("Dozen", from the OpenCL / OpenGL / Vulkan Compatibility Pack), a software renderer (lavapipe / llvmpipe, SwiftShader), or a layer installed with the Vulkan SDK;
on laptops, the integrated GPU is used instead of the dedicated one.

What to do

At startup, after picking the Vulkan device, check for these cases and show a clear, plain-language dialog:

Translation layer or software renderer (device name / driver ID: Dozen / "Microsoft Direct3D12", llvmpipe / lavapipe, SwiftShader, VK_PHYSICAL_DEVICE_TYPE_CPU): "Slipstream isn't using your graphics card's own driver. Install the driver from your graphics card maker: NVIDIA (nvidia.com/drivers), AMD (amd.com/support), Intel (intel.com/support)", naming the vendor of the real GPU when we can see it (e.g. from the OS adapter list).
A dedicated GPU exists but an integrated one was chosen (laptops): explain how to pick the high-performance GPU (Windows Settings > System > Display > Graphics).
Driver too old for features we need: say so, with the same links.

The dialog must allow continuing anyway ("Continue anyway" + "Don't show this again for this graphics setup"), in case we misjudge a setup. Log the decision and the device details either way.

Notes: no Vulkan SDK is needed to run Slipstream; the text should say so, since people find the SDK through search results and install it by mistake.

Some users end up running Slipstream on a Vulkan device that isn't their real GPU driver, and see broken rendering (for example every texture white) with no explanation. Typical causes: - the GPU vendor's driver isn't installed (Windows' generic Microsoft display driver has no Vulkan), and something else answers instead: Microsoft's Vulkan-on-Direct3D 12 layer ("Dozen", from the OpenCL / OpenGL / Vulkan Compatibility Pack), a software renderer (lavapipe / llvmpipe, SwiftShader), or a layer installed with the Vulkan SDK; - on laptops, the integrated GPU is used instead of the dedicated one. ## What to do At startup, after picking the Vulkan device, check for these cases and show a clear, plain-language dialog: - **Translation layer or software renderer** (device name / driver ID: Dozen / "Microsoft Direct3D12", llvmpipe / lavapipe, SwiftShader, `VK_PHYSICAL_DEVICE_TYPE_CPU`): "Slipstream isn't using your graphics card's own driver. Install the driver from your graphics card maker: NVIDIA (nvidia.com/drivers), AMD (amd.com/support), Intel (intel.com/support)", naming the vendor of the real GPU when we can see it (e.g. from the OS adapter list). - **A dedicated GPU exists but an integrated one was chosen** (laptops): explain how to pick the high-performance GPU (Windows Settings > System > Display > Graphics). - **Driver too old** for features we need: say so, with the same links. The dialog must **allow continuing anyway** ("Continue anyway" + "Don't show this again for this graphics setup"), in case we misjudge a setup. Log the decision and the device details either way. Notes: no Vulkan SDK is needed to run Slipstream; the text should say so, since people find the SDK through search results and install it by mistake.

sky_line added the

feature

label

2026-10-23 00:24:18 +00:00

sky_line added this to the Slipstream project

2026-10-23 00:24:18 +00:00

sky_line referenced this issue from a commit

2026-10-23 04:58:08 +00:00

#950 Startup driver check: warn when Slipstream runs on a translation layer, software renderer, or the wrong GPU

sky_line referenced this issue from a commit

2026-10-23 05:16:52 +00:00

#950 Startup driver check: warn when Slipstream runs on a translation layer, software renderer, or the wrong GPU

sky_line commented

2026-10-23 08:50:41 +00:00

Author

Owner

The startup check is in 1.4.0 Beta 7 (https://git.slipstreamviewer.org/sky_line/Slipstream/releases/tag/v1.4.0-beta.7). If you were the one seeing white textures: install Beta 7 and tell us what the startup check says (if anything), via Help > Report Bug.

The startup check is in **1.4.0 Beta 7** (https://git.slipstreamviewer.org/sky_line/Slipstream/releases/tag/v1.4.0-beta.7). If you were the one seeing white textures: install Beta 7 and tell us what the startup check says (if anything), via Help > Report Bug.

sky_line added the

status

testing

label

2026-10-23 08:50:41 +00:00

sky_line commented

2026-10-24 09:11:02 +00:00

Author

Owner

Shipped on main (a9eb343e10) — available in Jetstream builds.

Shipped on main (a9eb343e10) — available in Jetstream builds.

sky_line closed this issue

2026-10-24 09:11:02 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#950

No description provided.

Rows
Columns