konzeptionz

1. Assault rifle is not a long range weapon. Of course you are going to lose against a BR in a long range battle. 2. The BR is not the only weapon usable. The light rifle is actually better than the BR (more DPS.) The DMR is better than the BR at long range. 3. Nine assists seems pretty average to me. I've gotten as many as 25 assists in a single game. 4. That is absolute BS. Everyone that spawned near a BR in Halo 3, was using it. Aside from the limited amount of carbines, the BR was the only reasonable weapon to use for mid-long range. From that statement alone, I can tell you never played much Halo 3. 5. There were plenty of game types that started you off with the BR in Halo 3. It's asinine to only give people a close range weapon on spawn, unless the map is incredibly small. You can't possibly be expected to survive with an AR when the enemy team has you pinned down from across the map. 6. Seems like you're referring to lone wolves. It is a shame that the only FFA playlist in Halo 4, supports just one game type.

Bump. Seriously? this hasn't even been read yet...

I know there is already a thread for bugs and glitches. This one however needs attention, and I'm worried it will not get seen in that thread. I have encountered a bug in matchmaking that restricts my field of vision. All I can see is the very tip of the barrel on whatever gun I am using. The only thing I know for sure, is that I did not select a loadout when the game started. It auto selected for me. This bug does not go away after the match is over. It doesn't go away when you switch gametypes. In fact, it doesn't even go away after dashboarding. I looked pretty hard through Google and various forums, and I didn't see any reports of this glitch. The reason this is a game breaking bug, is because the decreased field of vision makes it extremely difficult to navigate around the map, and judging distance is a nightmare. Here is a video for proof of the glitch. http://www.youtube.com/watch?v=qlTHQiRe0_k Update: I've discovered how to reliably end this bug. I am still unsure of what causes it though. Starting a match in spartan ops, or any game type preceded by a cut scene, will end this bug.