Search results

Can confirm fixed in v2026.9.4.5400+. For existing vehicles, may need to remove the engines, the engine mounts, and re-add them back

Ran into the laggy timewarp on v2026.8.22.5348. Seems to occur when the ship trajectory "has no beginning". Attaching the screenshot and the save file, where it's occurring.

The following SPIRV-Cross commit should resolve this issue. As of the time of this post, it's not yet "rolled into" MoltenVK main branch, so would need to have a separate local branch and point to it when building your local MoltenVK build. https://github.com/KhronosGroup/SPIRV-Cross/pull/2669

It has happened to me as well.

Game Version [2026.8.22.5348] Operating System [Windows 10, macOS] What Happened When using an engine plate (4-pod, 3-pod, 2-pod) and side-attached tanks, be it directly attached or through a decoupler, one "booster" fires all engines, while the others only fire 1 engine. What Was Expected...

Completely understand on Mac OS being not supported currently. My question was more along the lines if the 9th layout set usage was necessary. If it is, the change would need to be made elsewhere (on the MoltenVK / SPIRV-Cross side). I'm looking into making those modifications in the background...

Game Version 2026.8.3.5117 Operating System macOS What Happened The new modification to RaymarchCloud.comp is using layout set 8 (9th, starting with 0). SPIRV-Cross, used by MoltenVK, currently has a hard limit of 8 for kMaxArgumentBuffer, due to the limitation of Tier1 Metal chips. Tier2, if...

I noticed the same issue with the previously-made vehicles. A newly created vehicle seems to have dV and staging correct.

Game Version v2026.7.9.5018 Operating System macOS What Happened With textures and shadows stored together under globalTextures, SPIRV-Cross incorrectly identifies textures2d as depth2d, causing 3 out of 4 values in vec4 to be lost. This results in incorrect clouds, planet colors, and possible...

Try to manually update to the latest Vulkan libraries released this/last week (v1.4.1). You would most likely need to "allow" the new library through the settings, once you replace the moltenVk dylib file. Play with MoltenVK environment variables, as some might help run the game better. Disable...