Spider-Man Remastered mods stopped working? Fixing the toc, updates and conflicts

Suit mods for Marvel's Spider-Man Remastered work by rewriting the game's packed asset archives, so the most common failures are not about the mods themselves but about what happened to those archives. This guide is for the moment a working setup stops working: after a Steam update, after mixing two managers, or after a mod that was fine last week starts crashing the game on launch.

If you have never installed a mod for this game yet, start with the SMPC Tool install guide and come back here when something breaks.

First, understand what the tool actually changes

Insomniac's engine reads its content through a table-of-contents file, usually just called the toc, inside the asset_archive folder of your install. The SMPC Modding Tool and Overstrike both work the same way at a high level: they keep the original archives, add the modded assets alongside them, and rewrite the toc so the game loads the replacement instead of the original.

That single file is the reason almost every problem below exists. If the toc is vanilla, no mods load. If the toc points at assets that no longer match the current game build, the game crashes. If two tools each think they own the toc, they fight.

Mods vanished after a game update

This is the one everyone hits. Steam pushed a patch, the game launched fine, and every suit is back to stock.

An update replaces asset_archive/toc with the vanilla version for the new build. Your mod files are still on disk, but nothing references them any more.

Fix:

1. Open the tool you normally use (SMPC Tool or Overstrike). Do not open both.
2. Let it re-scan the game folder. It will detect the fresh toc.
3. Your mod list should still be there. Tick the ones you want and run install again.

If the tool complains that it cannot find a backup, that is expected right after an update: the "original" is now the new vanilla file, and the tool will make a fresh backup when you install.

The game crashes on the splash screen after an update

Same cause, worse symptom. Some mods bundle assets that reference internal structures that changed in the new build. When the game tries to load them it exits immediately, often with no error dialog.

Work through it in this order:

1. Restore vanilla first. In Steam, right-click the game, open Properties, then Installed Files, and run Verify integrity of game files. That puts the original toc back. Launch once to confirm the game runs clean.
2. Reinstall mods in small batches. Enable a few, install, launch. Repeat until it crashes, and you have found the mod that needs an author update.
3. Check the mod's Nexus page. After a major patch the comments section fills up quickly with "works" or "broken on the new version" reports, and authors usually ship a fix within days.

Keep the mod that breaks disabled rather than deleting it. Once the author updates, you only have to re-enable it.

Two managers, one game folder

The SMPC Tool, Overstrike, and Vortex (which drives the SMPC Tool for you) all write the same toc. Using two at once produces confusing results: mods installed through one disappear when the other runs, or the game loads half of each list.

Pick one:

• Stick with the SMPC Tool if you like a simple checklist and mostly install suits.
• Use Overstrike if you want an open-source tool that also handles Miles Morales and the other Insomniac ports with the same interface.
• Use Vortex only if you already manage other games there and want everything in one place.

If you have already mixed them, verify game files in Steam to get a clean slate, then reinstall your list through the one tool you are keeping.

Two suits fighting over the same slot

Many suit mods replace an existing in-game suit rather than adding a new one. Install two mods that target the same suit and the one installed last wins, while the other silently does nothing.

• Read each mod's description for which suit it replaces. Authors usually state it in the first line.
• Prefer mods that ship a .suit file for a new slot when you want to keep the original.
• If you need two replacements for the same base suit, you will have to choose. There is no load-order trick that shows both.

Textures look wrong or half-loaded

A suit that shows up with flat grey panels or missing detail is normally an install that finished with an error you did not see, or an archive extracted with a broken rar tool.

1. Re-extract the download with 7-Zip and confirm the .smpcmod file is intact (it should be several megabytes, not a few kilobytes).
2. Uninstall the mod, install again, and watch the tool's log for a failed write.
3. Delete the game's shader cache if the game offers to rebuild it, then launch again.

Common gotchas

• Do not run the tool while the game is open. The toc is locked and the install silently fails.
• Cloud saves are unaffected by mods, but keep a copy of your save folder anyway before large mod changes.
• Photo mode captures show the modded suit, but trophies and achievements are unaffected: this is a single-player game with no anti-cheat.
• A mod built for Miles Morales will not install into Remastered even though the tools support both games. Check which game the Nexus page lists.
• If Steam re-downloads several gigabytes after you verify files, that is normal: it is restoring archives the tool replaced.

Where to go next

Browse what's on OpenMods for Spider-Man Remastered, or go back to the install walkthrough if you are rebuilding from a clean folder.