BF2 1.5 Alt-Tab Fix Through RendDX9.dll

[=RRF=Rebiv4]

This hotfix is causing MD5 kicks. I deleted PB and reinstalled, still happened.

[Snares]

Originally Posted by =RRF=Rebiv4

This hotfix is causing MD5 kicks. I deleted PB and reinstalled, still happened.

Keep using your bat files, as they will prevent the kick. The reason for the kicks is that Evenbalance probably haven't updated their checklists yet. Make sure you delete your cache as well.

[DDS]

EA games are the most incompetent developers I have ever seen.. release a "fix" that causes problems.. seen this from 1.0 forward.. unbelievable

[Snares]

Originally Posted by DDS

EA games are the most incompetent developers I have ever seen.. release a "fix" that causes problems.. seen this from 1.0 forward.. unbelievable

Well fortunately, this isn't a Evenbalance problem now. PR has to update their own check lists so that they will accept the md5 from this new hotfix. If you go play on a vanilla BF2 server, you shouldn't have any problems.

[DesmoLocke]

Originally Posted by DDS

EA games are the most incompetent developers I have ever seen..

Too bad EA is a publisher and DICE (EA Digital Illusions CE) is the developer.

Since applying the hotfix, I have had no issues with vBF2 servers. However, some of the MD5 checks when in PR servers is still causing a PB kick for some reason.
I suspect EvenBalance to correct it in due time.

[Snares]

Originally Posted by DesmoLocke

Too bad EA is a publisher and DICE (EA Digital Illusions CE) is the developer.

Since applying the hotfix, I have had no issues with vBF2 servers. However, some of the MD5 checks when in PR servers is still causing a PB kick for some reason.
I suspect EvenBalance to correct it in due time.

http://www.realitymod.com/forum/f27-...nddx9-dll.html Please carefully read the first post in this thread to fix the PB kick.

[DDS]

Originally Posted by Snares

Well fortunately, this isn't a Evenbalance problem now. PR has to update their own check lists so that they will accept the md5 from this new hotfix. If you go play on a vanilla BF2 server, you shouldn't have any problems.

\

THe "fix" came from EA Games, not PR. PR must then adapt to said "fix". So yeah this is an EA "problem".

[Snares]

Originally Posted by DDS

\

THe "fix" came from EA Games, not PR. PR must then adapt to said "fix". So yeah this is an EA "problem".

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.

[LMLM111]

Edit: Ignore this post. I made a mistake. Snare's post is correct. I'll leave what I put below but please ignore it.



The original post suggests using a rename method for the .dll files. This is not a good idea because if you accidentally click the wrong .bat file for whatever reason your .dll files could get mixed up.

Instead, use a copy over method from source files which are never changed:

dxbfstart.bat

c:

cd "Program Files\Battlefield 2"

copy RendDX9_hotfix.dll RendDX9.dll /y

DxBFMainMenu.bat

c:

cd "Program Files\Battlefield 2"

copy RendDX9_15.dll RendDX9.dll /y

This way, you can be sure that the right .dll is in place and that the wrong rendx9.dll was not renamed to the wrong source because no renaming is used.

[Snares]

Originally Posted by LMLM111

The original post suggests using a rename method for the .dll files. This is not a good idea because if you accidentally click the wrong .bat file for whatever reason your .dll files could get mixed up.

Instead, use a copy over method from source files which are never changed:

dxbfstart.bat

c:

cd "Program Files\Battlefield 2"

copy RendDX9_hotfix.dll RendDX9.dll /y

DxBFMainMenu.bat

c:

cd "Program Files\Battlefield 2"

copy RendDX9_15.dll RendDX9.dll /y

This way, you can be sure that the right .dll is in place and that the wrong rendx9.dll was not renamed to the wrong source because no renaming is used.

That's incorrect. If you keep RendDX9.dll in its original form, and RendDX9_fix.dll in it's original form, you can never accidentally rename the bat files. Copying takes much longer and creates fragments. Go ahead, try it. Run the bats in the reverse order, do anything you want. It will never mess up. Carefully look at the bat files and you will see why. In the start, you rename one bat file to *_15, and then rename *_fix to *. In mainmenu, the only possibly option is to rename * to _fix. The last line of mainmenu will not work, because the bat file will not rename another file to the same filename. You get

A duplicate file name exists, or the file cannot be found.

and the bat crashes, thereby removing any chance of messing up.