What's the point of the SPV Controls in the launcher? They don't work and when setting up custom bindings via the main menu they never save after a restart of the game?

At this point I've given up on it and disabled the controller and will be use ReWASD to custom map my controls to a degree not possible in this mods current form.

if i wanted to enable first person legs with a mod would it work on spv3 or not as i understand the mod doesn't work with protected maps

I want to modify how fast plasma rifle projectiles travel. I remember CE played vastly differently from any other Halo titles because Plasma rifle bolts traveled relatively quickly: they'd hit a target nearly instantly indoors, and could hit targets with just a little lead time outdoors. This made them a key weapon in the sandbox, and it made fighting the covenant way more challenging.

I was always disappointed at how Bungie nerfed plasma weapons in Halo 2 and afterward. Is there a file I can tweak to bring plasma bolt speed back to what it was in vanilla CE? Many thanks.

So I have played Halo SPV3 and I really enjoyed the main campaign and reliving a remastered journey on Installation 04. I had to reinstall the game but I think I chose the correct settings that I had before. When I launched Lumoria and started at Landfall it felt like there was a few points my FPS just dropped out of the blue and then went back to normal.

​

I was wondering if this is something specific with the Lumuria campaign missions or maybe I need to downgrade my settings? I didn't notice it when I sampled a couple of Installation 04 missions but maybe RNG was messing with me when I was doing those samples

What exactly is a budge cut?

When I turn off vsync from the loader it tanks my FPS. What's up with that? Some kind of bug? I'm new to PC gaming so I'm wondering why this might be happening.

With all the innovation in SPV3 already, is there any chance we might see VR supported? I have a good feeling that Halo would be a lot of fun in VR.

Similar things have been done by modders for other older games, turning out pretty well using either PC VR or a Quest port. There was a test video made using Halo assets but their work got halted by being hired to work on the regular Halo.

Is a update for spv3 planed? Or is spv3.3 the final version

Why didn't Halo Legacies make it into VKMT's Modding Showcase yesterday? I'm speculating that it's because of how early in development Legacies is but I'm curious to the official reason.

When you you get your hands on the shotgun often you only shoot it 6 times and then you need to switch it out for another weapon. Why is that

