"RimWorld isn’t the only game on Waylith. We’re working on something new! It may be a little while before we can share more details, but we couldn’t resist telling you."
f your PC is more than 10 years old, 1.7 may not run on it.
They could just support old CPU architectures. But they decided against it. That's sad. It wouldn't have been expensive at all. Surely the game would be slower on these architectures, but at least it would run.
Apparently, it actually has to do with Vulkan support, which makes this more of a GPU issue. Vulkan released in 2016, and while it was backported to many earlier GPUs at the time, this wasn't universally successful, hence the 10 year disclaimer. Still, building on Vulkan is a good move, so this seems entirely reasonable to me.
Even if all that wasn't the case though, "[older hardware support] wouldn't have been expensive at all" is a baseless claim.
That's interesting. If they're conservative with Vulkan feature requirements, I wouldn't be surprised to see it run on Linux with an older AMD GPU. A surprising number of old models are supported by the driver.
Probably gauging the extent of older archicetures among the players. To me it sounds like they didn't deem it worth the effort.
On a side note, I'd expect Steam to provide developers with a stat about what PC configs are the most common in that particular player base, like they do it with their surveys.
16 replies
"RimWorld isn’t the only game on Waylith. We’re working on something new! It may be a little while before we can share more details, but we couldn’t resist telling you."
Glad to hear that, I stopped playing the game since it just kept on getting slower as my colony progressed. I might have to start playing again.
Did you only play one colony?
Or did you play one endgame colony and that somehow slowed down everythign else? Because that one sounds like a bug.
I didn't have issues playing vanilla, the issues started to appears when I started using some modpacks. 😆
Amazing
1.7 fixes all the annoying linux issues people ,including me, were having. Just removinf Unity entirely was the solution after all
That's awesome!
Big!
Apart from someone pointing out it's Vulkan only:
How? Lots of mods I've seen just compile dotnet code, against Unity I am assuming. Did they ask Claude to rewrite Unity or..?
Also, savefiles being cross compatible is curious because most Unity games use the language feature of serializing random stuff to binary.
The crucial distinction is that they replaced the engine while preserving the game's managed-code interfaces and serialization format
They could just support old CPU architectures. But they decided against it. That's sad. It wouldn't have been expensive at all. Surely the game would be slower on these architectures, but at least it would run.
Apparently, it actually has to do with Vulkan support, which makes this more of a GPU issue. Vulkan released in 2016, and while it was backported to many earlier GPUs at the time, this wasn't universally successful, hence the 10 year disclaimer. Still, building on Vulkan is a good move, so this seems entirely reasonable to me.
Even if all that wasn't the case though, "[older hardware support] wouldn't have been expensive at all" is a baseless claim.
I see, that is reasonable. And then backporting to older GPUs would actually be expensive.
That's interesting. If they're conservative with Vulkan feature requirements, I wouldn't be surprised to see it run on Linux with an older AMD GPU. A surprising number of old models are supported by the driver.
The very next sentence is
Doesn't sound like they decided against it.
Probably gauging the extent of older archicetures among the players. To me it sounds like they didn't deem it worth the effort.
On a side note, I'd expect Steam to provide developers with a stat about what PC configs are the most common in that particular player base, like they do it with their surveys.