#Server hitreg today was awful

1 messages · Page 1 of 1 (latest)

oak kettle
#

I would say I've played for about 6 or so weekends and it's been good -> decent cause obviously 127 people. However today it was absolutely unbearable. (127vs127 official servers) Shots would not register, shots that would register would take a second or two to give me the hit marker. When I would shoot it felt like nothing was happening to the other player. This was confirmed with my squadmates in comms that they too were having issues.

neat oxide
#

i thought i was trippin, shit was terrible

topaz carbon
#

I wouldn't say TERRIBLE, but I did notice it was weird sometimes. Like getting killed behind a wall half a second later.

solemn lagoon
#

registration was fine but some people would get hit behind walls, seems like some kind of server lag

#

was only really noticeable when running into cover and dying to a delayed shot

oak kettle
oak kettle
#

ALSO bandaging was an issue. It would stop bandaging as if we had let go but we never had. Had to pickup people like 2-3 times today

mild night
#

Have understanding for it. Servers, cost a lot of money and time. We have to sup the devs. If we want it better. But can understand your frustration.

#

And point

vivid parrot
#

Seems like the server provider today had some sort of issue with performance, reducing the tickrate.

grim horizon
#

Had a few people saying my server was good (I host a community server)

Played one match of official servers and it was ehh

clever sky
#

I had no issues whatsoever.

#

And I am usually the one who says the hitreg was crap.

#

At very least, 32vs32 was flawless on the server I tried.

#

To the point where I managed to top score with FAMAS and Groza.

oak kettle
oak kettle
clever sky
#

I'd assume they run on the same servers still. But who knows.

oak kettle
clever sky
#

Isn't it like 4 times the amount?

oak kettle
#

Ya

#

lol xD

clever sky
#

Just weird how 32vs32 felt this stable to me, when sometimes it...doesn't. HyperXD

#

Whatever issue the server provider had, it should have affected 32vs32 as well then...or not. Oh well