Just throwing it out there but could it be (and i'm no techie) the different chipsets in the various 360's that are causing some to have problems and others not, do gamestesters test the games on the latest 360's with the latest chipsets onboard? My 360 is around 2 years old (my 7th due to RROD's) and obviously does not have the same chipset as the shiny new 360 slims. Can someone reply saying this is impossible or can people put what 360 they have and if they are experiencing issues, list them.

My 360 is a 2 year old white arcade model with the Falcon chipset and the main problems i have are:

Freezes around 2 times an hour
DLC save issue in various places
Cant enter The Strip
Numorous graphical gliches(guns floating 2 feet in front,characters getting stuck in scenery etc)

Heres how you tell which chipset you have
[IMG]http://i166.photobucket.com/albums/u102/Hainesy74/Xbox360_Model_Guide.jpg[/IMG]

They are supposed to test them on most of the system, so you shouldn't have too many problems that are specific to your system
out of you four one or two could be caused by you 360
the freezes may be caused by your system
and the guns floating is probably the other one the characters getting stuck in scenery is probably because of Havok
if you can't enter strip because it will not load then try wearing a coyboy hat, if it is locked kill the head of security.
the DLC they supposedly fixed in the upcoming patch

I imagine they have a variety of units just as they test the game on a variety of PC set ups.

You are assuming they do actually test them. The evidence would prove otherwise.
:wink_smile:

^ that would be the truth.. they didnt game test this game..

because if they did.. a patch would have been in the works long before it came out.

It svcks to buy a game and having to go on these stupid heavily moderated boards to find out which quests i need to skip so that i can enjoy a game i payed 60 dollars for.. not only that but the DLC has an announced DATE.. when the patch still doesn't have a ETA

My 360 is the new black slim and I have had the dlc save issue on 2 games.

I have a black elite model with the Jasper chipset and have not experienced any dlc or save game issues. Worst thing that happens are the progressively longer load times and a freeze at a load screen every 10 or so hours of gametime.

I've got the Halo 3 version (ugly green). And I can't check which chipset it has because it's being repaired. Does anybody know btw which chipset it has?

My problems with that console and New Vegas was that it froze once or twice and then red ringed me killing my console after some 10 hours of gameplay. Never had any other problems with that console. And while it debatable whether or not the game is to blame for, it would seem that the game certainly makes the console work harder even if you don't have to restart it all the time due freezing glitches, thus making the RRoD more likely to happen while playing this game. My console had an asthma and NV was a badass coach forcing it to run faster in circles while thinking too much at the same time. Those two seizures were fatal. :violin:

