Hello All,
Fist let me say I love playing Project Reality a great deal, which is why It's finally come to making this post...
Please bump this thread if you are one of the many who are consistently kicked from servers for a MD5 mismatch on your shaders. I know I probably won't get many bumps, since most players have abandoned PR due to this because the devs can't/won't fix it. I understand wanting to prevent cheating, but there has to be a certain point where you admit something isn't working, and look into doing it some other way.
I've followed all the necessary steps, scoured the forums and done everything suggested, but it just doesn't work guys. I just got an entirely new computer with no matching hardware and still get this error more often then not. Why can't it just work? Really?
So bump the thread if you feel my pain and maybe we can convince the devs to investigate an alternate way to simulate "suppression"
Thanks
Lets Start a Petition
-
Raic
- Posts: 776
- Joined: 2007-02-24 15:59
Re: Lets Start a Petition
the MD5 check kicks are coz of files not matching. So either you have edited them, cheating, or have somehow installed wrong. And the MD5 checks are done by PB. And you say "many" have problems. Haven't seen that many posts about it 
-
SevenOfDiamonds
- Posts: 215
- Joined: 2006-06-12 17:26
Re: Lets Start a Petition
I heard that if you start PR through BF2 (not from the PR icon start) you can have those problems. So if your not doing that and it still happens, reinstall I guess.
"They can also be used to provide public service messages: stay away from munitions; units are coming through; stay off the streets because the armored vehicles are dangerous.”
-Scott R. Gourley
-Scott R. Gourley
-
Rudd
- Retired PR Developer
- Posts: 21225
- Joined: 2007-08-15 14:32
Re: Lets Start a Petition
Dice keeps releasing new files, e.g. the md5 hotfix. (btw you're gonna need that)Why can't it just work? Really?
This means that PR servers need to be updated to mirror these changes.
The DEVs have released the necessary files to PR license holders. <- Ie...they've fixed it.
OMG DEVS YOU BROKE IT!!!!I know I probably won't get many bumps, since most players have abandoned PR due to this because the devs can't/won't fix it.
Its up to the Server Admins now to appy the necessary files, and up to the players to ensure they have the most current patches and fixes for both BF2 and PR.
-
DesmoLocke
- Posts: 1770
- Joined: 2008-11-28 19:47
Re: Lets Start a Petition
No petition needed. This probably needs to be in the PR Support sub-forum.
It sounds like he is one of the unfortunate few who can't get his game to work or he regularly plays on a server that hasn't updated to the latest MD5 hotfix?
It sounds like he is one of the unfortunate few who can't get his game to work or he regularly plays on a server that hasn't updated to the latest MD5 hotfix?
It's up to the Server Admins now to apply the necessary files, and up to the players to ensure they have the most current patches and fixes for both BF2 and PR.
-
CodeRedFox
- Retired PR Developer
- Posts: 5919
- Joined: 2005-11-08 00:47
Re: Lets Start a Petition
a Petition.....really? We are not some company that doesn't have or want to spend the money to fix something until the paying users demand a fix. We do this on our spare times and sometimes its doesn't always work. And besides what Dr2B Rudd said ever think it could be your computer? This is a big reason allot of game end up going to console. Too many variables to fix and check...then double check...and triple check when the user is the one with the issue all along.
And if you think its some kind of thing we don't care about, Dev's get the MD5 problem too. Difference is we normally figure it out by talking it out and sometimes reinstalling it.
Closed as this issue doesn't need a petition, keep asking around and testing until you get it right. I might be something as easy as cleaning a cache to your hardware drivers just dont work. I know it can be a pain, I've suffered them as well. But through trial and error I found my problem....which ended up being a local issue only.
And if you think its some kind of thing we don't care about, Dev's get the MD5 problem too. Difference is we normally figure it out by talking it out and sometimes reinstalling it.
Closed as this issue doesn't need a petition, keep asking around and testing until you get it right. I might be something as easy as cleaning a cache to your hardware drivers just dont work. I know it can be a pain, I've suffered them as well. But through trial and error I found my problem....which ended up being a local issue only.

"apcs, like dogs can't look up" - Dr2B Rudd



