Project Reality Forums

Rawkk, could you elaborate what your problem is (even by PM if you prefer it)?

I mean why exactly you can't start the game with the pr.exe file.

Oh and Arn , Did you mates buy Bf2 complete collection on EA download manager?

Do you use a different *.exe then bf2.exe to start normal bf2?

arn354 wrote:Do you use a different *.exe then bf2.exe to start normal bf2?

I'm sure there gotta be a different .exe file as the one from normal CD/DVD version have the disc 'protection'.

I still have the same problem on the Thor's servers : MD5Tool mismatch mods\bf2\shaders_client.zip (len=204 .

Deleted the cache shaders temp files.
Reinstalled bf2... Really don't know what to do now.

How do you start the game?

I suspect you don't use shortcut to pr.exe, right ?

Jagular - would you mind to create post in Private Serveradmin-Section how to enable those checks for all other pr-serveradmins who perhaps don't know how to?

I`ll try my best

There is thread about it already but I made some "comments"

Deadfast wrote:How do you start the game?

I suspect you don't use shortcut to pr.exe, right ?

Thx for your reply m8 :

I'm using a shortcut with this command line :

"C:\jeux\Battlefield 2\BF2.exe" +modPath mods/pr +menu 1 +fullscreen 1 +restart

Mister_RocknRoll wrote:Thx for your reply m8 :

I'm using a shortcut with this command line :

"C:\jeux\Battlefield 2\BF2.exe" +modPath mods/pr +menu 1 +fullscreen 1 +restart

You're welcome.
Besides I think we have a tournament squad in common


Anyway, the shortcut is wrong.
Change it to:

Path:
"C:\jeux\Battlefield 2\mods\pr.exe" +modPath mods/pr +menu 1 +fullscreen 1

Start in:
"C:\jeux\Battlefield 2"

change it to
C:\jeux\Battlefield 2\mods\pr\pr.exe" +modPath mods/pr +menu 1 +fullscreen 1 +restart
working folder (if after changes you got BF2.exe not found)
C:\jeux\Battlefield 2\

argh I`m late

Ok guys, I'll try this : thx for your reply.

I'm sure there gotta be a different .exe file as the one from normal CD/DVD version have the disc 'protection'.

I am aware of your mentioned. I am more concerned that they use perhaps another filename - pr.exe wants to start bf2.exe - if they use in their complete collection bf2full.exe for example, pr.exe will not find the proper file to start bf2.

Don't start BF2 from within the downloader. Use your Desktop-Shortcuts - show me your current bf2 start-up link - which file is the target?

objects_clients.zip mismatch...

damn!

edit: PB update solved it.. NOT

To Deadfast and Jagular :

Thanks a lot guys ! It's working so far ! Big thanks ! I was crying a river before you gave me the solution.

objects_clients.zip mismatch...

damn!

which install? patch or full?
objects_clients.zip is the largest file - probably your harddisk may be fragmented? Defrag and check again.

edit: PB update solved it

Perhaps it comes back - then check above.

It came back indeed, still getting kicked. (I have the patch installed)
Will try a defrag.

in addition it is important if the questioned file was

mods\pr\objects\objects_client.zip

or

mods\bf2\objects_client.zip


I will install tomorrow the previous pr and do a patch-installation. Perhaps there is a slight difference in the patched mods\pr\objects\objects_client.zip - then we have to add a second check to mods\pr\objects\objects_client.zip in pr.md5 .

It's the mods\bf2\objects_client.zip

thats bf2 - nothing with the checks in pr.md5 .

those are additional bf2-checks - reinstall patch 1.41 .

The checks in pr.md5 remain valid.

Bosco, it seems that you have the same problem that Deadfast & Jagular told me :

Look at your PR shorcut it should be something like that :

"C:\games\Battlefield 2\mods\pr\pr.exe" +modPath mods/pr +menu 1 +fullscreen 1 +restart

instead of : "C:\games\Battlefield 2\BF2.exe" +modPath mods/pr +menu 1 +fullscreen 1 +restart

In fact, pb is checking your bf2 directories instead of checking your pr directories : that's why he finds differences...

My shortcut is "C:\Programme\EA GAMES\Battlefield 2\mods\pr\pr.exe" +modPath mods/pr +menu 1 +fullscreen 1"

@arn: Yeah, will try to reinstall 1.41.

edit: Reinstalling 1.41 apparently fixed it