v0.13.7 — a 32-bit game no longer gets a 64-bit ReShade written into it

Every 32-bit game was one reinstall away from breaking itself. Fixed. (#69)

@sempie27's GTA IV folder listing had the whole thing in it:

dxgi.dll            5592064   9-9-2026 11:36:38
dlss5-feed.addon64   297472   9-9-2026 11:36:41
dlss5-feed.addon32   176640   9-9-2026 11:41:11

A 64-bit ReShade and the 64-bit add-on, in a 32-bit game's folder, written by an Install five minutes before the 32-bit half. GTAIV.exe cannot load a 64-bit dxgi.dll — the loader simply does not — so ReShade never initialised, the Home key did nothing, and nothing anywhere logged a reason.

The cause was ours, and circular. The first install creates host64\, which holds dlss5-feed-host64.exe — a 64-bit PE. The folder scan walked into it, the "prefer 64-bit" rule ranked our own helper above the real 32-bit game exe, and the next Install on that folder treated the game as 64-bit.

• host64\ is skipped in the scan now, and the helper is never a candidate wherever it is found.
• Install replaces a proxy DLL whose bitness does not match the game whatever the version marker says, and removes a stray 64-bit add-on from a 32-bit folder.

So an install already broken this way repairs itself on the next Install — no deleting files by hand.

If you have a 32-bit game (GTA IV, Max Payne, Spore, Mafia II classic…) and the Home key stopped working after a reinstall, this was why. Update and run Install again.

SHA-256 of dlss5oneclick.exe: e927b50929e90c995537728c05e160104e70e3a58c95ee271facdd83d854fad6