Born Again Noob

2007-01-19 08:00:44

#1

usmarine2007: Banned; +374|6639|Columbus, Ohio

I started playing this game again after not playing it for about 4 months or so. The last patch I remember is 1.31 or something like that.

What the hell has happened since then? Why is everyone hoping around again and why does it take a shitload more M249 rounds to kill a person? Hit detection has always been a problem, but is it worse now after 1.41 or am I just seeing things?

2007-01-19 08:03:01

#2

Flaming_Maniac: prince of insufficient light; +2,490|6978|67.222.138.85

They didn't change anything, it's just you

2007-01-19 09:11:56

#3

gene_pool: Banned; +519|6893|Gold coast, Aus.

No. the hit rego is borked even more since 1.41. If they don't fix it in 1.5....

gr...

They wont see it coming.....

2007-01-19 09:17:38

#4

Flaming_Maniac: prince of insufficient light; +2,490|6978|67.222.138.85

gene_pool wrote:
No. the hit rego is borked even more since 1.41. If they don't fix it in 1.5....

gr...

They wont see it coming.....

Really it's worse? I would honestly believe you, at some point it's just so damn hard to tell if it got worse or it's the same bullshit as always.

I bet there is no patch 1.5.

2007-01-19 09:19:19

#5

namelostonthetoilet: Member; +2|6609

we want 1.22 ranked back!!

2007-01-19 09:20:44

#6

gene_pool: Banned; +519|6893|Gold coast, Aus.

namelostonthetoilet wrote:
we want 1.22 ranked back!!

Wow, nice stats on your alias.

And yes, i agree.

2007-01-19 09:23:35

#7

Tro0per: Take off, hosers; +24|6688|Ontario, Canada

nothing like shooting at someone directly on the head only for dust to appear

2007-01-19 09:28:55

#8

usmarine2007: Banned; +374|6639|Columbus, Ohio

Tro0per wrote:
nothing like shooting at someone directly on the head only for dust to appear

Or some dude comes around the corner, you are in the prone, unload 50 rounds into him, he lives, you die after a three round burst.

2007-01-19 09:31:25

#9

Lucien: Fantasma Parastasie; +1,451|6925

Press the following buttons on your keyboard:

~
SettingsManager.U32Set GSInterpolationTime 80
SettingsManager.floaset GSDefaultLatencyCompensation 0.030

while ingame

2007-01-19 09:34:05

#10

usmarine2007: Banned; +374|6639|Columbus, Ohio

what does that do?

2007-01-19 09:37:58

#11

Sarciss: The Hunter; +163|6610|Too late for you to know...

SargeV1.4 what does that change in the gaming experience exactly?

2007-01-19 09:39:15

#12

killer21: Because f*ck you that's why.; +400|6862|Reisterstown, MD

I just aim to the left and it works everytime.

2007-01-19 09:47:26

#13

usmarine2007: Banned; +374|6639|Columbus, Ohio

killer21 wrote:
I just aim to the left and it works everytime.

A little Kentucky windage eh?

2007-01-19 10:11:19

#14

killer21: Because f*ck you that's why.; +400|6862|Reisterstown, MD

usmarine2007 wrote:
A little Kentucky windage eh?

Only in bf2. On the wiffle range, it is a little different. 5 expert badges do not lie

2007-01-19 10:14:41

#15

djphetal: Go Ducks.; +346|6607|Oregon

I think hitreg is worse in IO, but with vehicles i don't see it as much...

am I crazy? does anyone else notice this?
otherwise.... the game didn't change THAT much...

2007-01-19 10:17:01

#16

RDMC: Enemy Wheelbarrow Spotted..!!; +736|6837|Area 51

SargeV1.4 wrote:
Press the following buttons on your keyboard:

~
SettingsManager.U32Set GSInterpolationTime 80
SettingsManager.floaset GSDefaultLatencyCompensation 0.030

while ingame

What the hell does that change..I think its a ticket for a hardware ban..

2007-01-19 10:20:43

#17

killer21: Because f*ck you that's why.; +400|6862|Reisterstown, MD

djphetal wrote:
I think hitreg is worse in IO, but with vehicles i don't see it as much...

am I crazy? does anyone else notice this?
otherwise.... the game didn't change THAT much...

Are you kidding? How about when you TV a chopper and the missile goes right through the cockpit but the chopper is still flying? You don't think that is bad hit reg?

2007-01-19 10:22:01

#18

Surgeons: U shud proabbly f off u fat prik; +3,097|6761|Gogledd Cymru

that ^^^^^^ changes something to do with the lag compensation i thinks ?? am i right sarge

2007-01-19 10:24:39

#19

aujt74: Member; +11|6966|Scotland!

RDMC(2) wrote:
SargeV1.4 wrote:
Press the following buttons on your keyboard:

~
SettingsManager.U32Set GSInterpolationTime 80
SettingsManager.floaset GSDefaultLatencyCompensation 0.030

while ingame
What the hell does that change..I think its a ticket for a hardware ban..

All those settings change is the default lag compensation in BF2. By default the game assumes a ping of 100ms, however if you adjust the latency compensation to match your actual ping, hit reg gets a bit better. Its not a fantastic change but it makes a difference, if only a little one.

2007-01-19 10:47:00

#20

usmarine2007: Banned; +374|6639|Columbus, Ohio

aujt74 wrote:
RDMC(2) wrote:
SargeV1.4 wrote:
Press the following buttons on your keyboard:

~
SettingsManager.U32Set GSInterpolationTime 80
SettingsManager.floaset GSDefaultLatencyCompensation 0.030

while ingame
What the hell does that change..I think its a ticket for a hardware ban..
All those settings change is the default lag compensation in BF2. By default the game assumes a ping of 100ms, however if you adjust the latency compensation to match your actual ping, hit reg gets a bit better. Its not a fantastic change but it makes a difference, if only a little one.

Would I have to type that evertime I join a server?

2007-01-19 11:30:52

#21

aujt74: Member; +11|6966|Scotland!

Yup, well you want to match it to your current ping.
Also just noticed what Sarge copied/typed is wrong.
It should be: SettingsManager.floatset GSDefaultLatencyCompensation 0.030
not: "SettingsManager.floaset".

So, if you are pinging 30ms to a server, divide the value by 1000 and use that (i.e. 0.03). Say 50ms = 0.05.

The GSInterpolationTime is a slightly different matter, and i'm not as sure about it.

Since Dice has never released any documentation on BF2 netcode or hitreg you are mostly guessing as to how to change these values.
Googling using the names of the above variables brings up a fair number of forum posts or articles on the subject. However its all pretty much speculation, although reasonably informed speculation.

Also, those values are stored in the usersettings.con settings file which is by default stored in C:\Program Files\EA GAMES\Battlefield 2\mods\bf2\Settings. There is also another in the mod\xpack directory.
So I assume you could modify the default values of those variables to reflect your average ping i.e. to servers in your country/region so you would only have to modify them in the ingame console if you joined a "foreign" server.

2007-01-19 11:37:47

#22

RoosterCantrell: Goodbye :); +399|6751|Somewhere else

usmarine2007 wrote:
Hit detection has always been a problem, but is it worse now after 1.41 or am I just seeing things?

Seems worse. Some rounds, I'll shoot a stationary target 3 damn times with a sniper rifle and get nothing, other times, I can hit a running target moving lateral across my scope, A blind shot, and they drop.

My advice, get drunk. you're reaction times slow, and the hitreg improves since you aren't aiming at your target fast enough, but are infact aimed at the space next to them, where it seems to really count.

But, all in all besides ol' 1.12.. 1.41 is a good patch compared to the rest. IF the rumored 1.5 appear, I pray to the gods EA invests more time into it, even more so if it's the final patch.

I've never heard them say last or final patch, but if that does comes...... (thinking with severe dread) "oh fuck".

2007-01-19 12:45:58

#23

Des.Kmal: Member; +917|6889|Atlanta, Georgia, USA

killer21 wrote:
usmarine2007 wrote:
A little Kentucky windage eh?
Only in bf2. On the wiffle range, it is a little different. 5 expert badges do not lie

aiming has something to do with time? hax.

Add me on Origin for Battlefield 4 fun: DesKmal

2007-01-19 14:55:02

#24

TrueArchon: Enemy Sniper..." *BOOM* "Nevermind... got him...; +61|6866|Las Vegas, NV USA

Well... My overall accuracy has gotten a bit worse over the last couple of months...

But I think that's because I've tacked on about another 20 hours of support since then.

If anything, I think it's all about the same as it use to be, and I think all that time away has rusted up your skills. Give it time, and you'll probably be back to where you were.

BF2S Forums Born Again Noob

gene_pool wrote:

namelostonthetoilet wrote:

Tro0per wrote:

killer21 wrote:

usmarine2007 wrote:

SargeV1.4 wrote:

djphetal wrote:

RDMC(2) wrote:

SargeV1.4 wrote:

aujt74 wrote:

RDMC(2) wrote:

SargeV1.4 wrote:

usmarine2007 wrote:

killer21 wrote:

usmarine2007 wrote:

Board footer