Project Reality Forums

Okay I had another RenDX9.dll file dated 9/8/2009 3:08AM of 2,496KB (2,555,392 bytes) and it works. I checked again and that indeed was the file you sent me so my brain must be fried on too much of that incredible FH mod along with a high dose of PR mod. Sorry. Hope this helps someone out there with similar problems googleing these forums. The RenDX9.dll file dated 9/7/2009 2:12PM file doesn't work (for me).

Your right, sorry for my "pissy" attitude. This issue just peeled back some skin from back to EA/DICE "patch" days...

Thanks Snares for putting this up. And another thanks to the DEV's.

DDS

Snares wrote:I suppose it is kind of a "problem" in the sense PR must adapt to said "fix," but I'm not really too mad at EA right now. The original alt-tab problem was EA's, but the hotfix, in itself, is not. EA is not responsible for PR's specific MD5 check lists. I'm just really grateful that DICE was kind enough to do anything about it at all.

Soppa wrote:Actually I found this renaming method for avoid being kicked because using largeaddressaware patched bf2.exe here: https://www.realitymod.com/forum/f370-pr-tech-archives/56529-solution-vista-64bit-2gb-memory-crash-desktop-issue.html

I cant see any reason why this wouldnt work for other files too. You wont get kicked or banned by PB. Method is ugly but its workaround for sure.

Reason why you can get error message of locked files is because you are trying to overwrite them. You should rename files .old before "replacing" with original files, that way you cant get error messages of locked files.

NOTE: There could be little risk if PB is updated to check files MD5 sum's and keep some kind of history of em. This could be good update tho because this copying method makes whole PB quite useless

[FIN] SOPPA

Well PB is still quite useful. This is just one of many methods to check the general state of your game installation. PB knows just as well as we do that this method isn't very effective; their main tools are memory scanning, which is much, much more effective at preventing hackers. Honestly I think PB MD5 checks should be changed anyway. If you go into a server, press ~ and do pb_logmd5tool. You will notice that the servers that log file checks have many more random fps spikes than the ones that do not.

On a side note: I recommend trying BF2 without the largeaddressaware patch. The 1.5 patch has supposedly included a feature that allows BF2 to use more than 2 GB of ram. If you still need to use this method, here's an easy way to do it:

1: Make a copy of the original (and unmodified!) BF2.exe, and name it BF2_fix.dll.

2: Make ExeBFStart.bat, and put this into it: 3: Make ExeBFMainMenu.bat, and put this into it: 4: Before you start the game, run ExeBFStart.bat, and when you're at the game's main menu, run ExeBFMainMenu.bat. You cannot accidentally mess up the file names, so if you run it in reverse order, the only effect will be that you will be running on the unpatched BF2.exe, and you will still get kicked by the MD5 check. Simply restart the game and run the BAT's in the correct order, and you will be good to go.

Ok, is this fixed somehow? Because I am getting this in Vista 64 bf2 1.5 PR

lbgspam wrote:Ok, is this fixed somehow? Because I am getting this in Vista 64 bf2 1.5 PR

Is it a RendDX9.dll md5tool error? If so, you need to make sure you have the latest official hotfix installed: TV2 - Battle.no Portal - av spillere, for spillere If you do and it's still kicking you, then you probably have a different issue.

OK.The downloads are not thereAnd i cant try with them.
But i did too the .Bat things and it didnt help me.
I get kicked all the time..

do i realy have to not play anymore?
because its realy frustrating to get kicked 90% of servers!

The Project Reality installer asks you if you want to apply this if you have not got it installed. If you chose no, but now you want to install it, you can find the required .dll file in /mods/pr/readme/extras

I'm getting a RendDx9x2.dll MD5 kick. Should I modify the DxBfStart and DxBfMainMenu .bat files accordingly?

Another thing: My installer place is Program Files (x86). Should I put that space between the x86 and the word Files, or should I delete the space?