You are not logged in.
Pages: 1
// update: as of May 22nd: tested on windows - vulkan craps out, too - so it's a fault of the current unreal engine update - has to be fixed by epic and passed along from css
so, recently Satisfactory 1.2 dropped (at least the preview) and it seems the current UnrealEngine has issues with wine - no matter if 9, 10 or 11, no matter if wine(-staging), proton or proton-ge
when I try to launch satisfactory i fails due to some vulkan error
I thought: "well, ok, let's downgrade mesa then" - did so - now steam complains about missing dependencies: llvm which depends on libc++
now, i think i maybe could downgrade llvm and clang and libc++ from 22 to 21 - but I guess this will break a whole lot more that depends on current version 22
so - is there an easy way to downgrade mesa to say somewhere end of last year (november/december) safely along with its dependencies like llvm and libc++ without downgrading the whole system? or would it be more wise to just bite the bullet and completely downgrade the entire system to say 31st december?
I'm also not sure if this will even help and if it really is mesa or something related - but i doubt it's the game (if at all it's the new engine update)
I'm a bit puzzled how to go from here
it's not important - i finished the game last year with all achievements - i just wanted to give the new update a try
fun fact: when forcing dx11 or dx12 it works - so at least the dxvk translation works without issues - just the native vulkan render pipeline fails
yes, i can play on dx12 - but due to the additional translation I get quite a severe performance impact (have to reduce quality to mid to get about 60fps - while with native vulkan i get 160+ with high settings)
also the older current 1.1 works with up-to-date mesa - which strengthens my suspicions it's the UE update - maybe something within it is broken so downgrading mesa won't help anyway?
Last edited by cryptearth (2026-05-22 21:29:03)
Offline
Manually downgrading is like mesa => llvm => clang => libc++ => half your system ![]()
so can "steam" from Flatpak be a option?
or else, isolated "container" w/ Distrobox or Conty...
"Nothing matters" -a Nihilist
"Why bother thinking what matters?" -me
Offline
Do you even know it's a regression in that mesa version?
when I try to launch satisfactory i fails due to some vulkan error
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post the error and
vulkaninfo --summaryOffline
wine c++ runtime library
assertation failed
program: S:\common\Satisfactory\Engine\Binaries\Win64\FactoryGameSteam-Win64-Shipping.exe
File: ../src-wine/dlls/winevulkan/loader_thunks.c
line: 3151
expression "!status && "vkCreateComputePipelines""Fatal error!
Unhandled Exception: 0x80000003
0x00006ffffff40e74 ntdll.dll!DbgBreakPoint() []
0x00006fffff9486f6 ucrtbase.dll!UnknownFunction []
0x00006fffff96de83 ucrtbase.dll!UnknownFunction []
0x00006fffff9525ec ucrtbase.dll!UnknownFunction []
0x00006ffffc81fc96 winevulkan.dll!UnknownFunction []
0x00006ffff096bb07 FactoryGameSteam-VulkanRHI-Win64-Shipping.dll!FVulkanPipelineStateCacheManager::CreateComputePipelineFromShader() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\VulkanRHI\Private\VulkanPipeline.cpp:2345]
0x00006ffff0972f4b FactoryGameSteam-VulkanRHI-Win64-Shipping.dll!FVulkanPipelineStateCacheManager::GetOrCreateComputePipeline() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\VulkanRHI\Private\VulkanPipeline.cpp:2275]
0x00006ffff097a829 FactoryGameSteam-VulkanRHI-Win64-Shipping.dll!FVulkanDynamicRHI::RHICreateComputePipelineState() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\VulkanRHI\Private\VulkanPipeline.cpp:2254]
0x00006ffff6ebfbb7 FactoryGameSteam-RHI-Win64-Shipping.dll!FCompilePipelineStateTask::CompilePSO() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\RHI\Private\PipelineStateCache.cpp:3085]
0x00006ffff6ec607d FactoryGameSteam-RHI-Win64-Shipping.dll!FPSOPrecacheAsyncTask::DoTaskWork() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\RHI\Private\PipelineStateCache.cpp:643]
0x00006ffff6ec6115 FactoryGameSteam-RHI-Win64-Shipping.dll!FAsyncTaskBase::DoWork() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\Core\Public\Async\AsyncWork.h:289]
0x00006ffff6ec609e FactoryGameSteam-RHI-Win64-Shipping.dll!FAsyncTaskBase::DoThreadedWork() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\Core\Public\Async\AsyncWork.h:313]
0x00006ffffa163408 FactoryGameSteam-Core-Win64-Shipping.dll!FQueuedThread::Run() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\Core\Private\HAL\ThreadingBase.cpp:1459]
0x00006ffffa3a3cd4 FactoryGameSteam-Core-Win64-Shipping.dll!FRunnableThreadWin::Run() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:159]
0x00006ffffa3a39e9 FactoryGameSteam-Core-Win64-Shipping.dll!FRunnableThreadWin::GuardedRun() [D:\HordeAgent\Sandbox\Rel\Sync\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:79]
0x00006fffffec1609 kernel32.dll!UnknownFunction []
Crash in runnable thread PSOPrecompilePool #2it's the same message no matter the wine/proton/proton-ge or kernel version
[main@main ~]$ vulkaninfo --summary
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.350
Instance Extensions: count = 26
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_layer_settings : extension revision 2
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_maintenance1 : extension revision 1
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 12
---------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MANGOHUD_overlay_x86 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MANGOHUD_overlay_x86_64 Vulkan Hud Overlay 1.3.0 version 1
VK_LAYER_MESA_anti_lag Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_MESA_screenshot Mesa Screenshot layer 1.4.303 version 1
VK_LAYER_MESA_vram_report_limit Limit reported VRAM 1.4.303 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
Devices:
========
GPU0:
apiVersion = 1.4.335
driverVersion = 26.0.6
vendorID = 0x1002
deviceID = 0x747e
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 7700 XT (RADV NAVI32)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 26.0.6-arch1.1
conformanceVersion = 1.4.0.0
deviceUUID = 00000000-2d00-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
[main@main ~]$vkcube/vkgears and even llama.cpp work no problem - i can even passthrough vulkan via venus to a vm - so it's not the vulkan stack itself
downgrading mesa is just a thought - but it's likely it's just the games engine version (vulkan is experimental in UE5 since it was added - and according to a game dev stream they don't touch the render stuff at all but just take what unreal provides - so if anything a bug report has to be filed directly to unreal)
using dxvk and run dx11 or dx12 works - downgrade to satisfactory 1.1 works with vulkan
i thought it to be easier to "roll back arch to end of last year" - yea, no - not without either breaking a lot of stuff or rolling back the entire system
Offline
https://github.com/ValveSoftware/Proton … 4306132789
https://bbs.archlinux.org/viewtopic.php?id=312689
How the turn tabled ![]()
But that was on mesa 26.0.5-1 and you're intending to downgrade to some 25 version? Is this a confirmed regression (ie. "used to work") on your side?
The latest comment is from some nvidia user…
Offline
well - looks like unreal engine updates and its experimental vulkan rendering comes up again every once in a while
downgrading mesa was my best first shot as that was what was updated since i last played the game before the 1.2 patch - but didn't expected it to be that complicated - hence, no, not confirmed regression as unable to test
anyway - as anything vulkan related does work except for satisfactory (i successfully tested other games both linux native as windows via proton) I guess it's an issue with the new engine update is just not yet supported by wine/proton and that it will likely get fixed with some upcomming wine11 based proton(-ge) and I either have just to wait or bite the bullet and use dx12 for the time
marking this topic as abandoned as too complicated for expected negative result
Offline
For The Record:
If in future you need a different mesa version then the one in repos
- downgrade using package cache or arch linux archive will work if both versions use the same llvm version
- In case they don't , building it yourself is the best solution.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
as a last effort i tested windows - and boi ... even on windows the current 1.2 experimental build is complete broken when using vulkan - it's even worse than back when i used amdvlk / amd-pro instead of mesa radv
guess that confirms it's not proton/wine nor mesa nor anything in the stack other then the new unreal engine update - guess I either have to play in DX12 and just take the performance hit from the dx-to-vk translation ... or wait until unreal gets a fix out and the game devs patch the game
changing to solved as this is clearly the games' engine fault
Offline
Pages: 1