1.03 Bugs

[Towie]

Re: 1.03 Bugs

The commurose dont work when you move, same thing with the minimap Zoom. it really sux when you run to hide from armour and you spot it and what happens is that you fire at it....

[[SAJ]Sentinel]

Re: 1.03 Bugs

- There is nowhere mentioned how to search for partial server names. After some trial&error and SQL knowledge I tried "%" as a placeholder and succeeded.

You serious? They accept % and they seemingly process it?

Can't wait to see if people will have fun with SQL injection (they probably already did, I guess).

[BarkingSquirrel]

Re: 1.03 Bugs

"new EA Message"
- A blank window with 2 buttons that basilc dont tell the user anything about whats going on.
- Clicking the open button caused BF2 to crash and opend the Internet Explorer. Im using FireFox, it is set as the default handler for the http protocol and html files. There is no reason to start MSIE.
- The opend site does not exist .. in fact you get a 403 Access Denied

Apparently they've changed the page. I just told it to view the message, and it opened http://www.eagames.com/official/batt...yupdate_093005 It still pops up the next time you run BF2 though, so ASE still won't work.

[imported_Psycho]

Re: 1.03 Bugs

Theres a fat ass space of nothing at the west of dalian plant and if you fly over it you die instantly what ever height you are at

When you write a message with the letter E at the end of it you still exit the vehicle think the idiots could have fixed that.

[Keith Maniac]

Re: 1.03 Bugs

"new EA Message"
- A blank window with 2 buttons that basilc dont tell the user anything about whats going on.
- Clicking the open button caused BF2 to crash and opend the Internet Explorer. Im using FireFox, it is set as the default handler for the http protocol and html files. There is no reason to start MSIE.
- The opend site does not exist .. in fact you get a 403 Access Denied

This has got to be THE most useless feature EVER added to any game. Now the link actually works and it takes you to official Battlefield 2 website and there you can read that the 1.03 patch is out! BOO'****ing'HOO thanks for the info!

What's the point of having an "EA Message" in the game when in order to read that message, you actually have to quit the game?! WWW-is for those ******** messages, not the game.

I'm not sure is this new "EA Message" to blame for ASE not working again, but that is the case now. In 1.02, ASE worked just fine, now they decided to **** it up. Does DICE think that most of the BF players are 12 year old kids (=gamespy users) who can't use ASE because it's so complicated program? Doesn't anyone in DICE use it? Seems to me that they don't play this game online at all. That would explain NOTHING done with bunnyhopping & diving in air..

... WTH where those "testers" doing the past month?!

Everything else but the actual testing? :)

[benicuuur]

Re: 1.03 Bugs

I've got the "Your cd-key is not valid" bug too.
(The patching was not easy, the same "patching failed" message appeared as the past patches. I installed in safe mode, and it worked.)

Ok, I deleted the whole game, reinstalled it to it's original install directory. I found a few servers, that still runs 1.00, and my cd-key was ok, the map loaded.
Exit --> Safe mode --> 1.03 patching --> try connect to a server --> "Your cd-key is not valid"

WTF????? I've got original BF2.
If anyone knows the solution, please share it.

Someone told before that this problem can be handled, by running a file, bfcdkeycheck, or something like this, but I couldn't find it, even if I searched my entire hard drive including hidden directories...

[DrunkenPirate]

Re: 1.03 Bugs

Mines.

They can be destroyed just by shooitng at them apparently, anything that is explosive will remove them, grenades, SABOT rounds, Stingers, even the BH minigins.

:|:

[BurnTheWeed]

Re: 1.03 Bugs

Repetative sound bug (since ver. 1.00) still happening. I wrote a thread about it here:

http://www.totalbf2.com/forums/showthread.php?t=34238

[F-1]

Re: 1.03 Bugs

selecting the "Not Full" check box while browsing for a server wil cause the game browser not to show any server. uncheck the "Not Full" oiption and you will see alot of servers that are not full. It was working before the patch and now it is broken.
Everyone already noticed this, but the filters now in the game browser are not working. they used to work before the patch.

