Just got done playing the mammoth level again. Towards the start I died trying to drive through the first river in a warthog. So next time I got back on the mammoth, then watched 2 marine NPCs drive a hog through that same river completely and utterly unharmed. So I jumped off the mammoth and tried to claim the warthog - but the AIs drove off back through the river and I died trying to chase them on foot.
Next time I just stayed on the mammoth. At the set of 3 generators creating a shield blocking the mammoth's path (before the second AA gun), after killing everything I took a ghost and drove it along the road ahead of the mammoth to the second AA gun. At the second AA gun I climbed out of the ghost to use the targeting device, did not move at all, used the targeting device, then tried to climb back into the ghost I was stood next to but it had disappeared. After 3 seconds, while moving a distance of NOTHING the ghost had disappeared.
I continued, with tears of lamentation in my eyes for the fanchise once known as 'Halo'.
After taking out the second AA gun I took a warthog and tried to drive on to the control centre ahead of the mammoth. I died a couple of times trying to pass through the next couple of rivers. With some trial and error I managed to find a path through the first couple of rivers without dying (I forded them on the right where it's rocky - try it). Then on a stretch of safe road shortly afterwards the game took control away from me and made the Master Chief climb out of the Warthog, at which point the Warthog exploded for no reason.
This shit - and it is shit - would never have passed with Bungie.
You're taking a sandbox engine and retrofitting it for better graphics, then trying to pretend you still have the sandbox gameplay until someone tries to do something you haven't scripted for (how can you *not* expect someone to drive a Warthog down a fucking road?) at which point things disappear or some horribly, crudely enforced event (based on a bastardised rule from the original Bungie games) fingers you.
This is not Halo.This is not a game that is intended to be played to destruction in whatever manner you as a gamer (who enjoys the gameplay mechanics) deems enjoyable. This is a developer taking all the resources that allow a game to be made fun to replay 20 (or more) times over and instead allocating them into graphics that will only ever be most appreciated on the first play through.
This is a conscious decision. Whoever made these choices did so deliberately and with a calculator and is a most definitely a tech and not a gameplay person. Unless the power structure within 343 changes we will probably see more of this shit in the next Halo.
Yeah, I think it's a memory thing too. And after tonight's Mammoth Disappointment my Impotent Rage meter has just gone up from Grunt to Jackal!
Yeah, it not only plays badly (and suffers from all the usual 3D into the screen shooter issues) but then it turns into a really bad version of Rouge Squadron. I also had a couple of glitches where my ship would turn hard to the side and asplode into the wall, with nothing I could do to stop it. For some reason the variable covering pitch and/or yaw just went maximum to the right or down. Hands down it is the least enjoyable and most worthless level in the game.
The more I play Halo 4 the more I realise it's not really a Halo game as you know it. Kind of like, you're expecting a wolf, but it just turns out to be Pug wearing a nice looking wolf hat. Not that there's anything wrong with Pugs, it's just that they tend to derp where wolves would howl.
Next time I just stayed on the mammoth. At the set of 3 generators creating a shield blocking the mammoth's path (before the second AA gun), after killing everything I took a ghost and drove it along the road ahead of the mammoth to the second AA gun. At the second AA gun I climbed out of the ghost to use the targeting device, did not move at all, used the targeting device, then tried to climb back into the ghost I was stood next to but it had disappeared. After 3 seconds, while moving a distance of NOTHING the ghost had disappeared.
I continued, with tears of lamentation in my eyes for the fanchise once known as 'Halo'.
After taking out the second AA gun I took a warthog and tried to drive on to the control centre ahead of the mammoth. I died a couple of times trying to pass through the next couple of rivers. With some trial and error I managed to find a path through the first couple of rivers without dying (I forded them on the right where it's rocky - try it). Then on a stretch of safe road shortly afterwards the game took control away from me and made the Master Chief climb out of the Warthog, at which point the Warthog exploded for no reason.
This shit - and it is shit - would never have passed with Bungie.
You're taking a sandbox engine and retrofitting it for better graphics, then trying to pretend you still have the sandbox gameplay until someone tries to do something you haven't scripted for (how can you *not* expect someone to drive a Warthog down a fucking road?) at which point things disappear or some horribly, crudely enforced event (based on a bastardised rule from the original Bungie games) fingers you.
This is not Halo.This is not a game that is intended to be played to destruction in whatever manner you as a gamer (who enjoys the gameplay mechanics) deems enjoyable. This is a developer taking all the resources that allow a game to be made fun to replay 20 (or more) times over and instead allocating them into graphics that will only ever be most appreciated on the first play through.
This is a conscious decision. Whoever made these choices did so deliberately and with a calculator and is a most definitely a tech and not a gameplay person. Unless the power structure within 343 changes we will probably see more of this shit in the next Halo.
I'm thinking the disappearing weapons thing might be a memory issue. I vagely remember a Bungie dev talking about how you need to decide on this capability (persistent weapons) early on, incorporate it into your memory budget, and then stick to that memory budget. I'm thinking you're correct that 343 prioritized graphics over gameplay.
Yeah, I think it's a memory thing too. And after tonight's Mammoth Disappointment my Impotent Rage meter has just gone up from Grunt to Jackal!
Also, the flying section in the last level is one of the stupidest, most tedious, most uninspired aspects of the game (and a lot of the SP campaign feels uninspired). I mean seriously? This is all they could come up with for a flying mission? It's the most un-fun way to go about it.
Yeah, it not only plays badly (and suffers from all the usual 3D into the screen shooter issues) but then it turns into a really bad version of Rouge Squadron. I also had a couple of glitches where my ship would turn hard to the side and asplode into the wall, with nothing I could do to stop it. For some reason the variable covering pitch and/or yaw just went maximum to the right or down. Hands down it is the least enjoyable and most worthless level in the game.
The more I play Halo 4 the more I realise it's not really a Halo game as you know it. Kind of like, you're expecting a wolf, but it just turns out to be Pug wearing a nice looking wolf hat. Not that there's anything wrong with Pugs, it's just that they tend to derp where wolves would howl.
Last edited by a moderator: