@Polymarket I’ve underperformed purposely. If they don’t want to pay me what I’m worth then they won’t get their moneys worth either. I’ll coast doing the bare minimum. This is the environment they created!
@Halo Beat the game on Legendary already and I’ll never pick it up again. Thanks for 3 days of entertainment. See ya in 5 years or however long it takes to make a game these days.
@HylianX7935 I’d say it’s people like you that prop up these failures with your infinite amount of excuse making and blame shifting. We should have purged you bozos a long time ago.
Honestly, it’s a bit of both, and that’s typical for early-access UE5 titles paired with brand-new GPU architecture:
•Nvidia’s side: the 610.82 hotfix didn’t fully resolve it for everyone — some 5070 Ti owners still crashed after a clean install,  which suggests the driver itself has an incomplete fix, not just a config issue on your end.
•Halo/Unreal Engine’s side: the crash is tied to a specific scripted sequence (the bridge push in Keyes), which points to something in how that mission’s assets, shaders, or memory handling interact with RTX 50-series hardware specifically — not a general “this driver is broken” problem, since it doesn’t affect all games or even all NVIDIA cards.
@RoyalDeathClaw@lodahb0llcks@Nick_Marseil You’re comparing a console that sold 150 million units to a console that sold 25 million units. There’s nothing wild about it. SOCOM was the broader appealing game but so are McDonald’s cheeseburgers. Halo was one of the only reasons to even buy an Xbox back then.