As the title states, the UA/HUL[3] attachment for the Recon Helmet, and the Multi-Threat [W] cuirass (Chest armor), don’t even appear as selectable options, when playing the Halo Reach campaign offline;
which is currently the only way we’re able to see our custom-set armor in the cutscenes & in-game.
They’re both only visible, selectable options, when connected to XBox Live, but the armor that appears in cutscenes & in-game (when playing the campaign, while connected to XBL), reverts to the default armor, despite what our custom armor settings are saved as.
Seeing this is frustrating, as we’ve downloaded these armor parts onto our HDD, with the pre-order codes provided, so they should be usable offline, but they aren’t.
This is even more frustrating , since UA/HUL[3] Recon, in particular, is the helmet I equip whenever I play the campaign mission, Nightfall (for full lore immersion).
So, despite having the data on our HDD, we can no longer equip these armor parts for offline Campaign gameplay.
Is it feasible to at least get a patch for this?
Cause this is literally paid content (for those who pre-ordered the game).
These armor parts are downloaded onto our HDD and should be equippable offline, despite the server(s) now being offline.
We should still be able to use locally stored items on our HDD, that we paid for…! Please release a patch to fix this, 343i…!
The officer elite and the recon helmet attachment for me do work when I turn my xbox offline. For some reason though I though they didn’t work but I found out the other day that the legendary flames (red) work on my XSX, but for some reason they wouldn’t pop up for me on my Xbox 360 which I find odd. My waypoint armour though isn’t selectable for me.
The thing for me that hurts the most though is that Recon from Halo 3 isn’t accessible to me anymore. Just with the whole story behind that armour set to just be taken away…saying it really sucks doesn’t really describe it. I really wish 343 would patch the games to make that stuff accessible for people but it’s 343 so I’m not holding my breath, they tend not to care nearly as much about the fans that like to play on the older games I find.
I also find it really odd that you can access your armour offline for Halo Reach but not online, I don’t really know how that works tbh.
Huh… So the opposite happened to you…
Thing is, I fully expected for what happened to you to happen to me as well (as a common result), and yet what happened to me was the inverse of what happened to you; I truly thought Waypoint armor support would collapse (for me) & re-lock what I’ve already unlocked, but it somehow didn’t (?) & Waypoint data is somehow still afloat with whatever final piece of data it received (in which case, I don’t understand why other things like our Service Record couldn’t function locally in-game, the way Waypoint still somewhat functions?).
[Clarification: I already unlocked the Waypoint armor before Server Sunset, and they’re still accessible to me.]
Especially when playing Campaign…!
343i should release a hotfix/line of code that tells the game to stop attempting to sync to servers & just display locally-stored data.
What happened to both of us, just informs me how messy the netcode was, that was supporting everyone’s data. Because the expected result was for everyone to experience the same outage, rather than the variances both of us & others have reported.
I think it would’ve just been easier/better if 343i had instead (of sunsetting, had) handed over server-hosting duties to Microsoft, to house the server along with the other servers that still host XBL on 360.
Win-win for everyone. But nooo…
That is odd. Smh Further netcode inconsistencies…
WUT…
I’ve seen YouTube clips of people still being able to access it, but I’ve yet to set aside the time to verify it for myself (I’ll definitely update here once I do).
With how varied our results are & how messy the netcode is, I truly hope I haven’t lost mine either.
Completing Vidmaster: Endure on ODST was the worst/most grueling of the Vidmaster’s Challenges, to attain it, so yeah, I’m right there with ya.
I’d say… ‘gut-wrenching’, ‘heart-breaking’, and/or ‘devastating’, would be close/apt descriptors…
It would be as if… you got on those tower-drop amusement park rides, and the height you reach represents all the effort, hard-work, & time you put into getting Recon, only for the operator (343i) to press the release button to let you fall back to the ground. And the falling feeling is the feeling of losing Recon.
I’m sorry you can’t access your Recon armor anymore… …and I know it’s not the same, but I hope you find solace in knowing… that, even though you can no longer access your Recon in Halo 3, that your memories of having earned it still live on, and that no Server Sunset can take that away.
Gone, but not Forgotten [“M.I.A., not K.I.A.”].
I’d say, it isn’t so much about Apathy, as it is Incompetence (outsourcing to contractors & hiring non-veteran devs to handle an established franchise) & Uninspired/Non-innovative/Poor Leadership. (The worker shortage environment on affordable veteran devs doesn’t help, either…)
They should reshuffle/hire/promote a new studio head who runs a ‘tighter’/more-focused ship, and is also more in-touch with their games & the playerbase/Halo community - a Problem-Solver (not a Feelings-Accommodator - that’s what H.R., P.R., & Community Managers are for).
Everything else (such as better/more efficient work practices) will fall into place from there.
‘Take care of the games & players, and the players will express their appreciation & reciprocate accordingly.’
, since UA/HUL[3] Recon, in particular, is the helmet I equip whenever I play the campaign mission, Nightfall (for full lore immersion).
release a patch to fix this, 343i…! 
So the opposite happened to you…
?) & Waypoint data is somehow still afloat with whatever final piece of data it received (in which case, I don’t understand why other things like our Service Record couldn’t function locally in-game, the way Waypoint still somewhat functions?).
