Project Reality Forums

I had the packet loss kicks before trying your fix, and nothing changed after applying your fix.
I tested it out by seeding a server for about 2 hours while I was AFK, when I got back I was kicked out of the server with the losing keypackets message.

DonDOOM wrote:I had the packet loss kicks before trying your fix, and nothing changed after applying your fix.
I tested it out by seeding a server for about 2 hours while I was AFK, when I got back I was kicked out of the server with the losing keypackets message.

Yeah this isn't meant to fix that anyway, and besides... pretty sure that's not a punkbuster issue to begin with... but I have no authority on the matter

Ah okay I misunderstood, I thought it was meant to fix both of the issues. Great job with fixing the initial join issue, it was definitely one of the more annoying bugs.

I get to dropbox fine but when I click the link I get the option to run or save when I click save i get a message " could not download ... "

Never mind I got the fix from a friend and it works a treat, thanx

ukVandal wrote:Never mind I got the fix from a friend and it works a treat, thanx

He called me "Friend" should I be worried.

Thanks OP nice fix and a new friend!

This works and I hope more people will see this.

Also, I found an alternative (but not very good way) to avoid the problem. I found that if I tether my phone to my laptop and use the phone's 3G as my internet connection, I won't get the error. However, I do get 180-200ms ping so its not really worth it.

Sorry, it didn't work for me.

Your PB archive is just a downgrade to the previous PB client version 2.241.

With this old version I didn't get disconnected initially, but after some minutes in game I had "connection lost", no pb error messages. Tested on serval servers. pb_sleep didn't matter.

When my client got updated to the lasted version 2.306, the usual bad behavior was restored.
(initial disconnect, proper game).

TeRR0R wrote:Sorry, it didn't work for me.

Your PB archive is just a downgrade to the previous PB client version 2.241.

With this old version I didn't get disconnected initially, but after some minutes in game I had "connection lost", no pb error messages. Tested on serval servers. pb_sleep didn't matter.

When my client got updated to the lasted version 2.306, the usual bad behavior was restored.
(initial disconnect, proper game).

Strange, it's still working for me

To your information,

It is a PB problem, I talked to BloodyDeed several times, we did some tests and can reproduce this problem without any Mod. If you update your BF2 to 1.5 with the Alt Tab fix and then use the update tool from PB the problem with the first disconnect shows up.

Last week PBs website and server was down for a few hours, voila, no problem.

It's sad that noone from evenbalance can fix these two problems.

Regards

Stickied

It's sad that noone from evenbalance can fix these two problems.

I would rather say they ignore it because its BF2.

its a nice fix tho and I have to try it sometimes

So do I understand correctly that this workaround just involves using an old version of PB?

Doesn't PB auto-update though and won't it kick me if I'm using an outdated version, as surely it needs to be kept up-to-date to prevent hackers using cheats and loopholes in old versions that have been plugged since?

doveman wrote:So do I understand correctly that this workaround just involves using an old version of PB?

Doesn't PB auto-update though and won't it kick me if I'm using an outdated version, as surely it needs to be kept up-to-date to prevent hackers using cheats and loopholes in old versions that have been plugged since?

Still works to this day. Dunno why, but it works

[R-CON]Psyrus wrote:Still works to this day. Dunno why, but it works

Ah well "Our's is not to wonder why" and all that

This is working great for me on both my PCs. Thanks

This works great. Just tested out moments ago. Awesome.

I uninstalled Punkbuster Service, uninstalled PR, restart, Install PR and during setup, not tick both options of Updating Punkbuster, updating punkbuster via setup and adding Battlefield 2, checking for updates and then run the game as normal.

Run as different profile, and it got fixed!