No matter what I do, I can’t get the game Satisfactory to start under Linux in the Intel Core Ultra 5 125H. I suspect the Intel driver is too new and/or the Unreal 5 engine does something unexpected.
If anyone with a Core Ultra Framework 13 wants to help me troubleshoot, I’d be grateful!
have you tried forcing the other renderers with the command line flags?
you can force vulkan or dx11. try both, to see if one works.
Yes, I tried every combination of flags and Proton versions.
I was under the misconception that Ultra and 14th gen was the same thing. Which gen is Ultra?
so much for sensible naming schemes…
Even though this article seems to use 14th gen to refer to Meteor Lake as well.
Check the Mesa drivers and the kernel version. Simple, but it might be the problem.
Also, when you’ll play it, think about getting a private server. My friends and I got one from here for $6 and enjoy the game much more. And the 1.0 update rocks!
I already have the latest kernel and driver, given I am in EndeavorOS, which is rolling release.
private servers are awesome if you want to afk for resources but dont want to leave your game running (you can set the server to keep running even if nobody is online)
selfhosted one off an old gaming pc about a year back, played with one other friend.
You need something quantifiable as a starting point.
Description of what you mean by not working? No window? Flashes?
Logs?
Crash?
Stacktrace?
Turn on debug/verbose logging?
Run from terminal and check the logs?
What are other people saying in the Proton comments?
Is process running?
Do any other games work?
I have done all of that, no useful information came out of it. I’ve tried every combination of Proton flags and rendering API flags.
The game crashes after the splash screen on launch with DX11 and DX12, and hangs on the loading spinner with Vulkan.
Every other game that I tried works.
Which is why I’m asking if anyone with a Meteor Lake laptop has gotten it to work.
But I mean that is the first details in this thread. So there is no stacktrace or anything available? I dont have meteor lake to test.
There are too many combinations of flags for me to provide a FactoryGame.log of each of them, but here is one.
Other logs don’t look much different.
If you’d like me to try something specific, let me know.
[2024.09.21-17.34.57:256][ 0]LogWindows: Error: === Critical error: ===
[2024.09.21-17.34.57:256][ 0]LogWindows: Error:
[2024.09.21-17.34.57:256][ 0]LogWindows: Error: Fatal error!
[2024.09.21-17.34.57:256][ 0]LogWindows: Error:
[2024.09.21-17.34.57:256][ 0]LogWindows: Error:
Interesting. I don’t have any experience Unreal Engine 5 but it seems like usually the exception handler should have a stacktrace. Looks like you might be able to change the log level in the Engine.ini as per SML Logging :: Satisfactory Modding Documentation Not sure if this will give you anymore clues.
[Core.Log]
Global=Warning
LogSML=All
LogGame=Verbose
Is there a wine side log file?
Interesting version of the intel driver in the log 31.0.101.4576 which dates back to July 2023 which predates core ultra support.