Except it was horribly broken. On this very page you refer to it as a "horrid mess".
Printable View
Except it was horribly broken. On this very page you refer to it as a "horrid mess".
For Special Forces, it was a horrible mess. Firing a Tow would crash a server. That IS a mess. Playing regular BF was not a horrid mess. Sometimes I would encounter a bug. Sometimes I wouldn't. You might have played the game for 20 hrs tops. You only have a little over 3000 points. Why are you suddenly the authority?
Why am I the authority? Because I played 1.2 and noticed my rockets firing through shit, me dying without hearing ANY audible sounds, and getting a massive increase in teamkills (literally triple the normal). One can play a game, any game, for 20+ hours and get a feel for how its supposed to be and notice when something is wrong.
Just like you can blow your load over any crap DICE shits in your direction I can call it shit when its shit. I *HOPE* 1.21 is fixed but if its not the game is getting uninstalled, not that EA/DICE cares they got my $70.
I'm downloading it now from www.bf2s.com
I'll be on Xfire most of Friday afternoon/evening since I'm leaving for spring break on Saturday afternoon.
Just got done playing a couple rounds on Wake Island and it seems as though the red name bug has been fixed. I didn't encounter it once so even though it wasn't mentioned in the patch changes, it seems to have been addressed. Same goes for the rocket bugs.
I may encounter them in the future so I better put this disclaimer up here right now for Diff's sake. It MAY happen, however, I actually tried the game out instead of simply trolling an internet forum and the big problems seem to be fixed.
So I downloaded the 1.2-1.21 patch and experienced some problems, so decided to download the entire 1.21 patch and reinstall both BF2 and SF. The server(s) I usualy play on had yet to update to the new patch, so I was unable to see if the game ran fine on them, but I did play on a 64 man server on Karkrand and the game ran as smothe as I could hope for (albeit on low settings). I'm thinking I may have messed up one of the eariler patchings which caused my game to run poorly, so hopefully now it will play fine. The way it was running earlier, I'd have been lucky to get a kill the entire map. Look forward to playing this online again.
"- Fixed the error in Client - Server communication causing sound, animation and other
sync issues."
I think that is the fix for the AT rockets and of course the silent sounds issue. So in my playtime it appeared fixed. AA seemed weaken again, but not as weak as before 1.2. I'll be playing late tonight if anyone is around on xfire.
My initial thoughts after playing with the new patch for a little while:
It might just be that my connection is being its typical, temperamental self, but the game's latency issues seem to have been slightly curtailed.
The name glitch STILL exists (note: it happened to me once in my two hours of playtime) despite the fact that it has been a notable and aggravating bug since BF 2 first shipped to retail. :wtf:
The PKM needs to be "adjusted for accuracy" in a negative way (a sniper should not be consistently getting out-shot from 200+ Meters).
There should be some way to blow up claymores. I like how I no longer have to worry about TKing idiot teammates, but it's ridiculous that claymores are now completely indestructible. The decrease in deployable claymores helped some, but it’s still way to easy to defend key choke points with a pair of well-placed claymores.
Catch me on Xfire tonight if you want to join up; it’s the last time I’ll be playing until March 20.
You know, for all this name bug bitching - I Think DICE should just go back to the 42/nam style name colour conventions - that is - americans or allies as blue always and mec/china/axis as red always
This is from a BF2 Developer explaining the Red-Name glitch:
The Red/Blue nametag bug is the most complicated issue we have to deal with.
Just to clear up any misconceptions, this is what is occuring.
The server tells the client who belongs to the various teams. Every so often, the client does not recieve the message. We do not know what is the root cause of this issue, or if there is only one cause. From what we have seen, there are potentially many causes.
What we have implemented in 1.2 is a system where the server requests a verification from the client. If the server does not receive this verification, the bug is occurring and the server sends the message again to that client. Obviously, sending messages over and over would be a massive burden, so the server will only try to send this message several times before resuming its normal behaviour. What this does is reduce the occurences of the issue, but it does not eliminate the issue.-------
So what I've heard is that if you encounter it, switching teams fixes it most times. Maybe a re-connect to the server.
I honestly wouldn't mind if they just went back to the old style of BF1942. That would be the easiest, IMO.