Constantly losing connection in the middle of a game.

[Mariospeedwagen]

This started a month or two ago. Sometimes it's 5 minutes in, sometimes it's an hour, but it happens every day and usually multiple times. This makes the game essentially unplayable. I went as far as reformatting and going back to XP Pro from Windows7(for this and some other unrelated reasons). Still having the same problem. I have also uninstalled BF2/PR multiple times to try and fix this. The only thing I can think of that would cause such an odd problem is that BF2 is installed on the storage partition of my hard drive, rather than the system partition.

Note: I am losing connection to the server, NOT crashing to desktop. And yes I have tried running as admin.

Specs:
Geforce 8800GTS
Athlon X2 4800+
I wanna say 4GB memory?
Windows XP Pro

[SnipeHunt]

I've got this and I think alot of people do. I think it is a problem with PR. I have a very fast/good internet connection so I know it is not my connection that is causing the loss. Some times it happens just a few minutes in, sometimes not at all.

I have noticed it seems to occur mostly, if not exclusively when the server is full.

WIN7 64bit
GTX460
8GB DDR2
Quad Core @ 3.0Ghz

[IINoddyII]

I think it is a problem with PR.

Have you tested on vBF2 ?

My understanding the issue was that this was a punkbuster update causing the problems - not specifically anything to do with PR.....

Refer to this thread for instructions to create a log file of the error and submit a ticket to evenbalance to investigate.

[SnipeHunt]

Have you tested on vBF2 ?

When was the last time you fired up vanilla?

"Join a PB server, and drop the console with ~, then type
pb_logtofile 1
and then
pb_writecfg

This one?

I updated punkbuster to see if that is it. The thread you posted does not fit my particular siuation. I just get "connection to server lost" nothing about packet loss.

[Psyrus]

Swap routers with a friend for a few days [different brand/model] and see if it fixes the problem.

[SnipeHunt]

does not, bypassed router and went modem --> PC and still get it.

[Psyrus]

does not, bypassed router and went modem --> PC and still get it.

And the modem is not the problem, either?

[SnipeHunt]

I have not swapped it to be sure, but highly doubt it. it is fairly new motorola surfboard cable modem, good quality, error logs don't show any problems, all of my hardware plays other games without fault.

Also this specific problem is fairly widespread and fairly commonly heard about ingame.

[Mariospeedwagen]

I think I saw in another thread that people aren't updating their vBF2 to 1.5 and just leaving it at 1.41. Is that how we SHOULD be installing or did I read something wrong? Because that could be the problem. I guess.

[Psyrus]

I think I saw in another thread that people aren't updating their vBF2 to 1.5 and just leaving it at 1.41. Is that how we SHOULD be installing or did I read something wrong? Because that could be the problem. I guess.

No, what you misunderstood is that you can't patch straight to 1.5

You have to:

1. Install BF2
2. Patch to 1.41
3. Patch to 1.5
4. Install PR parts 1, 2 and 3
5. Load up VBF2 and login to a profile to create the appropriate settings' files
6. Load up PR & play

I have not swapped it to be sure, but highly doubt it. it is fairly new motorola surfboard cable modem, good quality, error logs don't show any problems, all of my hardware plays other games without fault.

Also this specific problem is fairly widespread and fairly commonly heard about ingame.

And if you'll notice my join date, I've been playing the "help other people troubleshoot their issues with PR" game for quite some time and have a fair amount of experience with the various issues (1, 2, 3). The steps in which to isolate the issue are pretty much as follows (in descending order if the previous step didn't work):

1. Check if router/modem is the issue (includes forcing a wired connection if currently using WiFi)
2. Check if any user-end firewall/antivirus programs are installed and conflicting
3. Ascertain if the problem can be consistently reproduced, thus narrowing further troubleshooting options, for example:
   • Trying PR on other computers on the same internet connection to eliminate the ISP/connection as a source of the issue
   • Checking if it happens in VBF2 as well (like Noddy said)

I'm not on board with it being a punkbuster issue though, but I never like to rule anything out 100%. Hell, you might've angered an ancient Incan monkey god and it's throwing ectoplasmic fecal matter at your server connection at random times, causing you to disconnect - but those kinds of solutions should be kept to the bottom of the troubleshooting list, imo.

[SnipeHunt]

• Check if router/modem is the issue (includes forcing a wired connection if currently using WiFi)
• Check if any user-end firewall/antivirus programs are installed and conflicting
• Ascertain if the problem can be consistently reproduced, thus narrowing further troubleshooting options, for example:
  • Trying PR on other computers on the same internet connection to eliminate the ISP/connection as a source of the issue
  • Checking if it happens in VBF2 as well (like Noddy said)

I'm not on board with it being a punkbuster issue though, but I never like to rule anything out 100%. Hell, you might've angered an ancient Incan monkey god and it's throwing ectoplasmic fecal matter at your server connection at random times, causing you to disconnect - but those kinds of solutions should be kept to the bottom of the troubleshooting list, imo.

I am trying to keep note if this is happening on full servers consistently. I am not 100% sure, but getting there.
Gonna try the logfile to see if that picks up anything.
That seems like the most logical troubleshooting step::



Thanks for the assistance Psyrus and Noddy, but I unintentionally hijacked Mariospeedwagen's thread by putting in my .02 that I am also experiencing the same problem he is... Perhaps troubleshooting steps should be directed to him before me.

[Psyrus]

Thanks for the assistance Psyrus and Noddy, but I unintentionally hijacked Mariospeedwagen's thread by putting in my .02 that I am also experiencing the same problem he is... Perhaps troubleshooting steps should be directed to him before me.

Who they're addressed to hopefully won't matter

Both of you are experiencing the same (seemingly, at least) issue, and the troubleshooting steps are the same regardless of root cause (as of yet, unknown), so it shouldn't make a big difference.

I hope we can get to the bottom of it.