[QXJZ]Capt_Kefra
Alright, you're good to go!
+124|7198|Honolulu, HI
Sorry for spamming the forums, this is my second thread in less than 12 hours but I'm so damn happy I couldn't help myself.

So everyone's heard all the possible ways of reducing lag/connection problems.  If you've already tried the following:

*Check your network connections and make sure your router (if any) and modem have the current firmware versions.
*Make sure no firewall or antivirus programs are running in the background...
*...as well as any P2P or downloads...
*...and other programs that might steal bandwidth, e.g., instant messaging apps, IE/Firefox, etc.
*Turn off VoIP if not using it, and do not use EAX unless you have a totally kickass sound card.
*Use the SettingsManager.floatSet GSDefaultLatencyCompensation command in BF2 console.

If you're reasonably sure your hardware is fine, and are still getting mucho connection problems, you just might need to uninstall and reinstall BF2.  Before starting, be damn sure you can reinstall it afterwards--in other words, if you're messy like I am, spend 20 minutes or so to locate the complete set of Install discs and the manuals so you can provide the CD-keys when asked.  Now then, here's the procedure I used:

1) From the Control Panel's "Add and Remove Programs" utility, uninstall BF2 (this will take care of Euro Force if you have it too) and Special Forces (if applicable).  If you're running 1.2 or later, the Uninstall program will allow you to keep your profiles and server prefs on the drive--do so, since you're reinstalling anyway.
2) Defragment your hard drive!  I can't stress the importance of this enough.  (Right-click on your System drive in My Computer, go to Properties, and choose "Defragment Now" under the "Tools" tab.)  You will need to have 15% free space if you want it to have any effect (~6 GB of free space per 40 GB of drive size).  If you don't have enough, delete some pr0n.  Expect this to take about 1 minute per gig of crap on your drive (at least on my pokey 5400 rpm IDE piece of crap).
3) Once the defragging is done, reinstall BF2.  You will be prompted to install GameSpy and register, etc.  You don't have to (especially if you already did the first time around).  DirectX 9.0c will "update" (even though DX9.0c is still the current version--don't worry about it).  Then you will be told to restart, but don't.
4) If you have Special Forces, reinstall it now.  BF2 will be patched to 1.1 (useless, and it takes a while too, but there's no way around it) and then the SF expansion will install.  Again, you'll be offered GameSpy and registration (skip it) and a restart prompt.  Don't do that yet, though.
5) Now then.  At this point it gets a little different.  If you have Euro Force and/or EA Downloader, open it now and download the Full BF2 1.22 patch (about 350 MB, or 30 minutes on a T1).  If you don't have EA Downloader, get the Full BF2 1.22 patch direct from EA's website or from the bf2s files!  Once you got it, install it.
6) After patching (if applicable) install Euro Force.  Euro Force won't work on anything less than BF2 1.2; that's why you patch first.
7) NOW, restart, finally (by not doing so earlier you saved as many as 3 restarts).
8) Run BF2 to make sure everything went through okay.  Enjoy your connection-problem-free BF2!

Obligatory Disclaimer:  I accept no responsibility should you completely hose BF2 and/or your hardware by following this walkthrough.  I don't see how that could happen, but I shield myself from it nonetheless.  Furthermore be advised this may not solve your connection problems, especially if your hardware is really the culprit--all I can promise is that it worked for me, and I tried every other hardware and software solution I could find.

With that said, hope it works for you too!  No more trying to knife someone and ending up shotgunned at point-blank from a connection problem!

Last edited by [QXJZ]Capt_Kefra (2006-04-18 21:06:21)

Landepaukku
Finnish bush-man
+23|7307|Finland
Nice guide for a little something else this time!

Although i rather seldom get connection probs this will definitely help the ones that have them.
Friluftshund
I cnat slpel!!!
+54|7183|Norway
Nice!

Especially the firmware bit on the router - havn't seen that suggested before..

[QXJZ wrote:

Capt_Kefra]
*Use the SettingsManager.floatSet GSDefaultLatencyCompensation command in BF2 console.
Perhaps not wanting to appear like you have re-invented the wheel or something? But I don't know about this one, so perhaps you'd like to include it in the guide?
What does it do, and how do you change it/mess with it?
polarbearz
Raiders of the Lost Bear
+-1,474|7259|Singapore

Sometimes its the ISP that sucks.
[QXJZ]Capt_Kefra
Alright, you're good to go!
+124|7198|Honolulu, HI

Friluftshund wrote:

Nice!

Especially the firmware bit on the router - havn't seen that suggested before..

[QXJZ wrote:

Capt_Kefra]
*Use the SettingsManager.floatSet GSDefaultLatencyCompensation command in BF2 console.
Perhaps not wanting to appear like you have re-invented the wheel or something? But I don't know about this one, so perhaps you'd like to include it in the guide?
What does it do, and how do you change it/mess with it?
This was mentioned in another thread a week or two ago.  Technically I'm not sure how it works, and be advised it's not meant to remedy the "There is a problem..." messages.  But some people said it reduces "jitter" or minor lag and most agree that it really does work.

Anyway, the GSDefault LatencyCompensation command, as the name suggests, compensates for a high-ping.  You know, when you're sniping and you'd swear the crosshair was right on the guy, but you get a puff of smoke, or you're in the middle of a knife fight and the guy knifes you from 10 feet away?  That kind of ping-related stuff.

So how it works is, you bring up the BF2 console (hit tilde) and type:

Code:

SettingsManager.floatSet GSDefaultLatencyCompensation #.##
and hit Return.  A response of 1 means BF2 understood the command.  If you get a 0, check the spelling and try again. (Note the spaces, you do need to type them, even if it doesn't look like they're showing up in the console.) The # signs are for your ping.  I'm quite sure it's in tenths of a second, so for instance if your ping is 150 you would put 1.5 or 1.50, and for a 75 ping you'd use 0.75.

You're free to try it out, and (WARNING) I'm not really sure if the above is entirely accurate.  You might need to actually put 0.15 for a ping of 150--all I know is, when I use 1.5 (for a ping of 150) my bullets seem to land way more often.

Try it, see how it goes!
[QXJZ]Capt_Kefra
Alright, you're good to go!
+124|7198|Honolulu, HI

polarbearz wrote:

Sometimes its the ISP that sucks.
Agreed.  If you suspect your shitty ISP to be at fault, test your connection with a bandwidth benchmarking utility like www.numion.com.  Their SpeedTest checks your download and upload speeds (and also calculates your actual web-surfing speed by downloading banner ads from websites).  If you're paying for a 256 kbps cable modem but Numion says you can only download and upload at 100 k max, well, an angry phone call or two is in order, eh?

(Side note: Numion said I upload and download at ~600 kbps so I figured, for once, my ISP wasn't to blame.)

Edit: sorry for advertising--I know it sounds like I'm in Numion's pocket. (I'm not, for the record.)

Last edited by [QXJZ]Capt_Kefra (2006-04-19 05:14:53)

[)r@ke
Member
+16|7122|Indiana

polarbearz wrote:

Sometimes its the ISP that sucks.
Oh man, as soon as I saw this, I was rolling my eyes, thinking "yeah.... Comcast sucks sometimes..."

They suck, but I guess they're better than nothing -- since they're the only non-DSL service provider in my city.  And the only non satellite TV service provider in my city...  Gotta love being stuck somewhere with no competition for the nation's largest provider.  I'm getting in hard in my rear every time a bill comes in the mail -- just cuz they can since they have no competition.

Board footer

Privacy Policy - © 2025 Jeff Minard