It'd be interesting to see if the hardware makes a difference. I have an Xbox Arcade (purchased a little over a year ago), no HDD, using a 4GB Flash Drive and two Xbox cards as storage. No DLC issues, a small handful of freezes, standard graphical glitches everyone's getting (but nothing serious like a companion getting stuck, just a couple times stuck in a rock or stuck while trying to climb or drop down from somewhere I probably shouldn't have been). If your hardware though is any indication, it sounds nearly identical to mine, unless there was a major difference within a year of manufacturing the older Arcade model before the Slims came out.

For the record, I play on a 2008 white Falcon (60GB). Never RROD'ed.

I'm 50 hours in the game, never froze, no DLC bug. I've only encountered minor bugs (3 Radscoprions stucked in the ground). Installed on the HD (as I do with all the games I play). So far, so good.

My old one got the RROD so I got a new one. Still got the error

To avoid compatiblity issues the chipsset in consoles are always the same. What you referring to (Xenon, Falcon, Japser, Vejle) are the regedesign of motherboards. Those revision aimed primary to make the console cheaper and to lower the power consumtion/reduce heat.

Mine is 2 years old as well and no major bugs.

I, too, have the eye-pleasing green Halo 3 edition. If yours is like mine, it'll have the Falcon, based on that chart linked above.

I suffered the freezing-when-going-into-VATS corruption immediately after downloading the very first patch. It didn't corrupt all my saves, but it did cost me more hours of work than I wanted to repeat. Otherwise, I've avoided Come Fly With Me and kept my Old Cowboy Hat on while on the Strip, so I've avoided those bugs so far.

All the other minor glitches and bugs have been present, however.

I have a black elite Jasper

But I doubt it's the chipset - it's the game. I played through twice with two entirely different results. 1st time tons of really annoying bugs but no game-ending bugs. My 2nd time EVERY hateful game-ending bug.

The 1st time on release day it went very well for the 1st 10 hours or so then started slow-loading and freezing on a par with FO3. It worked much better once the early patch went live ... for a while then it started taking forever to load, froze WAY too often, companions going missing on their way back to the Lucky 38, and tons of graphical glitches, clipping, invisible walls, and NPCs, mobs and my avatar frequently getting stuck in the environment. BUT no game-ending bugs and I even did the McCaffrey or whatever bounty-hunter quest with no old cowboy hat. I didn't like my choices or the way I was proceeding in the game so I decided to finish up without doing any more side-questsand re-roll.

My 2nd playthrough started out excellent, loading times good with very few freezes - still lots of graphic glitches, but that's to be expected in a Bethesda game BUT the further I got the more game-ending bugs popped up.

Companions were getting lost all the time and not just on the way to the Lucky 38. I save often so I'd revert to a save and find them. Then after I recruited Gannon, I could no longer send companions to the Lucky 38, I could only dismiss them or keep them. I read online if you deleted the 1st patch you could again send them to the Lucky 38 so I did that and it worked for a while, until I could no longer get INTO the Lucky 38 Elevator. I got Lucky at the Lucky 38 and accidently clicked on Boone and HE borught up Victor's Dialog so I could go up to my room and then it started working again.

After deleting the patch every time I would start up it would tell me I was missing DLC but I would just say continue and it was OK UNTIL I decided to tempt fate and did the bounty-hunter mission in this glich-fil;led playthrough and even then I ws OK until got the epic-fail auto-save corruption black screen of death when I tried to enter the strip. Had to go back a several saves, go buy the 'old cowboy hat' and limp through to finsh this bug-fest saviong every 2 minutes or so. Couldn't get Boone to give me the dialog to finish his Quest. Got trapped in the Remnants bunker with no way to exit and oh so many other fun bugs you would have thought the game was in pre-alpha NOT a retail version.

With the 2 very different sets of bugs in 2 different playthroughs on the same machine, I'd be inclined to say it's definitely the game and not the chipset.

I have the Falcon chipset and seem to experience some of the same glitches you have, but nothing game crashing (save the entering the Strip glitch, but I always had Old Cowboy Hat anyway cause I thought it looked rad). It would be interesting to get a list of people's chipsets and their issues and see if they're related. I'll make sure to make a note of it when discussing game issues with other troubleshooter's.
Many of my friends have pointed out that just restarting the game every 2 hours seems to combat a lot of the freezes, the long load times, and the graphical glitches. Makes me wonder how stable the engine is.

I can't seem to get a straight answer out of anybody, no matter who I ask, but what happens with "Come Fly With Me" that glitches/breaks the game? I've done it on all my playthroughs and found nothing wrong, but curiosity leads me to beg this question.

I have the newest Halo Reach 360S model with the "Vejle" chipset. And I have the DLC error, lost a 90 hour save, and only had one good save which was at 25 hours. So I lost 65 hours. So I can vouch that it happens on the newest chipsets also.

I've got the new slim and my game locks up every other hour, I love this game, I just wish I could play it without rebooting my 360 every 5 minutes

No one knows because it doesn't happen to everyone. I know I didn't do the re-alignment of the rockets, so it's possible that's why I did not experience the DLC issue. I also didn't talk to the wannabe Ghoul character at all before the end. I just left him be. So it's possible he disappears if you let him in on the secret that the head ghoul tells you (or interact with him in any way other than giving him the items), and that's what's triggering this issue for some. I don't know. It has nothing to do with the spacesuit because I have it, it has nothing to do with going and getting the fuel from the body, because I did that... It also may be a complete coincidence and have nothing to do with the entire quest, as people have bypassed it but still had the DLC error.

What might have been nice, and I KNOW, we're all not supposed to be the beta testers and whatnot, but what would have been nice is if everyone who experienced the DLC issue had documented what all they had done to try and find a common thread. Not just a "Oh I went to this vault and now my save is corrupt". What did you do in the vault? Did you explore the whole thing? Did you kill an NPC that you maybe should not have? Those would be very helpful things. I know that everyone is not a trained Beta tester and also shouldn't have to be to play a game, but it would have been helpful to the Developers (though they apparently have a handle on it now).

Like you I cannot say for sure because I am not really "in the know" when it comes to that stuff, but I can speak from experience. I have the Xbox 360 S and I have all the freezing and DLC bug errors that everyone else has been complaining about.

YOUR 7th 360??? Wow, are you getting them fixed or just buying new ones? You do know there is a 3 year warranty for every 360 don't you?

I bought mine on launch day and i still have the same one. I got the red ring of death once, sent it to MS to be fixed and had it back within a week. It's the same one (I checked the serial #) and it's worked perfectly ever since.

I'm getting my console back probably next week from maintenance after RRoD process. I just noticed from xbox online service center that my serial # has changed. So they are sending a different console back. This "new" one has warranty til march 2011. Apparently they are sending old repaired consoles in exchange so they can have faster service -> some day somebody else is going get my old repaired console (in Europe).

Does anybody here have experience with these old repaired consoles that come back from ms? Are they reliable at all? Has Microsoft somehow managed to improve the innards of those broken consoles compared what they used to be in their earlier lives... or should I just give up and get a Slim?

Thanks.

Like I said, I have a launch day Xbox 360 that's been fixed once and it still works great. They don't improve it, they just fix it. MS has never said what part was faulty so as not to throw whoever manufactures that part under the bus, but they know what the problem was and they fix it.