maulver07
Mensagens : 471 Data de inscrição : 01/09/2010 Idade : 37 Localização : Lagoa
| Assunto: Black Ops Path 1.05 falançado para ps3 Qui Dez 23, 2010 10:15 am | |
| Many PlayStation 3 owners have been having a hard time with Black Ops despite multiple attempts at trying to fix it by the developers, Treyarch. Connection issues have been the bane of many PS3 Black Ops fans since release. So, Patch 1.05 was released on the PlayStation 3 today, hopefully putting an end to the problems. Get the details after the break. Patch 1.05 released at 2AM PST on 12/22/10. This patch is part of a series of ongoing improvements to online connectivity which will be continued over the next few weeks. Treyarch is dedicated to ensuring the best gaming experience for the fans, and we’ve been actively working with you to continue to improve the game based on your feedback. As always, keep the feedback coming through the community forums. LIVE FIXES
12/22 (full patch 1.05)
- • Improved party reliability when leaving with party – an additional
step in an ongoing series of party improvements continued in the next patch
- • Improved UPnP functionality – further expands the game’s
capability to open NATs on routers with universal plug and play enabled
- • Enabled mute functionality in Playercards in the pre-game lobby
- • Enabled kick functionality in party and private match lobbies
- • Addressed an issue where the pre-game lobby would not always
display properly when multiple players leave the lobby after a team split
- • Addressed an issue where the pre-game lobby would appear stuck on the countdown timer while waiting to balance teams
IN PROGRESS:
- • Addressing a freeze that would occur in rare situations involving a
combination of high player counts and many killstreaks / explosions occurring simultaneously in a concentrated area
- • Further improvements to party reliability to address an issue
where mixed NAT types connecting and disconnecting can cause players to drop in some situations
- • Investigating “infinite loading screen” issue reported by some users
| |
|