Project Reality Forums

This is not a technical support issue as it seems from the title. I've seen it a few times now, for seemingly no reason, half of a team will CTD at the exact same time. There seems to be no cause of it that I can identify, so I have no steps on how to reproduce it.

https://www.realitymod.com/forum/f26-pr ... plate.html


You should use some evidential Proof to verify such bugs. I've experienced this but the world doesn't end. and only like 3 people disconnect. Maybe it feels like the server got half emptied out because there were clan members on it...


Try using Templates provided next time.

Try 12 Wilkinson, not 3.

Like I said, there seems to be no cause of it, so I can't exactly use the template.


Don't take your grudges over here next time.

Fighter wrote:Try 12 Wilkinson, not 3.

Like I said, there seems to be no cause of it, so I can't exactly use the template.


Don't take your grudges over here next time.

Grudge? Where is this coming from?

w/e.

Before BF2 1.5 patch, problems like this were symptom of a griefer/hacker causing players to crash. I really hope it's not the case here :/

That usually crashed the whole server tho...

I've also seen cases where if you have the bad language filter on that gives you a personal message when you curse, when they player curses too many times and gets kicked, everyone in their squad CTD"s including the squad on the other team with the same squad number.

I and 2 friends play together regularly, last night, I (I have intel cpu, ati video card) and my friend (amd cpu, ati video card) both crashed, the other guy has a shitty intel cpu, and an old nvidia video card.

There is so much random stuff that can invoke a CTD, a lot seems to be due to memory also so watch that bf2 is not using up all your RAM. Try manually deleting pr and reinstalling to fix any corrupted files.

Guys this is a topic for one CTD issue, not individual ones caused by client hardware.

This appears to be a server-related issue that I described.

thanks for reporting!

please make sure to follow this template when reporting a bug in the future.

If this has not happened more than the one time that it has been reported and can not be replicated then it probably was a server side malfunction.

So unless someone with more information steps forward then there is not very much we can do.