1.4 Feedback and Error Reporting

Re: 1.4 Feedback and Error Reporting

The ability of players to program macros into their keyboards is ruining the game, so EA/DICE, please disable them.

I saw a guy spinning the turret of his tank like a top, a guy jumping/proning/rolling/shooting, a guy spinning his .50 cal like a top, and a jet doing some impossible moves yesterday, all using macros.

It gives players with these keyboards an unfair advantage, so let's level the playing field and disable them.

[ponton]

Re: 1.4 Feedback and Error Reporting

CPU - Intel Penitum 4 2.4GHz HT @ 2.80
GPU - nVidia GeForce 6600GT AGP @ 550/1000
RAM - 2 x 512 MB Kingston
Soundcard - Creative Audigy 2
Patch Type - Incremental
Event - Invisible parts of "baazar booth" in "Road to Jalalabad" (from one side only). Tested only this one because connot find any other to climb on. (didn't loook carefully ). And theres "invisible wall" where this part should be.
Source - BF2 Multiplay server, 64players,infantry only
Reproduced Successfully? - yes, persistent
Evidence - screenshots

Second:
<Specs above>

Event: with paddles equipped, i can hear healing sound
Source - BF2 Multiplay server, 64players,infantry only
Reproduced Successfully? - no
Evidence - none

Re: 1.4 Feedback and Error Reporting

Oops, yeah. I had copied one in and forgot to switch it to zero.

I did the SWBFII beta thing through FP. Worked pretty well, but we hardly every got any feedback from our feedback.

Excellent suggestion on the auto error send. That would create a nice database for them.

Re: 1.4 Feedback and Error Reporting

You mean +fullscreen 0? Windowed mode? Because full window mode would never show an error message or anything, but most of the times when it crashed, I would hear an error but no window. And I tried windowed mode but that didn't allow for an error message to pop up either. Nonetheless, it's fixed.

Yeah, open betas are definitely a great idea. But as I understand the BF2142 "open" beta will only be available to those who register somewhere, such as GameSpy/FilePlanet. I doubt they would release the beta game to every single individual, but who knows, perhaps they will. Another thing that should be done is implementing an excellent error reporting tool, so that whenever someones game crashes, they can send this report straight to EA/DICE and they'll gather all the errors and create patches from there, starting with the problems, and not modifying/implementing new things into the game.

Re: 1.4 Feedback and Error Reporting

If you use +fullscreen 0 in your shortcut, a window will pop up and display the crash info.

I sure hope BF2142 is first released as Beta. Heck, all games should be released like that beforehand.

Edit: Oops, fullscreen 0

Re: 1.4 Feedback and Error Reporting

Comp specs: Athlon XP 2100 (1.73 GHz), 512MB PC2700 DDR, Radeon 9500
Patch: 1.4 incremental, following by a re-patch with full after the problem appeared. Over 1.3
Problem: 1.3 would ALWAYS crash to desktop right after a MP game loads, not caused by moving or clicking anything. At the same time, 1.4 would never run.
Solution: I've tried everything from changing drivers to clearing CMOS, but that did nothing but waste time. I finally decided I should re-install and I did.. now it works fine. I patched with 1.4 full over 1.0

Comp specs: Athlon XP 2100 (1.73 GHz), 512MB PC2700 DDR, Radeon 9500
Patch: 1.4 full over 1.0
Problem: Crashed after clicking Join Game on MP, dump file said:

D:\Aphrodite\BF2_1.4\Code\BF2\Physics\PhysicsNode. cpp(970): Error: Physics: When calculation inertia there is no collision mesh for object jep_vodnik

Also 1 CTD while playing game, dump is unreadable.
Solution: Well, I patched 1.4 full over 1.4 again just to make sure it wasn't corrupted, and also played an SP game with all the vehicles on the RTJ map. Use WinDbg to read your crash dmp files in your My Documents folder.

Bug/glitch: After updating server list repeatedly, all servers would show 20 ms ping time.

Bug/glitch: Marking a server as a favorite caused it to disappear.

Bug/glitch: While hosting a server as a local game, parts of the server details while loading wasn't shown.

Re: 1.4 Feedback and Error Reporting

This is with 6 people in Mastuur (99fps):



This is with ~16 players in Mashtuur right after the game started(44fps):



This is on Sharqi with 64 players (25fps):



If you want the larger pics I can show those too, but it is nearly impossible to see the FPS number up there because picturetrail.com shrinks everything. My temps never exceed 55*C according to Rivatuner, Bf2 is my default driver setting, with everything on high performance and least image quality.

With the below rig, that can handle every other game without a hiccup, this is F***ING REDICULOUS!

Quoted because it's important and has to be heared by DICE.

I got the same problem and will post some caps later.
Also from Sharqi and Ghost Town.

Maybe I can make a chopper-lag movie also we'll see.

Re: 1.4 Feedback and Error Reporting

Mod: BF2
Patch: Full 1.4 Patch
Event - Lots of shaking when prone near edge of roof due to collision with small ledge.
Reproduced Successfully? Yes, lots in RTJ.
Evidence - none, just try it in-game.

Mod: BF2
Patch: Full 1.4 Patch
Event - I seem to slide when jumping onto boxes in RTJ.
Reproduced Successfully? Yes, in RTJ.
Evidence - none, just try it in-game.

Mod: BF2
Patch: Full 1.4 Patch
Event - Enemy Red Tag does not show sometimes
Reproduced Successfully? Yes.
Evidence - Screen405 below

Mod: BF2
Patch: Full 1.4 Patch
Event - Extreme jump height.
Reproduced Successfully? Yes, lots.
Evidence - Screen408 below

Mod: BF2
Patch: Full 1.4 Patch
Event - Hung up above ladder on RTJ Hotel ladder
Reproduced Successfully? No
Evidence - Screen412 below

Mod: BF2
Patch: Full 1.4 Patch
Event - Repairing (wrench) icon does not show when repairing assets from vehicle in RTJ.
Reproduced Successfully? Yes
Evidence - none, try it.

Re: 1.4 Feedback and Error Reporting

Please people .. POST PROOF!

YES! POST SCREENSHOTS WITH renderer.drawfps 1

YES! POST VIDEOS

JUST POST PROOF

Statements without proof are less likely to be looked at or taken with any degree of seriousness.

We are being given a chance to help change things..make it count.

This is with 6 people in Mastuur (99fps):



This is with ~16 players in Mashtuur right after the game started(44fps):



This is on Sharqi with 64 players (25fps):



If you want the larger pics I can show those too, but it is nearly impossible to see the FPS number up there because picturetrail.com shrinks everything. My temps never exceed 55*C according to Rivatuner, Bf2 is my default driver setting, with everything on high performance and least image quality.

With the below rig, that can handle every other game without a hiccup, this is F***ING REDICULOUS!

Re: 1.4 Feedback and Error Reporting

A few minor things:

CPU - AMD64 3200
GPU - NVIDIA 6600GT
RAM - 2x512
Soundcard - onboard NFORCE 4
Patch Type - incremental
VideoSettings - see attachment


Event - Dead soldier shows as shadow only for ~5 seconds. It seemed as if the revive time was really short in this case.
Reproduced Successfully? yes
Evidence - see attachment (screen002)

Event - shallow water on road to jalalabad does not show as the usual darker patch on the hud map
Reproduced Successfully? yes
Evidence - see attachment (e.g. screen002)

Event - map vote does not tell what is being voted for
Reproduced Successfully? not yet, it was a vote for jalalabad, 64 players after jalalabad 32 players, i think
Evidence - see attachment (screen003)

Event - enemy killed by pistol flys away as if he was hit by grenade
Reproduced Successfully? not yet
Evidence - see attachment (screen005), note kill message, position of kit and position of enemy


Bug reproduced: 2 vehicle drops right after another as commander

Re: 1.4 Feedback and Error Reporting

I'm working on a 1.3 patch for another game and having a separate, private board accessed by password helps keep things focused. People can still post feedback in the publlic forums too, but it certainly reduces the Beavis and Butthead posts.

Really good to see DICE posting here.

Yeah :)

