Someone on the EA boards found a possible fix to CTD's
http://forums.ea.com/mboards/thread.jsp … p;tstart=0
http://forums.ea.com/mboards/thread.jsp … p;tstart=0
I remember I used to use it when I first got BF2 and it solved the CTD issue on my older PC. Even if you have a newer PC, it might help.
Go to C: \Program Files\EA GAMES\Battlefield 2\mods\bf2\Settings
Open up videoDefault. con with notepad
Change
rend erer.allowAllRefreshRates 0
to read
renderer. allowAllRefreshRates 1
Do the same with C:\Program Files\EA GAMES\Battlefield 2\xpack\bf2\Settings VideoDefault.con if you have Special Forces.
This allows the game to run the refresh rate of your PC instead of it expecting it to be 60 or 75htz. There are a few reasons this can happen and its not always easy to spot.
Let me know if it helps!
erm wots a CTD lol :-)
ctd = crash to desktop
Its not that crap making ctd happen its the TCPIP limiter. In the new win XP the TCPIP has a limit of 10 transponds a second, check the Help stickys to find the link to download the software to remove the limiter. I've done it and i havent CTD since. Hope this helps
Phil
Phil
Last edited by pippin_death (2006-07-21 11:06:49)
A link might be nice pippin?
do we just keep saying Y Y Y Y Y and follow and not change anything? will it give a virus?dontfeedthenerd wrote:
http://www.lvllord.de/?lang=en&url=downloads&PHPSESSID=5155e7c8f53aef581c5136dc0457efca#4226patch
Entertainer
funny how i had my set to 50 from the start and.. yet since 1.3 it still happens....pippin_death wrote:
Its not that crap making ctd happen its the TCPIP limiter. In the new win XP the TCPIP has a limit of 10 transponds a second, check the Help stickys to find the link to download the software to remove the limiter. I've done it and i havent CTD since. Hope this helps
Phil
funny that...
Ever since downloading patch 1.3 I've had this CTD quite often; this problem never occurred before patch 1.3 and it is becoming quite irritating when it does happens. Does anyone know of any new info on patch 1.4 besides what is listed in BF2S forum on this issue.
memory timings, bumping them up = no more ctds
All you do when you get CTDs is move / delete bf2 folder from my docs, and you dont get them for like a month or 2
/wincyborg_ninja-117 wrote:
memory timings, bumping them up = no more ctds
i rarely get the CTD'S ingame or when a map is loading, however, i do get CTD's when you click the join game button or you hit escape at the loading screen when "join game" comes up. BUT, for that, i use jappes advice in this thread and havent crashed when hitting escape or clicking join game at the loading screen for about 5 months now.
Last edited by eagles1106 (2006-08-13 21:47:49)
thats what most ppl get, bump your memory timings and your goldeneagles1106 wrote:
i rarely get the CTD'S ingame or when a map is loading, however, i do get CTD's when you click the join game button or you hit escape at the loading screen when "join game" comes up. BUT, for that, i use jappes advice in this thread and havent crashed when hitting escape or clicking join game at the loading screen for about 5 months now.
Funny that, sometimes I get CTD exactly as I see the map load while walking into the room with a soda, without touching anything
Am I the only one here who gets a CTD sometimes just when I move the mouse toward the button at the bottom right? Sometimes it has to highlight the button for the game to crash, without clicking on it, but others I just move the pointer a bit and bingo, back to looking at my desktop.eagles1106 wrote:
i rarely get the CTD'S ingame or when a map is loading, however, i do get CTD's when you click the join game button or you hit escape at the loading screen when "join game" comes up. BUT, for that, i use jappes advice in this thread and havent crashed when hitting escape or clicking join game at the loading screen for about 5 months now.
any fixes for server crashes ?
I tried the refresh rate change awhile back, didn't work for me.
Edit: but I'm sorta glad it didn't, because if it had, I would have been even more pissed that DICE couldn't release a hotfix changing ONE NUMBER in a config file.
Edit: but I'm sorta glad it didn't, because if it had, I would have been even more pissed that DICE couldn't release a hotfix changing ONE NUMBER in a config file.
Last edited by xintegrityx (2006-08-14 11:04:38)