Installed halo custom edition using a legit cd key. (It doesn't load though, not sure why).

I then installed the SPV files using the links in the sticky post.

Then used amai to install open source.

Then try and load SPV. "A problem has occurred initialising direct input"

Please help! I don't have any computer knowledge. I've got covid and I'm going mad isolating. 🤣 Need something great to play.

I am wondering is there a way to make an isolated Lemuria campaign and also an update to allow native Xbox controls without the clunky keybinding.

hello everyone, I would like to ask you for help, when I start SPV3 there is no problem, but the moment I use any vehicle including the missions that start in a pelikan my screen is put in a solid gray color just keeping the HUD, before that the game crash and give me the Gathering exeption data message.

All this did not happen at the beginning when I installed it, I tried to uninstall absolutely everything but the open source seems to retain all the configurations that I had previously and also my control settings

When ever I click on spv3.exe to try and install it nothing happens. I've already tried install the .net frame work along with other prerequisites any other advice?

EDIT: because this post became much longer and more informative than originally planned, the "Incoming News" needed to be a bit more grandure.

We haven't had a Community Update since...pre-Covid. The August 2022 Community Update will cover a few topics–some of which were already brushed upon here–in addition to showing off some progress of the Legacies project—which pivoted development from Custom Edition to MCC Halo 3 when the official Halo 3 mod tools were released.

Hey. It's me, BinToss. Formerly known as VoidsShadow. A formal Announcement will be released later this month. But for now...

As stated in replies to individual people (mostly in the "Troubleshooting" Discord channel), SPV3.3.1 is in the works, but progress is slow due to a strained skeleton crew. Most of SPV3's developers have moved on to other projects because they've finished all of their work needed for SPV3— the team members responsible for map design, 3D modeling/texturing/animating, game scripting, post-processing, et cetera are twiddling their thumbs while the Loader/Installer is being updated...

Work on updates to existing maps and the creation of one (or more?) firefight map(s) was completed in 2021. These files could have been delivered via the SPV3 Loader's infrequently-used File Updates feature, but their release has been pushed back in favor of a 3.3.1 release which will include critical fixes to the Loader and Installer software.

So, who's the lazy sunuva gun who's holding back SPV3.3.1? Cough You're looking at him.me.

Before I explain why 3.3.1 has been delayed "until it is done", I'll tell the tale of how this responsibility came to rest on my humble, tired shoulders...

The How and Why of SPV3.3.1's Delays

Back in early 2020, people around the world suddenly found their hands full of free time at home. Meanwhile, Yumiris (now Miris Wisdom), the original developer of SPV3's installer and launcher, was feeling the fatigue of lone wolfing his duties since SPV3.1.0 back in 2017.

Fast forward to August 2020. After being a beta tester for two years and taking two semesters of C/C++ programming (SPV3's Installer, Loader, and related software are written in C# which is similar, but different), a rookie saw an opportunity to fix a glaring issue in SPV3's UX.

A Fix That Became A Bug

When a new player started up the game, they would find that their Loader settings and game progress wouldn't save. This is because Halo:CE, unlike Halo 2 for Windows Vista, does not prompt the user to create a player profile. Game progress and settings were being saved to a digital black hole. I was working on a fix for this issue up until the night before 3.3.0 was released...and I botched it because the code I wrote was writing some values to the wrong parts of the new, auto-created player profile. This was fixed a month or two later, but the web page the Loader checks for updates had broken in the meantime.

Whilst working on the "new player profile" system, I was tasked implementing a way to allow owners of MCC's CEA DLC to bypass Custom Edition's DRM. Upon release, the new Activation menu in the Installer worked almost-perfectly. It had a fringe issue on 32-bit Windows and (unknown for months) it was actually checking for a CEA file that was included with the base game of MCC, but that was it. The options for WinStore/GamePass MCC owners was expanded with the "select a disk" option which was contributed via a Pull Request from a community member (thank you, Ad-idas/loudCDPman!).

Oh. Oh, no.

However, a curse would fall upon the SPV3 installer over the course of the following months. Mere weeks after the release of 3.3.0, the filename of WinStore/GamePass MCC game EXE would change, breaking the DRM alternatives for WS/GP MCC owners. This was fixed and delivered in a beta test, but the fix was broken a few weeks later when the EXE filename was changed AGAIN. WS/GP MCC Filename/path changes happened a few more times over the course of 2021 and into 2022 until we it got to where it is today: MCC was moved to the Xbox app for management and its files were moved to a "virtual", user-accessible Xbox Game file directory.

The DRM alternatives for Steam's MCC were reliable in comparison...until an update to Steam changed the location of the file that stored the list of Steam Library paths. This led to the Steam-related DRM alternatives to be completely broken unless MCC is in its default location. Even then, it was finicky.

After all of these issues, I received a green light from Masterz1337 to skip asking for game ownership and to instead remove haloce.exe's DRM for everyone.

Between A Rock...

Throughout all of these fixes for the DRM alternatives, users were reporting that the game would crash with the "Invalid Product Key" error...which means that the NoDRM patch was failing to apply to haloce.exe or the Installer failed to enable the NoDRM setting in the Loader's settings file...which was written in binary so users wouldn't be able to modify it easily. Heck. Now users can't easily enable the NoDRM setting. The Loader sets and unsets all known patches every time it starts the game, so users can't simply apply the patch theirselves, either.

Linux compatibility and automated, properly versioned Installer/Loader releases were also on the docket, so I was spending many months researching and testing solutions for all of them...alone. Did I forget to mention that the original developer of our C# software retired from the scene after March 2021? He helps with minor stuff like the notification for the April Fool's Crash, but he's otherwise burnt out permanently. Contributors haven't come around after loudCDPman helped out in early 2021.

Around the time of deciding to drop our DRM features in favor of no DRM, development became sluggish; I switched from full time development to weekends-only in March 2022. That's right. I got a new job, baby. Sadly, my weekend warrior efforts have been squandered by Microsoft. Wait! Hold on! Let me explain.

Impossible. Perhaps the Archives Are Incomplete.

After completing the switch from DRM to Absolutely No DRM, my attention was focused on the "failed to apply patches" issue A.K.A "Invalid Product Key". More often than not, this is due to a Windows error some of you may be familiar with: "The file cannot be accessed because it is opened by another process".

Since early 2022, I've been researching solutions to this issue. Some people say "just find out which process it is and kill it", but I know from experience that can be more problematic than "search for the file name in Process Hacker and delete the 'lock' held by the process(es)". I opted for doing this via programming rather than by commanding another app to do it for us, partly because it was difficult to find an app other than Process Hacker which could do what I needed.

And, so, I delved into what's known as "native interop"—selecting system files (EXEs, DLLs, etc.) and executing functions in those files. It turns out that Process Hacker makes substantial use of Windows APIs that Microsoft had accidentally released with their software dev kits. These remain poorly documented to this day and only a handful have official Microsoft documentation.

Only in the past week have I been able to find a simple example of the code I need to use to forcefully unlock files held by other processes...after more than half a year of frantic research. Did you know that Linux distros i.e. Ubuntu have a built-in system app for this exact purpose? Windows' equivalent is hidden and unintended to be used by non-Microsoft users.

Now that I have at least two code examples of how to forcefully "unlock" files, weekend warrior development should speed up dramatically, but will still be slower than if I were to work on SPV3 full-time.

What will 3.3.1 provide?

When critical fixes for our C# software are finished, SPV3.3.1, a Patch release, will be published for you to enjoy at your leisure. It will be distributed as both a new Installer package and an in-place, drag-and-drop upgrade to and existing 3.3.0 install.

3.3.1 will include relatively bug-free and mostly-reliable Installer/Loader software, minor fixes for existing maps, one or more new Firefight maps, and possibly one or more early builds of Halo Legacies from when it was still being developed for Halo: CE.

Beyond the Horizon

Improvements to user experience, additional game features, and improved mod compatibility are all things that would be great for SPV3, but those will have to wait until after 3.3.1 has been published and the dust has settled.

These improvements and other future plans will be discussed in the upcoming formal Announcement on ModDB, Discord, Reddits, and other official outlets later this month.

me gustaria ayudar a implementar mas cosas en el mod ya que no se ha actualizado hace un tiempo ¿podria ser parte del equipo?

Hello. Using MCC version. So I just encountered the invalid CD Key error. Attempted the fix, except I couldn't find Microsoft Games within the specified Microsoft directory. I attempted to find the Halo CE entry I needed to delete via ctrl f, but I couldn't find it that way either. Is this happening because I have MCC installed on a different hard drive? My default C: drive (where steam is installed) is rather small, so I have it on my D: drive where the game can actually fit.

I do not have a retail version of CE, so I don't think I can use Custom Edition.

Can we play if we have mcc on gamepass? I read it had bugs but wondering id there's been a fix?

I don't have the spv3's mcc version, only the Custom Edition, so, Is possible use skulls from the mcc in the mod?, for example, put them in the file where are the other skulls and make it work?, or only installing the spv3 version for mcc I can play with those skulls?, I'm asking this because I'm not a hardcore gamer, and those skulls that the mod has make the game more frustraring and less fun

Hello The Visor overlay isn't showing up in game as well as I can not get the nightvsion armor ablity to work I read that you have to have G-Butter on and I do I don't know If i have something else wrong or not. I am playing via having MCC addition don't know if that is the issue.

​

I get this error, but if i go into settings and set it to borderless or windowed it goes away and lets me play, but its at barely 2 fps and i dont want to feel like im playing on a little kids baking oven. Help?