FusionFix

THIS MOD WILL KEEP GETTING UPDATES.

FusionFix

Keeps Fusion working. Fusion is the tool that lets several mods add props and

shop entries to the same game at once; when it does not run, or when a mod fights

it over the same list, those props spawn as error.

FusionFix does not contain or replace Fusion. It sits next to it and makes sure

it does its job.

What it does

Starts Fusion with the right folders. Fusion's own launcher predates the

current mod manager layout and can end up looking for your mods in a folder that

does not exist. When that happens it builds nothing, and every modded prop in

your game is an error. FusionFix hands it the real paths instead. If Fusion

already started itself correctly, FusionFix leaves it alone rather than starting

a second copy.

Rebuilds after you change your mod list. Install a new prop mod and Fusion

does not always notice, so the new props keep spawning as error however many

times you relaunch. FusionFix watches what is in your profile and forces a fresh

build when it changes.

Turns off mods that fight Fusion, and tells you which. Some mods ship their

own full copy of the game's prop list instead of the small add-on table Fusion

knows how to merge. Two mods claiming the same list means only one of them

loads. Either that mod's props are error, or everyone else's are. FusionFix

finds them, sets them aside, and puts a page on the main menu naming them:

THESE MODS WERE TURNED OFF BECAUSE THEY CONFLICT WITH FUSION

They replace a datatable Fusion also writes, so only one of them could load.

• devname-AnotherVotVnameJoke
• someone-othermod

Ask the author to publish their rows as a Fusion _list delta table.

[ BACK ]

Says what went wrong. When Fusion chokes on a mod its own log says nothing

useful about it. FusionFix reads it and names the pak on your next launch, in

FusionFix.log next to the mod.

Read this before installing

A mod it turns off is renamed, not deleted. Something_P.pak becomes

Something_P.pak.fusionfix-disabled and nothing is lost. It comes back on its

own the moment nothing is fighting it any more; the mod gets fixed, or the

other claimant leaves. If you would rather be told than have anything moved,

put conflict_action = notify in the config.

A mod that replaces the prop list wholesale cannot be rescued. Pulling its

rows back out of a full copy is not something anything outside Fusion can do.

Turning it off keeps the rest of your game working; the real fix is for that mod

to ship its rows the way Fusion expects. My own AAKO was one of these, and I fixed it. (thank god)

Fusion restarts the game once. After it rebuilds, Fusion relaunches VotV

itself. That is Fusion's behaviour, not a fault, and you will see it on the first

launch after changing your mod list.

Overlay-installed mods disappear on that restart. Fusion drops the overlay

folder when it relaunches, and nothing outside Fusion can stop it. FusionFix

says so in the log when your profile uses one.

Requires

• Fusion
• unreal_shimloader

Settings

All optional. Create shimloader/cfg/FusionFix.cfg only if you want one of

them.

enabled = 1 turn FusionFix off without uninstalling it

conflict_action = disable disable, notify, or ignore

language = en en or tr, for the menu page

launch = auto auto, always, or never

preview_notice = 0 draw the menu page once with fake names, to see it

FusionFix.log and FusionFix-report.txt sit next to the mod in your profile.

Those two are what to send if something looks wrong.

Linux and Steam Deck

The DLL override is dwmapi, not winhttp. that is the one shimloader

actually uses. Guides quoting winhttp are copying BepInEx instructions, and

following them leaves you with no mods loaded at all.

WINEDLLOVERRIDES="dwmapi=n,b" %command% --mod-dir "Z:/.../shimloader/mod" --pak-dir "Z:/.../shimloader/pak" --cfg-dir "Z:/.../shimloader/cfg"

Replace the path in every argument, not just the first. More in LINUX.md.

Credits

Voices of the Void is the work of mrdrnose. Fusion is NynrahGhost's,

and