Tweet
Ja man glaubt es kaum, aber es ist soweit
EA hat jetzt den Patch 1.1 angekündigt, dankeschön an Moby3012 für die Info.
Hi guys,
My name is Amer Ajami, and I’m one of the producers on Battle for Middle-earth. As many of you already know, our Executive Producer, Mark Skaggs, has made a commitment to continue supporting BFME well beyond its release date. With that in mind, I would like to address some of the concerns that our community has surfaced in the last week since the game’s launch:
1. Will there be a patch? Yes. We are currently working on the first patch for BFME. This patch, which we’re calling 1.01, will include several miscellaneous fixes and tweaks, and it will also address some of the issues raised on the forums since release. These will include, but are not limited to, the following:
· Buddy list with messenger: We know that a lot of people have been asking for a fully functioning online messenger, and we’re working on including one in 1.01.
· New multiplayer maps: Patch 1.01 will include three, possibly four, new multiplayer maps created by our team.
· Improved NAT connection: We’re constantly tweaking our network code to make it more streamlined and supportive of as many routers and firewalls as possible. Having said that, users that are experiencing NAT issues should refer to the readme, as it contains a lot of information for possible workarounds.
[MEHR]
· World Builder fixes: Several World Builder issues, such as the grove/tree tool freezes, will be addressed.
· Video card glitches: We’re working with Nvidia to try and solve the rare crash that occurs with some 5900 Ultra cards.
· Chat lobby glitches: The issue where selecting one user will sometimes select all users in the chat lobbies will be addressed.
We’re also going to be carefully reviewing race balance and make any tweaks necessary. Patch 1.01 is currently scheduled for release in mid-January.
2. An active presence online: Key members of the BFME team, including myself, will be making periodic updates to various forums and talk about key issues within the community. We’re aiming to have chats with our designers, map-creation contests, giveaways, patch discussions, and other community interaction throughout the coming months. You’ll also be hearing about a new community manager who will be working within the BFME team to support our game and our community online. More news on that later.
3. Disconnect “bugs” in the ladder: Many users who are playing Quick Match online have been complaining about a “bug” in our code that prevents disconnected games from registering a loss on the ladders. This is not a bug and is actually a purposeful design decision. Our network infrastructure is set up as a peer-to-peer system with no heartbeat server, which makes it hard to reliably tell who caused a disconnect in any given 2-player match. The fair way to handle disconnects in this situation is to simply call the game null and void, assigning neither a win nor a loss to either player, and leave their win/loss streaks unaffected. As an honest player, what’s worse to you: Getting a loss because you played against a griefer who disconnected, thus killing any win streaks you had going - or having that game be null and void, leaving your stats untouched? We know the current implementation is not ideal, but given the technical limitations that we have, this was the best answer.
Having said that, we actually do still track disconnects, but we don’t display it to the user. Outside of the development team, you guys are actually the first to hear about this. After the first patch is released, we will be monitoring the ladders for users with an abnormally high number of disconnects, and kick those users from the ladder. Of course, regular users who are victims of griefers or who have honest network problems will remain unaffected.
4. Manufacturing defect in a small batch of CDs: A small number of users have experienced an error message when trying to install the game, or when attempting to run the game. This typically happens with the CD version of the game (DVD should be fine), and is caused by a bad batch of CDs (specifically Disc #2). Our customer service site has been updated with the steps that users with bad discs should take to contact EA’s warranty department. Basically, if you bought a game from this small bad batch, EA will send you a new copy, no questions asked. Details are below:
http://eatech.custhelp.com/cgi-bin/e...i=&p_topview=1
You can expect to get more such updates from me and a new community manager in the near future. Please feel free to contact me through Craig Owens or Aaron Kaufman if you have any questions.
EA hat jetzt den Patch 1.1 angekündigt, dankeschön an Moby3012 für die Info.Hi guys,
My name is Amer Ajami, and I’m one of the producers on Battle for Middle-earth. As many of you already know, our Executive Producer, Mark Skaggs, has made a commitment to continue supporting BFME well beyond its release date. With that in mind, I would like to address some of the concerns that our community has surfaced in the last week since the game’s launch:
1. Will there be a patch? Yes. We are currently working on the first patch for BFME. This patch, which we’re calling 1.01, will include several miscellaneous fixes and tweaks, and it will also address some of the issues raised on the forums since release. These will include, but are not limited to, the following:
· Buddy list with messenger: We know that a lot of people have been asking for a fully functioning online messenger, and we’re working on including one in 1.01.
· New multiplayer maps: Patch 1.01 will include three, possibly four, new multiplayer maps created by our team.
· Improved NAT connection: We’re constantly tweaking our network code to make it more streamlined and supportive of as many routers and firewalls as possible. Having said that, users that are experiencing NAT issues should refer to the readme, as it contains a lot of information for possible workarounds.
[MEHR]
· World Builder fixes: Several World Builder issues, such as the grove/tree tool freezes, will be addressed.
· Video card glitches: We’re working with Nvidia to try and solve the rare crash that occurs with some 5900 Ultra cards.
· Chat lobby glitches: The issue where selecting one user will sometimes select all users in the chat lobbies will be addressed.
We’re also going to be carefully reviewing race balance and make any tweaks necessary. Patch 1.01 is currently scheduled for release in mid-January.
2. An active presence online: Key members of the BFME team, including myself, will be making periodic updates to various forums and talk about key issues within the community. We’re aiming to have chats with our designers, map-creation contests, giveaways, patch discussions, and other community interaction throughout the coming months. You’ll also be hearing about a new community manager who will be working within the BFME team to support our game and our community online. More news on that later.
3. Disconnect “bugs” in the ladder: Many users who are playing Quick Match online have been complaining about a “bug” in our code that prevents disconnected games from registering a loss on the ladders. This is not a bug and is actually a purposeful design decision. Our network infrastructure is set up as a peer-to-peer system with no heartbeat server, which makes it hard to reliably tell who caused a disconnect in any given 2-player match. The fair way to handle disconnects in this situation is to simply call the game null and void, assigning neither a win nor a loss to either player, and leave their win/loss streaks unaffected. As an honest player, what’s worse to you: Getting a loss because you played against a griefer who disconnected, thus killing any win streaks you had going - or having that game be null and void, leaving your stats untouched? We know the current implementation is not ideal, but given the technical limitations that we have, this was the best answer.
Having said that, we actually do still track disconnects, but we don’t display it to the user. Outside of the development team, you guys are actually the first to hear about this. After the first patch is released, we will be monitoring the ladders for users with an abnormally high number of disconnects, and kick those users from the ladder. Of course, regular users who are victims of griefers or who have honest network problems will remain unaffected.
4. Manufacturing defect in a small batch of CDs: A small number of users have experienced an error message when trying to install the game, or when attempting to run the game. This typically happens with the CD version of the game (DVD should be fine), and is caused by a bad batch of CDs (specifically Disc #2). Our customer service site has been updated with the steps that users with bad discs should take to contact EA’s warranty department. Basically, if you bought a game from this small bad batch, EA will send you a new copy, no questions asked. Details are below:
http://eatech.custhelp.com/cgi-bin/e...i=&p_topview=1
You can expect to get more such updates from me and a new community manager in the near future. Please feel free to contact me through Craig Owens or Aaron Kaufman if you have any questions.
ich werde ja merken, was sich verändert hat, wenn ichs spiele *g*
Kommentar