So I picked the game type “Heavies” and went into a game as “join in progress”. The game wasn’t very far along. It was CTF on Exile, and both teams had just grabbed each others flag. So I spawn in and ran for a few feet, then died from what seemed like nothing. At first I thought that it was just lag and I had been run over by a vehicle or shot with a 1 hit kill weapon. A few seconds into the respawn screen I realized that the timer was stuck at 9. This usually indicates that the game is about to “black screen”. Well, that didn’t happen. I could swivel the camera around my dead body, and I could see other players still running around in the game. I tried to switch my POV to other teammates, but I couldn’t. I could only stare at my corpse. I then hit the back button to check the scoreboard and saw that my gamer tag wasn’t listed! So essentially I’m in a “spectator mode” but unable to move the camera away from my body. Eventually after quite some time the game finally spawned me in and my gamer tag was listed in the scorecard. I’m not exactly sure how this happened seeing that I was physically moving in the game one minute, then the game killed me and took me out of play. Anyone know how this bug occurred, or if it can be looked at?
This happens when there is a severe case of lag going on.
Sadly nothing can be done about it. With less people playing Halo 4 nowadays, perfect match ups without lag are almost impossible to find.
The Little Moa is correct. This issue is usually caused when the host chosen for the game has a very poor connection with you, especially when the connection he/she has is good for everyone else, causing large amounts of lag. The game essentially becomes desynchronized for you, and, as a result, it does not give you control of your body. On another player’s screen, you would appear AFK, when. in fact, you are simply desynchronized. There’s no real way to fix it, but it’s not a common issue, and is simply a side-effect of having a bad connection in host-based Multiplayer.
I am locking the topic as the issue has been, if not resolved, then at least explained. 