I've experienced the besieged/campaign freeze. That's been an issue since day 1 of the Xbox version. I've experienced it on every model I've owned from the 20gig premium to the 120gig Elite to the 250gig slim. So it not limited to old vs new model systems.
The zone freeze is nothing new either. That may be related to the lag freeze mentioned aboved.
Trying to report it to Microsoft results in "it's SE's problem, not ours". Reporting to SE results in "it's microsofts problem, not ours".
At this point I blame both parties. Microsoft for crappy hardware that can't handle the massive flow of network info, resulting in memory leaks. SE for being lazy and not adding the proper filters to prevent the network overflow that causes the memory leaks.
In other words: the PS2 version has filters that only allow so much data to be processed at one time and keeps new data in limbo until the old info has been purged from the memory. Without those built in filters in the game PS2 would crash more often than the Xbox. The Xbox version doesn't have that same type of filtering and allows new data in before the old data has a chance to purge. This results in information overload and the system stops responding.
A lot of of computers run into this problem if you try to open too many programs at once. Sometimes the system goes "ugh! Too much, too fast /wheeze" and freezes up or lags down really badly until it can purge enough data to become functional again.


Reply With Quote