Starfield’s Creations platform made mod installation easier but did not remove load-order or archive-invalidation failures. The game can start cleanly and still ignore every custom asset.
Fixing Creations Load Order and StarfieldCustom.ini
Verified field fixThe shortest safe order for this issue:
- Update the mod manager and verify each Creation supports the current game build.
- Back up StarfieldCustom.ini before adding archive invalidation or plugin lines.
- Test with only one content creation enabled, then add groups of two.
Archive invalidation is still a prerequisite
Loose-file mods need the archive settings in StarfieldCustom.ini, but a malformed INI can crash the game before the menu. Create the file from a known-good example, back it up, and keep only the lines the mod author documents.
[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=
[General]
; Keep only documented settings here.
; A malformed entry can prevent the game from starting. Creations still have dependencies
A creation can depend on another creation or a game update. Read the requirement list and load shared libraries first. If the Creations menu reports a conflict, remove the newer addition rather than letting the game shuffle a broken set.
Field notes before you change the build
A Starfield mod list is a dependency graph, not a popularity ranking. Confirm that the loader and shared frameworks match the current game build before sorting content mods. A missing dependency can look exactly like a bad load order.
Back up the active profile and a save before disabling anything. If the game starts cleanly with frameworks only, add content back in small batches and test the same menu, dialogue, or world load after each one.
- Do not mix two mod-manager deployments over the same game folder.
- Do not delete a content mod without testing a copied save first.
- Do not paste a load order from a different game build and expect it to be stable.
Check it before you keep it
Launch to the title screen before loading a modded save
0 / 5 completeKeep a known-good profile
Export the working mod list before the next patch. A short, documented stack is easier to repair than a folder full of files whose versions nobody recorded.
The line to keep
Start with the title screen, then the save. A clean INI and a short dependency chain are worth more than a full modlist.
Did this fix work on Patch 1.15.222 — Creations and stability?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 1.15.222 — Creations and stability. Votes are local-only telemetry.
Starfield: bench questions
2 answersDo I need StarfieldCustom.ini for Creations?
Why does my custom asset show as missing?
Modding & Load Order
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Starfield: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Starfield on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Creation Engine 2.
Starfield: Shader Stutter, Frame Pacing & Creation Engine 2 Config Tuning
A measured stutter-hunting routine for Starfield: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Creation Engine 2 settings file to edit.
Starfield: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Starfield without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.