Files
craft-launcher/apps
FractalEncryptandDevin aec1562e4a fix(windows): start on OpenGL when Direct3D 12 can't create the UI pipeline (#1081)
The launcher built its window once, on wgpu's first-choice backend, and exited
with code 1 when that backend couldn't create `egui_pipeline`. Nothing appeared
on screen, so it looked like the launcher had never started at all: on
Direct3D 12 some drivers refuse that pipeline (#111, #1081), and a 32-bit build
refuses it on every Direct3D 12 adapter even where the 64-bit build of the same
commit draws fine.

`StartupBackends` now tries the fallback backend after a start that couldn't
create its renderer. The fallback is OpenGL everywhere it exists (Metal is
macOS's only backend, so there is nothing to fall back to there). `WGPU_BACKEND`
still names the one backend a start uses, and a window that failed for another
reason — no event loop, no display — is not retried, so its error isn't buried.

Reproduced with the shipped `windows-x86` 0.14.0 binary and with a local i686
build: `egui_pipeline` fails in `ID3D12Device2::CreatePipelineState` with
E_INVALIDARG (0x80070057) on the RTX 4080 SUPER and on the AMD integrated GPU,
in both debug and release, while the x86_64 build of the same commit starts on
Direct3D 12. With this change the 32-bit build logs the failure and opens its
window on OpenGL. The 32-bit Direct3D 12 failure itself is still open: it is
below this repository, in wgpu's Direct3D 12 pipeline creation.

Part of #1081, not all of it: the issue also asks for a readable error naming
the backend when every backend fails. That needs a new user-facing string and
its row in every `complete_menus` catalog, so it stays open rather than closing
here.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
2026-11-03 10:07:42 -05:00
..