CALL OF DUTY
The Loading... never ends! I've tried deleting/re-installing the game from/to my HDD. I tried playing it off the disc between deleting and reinstalling, but nothing is working! I checked the disc and there are no scratches or smudges on it. Has anyone else had this problem? Anybody have a possible solution for me?
Works here maybe your savegame is corrupt (a few people reported such an issue already). Dont think it's your copy but could be too.
May I ask what Xbox? The RROD Generation, the 2nd generation, Elite, Slim? Cause I have a slim and not a single issue with it so far (friends of me have older 360s and they have a lot of issues).
I really hope it's not my save game... I put a lot of work into this one. Oh well, I suppose... I'm gonna exchange the game today, and if it doesn't work, I'll just start a new game I guess. Luckily, I got the "Completed Game on ...." achievements before the endless loading screen, so I could just replay on Human mode (I had originally played through on Hero, and had a rough time at certain parts) if I want to just get to the end quickly.
My first Xbox 360 was about a year after they came out. Unfortunately, I'm actually on my fourth or fifth unit. All had been sent in to Microsoft for repair/replacement (for the RRoD). So I'd assume this unit might be the 2nd generation? Then again, there's no HDMI port, so I guess that means it's still 1st gen...
It's a miracle! This morning, I decided to once again try my luck. First I attempted to play it from the HDD, with cleared cache and NOT install the Live Update. It failed. I then uninstalled it from the HDD, played from the disc, still without running the Live Update, and it worked! Thanks for all your help guys! Crisis averted
On the Xbox360achievement website one guy apparently found out whats causing this:
Done with it! deleted all saved files excepot the actual game save... took game and HDD to friend's house, still does it. Something in the save file that won't let the game read/interpit the load sequence...
The savegame is apparently causing it.