SM
Satisfactory Modding•4w ago
Fitz

Sticky Resource Markers

I have a reproduceable crash with Sticky Resource Markers. I can turn the mod on and it works just fine, but after completely closing the game I will get a crash to desktop when loading the save game. I have some resource-related mods that might be interacting badly (https://ficsit.app/mod/ResourceNodeRandomizer, https://ficsit.app/mod/CrashSiteBeacons https://ficsit.app/mod/DestructibleDeposits are possible culprits; I know a recent version of Crash Site Beacons mentioned Sticky Resource Markers in the changelog.) The crash goes away with SRM disabled, but if I enable SRM and disable CSB, it still crashes. SMM debug attached.
Crash Site Beacons - SMR
Places map markers at every crash site.
Destructible Deposits - SMR
Allows resource deposits to be destroyed with Nobelisk

SMMDebug-2025-02-07-...

5 Replies
FICSIT-Fred
FICSIT-Fred•4w ago
SMM Version: 3.0.3
SML Version: 3.9.1
Installed Mods: 94
Game: WindowsClient CL 385279 from steam
Path: `d:\SteamLibrary\steamapps\common\Satisfactory`
Command Line: cmd /C start  steam://rungameid/526870-NO_EOS_OVERLAY
SMM Version: 3.0.3
SML Version: 3.9.1
Installed Mods: 94
Game: WindowsClient CL 385279 from steam
Path: `d:\SteamLibrary\steamapps\common\Satisfactory`
Command Line: cmd /C start  steam://rungameid/526870-NO_EOS_OVERLAY
-# Responding to Key Details for SMMDebug-2025-02-07-01-57-18.zip triggered by @Fitz
Fitz
FitzOP•4w ago
One thing I should mention: if I disable SRM, load a save and then save it to a new name, enable SRM and load the new save it doesn't crash. So that feels like something going wonky in the reload with existing state vs init with no state code paths.
McCovican
McCovican•4w ago
SRM dev seems pretty responsive on GitHub, you might want to try posting this there: https://github.com/Epp-s-Satisfactory-Mods/StickyResourceMarkers/issues Looking at faulting module in the logs, it does indeed appear to be SRM itself that is failing. However, the lead-up to that suggests there's perhaps a little more to it. Archipelago was doing a lot in the milliseconds immediately prior, and then the RHI thread crashed, which leads directly into the SRM module falling over. I would make sure to post this log to the SRM GitHub. I think the interaction of Archipelago and SRM could be the issue? CSB doesn't appear to be doing anything around that time (and, I'll be honest, I haven't exactly been here for years, but I've also never seen a Digby mod implicated in a crash).
GitHub
Issues · Epp-s-Satisfactory-Mods/StickyResourceMarkers
Scanned resource node compass and map markers stick around! - Issues · Epp-s-Satisfactory-Mods/StickyResourceMarkers
McCovican
McCovican•4w ago
cc: @Jarno (the Archipelago guy) ― do you see anything in this that I might be missing?
Jarno
Jarno•4w ago
:adithinka: The stack trace does not look familar to anything iv seen with Archipelago AP was doing a lot of stuff right before the crash, seems it found that you unlocked some new things so i started to send out those checks to the server Archipelago behaviour seemed normal there, i should probably optimize that code and send some things grouped together tho

Did you find this page helpful?