Originally posted by Dangerdog
1.4 Feedback and Error Reporting
Collapse
X
-
Guest repliedRe: 1.4 Feedback and Error Reporting
it's only a part, try to setup a macro and you'll see.. -
Guest repliedRe: 1.4 Feedback and Error Reporting
Bug: Healing while holding shock paddels (i also experientst that in the incremental patch 1.3)
CPU: Amd Athlon 4000 64 bits
GPU: Ati X1600 (or something like that)
RAM: 1.5 Gb
Soundcard: intergadete
Patch Type: incremental
Event:Healing while holding shock paddels (i also experientst that in the incremental patch 1.3)
Source: in game
Reproduced Successfully? - yes
Evidence: WTF is that? :SLeave a comment:
-
Re: 1.4 Feedback and Error Reporting
If that's all the juice a prone spamer can muster then I could live with that. :laugh:Originally posted by strikeagle83edit: video http://media.putfile.com/bf2-14b2-crouch-proning
Mission accomplished DICE, dolphin diving is dead. :salute:Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
my game crashes when its at the black screen when loading up the game..theres no need to post my comp specs it works fine on 1.3 ..i used a full patch too.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
MAKE A DELAY FROM CHANGING FROM AND TO ALL PLAYER STANCES (STANDING // CROUCHING // PRONING)
BECAUSE THE ABILITY TO EXPLOIT INFANTRY MOVEMENT IS STILL POSSIBLE.
-------------------------------
here is a list of the six possible movement patterns which in combination can be used;
prone to crouch
prone to stand
crouch to prone
crouch to stand
stand to prone
stand to crouch
NOT all of these have delays implemented within them, so if you know which ones do not, then you can still exploit your movement excessively.
----------------------------------------
SIMPLY ADDING A FIRING DELAY UPON STANCE CHANGE IS NOT SUFFICIENT.
YOU HAVE ADDED "SOME" STANCE CHANGING DELAYS, BUT NOT ALL OF THE NECCESSARY ONES TO COMPLETELY REMOVE THE EXPLOITATIVE MOVEMENT.
PLEASE ADDRESS THIS, THANKS.
edit: video http://media.putfile.com/bf2-14b2-crouch-proningLeave a comment:
-
Re: 1.4 Feedback and Error Reporting
CPU: AMD Athlon 3000+ XP
GPU: Nvidia 6600
RAM: 1024MB DDR PC3200
Soundcard: AC 97 (onboard)
Patch Type: Full (Beta 2)
Game Type: Conquest
Event: Failure for all objects to render after "alt-tabbing" back into BF2
Source: In game
Reproduced Successfully? Not attempted
Evidence: 2x Screens (below)

And...
Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
bf2 1.4 beta 2
i cant go into details, but i was driving along in a tank 64 player road to jalalabad, and bf2 randomly minimized for no reason, which hasnt happened beofre. a few min later, i was running along on foot as a sniper and it CTD.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
What really needs to be added is a column in the browser to sort by MAP size, not just player count. I hate wasting my time looking for a 16 or 32 player map, and finding 200 16 player servers running 64 player maps.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
Adjust the 'Refresh Rate' in your display settings for your monitor. Mine would not work at 85 but would work at 75 for some patches; but than the opposite for other patches. Do tell if that fixed your problems or not.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
this whole game has been beta since release..Originally posted by LeehamOr maybe you're expecting a 100% problem free patch which is NOT going to happen in ANY game
Or maybe you forget it is BETA
we're all paying beta testers..
funny how ea *** kissers still defend them after a year on the market
and they still got bugs out the wazoo.. and just for your information..
other games do YES, do fix 99.9% of their problems within weeks of
release...
SAY NO TO EA *** KISSERS. ITS BECAUSE OF THEM, EA THINKS THEIR
CODE IS ACTUALLY GOOD.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
This also happens to me. If you take a look in the Event Viewer I"m also seeing this:CPU Pentium D 920
GPU NVIDIA 7800 GT 256MB
RAM 4*512 Corsair
Soundcard Soundblaster Audigy SE
Patch Type 1.4 Beta 2 Full
Event Windows Critical Error upon quitting the game
Reproduced Successfully? Yes
Evidence Exiting game
O/S Windows XP SP2
The above event only appears when bf2 exits and only happens after patch to 1.4....so don't tell me it's spyware or virusesEvent Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 7/15/2006
Time: 11:33:14 AM
User: NCLIFFORDXP\nclifford
Computer: NCLIFFORDXP
Description:
The 5702b4bh service was successfully sent a start control.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
CPU AMD Athlon64 4400+
GPU BFG 7900GT
RAM 2GB
Soundcard Realteck integrated in Asus A8n32-sli
Patch Type Full (1.4)
P.S. Yes I just joined to post this cause it's annoying.Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
CPU AMD Athlon64 3200+
GPU nVidia GeForce 6600LE 256MB
RAM 1GB
Soundcard X-Fi Fatal1ty FPS
Patch Type Incremental (1.4)
Event Game suddenly drops back to desktop, completely instantaneous. There is none of the usual associated Windows error messages or indeed anything at all to indicate what happened. There is also none of the usual `memory/page file lag` which occurs when quitting BF2 to desktop which is very strange indeed. Suddenly in the middle of a round I'm just back staring at the desktop and the game is no longer running.
Source BF2 Ranked server
Reproduced Successfully? This has now happened perhaps 4-5 times in a half dozen or so rounds I played. There seems to be no pattern I can figure out and I never had it happen with 1.3 or 1.4 Beta 1 patch. Will continue trying to come up with a way to reproduce this one.
Evidence Former EA tester? Hm, perhaps something like DUmeter can show the sudden `cut` when the game stops running. Otherwise, not really a capturable crash.
EDIT: I can also vouch for the random "connection problem" messages that seem to have returned post-1.3. On an 8MB link too.Leave a comment:
-
Re: 1.4 Feedback and Error Reporting
hmm i think i saw somewhere that EA/Dice didnt know the cause of this and justified it as a random bug, as it happens in 1.3 aswell, but updating PB used to be a temp fix for meOriginally posted by StizzleCPU AMD Athlon XP 3000+
GPU nVidia GeForce 6600 128Mb
RAM 768MB RAM
Soundcard None, i have onboard sound.
Patch Type Incremental (1.4)
Event Continous Disconnecting, not even a "there is a problem with your connection" just a straight "crash to browser" followed by "connection to server has been lost", this also happens quite alot when a map is loading, the map will load than it will lose connection as soon as it's finished loading/verifying
Source BF2
Reproduced Successfully? Yes, quite a few times. To the point where it happened all the time, i just uninstalled BF2 completley and I will try the full 1.4 beta patch
Evidence Didn't think i'd need any, if anything all it would be is a screenshot showing "connection to server has been lost" :|:
Other Notes I thought it was my internet connection but i can play CoD2 without problems for long periods of times. Might be a BF2 bug
My internet is: AOL Broadband 1Mb
Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
CPU Pentium D 920
GPU NVIDIA 7800 GT 256MB
RAM 4*512 Corsair
Soundcard Soundblaster Audigy SE
Patch Type 1.3 & 1.4 Beta 2 Full
Event Looping sound when commander gets chosen or at the beginning of every game
Source In Game
Reproduced Successfully? Yes
Evidence During game play
O/S Windows XP SP2
CPU Pentium D 920
GPU NVIDIA 7800 GT 256MB
RAM 4*512 Corsair
Soundcard Soundblaster Audigy SE
Patch Type 1.4 Beta 2 Full
Event Windows Critical Error upon quitting the game
Reproduced Successfully? Yes
Evidence Exiting game
O/S Windows XP SP2Leave a comment:
-
Guest repliedRe: 1.4 Feedback and Error Reporting
I have not seen a single bug submited during Beta 1 addressed in Beta 2. NOT A SINGLE ONE. What a humongous waste of time.
Its quite clear that DICE are going to put out 3 identical betas of the patch, and then the final 1.4 patch and it will be exactly the same as the first Beta. And then turn around and blame the community claiming "You guys Beta tested it".Leave a comment:
Leave a comment: