BF2S Forums [Battlefield: Bad Company 2] Official Thread

zeidmaan wrote:

Sisco10 wrote:

Sniping, well. It is weird. There is bullet drop, but it seems it changes with every shot. I´ll credit that to the netcode/hitreg/lag though.
Weirder thing is, when you use the 4x Scope there seems to be no drop at all. Only on extreme ranges.

I think, and Im not sure, that the amount of drop changes with you erm... "sway position" when you fire.

Ill try to explain.
You croshair keeps moving up and down and up and down and up and down... if you fire when the croshair is at the top most position you will have more drop than if you fire when its at its lowest point. Atleast thats what it looks like to me but I never paid too much attention to it. You should try it and tell us about it

wah1188 wrote:

Damn I want a beta key

wah1188 wrote:

I just want to know how it runs on my computer. Played it on 360 and it's pretty awesome.

Sisco10 wrote:

FloppY_ wrote:

zeidmaan wrote:

I think, and Im not sure, that the amount of drop changes with you erm... "sway position" when you fire.

Ill try to explain.
You croshair keeps moving up and down and up and down and up and down... if you fire when the croshair is at the top most position you will have more drop than if you fire when its at its lowest point. Atleast thats what it looks like to me but I never paid too much attention to it. You should try it and tell us about it

That is my theory aswell..

Or maybe, if you fire while swaying down, the bullet drops further and vice-verca

That makes sense, in a totally non-sense way, if you know what I mean . I will try tomorrow.

dill13 wrote:

Sisco10 wrote:

Weirder thing is, when you use the 4x Scope there seems to be no drop at all. Only on extreme ranges.

Ok the less your zoomed in the less noticable bullet drop will be. if you dont understand why then think of it like this look at something without the scope then look at it without moving the object gets bigger so the bullet drop will seem like its more.

So QA found out a debug setting we used for logging errors was causing the CTD's after DICE left last night. As such the patch is good to be released and is going live within the hour.
Steam users will have to wait until this evening to update as we need Valve to wake up to make it live their end. If you want to run the latest version you can uninstall the Steam version and grab the client from any host here: Battlefield Blog and use the same login details as before.

You can update automatically when loading BFBC2 or you can manually run the updater from your install directory (run as Administrator if you experience update issues or errors)

As promised here is the Changelog for R3 as provided by Kalms.

This update is about performance and stability again. We are not doing any changes to the game's datafiles.

    * Reduced input "lag"
      On machines where the CPU would out-run the GPU, sometimes the GPU would queue up several frames' worth of rendering commands.
      This could lead to the game having a high framerate, but input still feeling very sluggish.

    Now there's a limiter on how many frames the CPU is allowed to be "ahead" of the GPU.
    Control this setting via Settings.ini. Default setting: RenderAheadLimit=2

    * Performance optimizations with biggest improvements on dual-core machines
    * Fixed black "masks"
          o The soot on buildings with holes in them had a bugged renderpath. We switched that over to a more well-tested renderpath.
    * Improved hit-detection
          o We've gone through the hit detection logic, and client+server will now give more consistent results.
    * Fix for some "rubberbanding" issues
          o C4 should stay attached to vehicles and not rubberband around
    * Reduced spikes/dips in framerate
    * Various fixes for alt+tab related CTD on Dx9
    * More fixes for random CTD on Dx9
    * Fix for crash when you're in a vehicle that gets destroyed

    There was a race condition in the code;
    System 1 thought "oh hey, you're leaving vehicle X"
    System 2 thought "the vehicle got destroyed, let's remove it"

    If system 2 ran before system 1, chaos would ensue.
    This was actually fixed in the retail version since a month, but it was only when we got detailed crash reports from the community that we understood *why* the Beta was crashing.

Likely bugs in this build
I wouldn't be surprised if it (still) has trouble remembering your settings between rounds. It would be nice to have that fixed too, but it's better to get a patch out now, and look at the settings issues afterward.

-Mikael Kalms

TimmmmaaaaH wrote:

You have to remember this is made by the same people who brought you the mismatched iron sights/scopes in BF2.

I am getting better at sniping, but it is a bit random. Switching to the SV-98 just put me back to square one

Still, when its you against 2 or 3 guys and you pop up 3 times and kill them all its just the best thing. So much more satisfying than the automatic guns.

Last edited by Spark (2010-02-18 03:10:18)

TimmmmaaaaH wrote:

Awesome patch is awesome.

I hope it is as good as it sounds.

Last edited by Spark (2010-02-18 03:45:12)

GC_PaNzerFIN wrote:

CTDs, AF doesn't work at all (explains why my FPS over doubled). Hitreg seems to be working great at least for sniper rifle... as much as I tried it before CTD...

FloppY_ wrote:

csmag wrote:

The update is out on steam

ffs good job steam    > : (

I had to log out and back in to get it... now I don't want to play...