My guess is that DICE did not include the 1.02 patch in 1.03.

[maverick1970]

Re: 1.03 Bugs

"new EA Message" - A blank window with 2 buttons that basilc dont tell the user anything about whats going on. - Clicking the open button caused BF2 to crash and opend the Internet Explorer. Im using FireFox, it is set as the default handler for the http protocol and html files. There is no reason to start MSIE. - The opend site does not exist .. in fact you get a 403 Access Denied !

I am having a problem with the new message window due to the fact that I use Gamespy and Xfire to connect to servers. For those that use the two applications know, all you do is double click on the server you want, the game loads, and you then select your account once in the game.

From this point BF2 would usually start to connect to the server that I selected from Gamespy or Xfire, but now the stupid message from EA pops up and is preventing me to connect.

[Shad_Blunt]

Re: 1.03 Bugs

Went to take a control point last night.
We had used a jeep to get there, wife was in gunner position I was standing beside it with flag between us.

A group of 3 enemies rounded a bunker in another vehicle and hit OUR jeep. Both jeeps explode.

My wife gets 3 kills on the enemy and A TEAMKILL for me.
This was fixed?
No.. EA, it wasn't.

[BurnTheWeed]

Re: 1.03 Bugs

selecting the "Not Full" check box while browsing for a server wil cause the game browser not to show any server. uncheck the "Not Full" oiption and you will see alot of servers that are not full. It was working before the patch and now it is broken.
Everyone already noticed this, but the filters now in the game browser are not working. they used to work before the patch.

My guess is that DICE did not include the 1.02 patch in 1.03.

yep, I've got the same problem. :hmm:

[5by5]

Re: 1.03 Bugs

Having left EA's employ in 1999, it's sad to see that nothing's changed in Product Development... It's a simple patch guys... Nice job. SPOODY_STRUCT strikes again!!!

Anyways I've found since 1.03 the invalid CD-Key issue is almost as annoying as the programmer commenting when I plug my ZBoard in and auto launch "BF2.exe +menu 1 +fullscreen 1"
-----
Error! Shaders/StaticMesh.fx not found!!!_DO_check your working directory_AND_sync your shaders folder before calling upon your local rendering programmer / GP. (really!)
-----

GP - Are you DFWMIFV??? If so, I'd suggest a new line of work...

Again, nice job guys and I can't wait for 1.04

[sT0nY]

Re: 1.03 Bugs

my game
works 100%
i got a pimped out computer though 3.4 ghz proccesor 4 gb-ram radion x800
but sometimes my game just crashed to desktop without warning me. i hate when it happens..

[DakotaDoc64]

Re: 1.03 Bugs

I still get rebooted every time I attempt to join a PB enabled server, been fighting this for a month now... updated PB, didn't help a bit.

I give up.

I had this problem with 1.02 and previous. Do you or did you have an Iomega Zip drive and drivers installed on your system?

Search the forum for this problem.

1. I have noticed a bug with the browser. If I have "same version only" and "ranked servers only" and select any other option on the left I get zero servers. If I unselect the two above and select each option one at a time, each option works. But as soon as I add "same version only" I get a blank server browser.

2. Adding clan tags as reported here already. Found that out immediately. The tag sticks but does not show when re-logging in. To remove the tag you have to enter somthing (anything) and backspace over it. Then log in and it is gone. Or find the file were this information is stored.

3. Immediate crash to desktop when selecting new unlocks. Got three but game CTDT every time I unlocked a weapon. Anyone else have this problem?

4. Friendlies in IGLA missle sites show up as an un-X'd box as an enemy.
This at least in Wake Island. I was really getting tired of TK'ing this poor sack.

5. Blowing up enemy artillery on Wake Island (near airstrip) when airstrip has been captured to USMC team gets you a "team vehicle damage" warning not points for destroying enemy commander assets.