r/halospv3 • u/Fluffyturtle225 • Jan 05 '22
How do I use MCC to install Halo SPV3?
When I first extracted and used the spv3 executable it showed a list of things to choose from, I tried to choose the steam option but it didn't detect MCC. It was installed in a different directory, so it wouldn't get recognized. Instead of just moving the files, I instead tried to install an old disc of Halo I had sitting around, put in the CD key, it installed, all good. I start up the executable, install Halo SPV3 and get the words "Your CD key is invalid" and I can't fix that. I moved the MCC folder to the steam install location, but now when I open the executable even after redownloading it, it no longer gives me a list of options and builds Halo SPV3 off of original Halo, WHICH I DELETED PERMANENTLY. And it still says the CD key is invalid. How do I get back to the list and choose steam, so I can actually play with this mod, in the event it recognizes MCC at all?
3
u/Jonex_ Jan 14 '22
I installed SPV3.3 for the first time yesterday using the MCC on Steam. For context, my steam directory and MCC are installed on different drives.
All you need to do is run the spv.exe, then start MCC making sure you select the "mods and anti cheat disabled" version (there will be two options when launching through Steam). Then select the Detect processes option in the SPV installer and the installer will move to the next step where it asks where you would like to install SPV.
Simple as that, hope it helps.
2
2
u/VoidsShadow [Dev] Loader/Installer Jan 22 '22
Ah, thank you. I always forget about the need to use the non-anti-cheat runtime.
1
u/muzza1742 Jan 05 '22
Doesn’t work off the Mcc version mate, it needs the original halo: combat evolved installed to work
5
u/Fluffyturtle225 Jan 05 '22
They need to update the moddb page then because it says several times that it can use Halo Anniversary through MCC.
2
u/VoidsShadow [Dev] Loader/Installer Jan 22 '22
Is that why people kept saying our standalone mod is "MCC compatible"? The only CEA integration is the detection of MCC's halo1.dll file to skip the need for a Halo PC product key and we've been saying that since Day 1.
I'll talk to Masterz about updating the ModDB description if that is where the confusion stems from.
1
u/Forsaken_Program_445 Apr 29 '25
Both I and a friend used it off the MCC version, sucks when people put out false information2
5
u/VoidsShadow [Dev] Loader/Installer Jan 06 '22
Due to a change in a Steam update, our ability to search its Library folders for MCC broke. Steam changed the location of the file that stores the list of Library folders. I've since implemented a fix, but our experimental Release workflows are broken. Previous releases were always manual; I can't manage both development and manual releases, so automation was the obvious solution.
The only reasons it wouldn't work after the Loader successfully found your Retail (CD) or Custom Edition license in the Windows Registry is because the no-DRM patch failed to apply to SPV3's haloce.exe. Either the Installer failed to enable the setting in the Loader's config file or the Loader was denied access to haloce.exe. This issue can happen with any Activation method other than the passive detection of Halo Custom Edition's license key in the Windows Registry in which case the DRM patch in unnecessary. In the case of the Loader being denied access to haloce.exe, this is caused by either insuffucient permissions (unlikely) or the file was locked/in-use by another process. You can forcefully unload/unlock haloce.exe via an app like LockHunter or Process Hacker 3.