Embedded Files
News Archive
News Archive
Old News & resolved issues.
15.07.2025 - Harmony Error On MacOS [1.6]
(Solved)
15.07.2025 - Harmony Error On MacOS [1.6]
(Solved)
If you're playing RimWorld on MacOS and run into issues, make sure to check your log and see if Harmony itself is actually initializing. There's currently an issue with the latest Harmony version not loading properly for users on MacOS. Look out for the message; "Error while instantiating a mod of type HarmonyMod.HarmonyMain" to see if you're affected.
The solution (or just precaution when running the game on MacOS) is to use this version of Harmony instead. Optionally, running the game through Rosetta seems to bypass the issue as well. We recommend keeping an eye on the case even after switching to the alternative Harmony version, just in case something changes and the original Harmony gets updated with the fix included.
Thanks to Samboy (Ludeon) for bringing this to the attention of the community!
UPDATE: Issue has since been fixed and the latest Steam WS version of Harmony has those fixes now included as well. So make sure to swap back to the regular version again, to not run into different issues later when the mod gets further updates!
12.07.2025 - GPU-related Crashes In [1.6]
(Solved)
12.07.2025 - GPU-related Crashes In [1.6]
(Solved)
As Ludeon Devs confirmed earlier, there is currently a not fully understood issue with 1.6 on systems using a GeForce GTX 1060 6GB vRAM (EDIT: As multiple sources confirmed, the issue is affecting other GPUs as well!) causing errors like; "D3D11: Failed to create RenderTexture" or; "d3d11: failed to create 2D texture shader resource" - as a solution, affected users can use -disable-compute-shaders as a startup parameter.
Update:
15.07.2025 - As of July 12. Ludeon implemented a temporary fix for Steam users. Starting the game through Steam now automatically adds the startup parameter. All other users can still add it themselves using the regular ways (File-shortcut, setting it in RimPy/RimSort, etc.) Ludeon also announced to have a permanent/proper fix for it shortly.
Feb. 2025 - VE Framework ReachabilityCheck [1.5] (Solved)
Feb. 2025 - VE Framework ReachabilityCheck [1.5] (Solved)
A recent update to Vanilla Expanded Framework introduced issues with a list of other mods. The full list of affected mods and inner workings is still investigated, but here's what is known so far, including a partial fix for one case.
Mods confirmed to be affected are currently:
Other mods (CE, Hospitality, Allies Are Helpful - still unconfirmed though) which can be potentially affected by it tend to be related to melee combat at the very least but those above are confirmed. For users of Search & Destroy it is generally recommended to switch to is successor Tacticowl to begin with.
UPDATE!
18.3.2025 - the Steam version of Tacticowl has been updated with the fix. Make sure to force Steam to update properly!
4.4.2025 - there are reports that the mentioned Tacticowl update caused new issues, potentially in connection with another mod. It results in social fights between pawns leading to melee-attacks being applied comically fast. Author/Maintainer is aware and looking for a fix.
23.4.2025 - recent patch to Tacticowl should have fixed the remaining issue as well!
2.7.2025 - after months of observation, there don't seem to be many instances of this issue left. Most mods seems to have been fixed. If the error will show up with 1.6 again, we'll update this info of course, but all signs hint that it can be considered resolved and this post will now go archived.
As an easy tell, if you're affected by this specific issue, you can check your logs for errors like this. It usually is caused by an animal but doesn't seem to be restricted to it.
The telling parts are the errors around Pawn_StanceTracker and ReachabilityImmediate.
Page updated
Google Sites
Report abuse