Project Reality Forums

Whenever I attempt to join a BF2/PR server the game immediately CTD's with no error message. Help plox <3

welcome to the PR forums,

[R-COM]LITOralis.nMd wrote:Are you running any type of overlay program? MSI Afterburner, Overwolf, TS3 overlay, RAPTR, etc. All can cause this type of problem.

'[R-COM wrote:LITOralis.nMd;1986764']" "

Have you tried changing the resolution from inside PRLauncher?
Have you tried running in windowed mode from inside PR launcher?

[R-COM]LITOralis.nMd wrote:Have you tried changing the Windows Default Playback and Default Recording devices to something other than your fancy headset and mic?



I think That line of G series headsets usually require some extra steps to get running with PR?

Post some system s specs please: Can you please open PRLauncher,
click Support
click Copy to Clipboard
then paste everything into a reply on this thread.

Thanks.

[R-COM]LITOralis.nMd wrote:You have an overlay program running?
Overwolf, TS3 overlay, Skype overlay, RAPTR, MSI Afterburner, etc, all will cause this type of CTD.
Shut down overlay completely, then try again.

Then, try running in windowed mode, when you CTD in windowed mode it will show a popup window with the error msg. screencapture or write down that error message and post back here.

Just to be clear, in both vanilla BF2 and in PR,
you can launch the game, ?
created an online account, ?
log in to your online account, ?
Can get to the server browser window?
Can see servers listed in the browser window?

IF yes to all of the above, there are generally two common problems:
1. Overlay program is causing BF2 to crash on loading up the game
2. Your firewall/antivirus/router/internal router's firewall is blocking the ports needed to connect to a BF2/PR server.

Seeing as you can not join a vanilla BF2 server, let's use vanilla BF2 to trouble shoot this.


What firewall/antivirus/router/internal router's firewall do you have? Please list them all.

The newest AMD drivers have RAPTR overlay software silently installed ( bloatware IMHO ) and it causes this crash.

The newest Comodo Firewall has a new HIPS detection that is causing this crash.

Post back some info an