You know...does the way of reporting bugs via fan forums seem somehow to be lacking in professionalism? Maybe not. Maybe it's just me, but I would have contect forum ownersz and asked if a new section could have been opened just for 1.4 and maybe a proper format of reporting and a thread where every report that doesn't conform get's deleted ?

Re: 1.4 Feedback and Error Reporting

CPU - X2 3800 @ 2.7
GPU - X1800XT
RAM - 3G OCZ
Soundcard - Audigy
Patch Type
Event
Source
Reproduced Successfully? yes, repeatedly
Evidence

When on Jalalabad non infantry only as the US commander, each time the MEC dropped a vehicle it would reset my vehicle drop timer, we did this repeatedly..

however when I dropped my vehicle the MEC commanders timer wasnt reset..

also

http://img.photobucket.com/albums/v402/ojibewa/screen059.jpg

when dropping a vehicle at this point between the buildings the vehicle will shoot thru the building at random points...

could be used for exploit..

Re: 1.4 Feedback and Error Reporting

I posted in the other thread because this one was for bug reporting, But I complied with your wishes and posted in this thread, and my posted was deleted, without any sort of explanation, so asked why it was deleted and again my post was gotten rid of without any sort of response. Now Id like an answer, a simple yes or no will do

but this post will too get deleted so I dont even know why I ****ing bother with it.....

I guess this thread should not be where we give our feedback. Perhaps the name of the thread should be changed from "1.4 Feedback and Error Reporting" to just "1.4 Error Reporting"?

I too thought this thread was were we give our constructive feedback.

Re: 1.4 Feedback and Error Reporting

Please people .. POST PROOF!

YES! POST SCREENSHOTS WITH renderer.drawfps 1

YES! POST VIDEOS

JUST POST PROOF

Statements without proof are less likely to be looked at or taken with any degree of seriousness.

We are being given a chance to help change things..make it count.

Alright give me a minute.

Re: 1.4 Feedback and Error Reporting

CPU = Dual Core 3,0 GHZ P4 2x 2 MB cache Presler
GPU = 7600 GT 256 MB
RAM = 1024 DDR2/533 Nanya
Soundcard = Onboard
Patch Type = 1.4 Beta Full
Event = 1. It keeps switching off AA, while i set it to 2x, i never had this problem before, also seem to happen at other people and with all kinds off settings, also it resets your settings of Video when u install 1.4
2. Still "There is a problem with your connection"
3. Extreme lag at Road to Jalalabad
Source Playing 1.4 BETA
Reproduced Successfully? Unfortunately : yes
Evidence Big yellow word in middle of screen, and AA off in menu, moving like a aline on Jalabad with pauses.