|
|
 |
| [Jul 08, 2005, 11:17 pm ET] - Share - Viewing Comments |
A new Battlefield 2 Community Update has a status report on plans for a
hotfix for memory leak issues with Battlefield 2 version 1.01. Although the site
states "EA and DICE are committed to getting a fix for
v1.01 as soon as we possibly can," in the meantime they are suggesting
that users downgrade by reinstalling the original unpatched version of the game:
HOTFIX for Battlefield 2 v1.01 Coming Soon
First off, a HUGE thanks to all of you who emailed me in regards to the
memory leak found in the update we released earlier this week (v1.01). Your
emails found their way to our production team and they’re in the process of
evaluating what needs to be done in order to get this fixed. In the meantime,
and since the 1.01 update is causing memory leakage on some systems, we
recommend that you reinstall the game and NOT the v1.01 update we
released earlier this week.
Reinstalling Battlefield 2 will not affect your in-game medals or ranked server
statistics. EA and DICE are committed to getting a fix for v1.01 as soon as we
possibly can and will continue to keep you informed through this web space in
the coming days.
NOTE: If you installed and are running the newer server files (Win and Linux
versions) we made available earlier this week, please revert those as well. We
found that those files had the same issues with memory leaks as did the v1.01
update. You can download the older versions
here.
Post Comment
Enter the details of the comment
you'd like to post in the boxes below and click the button at
the bottom of the form.
 |
| 15. |
Re: No subject |
Jul 9, 2005, 04:03 |
pob |
|
|
"I bought the hype because I enjoyed the demo, but being booted off the server after every match is really boring, and the servers are thinning out WAY fast... "
i had that problem...i play it over a network, connecting to the internet gateway machine which runs wingate/wingoat...a little piece of software that, for most people, probably got replaced by ICS ages ago.
i was originally using its NAT connection sharing mode. Each time I'd get booted at the end of the match, even with firewalls turned off. Swapped over to using its replacement network winsock instead, which doesn't work with games needing UDP (in my past experience), and now things work fine.
|
|
|
|
|
|
|
|
| |
|
|
.. ..
Copyright © 1996-2013 Stephen Heaslip. All rights reserved.
All trademarks are properties of their respective owners.