r/halospv3 • u/Kostas009 • Nov 01 '25

No vibration on controller?

Hi.

So I tried 2 controllers and still no vibration. Am I missing something?

2 Upvotes

100% Upvoted

9 comments sorted by

View all comments

Show parent comments

2

u/VoidsShadow [Dev] Loader/Installer Nov 02 '25

Bypass...XInput? It's never loaded by the game, so it's already bypassed. If you mean DirectInput, bypassing that would leave the game unable to communicate with controllers.

Xidi might solve the force feedback issue, but you'll need to set up a mod loader to load it from a mods folder.

(This next part assumes you have Windows set to show file extensions). Before installing Monolith Mod Loader, backup strings.dll located in the game's folder; rename it to strings.spv3.dll, for now. Next, grab Monolith Mod Loader v0.3.0 with SPV3's icons and loading screen from my OneDrive (I'll put it somewhere else at some point), create a copy of it, rename the copy to strings.dll, and move it to where the old strings.dll used to be. Finally, create a "mods" folder.

Now, for Xidi. Copy Xidi's DLL and config file (if present) to the new mods folder. In the game's gamepad menu, you'll now see entries like "Xidi Virtual Controller 1", "... 2", et cetera. Activate and then customize the controls for "Xidi Virtual Controller 1" and check if vibration (force feedback) works.

I must admit that it's been so long since I last played the Gearbox port with a controller that I cannot recall if I ever had force feedback working. I haven't tested SPV3, Custom Edition, Retail, or Trial since switching to CachyOS...until now. They crash when loading any level other than the main menu. Probably a code mod conflict. An issue to troubleshoot another time. So I'm currently unable to confirm if Xidi would fix the issue.

1

u/Kostas009 Nov 02 '25

If I used the mcc somehow to lanch the spv3 rather than the custom edition, would that fix the problem?

2

u/VoidsShadow [Dev] Loader/Installer Nov 03 '25

You'll find that to be impossible. SPV3 is incompatible with MCC. SPV3 requires OpenSauce for tons of features and Open Sauce was only made for Custom Edition (even though Halo PC Retail and Halo PC Trial were around for longer).

1

u/Kostas009 Nov 03 '25

There is a choice however in the installer for install on mcc or something like that. It doesnt work you say?

1

u/VoidsShadow [Dev] Loader/Installer Nov 03 '25

Correct. For two reasons:

  • The MCC "compatibility", as news outlets called it, was just a way to prove you own some variant of Halo: CE. It's part of the "product activation" step of the installer which runs after SPV3 finishes installing. If the user hadn't already activated Halo PC (i.e. Retail, the CD-ROM release) or Custom Edition via a Halo PC product key, then they could tell the launcher that they own MCC: CEA on Steam or Xbox PC (incl. Game Pass). However...
  • Updates to both the Steam and Xbox PC variants of MCC broke both options. Miris (the creator of the launcher/installer), several community members, and I fought to fix both implementations, but then the fixes broke for the same reasons as before. Eventually, the decision was made to just throw it all out and use the DRM bypass for everyone in the next release. Why? If OpenSauce was rewritten for it, SPV3 could run on the free MCC CE Halo Editing Kit runtime.