Project Reality Forums

OKay guys so i did the following and it WORKED search run then browse "C:\Program Files (x86)\Project Reality\Project Reality BF2\mods\pr\bin\PRLauncher.exe" +join 64.237.49.109:17567 Mkae sure you put the +join at the end of the run exe then login and after the intro you will get a brief green screen and you will come up to the main menu

Deadmanfoot wrote:OKay guys so i did the following and it WORKED search run then browse "C:\Program Files (x86)\Project Reality\Project Reality BF2\mods\pr\bin\PRLauncher.exe" +join 64.237.49.109:17567 Mkae sure you put the +join at the end of the run exe then login and after the intro you will get a brief green screen and you will come up to the main menu

Didn't even get in the intro.

Good Evening,

Now this is priceless comedy. This guy comes in and posts this like he found the workaround when I posted the below quite a few hours ago. ??:

RAWSwampFox wrote:Good Afternoon,

Well, I think I found a workaround. Create a shortcut for PRLauncher on your desktop and change the command line to look like the following:

"C:\Program Files (x86)\Project Reality\Project Reality BF2\mods\pr\bin\PRLauncher.exe" +join 64.237.49.109:17567


The important part is the: +join 64.237.49.109:17567

If you get a 1005 error, try again and it will usually launch. You will receive a message when you launch about not being able to read the server but you can go to Deployment mode and select which server you want.

The IP address above is for the HOG server.

I'm loading Saarema right now.

But then again I could be totally missing it. JUST TOO FUNNY

Deadmanfoot wrote:OKay guys so i did the following and it WORKED search run then browse "C:\Program Files (x86)\Project Reality\Project Reality BF2\mods\pr\bin\PRLauncher.exe" +join 64.237.49.109:17567 Mkae sure you put the +join at the end of the run exe then login and after the intro you will get a brief green screen and you will come up to the main menu

Good Evening,

One thing that I have noticed is that most of the European servers are up and functional, fully pop'ed and have been all day.

RAWSwampFox wrote:Good Evening,

One thing that I have noticed is that most of the European servers are up and functional, fully pop'ed and have been all day.

Noticed that too. One guy (canadian) said that he get the error but a friend in Netherlands can play

RAWSwampFox wrote:Good Afternoon,

Well, I think I found a workaround. Create a shortcut for PRLauncher on your desktop and change the command line to look like the following:

"C:\Program Files (x86)\Project Reality\Project Reality BF2\mods\pr\bin\PRLauncher.exe" +join 64.237.49.109:17567


The important part is the: +join 64.237.49.109:17567

If you get a 1005 error, try again and it will usually launch. You will receive a message when you launch about not being able to read the server but you can go to Deployment mode and select which server you want.

The IP address above is for the HOG server.

I'm loading Saarema right now.

how do i change command lines?

Good Evening,

Create an extra shortcut so you don't mess with the original.

Right click
Properties
Put the +join ######### at the end of the long line that fills up the "target" box.

Hope this helps.

@RAWSwampFox

Your solution worked for me, but only once. The second time I tried to launch the game I was back to the same problem and CTD. From what I see, as some of you pointed out, those of us on this side of the ocean are having problems, while Europe is fine. We'll just have to see what happens.

Nakata wrote:Noticed that too. One guy (canadian) said that he get the error but a friend in Netherlands can play

Portuguese - BR

Tambem estou com o mesmo problema !

English - US

I have same problem !

i just forgot to give credit to swamp but you didnt really explain the command line thing so doing it through run was just easier guess you cant help out without people being mean

RAWSwampFox wrote:Good Evening,

Now this is priceless comedy. This guy comes in and posts this like he found the workaround when I posted the below quite a few hours ago. ??:



But then again I could be totally missing it. JUST TOO FUNNY

does giving credit mean that much?

Good Evening,

I just thought it was hilarious. The wording just struck my funny bone.

I'm "glad" I haven't been the only one having this issue. At first I thought it was b/c Win7 had an update that I installed w/o seeing what it was, but I checked to roll back and they were all for MS Office.

RAWSwampFox, your solution works for me, but it still crashes on new map load.

From skimming over a few of the earlier posts, it seems the Devs are not yet sure what the cause is, but it probably is on the server end.

I doubt they would even read this thread, but is anyone having no issues logging in at all?

RAWSwampFox wrote:Good Evening,

Now this is priceless comedy. This guy comes in and posts this like he found the workaround when I posted the below quite a few hours ago. ??:



But then again I could be totally missing it. JUST TOO FUNNY

I can confirm this fix does work! I'm in HOG currently with 50 other people. Simply change command line on a 2ndary shortcut and it will load. Great fix Swamp!


First time login to the site in years.... look join date wow

Can't play, in NZ.

DerelictMonster wrote:Having same issue. Not so tech savvy either. I guess I will wait for a solution. I appreciate any one's feedback. I did a fresh install and update of PR. Still same issue.

Same here.
Played no problem up to yesterday night. Today I either get:
1005: Error receiving from server. (10054), or
get past that but CTD before main ingame menu arrives.

fresh install and update.
I did save and reuse my ProjectReality folder in documents folder

same issue(s).

Edit: random luck? or the problem is over? I finally got thru to main menu and was able to join a server. Must have been because I posted here ........

Edit2: CTD after each of two rounds, able to get back on after multiple attempts with varying levels of progress.

Edit3: a day later (~24 hours) the game seems to load and run (and crash) about the same as it usually does. Maybe the three insta-CTDs I experienced are nothing unusual, just me being hyper-sensitive. Or maybe the inst-CTDs are a bit more often than "usual".

So resolved for this user (unless some of those long eixisting abrupt CTDs can be addressed).

A buddy from the UK was able to log in fine, everyone including me (North America) had the crash after intro.

Me too will try direct to my local Pacific server below

Same here. ((((((

I had no problems playing today, guys. Only tried once, though. Can everyone confirm it's been fixed for you as well?