Repository navigation
Conversation
f1ames0ff
force-pushed
the
feature/linux-support
branch
from
November 18, 2026 16:10
c6f6696 to
a38292e
Compare
added 11 commits
November 18, 2026 20:37
Restore the Unix platform layer removed by the Windows-only cleanup (pl_linux, sys_sdl_unix, net_bsd/net_udp, POSIX helpers) and merge the non-Windows CMake branches back into the current build: GCC flags, system Vulkan/SDL2/OpenAL, codec find_package paths, and the platform source lists. Port the Win32-only file handling in the pkz, material loader and editor to POSIX (opendir/readdir, rename, tmpfile, pkz handle dispatch), define _GNU_SOURCE for mimalloc's clock_gettime, and supply max/min for the texture manager. The renderer submodule gains the Xlib surface and the non-Windows FSR stub; the NVRHI max-binding-layouts patch is applied to the submodule by the Linux build script.
The host now builds the FSR 3.1 Vulkan provider from the vendored FidelityFX SDK before configuring the engine. build_win.ps1 builds the provider with AMD's SDK CMake and deployment copies the source-built DLL; build_linux.sh builds the Linux .so with the glslangValidator permutation generator. The renderer submodule pointer advances to the source-build commit. Linux verification: provider 3.1.4 dispatches 854x480 -> 1280x720, GPU upscale 0.21 ms and CPU upscale 0.220 ms, no TAAU fallback; CTest 6/6 passed. Windows source build is wired but requires a Windows build/run to be exercised.
A fresh Linux checkout otherwise builds with c_MaxBindingLayouts at the stock 8, so the RHI ray-tracing pass is unavailable and the game aborts with 'the frame cannot be drawn'. Mirror build_win.ps1: apply third_party/nvrhi-max-binding-layouts.patch for the build and reverse it on exit. Verified from a fresh clone of the pushed branch: the provider dispatches 854x480 -> 1280x720 and nvrhi is clean after the build.
The windows-2022 hosted image has no usable Vulkan SDK, and the vendor NSIS installer can hang in a headless session (Start-Process -Wait follows its child process tree). The job now downloads the headers and dxc assets directly and uses the repository's checked-in vulkan-1.lib, avoiding the installer entirely. This is required for the Windows FSR source-build gate to start.
Picks up renderer 25af42d: the two ffx-api headers use <FidelityFX/...> instead of the case-mismatched <FidelityFx/...>, and the tracked FidelityFx symlink is removed. That symlink was the cause of the Windows CI provider copy failure (Copy-Item could not resolve it). Patch 0006 covers external SDK checkouts.
Picks up renderer commit for the QR_DXC hint order and passes -DQR_DXC from build_win.ps1 when VULKAN_SDK is set. This unblocks the Windows CI GPU-test shader probes, which were picking the Windows SDK dxc without SPIR-V codegen.
The Debug qray_cluster_lists_tests and qray_gpu_context_tests exit with 0xc0000135 while Release passes. Print dumpbin /dependents and the deployed DLL list before the test step so the missing loader is identified.
The Debug qray_cluster_lists_tests and qray_gpu_context_tests import vulkan-1.dll because their objects contain unreferenced Vulkan entry points; the hosted image has no system loader. Fetch the Silk.NET Vulkan loader native package and put vulkan-1.dll into the minimal SDK's Bin, which is on PATH for ctest. Remove the temporary dependency diagnostics step.
Windows CI run 42023882552 passed Debug and Release: provider source build, five-export dumpbin check and CTest. The hosted runner has no Vulkan device, so the in-game Windows run remains the manual GPU gate.
A workflow_dispatch Release run now attaches quakeray.exe, the runtime DLLs and id1 assets to a pre-release, so a Windows build can be downloaded and tested under Proton on a Linux GPU box. Normal PR/push runs are unchanged.
f1ames0ff
force-pushed
the
feature/linux-support
branch
from
November 18, 2026 20:13
a38292e to
12bc91b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
amd_fidelityfx_vkprovider with a source build of the vendored FidelityFX SDK 1.1.4 (renderer submodule commita286fda1).build_linux.shbuilds the provider with a glslangValidator permutation generator, then configures and builds the engine. The provider is FSR3.1-only, exports the five FFX API entry points, carries thelibamd_fidelityfx_vk.soSONAME and is resolved through RUNPATH.build_win.ps1builds the provider through AMD's SDK CMake and bundledFidelityFX_SC.exe, then passesQR_FFX_VK_LIBRARY/QR_FFX_VK_RUNTIME_DLLto the renderer. Deployment, editor and GPU-test targets copy the source-built DLL.rgba16f; the opaque FSR3 context grows for 32-bitwchar_t; Vulkan scratch arrays are 16-byte aligned (fixes the GCC-O2movapscrash inCreateBackendContextVK); portableFFX_API_ENTRY; non-MSVC version literal.Linux verification
build/linux-cleanbuild from scratch: provider and 40 permutation headers built, CTest 6/6 passed.854x480 -> 1280x720;qperfdumpshows GPUupscale 0.21 msand CPUupscale avg 0.220 ms.640x360 -> 960x540.Windows verification
Windows CI run
42023882552passed both Debug and Release:build_win.ps1built the provider from the vendored FidelityFX sources, thedumpbincheck found all fiveffxCreateContext/ffxDestroyContext/ffxConfigure/ffxQuery/ffxDispatchexports inamd_fidelityfx_vk.dll, and CTest passed the non-GPU suite. The hosted runner has no Vulkan device, so an in-game Windows run remains the manual GPU gate.Full details:
docs/fsr-linux-source-build.mdandrenderer/Source/FidelityFX_SDK_1.1.4/README.md.Fresh-clone follow-up
A fresh clone of the pushed branch initially exposed one missing piece:
build_linux.shdid not apply the pinned NVRHI max-binding-layouts patch, so the RT pass was unavailable and the game aborted. The script now applies the patch for the build and reverses it on exit, exactly likebuild_win.ps1. Re-verified from the fresh clone: the source-built provider dispatches854x480 -> 1280x720, and the NVRHI submodule is clean after the build.