>First of all, most people don't even really understand the way that the network code works. For example, the server does tick at 60Hz, it's the client update rate that is lower. That just shows a general misunderstanding.
>I think players have latched onto server tick rate as being the reason that certain things happen. One of the things that players are upset about is that if they get shot, where they perceive they were behind a wall, that this is a problem with server tick rate. Certainly there are contributions that could happen with both the server and the client update rates that could cause something like that to happen, but usually, in most cases, you're talking about latency.
>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
>Right now, for example, what we've seen is that it wouldn't work for about 20 per cent of our users. That's a problem we can solve if we get more testing on it, but we couldn't just put it live. As you know, we announced that number of seven million players last week. The last thing we want to do is take 20 per cent of those people and tell them you can't play Overwatch anymore because people were angry on the forums and we flipped the switch and added this thing.
You don't want more than 20 tick. You think you do, but you don't.
>playing against people in your same area
>latency
I have never been shot while behind a corner in Counter Strike.
this just makes me want to demand a refund.
>If you kill someone it's because of the tick rate
>If you die, it's because you're bad
Why did anyone even get hype for Blizzard again?
>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
This basically says "I don't know why you retards are whining, a whole .08% of games do the thing you want! Isn't that good enough?" That's incredibly insulting to customers and idiotic in general.
>>340760928
And the bad part that retards will buy into their shit.
But the game reeks of console shooter.
From bad tick rate to shit hitboxes.
>>340760474
I am waiting for the cucks defending this
>inb4 how can 20 ticks be real if ticks aren't real
>>340760474
>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
That's because nobody fucking plays custom matches, they do quickplay because you haven't incorporated a ranked system yet you daft cunt.
>>340760474
>tfw not a networking expert so you cant really talk shit at what hes saying
someone whos smart make an argument for me
>your house is on fire
>it actually isn't, you don't understand thermal dynamics and perceive that it's on fire because the roof collapsed in and you're just saying its because of the fire because you don't know what actually caused that to happen
>>340760474
>u sya u know the tick rate, butt u dont
>>340761327
Do you get exp from doing custom matches? That might be a large factor too people want the higher tickrate but don't want to give up progress on loot boxes.
Are people surprised that a casual fps also has casual netcode
>>340761369
just say 20 tick is a stylistic choice :^)
>>340761568
It's a feature
>>340761369
The tick rate measures how often the server updates per second
higher tick means more updates which means last second or clutch movements are recognized sooner than if they were lower.
Imagine if it were one tick a second. You stand up and crouch. Your opponent has a whole second to respond to shoot you in the head and kill you before the server info updates with 'you have crouched'.
It's a serious problem concerning quick reflexes and movements and in something, which I imagine Blizzard wants, that might be played at a 'professional' level that shit has to be as high as possible.
>/v/ can't refute his argument in the last paragraph
lol
>>340761469
Nope, no exp at all.
>>340761737
Because it's not really an argument.
> We could try to feed everyone in the room, but then we'd have to tell 20% of the room that they can't eat any spaghetti.
> What? Cook more spaghetti? Ludicrous, you think we're made of m- oh.
>20 percent of players can't handle 66 tick clientside
How are they even running the game?
>>340761737
>can't refute.
Nigga even on official forums people are bitching about getting shot through the walls.
They are just a bunch of jews that don't want buy good servers.
Fucking quake have better netcode than this. And I remember play in a 56k modem.
>>340761737
How would changing the tick rate stop people from playing? Are they catering to dial up users?
>>340761865
>it's a food analogy
lol
>Right now, for example, what we've seen is that it wouldn't work for about 20 per cent of our users. That's a problem we can solve if we get more testing on it, but we couldn't just put it live. As you know, we announced that number of seven million players last week. The last thing we want to do is take 20 per cent of those people and tell them you can't play Overwatch anymore because people were angry on the forums and we flipped the switch and added this thing.
THANK YOU BLIZZARD
No seriously thanks, I live in a country that doesn't have server support and the shitty tick rates have made the game completely playable for me.
> what we've seen is that it wouldn't work for about 20 per cent of our users
Interesting dilemma. I wonder how said 20 percent even experiences overwatch to begin with. Is this a networking or hardware issue? Said 20 percent, are they going to be marginalized through patches anyway, or will there be no updates to the engine because of them.
Either way every developer is between a rock and a hard place when the issues of lag and tick-rate seem to come up.
>>340762021
Ok, here it is in a non-analogous sense.
> We could try to make all of our servers 60 tick, but then 20% of our players wouldnt' be able to access the servers because there wouldn't be enough
> What? Run more servers? Ludicrous, you think we're made of m- oh.
>>340761737
That's like saying Oh I can't play graphic intensive games on my windows 98 toaster. The dev's shouldn't pander to 80% of the community with their neckbreathing, basement dwelling, forum trolls, instead they should make it to where the 20% of people who haven't updated Adobe because they think it's a virus, who still use AoL, and play flashgames on newgrounds are able to play the game.
>>340760708
I know this is a lie, because guns in Counter Strike have penetration through certain materials. Thin steel, wood, and so on. You can and probably have been shot around a corner in Counter Strike. By someone not using cheats.
Someone like me, who has shot people around corners and through walls.
>>340762170
I'm not really sure if it's a server thing. I think it's more of a, "people have crap internet" thing
>>340762108
Low tick rate benefits retards with high ping but fucks everyone with high ping.
This makes me wonder how they want this shit be a competitive game?
Even fucking dota have a decent tick rate in non competitive matches.
>>340762027
Maybe you should work on getting out of your shithole before you waste time in videogames and ruining things for other people.
>>340761131
What's insulting about telling people they aren't using the thing they are asking for?
Let the tryhards get refunds, it's once again a case of the vocal minority trying to bring elitism into what was intended to be a casual game.
These are the same fuckheads that ruin every other game with their fantasy of becoming a professional e-sports player.
>>340761131
I don't think you play Overwatch.
He's saying there is an option in Custom Game mode to alter the tick rate. He then said that only .08 % of matches use the increased refresh rate.
This is probably because:
A) Fucking Nobody plays custom matches, you don't get XP.
B) That .08 percent is probably including all game modes, including Quick Play and Brawl which people actually use.
Custom Game is for groups of 12 who want to play 6v6, or groups of 6 try hards who think this is an E-Sport. No one is using it.
>>340762381
>Even fucking dota have a decent tick rate in non competitive matches.
Yep. Dota has a tick rate of 30. Overwatch has a lower tick rate than a MOBA.
>>340762452
>waa people aren't allowed to be better than me
>>340762384
Sorry buddy I paid my money just like you and blizzard didn't region lock the game.
If they didn't intend for me to buy it they shouldn't have sold it here.
>>340762381
>Low tick rate benefits retards with high ping but fucks everyone with high ping.
The experience is shit with high ping anyway, so who cares?
>>340762449
That thing that crashes 90% of games that enable it, and is only available in a custom lobby system that requires you to invite 11 other people to play with you.
Wonder why people aren't using it...
>>340761740
Makes sense why there's .008% playing custom games then.
> It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
Go fuck yourself Blizzard. Obviously no one is using the feature because no one wants to play custom games, they want to play against OTHER PEOPLE
>>340762645
You also can't just search for custom games, you have to manually invite 11 other people if you want a full game.
>>340760474
>right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
That's because most people can't get 11 other people to play with/against.
People are asking for a better online experience in ALL game modes and Blizzard are acting like retards
>>340760474
Translation: 20 Tick rate is the minimum we can get away with thanks to our cupboard-sized hitboxes and people will eat that shit up anyway
>>340760474
>We implemented "high bandwidth" after that video that does 60hz
It also only does crashing and restarting the match every 30 seconds - 2 minutes :^)
You didn't fucking release shit, but utterly broken shit, as a reactionary measure to save face.
Also it is server update rate at 20 tick, it was fucking measured using networking tools, that's how we know.
>>340760474
>Go around a corner and into another room
>Get hooked by roadhog and pulled through 3 wall to him
>Watch myself get kills on people running around a wall while popping ult as 76
Seriously, there are some times the tick rate is excessively noticeable. There is no excuse
>>340760474
>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
>its available through a function that requires a person to organize a party of 12 people and hardly anyone one uses it. Clearly it's not that highly desired.
>>340760474
>Expecting Blizzard to recgnize their mistakes and fix their mess unless their back are completely against the wall.
BWHAHAHAHAHAHAHAHAHAHAHAH
Read the text you retards. 20% of players their clients crash when running at 60 tick. They need to fix that first.
>>340762538
It also reminds me that blizzard is salty as fuck because dota2.
They fucked SC custom games because of this.
>>340763117
>>340763018
see:
https://www.youtube.com/watch?v=H0zbpPCdhGk
on how Blizzard forgot to mention it's literally unplayable.
OP's sauce, for anyone who's actually interested in not just shitposting.
http://www.eurogamer.net/articles/2016-06-07-overwatch-blizzard-answers-the-big-questions
>>340762645
There's also the fact that ticking the option for custom games causes the game to crash. You literally can't play using it.
Plot twist : It's not going to be fixed.
>>340760474
>it wouldn't work for 20% of its users
>we have 7 million users playing, the last thing we want is this unspecified select group of people to not play our game
what the fuck?
>>340763334
100% of players suffer from the SERVERS crashing and restarting matches before it even begins (set-up phase) because it's unstable as fuck.
You all fell for the blizzard meme
Now prepare for the long dick of AAA up your ass for the 7th time
When will /v/ learn?
>>340763334
>We didn't use 60 tick because we're too incompetent as developers to actually functionally incorporate it.
I see why they don't want to speak plainly. That's pretty embarrassing.
>>340763238
This seriously
Just look at StarCraft 2. One of the most popular eSport/RTS games out now and two years later STILL no LAN
>>340760474
This isn't even a fucking argument. They're just blatantly lying and manipulating information to work in their favor.
>>340763832
this has to be a false-flag
>>340763401
Scrolled down and saw the following:
By including consoles statistics, consoles are causing 20% of players using the mode to crash because THEIR MACHINE is on a crap connection and fumbles the higher update rate because of Sony/Microsoft limitations.
wew lad
>>340763832
Haha, why my 20 tick of course!
>>340760474
>most people don't even really understand the way that the network code works
Already dropped.
WOW who would have thought? I guess they have also a ready excuse for the retarded hitboxes.
baby tier game is going to stay baby tier.
have fun in your paddling pool I guess.
>>340763097
That has nothing to do with tick rate and everything to do with your shitty internet.
>>340763957
Thats why you should never put crossplay or some shit with consoles.
>>340763651
I don't know why anyone thinks Blizzard is good.
Not just this game, Heroes of the Storm still has the client trace every single action of every single player in the game until you've reconnected. Disconnecting for 6 seconds takes almost 2 minutes to get back into the game and it takes so long to reconnect that by the time the game catches up with your original time it needs to catch up to the 2 minutes it spent reconnecting you.
Post yfw you are alive to witness overfags experiencing buyer's remorse
>>340762339
>thinks we're talking about wallbanging
>>340764103
Yeah....The horrible horrible...Google fiber internet.
>>340764261
What the hell is tick
>>340764023
That is not a 20 tick problem but a hilarious glitch.
I also love it when people post killcams as reasons why 20 tick is shit. Killcams will always never be good evidence of why 20 tick is shit.
It is shit, but don't use killcams as evidence.
>>340762452
Except blizzard is the one paying to set up and cultivating the game as an esport. Just like how they bought HotS a competitive scene without the game being set up for it or gaining it organically like pretty much every other major esport has.
>>340764628
>>340764546
>...........
I just threw up in my mouth and laughed it all over my chin and shirt.
>>340763957
Searched the article and found this
>Fast and responsive
>Literally everyone moves at more or less the same speed and there's no sprinting
>Killcams aren't common
Holy shit
>>340764023
Explain this to me because I have no idea what the fuck is going on.
>>340764261
>>340764702
Should havepoo in the loothen, too late now. RIP anon.
>>340764715
So, the tl;dr is I don't even know what is this game is about and how to play this game?
getting shot behind walls is zero-ping lag compensation and has been in shooters for 15 years
getting killed at the same time you kill someone else with hitscan weapons is tickrate
dashing then being teleported back to before your dash by mcree is tickrate
>>340760474
>I-it's not our fault, everyone just has shit internet!
Mean while other FPs online games with more people are doing fine.
>>340764758
Shadowplay fucks with model loading sometimes because it uses the graphics card. It has a habit of gobbling up all the vram and a lot of games nowadays use texture streaming.
It only happens sometimes.
>>340764932
From the chosen representative for Blizzard, yeah.
If they wanted fast and responsive, almost every offense class would be about TF2 scout's speed for a start.
>>340763468
So not only is it a broken feature.
>>340762841
Shit like this is fucking dumb.
>>340764715
Spot the underage
>>340764628
It's literally explained toward the top of the thread. Lurk moar faggot.
It was also quite obvious this was going to be the most PC, inclusive, family friendly game Blizzard has produced.
If you thought the low refresh rates, countless insta-gib mechanics, and idk the entire fucking aesthetic of the game was for no reason, then you should get a fucking clue.
You bought into the hype and Blizzard got your money. They probably get a couple extra shekels from you buying their loot boxes.
>>340765086
>implying it isn't just From being shit
>>340765086
That's started to become a problem for my 780.
Should last until 1080ti though
>>340765309
>implying i'm going to deny From's incompetence.
1 step ahed of u kiddo.
>>340765351
780 is what I have too.
>>340760474
Does Blizzard not have a PR department? They could have said this in a much less-inflammatory manner, but everything they publish just comes across as, "We know what you want, you're all just entitled manchildren, shut the fuck up and eat your shit."
Which is TRUE, but shouldn't be coming from the mouth of a multimillion (-billion?) dollar company.
>>340762381
the game is flat out unplayable with high ping because it starts making you bounce around all over the goddamn place
>>340764254
That's especially ridiculous because even LoL can drop you at the point you left. That means Blizzard is somehow more incompetent than the guys who programmed spells with invisible enemies.
>>340760474
>You think you understand, but you don't
>>340765534
>Literal kids who know nothing about programming trying to argue with people who program games fro a living
Fixed that for you
>>340765534
Passive-aggressive disdain for plebs is the meta of videogame PR nowadays.
>>340765534
Nah, they have a decade of that working just fine with WoW. Everyone vocally shitting on Blizzard in the forums, and them responding in kind. The people actually complaining also have the most vested in the game itself, and won't leave. If they could just quit, they wouldn't bother to complain.
>>340764261
I honestly had fun with it but it's just so shallow and casual. It isn't a game that I'll play for years like TF2 was. It's more like the fotm game I'll play for a few more weeks and move on.
>>340765534
>game company
>PR
Nigga, I think that only company that make games and have some PR staff is nintendo.
99% of PR can be boiled down into passive aggressive arguments.
>>340760708
I havne't been shot behind a corner in overwatch
>>340765668
not everyone is a retard like you
>>340764261
>>340762339
You misunderstand. He's never been shot through a wall on CSGO because he's never stomached playing that shit game for longer than a few minutes.
>>340766370
As a quake veteran.
Console shooters really,really hurt my feelings.CSGo too but thats another story.
>>340762339
Counter-Strike will tell you if you wallbang someone, or if someone wallbanged you.
>>340764261
Fuck you. Yeah I felt for the meme. It was fun for one week and then started to become boring and now this. No need to twist the knife...
>>340766038
>340766038
https://www.youtube.com/watch?v=rPOuldGZXoQ#t=3m35s
>>340765668
Their defense is literally "no no it's not the server that's updating slow, it's the client that's not sending enough information !".
You don't have to know a lot about programming to understand why this is bullshit.
>>340760708
>making things up to further your argument
https://www.youtube.com/watch?v=y6gfWuuW2b0
>>340765007
There's been so many times as genji where I press E then I clearly see him go into the animation for it and the sound effect plays, before getting killed by a hitscan weapon right in front of me. Then the kill cam shows me not using my E at all. It's not like I have high ping either.
>80 of players must suffer so the 20% can play
This isn't really even a Blizzard issue, it's a millennial issue.
>>340766687
>>340764261
>tfw being a poorfag paid off for once
>HE DIDNY REFUND OVERKEK
the hitbox is the bigger problem
force's video clearly shows that you can headshot people not even on the fucking screen and had absolutely nothing to do with them only just moving behind cover in the last second
Please tell me someone else is going to make a well thought out and retaliatory video on just how horseshit useless this is.
>>340767356
Nobody that knows better actually cares about overwatch
People confusing tick rate with desync. I want to laugh at it, but eh.
20tick rate is fine. It makes the network prediction easier too.
I.e
>I think players have latched onto server tick rate as being the reason that certain things happen
>One of the things that players are upset about is that if they get shot, where they perceive they were behind a wall, that this is a problem with server tick rate.
This is called desync. You are not synced to your actions on server, so your actions are wrong, and because they are wrong, people can do things that would be impossible if you where synced.
>>340767561
>I have no idea what I'm talking about : the post
>>340760474
>backlash
it's an advertise and abandon game, plebs get what they deserve
>>340766909
Happens a lot with many characters, never threw the flashbang as MCree, never iceblocked as Mei, didn't deflect as Genji, didn't shield as Zarya and so on.
It's super annoying to hear the sound cue and see the effect and just die.
>>340767948
What modern game ISN'T advertise and abandon??
>>340761671
Right and wrong.
Because ticks are async to your movement, and your movement is slow, less ticks won't change anything so long the tick rate is generally high enough to allow proper input.
And then there is a legacy issues: Some games are syncronized ticks. I.E Diablo 1(20?) or Prince of Persia(12hz?), any many fixed framerate games. You input on those ticks, and output so so many ticks later.
Async ticks doesn't work like that. You get to input on 144hz, do movement on 144hz. Your actions is then sent at 20 ticks a second.
Your computer also receives 20 ticks a second, that updates all enemy and ally positions and actions. Those ticks are not synchronized to you sending packages, so they don't slow down input.
Then there is game design. Overwatch do not have instant kill hitscan sniper rifles. Instant kill hitscan sniper rifles is one of those weapons where every single ping & packet advantage you get makes you wastely superior to those without them.
Overwatch instead tries to do supression and somewhat drawn out fights. If you and another player shoot at each other, you both fire at the same tick. You both take damage at the same tick, and you might die on the same tick.
This isn't "host is server" shit that can be a real issue in multiplayer games.
>>340768094
Dwarf Fortress
Toady has been working on it for ten years and it's his "life work"
>>340764261
I'm glad the overmeme is finally dying
>>340761131
>This basically says "I don't know why you retards are whining, a whole .08% of games do the thing you want! Isn't that good enough?" That's incredibly insulting to customers and idiotic in general.
You have a big reading comprehenssion issue.
he is saying the option is available for everyone but very little use it.
>>340764261
They got $30 in crates out of me and I'm already bored! I didn't buy the Origins edition I thought they wouldn't get me!
>those little icons that flash at the top-left side of the HUD are actually for packet loss and latency issues
Am I the only one getting them?
>>340767824
You don't move enough in 1 tick in 20hz to get behind a wall or don't. Either you get desynced and die, or your internet is stable and you get behind the wall.
I would argue Overwatch could have ticks down to 13-15 before it would be a problem, but you want a certain number of ticks.
>20% of players can't handle the tickrate being increased to less than what TF2 runs
LOL
O
L
They should just match the players that can't handle the rate against each other and rest with higher rate.
I'm already over the hype
I can see Overwatch is going to turn into WoW. Slow content updates, 6mo-1year. Could see it when nothing was fixed in beta to release. Social still bugged in all phases, been 2 weeks already and nothing was released. Joining matches that are instant losses, shitty leaver penalty
Instead they released some crappy update they had to roll back instantly because it messed the game up.
Expect expansions for stuff like twitter updates for your chars, pets that follow you around in battle, among other crap features. Is it too much to ask for quick fixes? and not have to wait another month so they can be released in one huge batch like they do with WoW, hearthstone, hots?
Whatever. so butthurt over how slow a huge company is.
>>340760708
That's because CS's lag compensation is the most ass backwards shit that shoves the hitbox ahead of the model in the direction it's moving in order to counteract the box otherwise falling behind.
Almost every other shooter in the world has proper synchronization that locks the hitbox to what you see by means of client-server rollback, including Overwatch. It's not quite the same, but you could compare it to fighting games' GGPO with the extra benefit of only needing to roll back players on an individual basis. It's the most accurate and fair system since that shit works both ways.
>>340768189
>tfw no multicore support ever
I'm not an expert on fps games or fps servers so I don't want to offer any opinion on the tick rate shit but I actually read this interview and I thought there was merit in something he said, "There's also not a lot of games using a killcam like Overwatch does, so it all sort of makes the problem more evident than I think it would be in other shooters.", He also mentioned how other shooters don't have abilities like Tracers blink or Genji's dash.
>>340768126
>Overwatch do not have instant kill hitscan sniper rifles.
>>340763651
Road hog is the biggest perpetrator of shit tick rate kills I see. I have literally watched someone get hooked from behind a wall. That hitbox+20 tickrate just do not seem to mix.
>>340769178
It has homing projectiles, and it has high damage sniper rifles.
But not instant kill sniper rifles.
You do understand there is a reason to pick beefy characters, right?
>>340768197
SAUCE
>>340769303
Widow maker insta kills anyone but tanks.
>>340769303
A headshot from a sniper rifle in overwatch kills every character instantly besides the 5 tanks. There is literally no functional difference between those types of snipers aside from cases that involve those characters, that still die in two hits anyway (or are killed if any kind of chip damage has been applied).
What's TF2's default tick rate? Light Googling tells me it caps at 66, but what's the standard? 33?
>>340769601
Dota defaulted at 24 until they changed it to 40, so I can't image it being any different.
OP is a fag, blizzard just asked people to test the higher tickrate for them
>>340769303
>pick the beefy characters
>who all move slow and the two out of the three with shields can't kill a Widow without lowering their shield
>Winston can't chase a Widow who uses the grapple towards her team because her SMG would melt him from a range
>>340769582
And only 2 characters has access to said weapons.
Some characters has ultimates that deals a lot of damage, with 1-3 seconds of wind up or visual cues.
>>340764261
>TORtanic will happen, you'll see!
>>340769601
By default it's 33 but the max is 66
you need god tier servers to be able to run a higher tick rate, or a game that looks like a potato (cs go)
the reasoning is because the higher the tick rate, the more latency will fuck you in the ass
the problem with overwatch and cod, is there is a lot of shit going on in the game, between ults and fancy graphic shit, which complicates things in the sense there's more things to send back and fourth with the server, where as a game like csgo it's pretty basic and to the point so less clutter
on one hand, high tick rate does and can work, but it's really dependent on the game, and the servers
and honestly speaking, servers and net code and the types of games just don't make high tick rates viable right now
if you want a good examplke, bf4 did a 60hz server, and ran into massive problems on maps with water because of the physics
the more pretty the game, the more crazy shit going on in the game (ults for overwatch, all the different kinds of attacks, all the kill streaks for cod), the more you will lag like a little bitch
>>340760474
I really don't care if the 20 tick is the problem or not and I'll admit I don't know enough about how netcode is programmed to be able to diagnose that as the issue.
What I DO know is that Overwatch has some of the worst netcode I've ever seen, and if they want to keep me playing and get me to buy their expansions or whatever down the line they need to fix that problem. I don't give a fuck if it's because of the tickrate or because Metzen shat on all the servers trying to corrupt them, the game feels unplayable unresponsive.
>>340770763
Graphics have nothing to do with server load. If you're over 15 you should look into suicide as a career choice.
>>340760474
YOU THINK YOU DObut you don't
>>340770774
cod has worse net code, honestly
but the reason it looks so bad is because there's a lot of shit going on in the game, i made a big post just above yours concerning the issues
right now, it's just not viable for a game with a lot of shit going on like cod or overwatch to have a high tickrate, because servers and a lot of peoples internets just can't handle how much info would have to be sent back and fourth
the more basic the game, the easier it is, the more bells and whistles, the more difficult it becomes
i mean bo3 is relatively 'simple' for the most part, but if you play it and get into a game where a lot of kill streaks start to get used, it almost crashes while shit is going on
unless a game looks like a potato and doesn't have much extra to it, high tick rates are extremely difficult
>>340771191
wat, i just fucking gave you an example with bf4, the pretty water has a lot of physics to it and it fucked high tick rate servers in the ass
i was being simple, sure, but generally the 'prettier' a game is, with lots of shit going on, the more tick rate is going to stress it
>>340771651
Graphics have nothing to do with physics, are you mentally challenged? Overwatch maps and projectiles are smaller, simpler and slower than tf2, a game from 9 years ago where people frequently played with 33-66 tick and any arena shooter from 16 years ago where ~100 was standard. Overwatch has very little in the way of CPU intensive gameplay, blizzard is just trying to rationalize their jewry with
>most people don't care
And it's working
>>340771651
> the pretty water has a lot of physics to it and it fucked high tick rate servers in the ass
A water tile is a water tile. Water works like water.
There is no amazing physics system as they claim there is, otherwise rerunning rivers to kill objectives would be a possibility.
>>340771937
nigga
for water to look great, it needs to have a fuck ton of physics behind it
for games to look great in enviornment and lighting, there's a lot of physics and shit in play
for every explosion, for every bounce of an object, there's a lot of physics that come into play, overwatch has TONS of shit going on it it, be it explosives, be it bouncing shit or otherwise
and i'm sorry, but honestly comparing tf2's graphics with overwatch and the type of shit that is going on to get it like that is retarded
>>340760708
>this just makes me want to demand a refund.
BLIZKEKS FINALLY
FINALLY
FINALLY BEGINNING TO REALIZE THEY DON'T HAVE TO EAT BLIZZARD SHIT24/7
>>340760474
They were confirmed to be lying though. Game actually is 20 tick according to reddit and the issue is "being looked into"
>>340771414
Dude overwatch doesn't even have nearly 1/4th of the stuff going on that BF does. All weapons in BF are projectiles, many are automatic so you've got hundreds of projectiles being shot at once at any given time, maps are far larger, up to six times more players on a team at once, and the physics used are way more sophisticated than what blizzard uses.
Additionally all the in game physics in overwatch aside from characters are done client side, shit like boxes and ragdolls don't actually tell the server where they are or what they're doing all the time, just that they exist or have changed state (like if they got hit they'll tell the server they got hit and give it some info like how hard and in what direction but the actual calculations are handled on each computer individually). To my knowledge BF handles a lot more of this stuff server side.
Ults also don't matter at all unless blizzard was insanely incompetent, something like Hanzo's ult is literally just a box flying through the map, it shouldn't take much more to work with than one of his normal arrows.
The graphics don't matter at all for tickrate because again, unless blizzard has some of the most incompetent programmers alive they should all be handled client side. Your computer knows what everything in the game should look like, it doesn't need the server to tell it what to do.
There is no excuse for overwatch not being able to do 60/60 aside from blizzard incompetence or laziness. If a game like BF4 can handle 60/60 with around the same amount of success that overwatch can (considering overwatch's 60/60 physics mode doesn't even work for 20% of people and BF4 actually fixed their high bandwidth option) there is absolutely no fucking reason why overwatch, a game that should reasonably take a tiny fraction of the bandwidth that BF4 requires given how little is actually going on in it comparatively, should feel the need to run at 60/20.
>>340772391
And as I said before games have been doing bouncing things for a long time with more people and higher tickrates, and particle physics aren't computed server side. There's not way you're not underageb&.
>>340772217
'water works like water'
some of you literally are the most stupid and ignorant people i've ever seen
at least some people in this thread said straight up they don't know enough about net code to complain about it, you should take their example and shut the fuck up, i gave you a clear fucking example even of how bf4 ran into problems just with their water and the physics with it fucking a server with 60hz tick rate
>>340772391
You don't know how any of those things are handled, do you?
>>340772639
Link. Googling for it gives a million shitposts.
>>340772391
Almost all of the things you mentionned are client side, not server side.
>>340761407
>your house actually could not be on fire, but only .08 of users use this feature.
>Actually if we were to put out your house, then 20% of the population wouldn't have water to put out their house. Since the population of the earth is 8 billion you can understand why we wouldn't want to hurt that 20%
>>340772746
>i gave you a clear fucking example even of how bf4 ran into problems just with their water
You didn't you asshole. You trusted a shit press release
>>340773145
I can't think of any clever ways to put these things, but don't forget the other problems with their "fix"
>custom games can't be played over matchmaking, so you need to take the extra work to find a group of 11 other people to play with
>you don't get xp from custom games
>no server browser
>Play at ping of 60ms
>Lowest I ever seen in any game ever
>McCree or Soldier 76 use their ults
>Run behind wall to avoid
>Die as I reach cover
>Pharah
>Gunfight with enemy
>Shoot rocket at nearly dead enemy
>Die myself of hitscan
>Rocket disappears halfway through
>Kill cam shows I never fired that last rocket
Favor the shooter my ass
>Watch network code video
>"We favor the shooter, but we also reward players for using their evasive skills"
>"When a Pharah uses her launch ability, she's virtually invincible for the beginning of the jump"
>Play Pharah
>Get shot at
>Press shift
>Get launched
>Die immediately 6 feet above ground
>Kill cam shows me getting shot as if pressing shift right before last bullet hits
>Enemy didn't even need to adjust aim
Gee, what a great and fulfilling escape I made!
>0.08% of all matches
Because nobody uses custom matches, and even few of those who might do, actually know about the feature.
arguing is pointless you fucking scumbags
either way, the uglier a game is means the less physics involved means the easier it is to crank the tick rate
cod has shitty netcode, overwatch apparently has shitty netcode, but it's not as easy as it would be for say, csgo or something
the battlefield team is one of very few that actually know how to have a modern looking game with high tick rateZ
blizzard is usually pretty good with supporting shit, and if they want into the competitive scene they probably will have to up it at some point, but i wouldn't hold my breath considering cod has had increasingly shitty net code for like ever and hasn't even bothered
>>340760474
>custom games
who the FUCK uses custom games
How can one person be this fucking dense/dishonest
the game is not balanced for 60 tick rate
>>340773624
>display a clear misunderstanding of client server relationships
>have some strange fixation with battlefield and call of duty
>type like somebody who failed english class, or is from a third world country
>can't remember arena shooters
yep it's an underage
>>340774020
if you think having 60 tick rate on a modern shooter is as easy to pull off as it was on an old potato arena shooter, you are retarded
>>340765007
>>340765007
this so fucking much, you are all fucking morons if you dont think tickrate doesnt matter and getting played by blizzard
>>340774276
Overwatch is smaller, slower, has less players and uses about the same amount of physics as say UT99 while using 1/5 the tickrate.
>>340773624
>the uglier a game is means the less physics involved means the easier it is to crank the tick rate
See >>340773130
>>340774276
But it is.
Protip: it has something to do with player's inputs and not physics/graphics
See also >>340772653
i agree
ive played on 64 tick and 128 tick servers in csgo. there is literally no difference
>>340762372
>servers run at 60hz
>client only updates at 20hz
>no in-settings option to make client update at 60hz
Battlefield 4 has 144hz/64 players servers, even my 15€ internet manages to keep up. But no, option menus scare console players, better not implement the feature at all.
battlefield 4 probably has a better engine for netcode related stuff than cod or overwatch
the only time cod had resemblance of good hitboxes was when they had an absurd amount of lag compensation in ghosts which came with it's own problems
>>340770241
>who all move slow
All characters are the same speed.
>her SMG would melt him from a range
Just use a barrier then
>>340774874
It was confirmed he was talking shit.
The server updates only at 20hz, client updates at 60hz.
Client ticks 60hz.
Client updates 60hz.
Server ticks 60hz.
Server updates 20hz.
So Calculating, sending, calculating, are all 20hz because receiving is so fucking slow.
When checking network traffic so you can see the send and receive it's like 11ms~ to 41ms~
And in addition the new video here:
https://www.youtube.com/watch?v=nilBzupE4Cc
shows frame rate also affects the netcode somehow, like some fucking amatuer From Software shit.
>>340765007
This. Tickrate isn't the cause of all of Overwatch's problems, but it sure as fuck is the cause of the some of them, and Blizzard is being disingenuous by pretending otherwise.
>>340775529
probably because blizzard wouldn't want to admit like call of duty that they can't do anything about the net code without a completely different engine
>>340760474
>Right now, for example, what we've seen is that it wouldn't work for about 20 per cent of our users
How is that possible? I've never heard of anybody being unable to play CSGO at 128Hz. Blizz full of shit as usual.
server eyes can only see at 20 FPS so it's just a waste at anything higher
Most of the time it feels like what happens in the killcam is the "alternate reality" rather than what actually happened.
>>340776242
>Do Winston's jump pack attack
>Get killed right after my feet leave the ground
>Ragdoll gorilla goes flying forward, carrying all that momentum
>Killcam shows me doing jetpack launch and then just flopping over, 0 momentum
Someday I'll get a recording of this
>>340776242
RETURN TO COMBAT ZONE
>>340776242
I love how the game acknowledges the fact that you used your shift by putting it on cooldown but it still let you die.
>>340760474
>tfw just going to play Ranked for the better tick rate
>Don't even care about ranks or playing super seriously
Definitely not the only person who is going to do this.
Basically going to ruin "Ranked" because everyone just wants to play the game where it responds properly instead of the shit quick play does.
>>340766687
>poorfags, friendless losers, and battleborn buyers false flagging
>>340760708
Good luck
They told me to fuck off when I wanted one IN THE RELEASE WEEK
20 tick didn't bother me until I started playing pharah
>1v1ing someone I have no business fighting as pharah
>they are bad though
>fire a shot that will be a direct hit
>they kill me or someone else kills me just after I fired
>my rocket fucking vanishes
That should not happen
>>340766953
>I am unable to weigh costs against benefits
You're focusing too much on the percentages. The 80% benefit only slightly from this while 20% suffer greatly.Not that I give a shit about third worlders and poorfags but did you expect a company to opt to lose 20% of their playerbase?
>>340760474
>It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
Is he fucking stupid? Of course the vast majority are going to be 20 tick games when that's the only option unless you can get another 11 people into a custom game with you and give up exp etc.
>>340765616
have you dc'd in LoL recently? you HAVE to completely restart your game if you don't want the enemies to be invisible or for your game to have ghost units everywhere
I don't understand though. First he says the game's already at 60Hz, and it's just latency..
Then he says they added a separate mode for 60hz and nobody uses it. So, do quick matches use 60hz or not?
>>340765007
>>340766909
Overwatch is especially shit at this becaue Blizzard coded it to trick the users into believing their game is smooth
https://www.youtube.com/watch?v=2_9uxcS3LuA&feature=youtu.be
In TF2 if you play with shit ping and fire a rocket, that rocket isn't going to appear until it actually fires on the server
In Overwatch that rocket appears instantly on your screen even though it's not actually there. It's user delusion.
>>340761369
because those smart networking people realize he's right and won't 'talk shit at what hes saying'
literally only inbred redditors who buy into CSGO memes think tickrate is the actual source of problems here
>>340760474
i've seen the aim assist in this game at work
20 tick is the least of your worries
>>340778475
Are you ESL? Tick rate is 60, client update rate is not. Fucking read.
>>340760474
>nononono guys you dont understand okay you're idiots it's so plain but it's just not what you think it is so please stop
>>340778475
Look it up on r/overwatch
Basically blizzard was really disingenuous about the tickrate and it is actually 20 hz. The client snapshot/update rate is also 20. No clue how the high tick version works
>>340778269
Does it really? Thought they had fixed that already. I stopped playing like 2 years ago so they could have reintroduced the bug. Even then I'm not saying Riot is good but more that Blizzard is down there in the list of shitty developers.
>>340779128
>Our servers are 60 ticks! They just don't operate as 60 ticks
Same problem anyway you try to slice it.
>>340776620
Well it's simple:
The client get the info that you used your shift, so you started the jump
The server, with its shit tick rate, still thinks you're falling. So it says "this guy's ded".
And since its the server, your client is updated with "you're ded"
That's why, on his screen, he appears to fly, even after being dead, but on killcam, he just fell in the pit
>JUSTWatch
>>340769297
Roadhog has another problem unrelated with tick rate. Basically his hook isn't a projectile but a hitscan with a delay. It's seriously retarded and it causes a bunch of the weird shit like hooks behind walls
>>340760474
Damage control.
Either way it's baby's first FPS made for literal shitters and people bad at videogames and underage.
I want you fucks to start posting on /vg/ and stop spamming your arbitrary threads here. This topic however warrants a /v/ thread.
>>340779710
>Cuckedwatch
>>340779825
>Seriouslywhydidnoonebothertalkaboutthiswatch
>>340760708
You can literally shoot through walls in CS you fucking yuro moron
>>340779314
>No clue how the high tick version works
It doesn't.
>>340760474
How can one man be so ignorant
He is literally belittling the consumer
When you can play head to head using LTE wifi from your phone while the other person is using a Ethernet cable , 100mb download 30 upload etc and you can land every shot because their hitbox is fuckhuge but they can't then you got a problem
>>340779553
Isn't it the server that is 60 tickrate and the client that sends at 20? So it is more like shift is pressed on the client, but it is not sent to the server until later unless a tick was already just about to happen, then the server updates with the delayed information and calculates the player died so it sends that info back to the player.
>>340763683
>one of the most popular rts
The game is dead and has been dead for ages
Korea stopped its broadcasting channel for 2 and made it into another channel for 1
isn't the whole deal that even if the client tickrate was 60, it wouldn't change the deaths or whatever? All it does is keep you up to date with the server, which has a receive-rate of 60.
>>340770382
And one of them is a core pick on good teams.
>>340767561
You probably spent 20 maybe 30 minutes to type out all that shit that not even you understand so for that here is a (you) for your efforts
>playing Hearthstone - The Shooter
>All these webms and shit with 60+ms
>I always have 20 ping
>Die behind walls, get teleported by McCree flash bangs, hooked behind corners, my projectiles disappear, Genji dashing through a target for a kill and getting teleported back while dying in kill cam.
This is the only game I have problems with.
If I had reviewed this multiplayer only game I would take a full point off because of how the netcode and 20 tick work.
Of course "people" (see Blizzdrones or the UC4 spastics) would have shit all over it and I would have gotten flack from higher ups for giving a Blizzard game a 7/10 instead of the 10/10 MASTAH PIECE score it doesn't deserve.
If you make a multiplayer only game and the multiplayer portion doesn't work well then you should be judged poorly for it.
Shit like DaS gets a partial pass because multiplayer isn't the main part of the game, multiplayer centric games do not deserve a pass. It's unacceptable.
Especially from a company that's been running a god damn MMO for over a decade, they know how networking works, they have no excuse other than wanting more dosh.
>>340760474
>blaming latency
smart thing to blame it on a thing you cant test for yourself
>>340781376
>7/10
It's what I would give Overwatch. Yeah it's fun. But I'm not calling it the best game.
It's clear the consoles are ruining this game for PC users.
>>340766630
CS:GO is literally a console shooter ported to PC.
>>340760474
This idiot is saying latency and tick is the same things and then says.
When the servers allegedly tick at 60, then why not tick the clients at the same rate?
>>340760474
That final part doesn't even make any sense, why aren't other games with higher tickrates having issues with huge amounts of people not being able to play the game due to the tickrate being too high? I dun geddit
>>340779710
>>340779825
>>340780008
>retards who fail to understand just how infuriating a game like this would be without generous hitboxes
Fuck off
>>340784701
people actually defend this?
>>340784810
>>340784701
>HE'S TOO FAST
>>340765086
had something similiar happen to me once, that bug almost ate my savefile. Had to restore some files for some reason after this happened
>>340784916
Doesn't this guy have a Doom review to write?
>>340760474
humans eyes cant see more than 20 ticks anyway
>mfw don't give a single fuck about some tick rate bullshit
Having good time is what matters, bitches.
>>340761131
>custom games
0.08 sounds high if anything
>>340760474
>It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
maybe because there's literally no custom server browser, and they just use shitty auto matchmaking
Finally got to play this on a lads PC.
Pharah is probably the hero on which I experienced the tickrate the most.
Her and Roadhog, but the hook mechanic feels kind of strange in general.
Favor the shooter is more of a problem than tickrate ever was.
>>340785286
This information makes hiking a lot scarier.
>>340760474
>>Right now, for example, what we've seen is that it wouldn't work for about 20 per cent of our users
Then just segregate them. That's how online game have been working for decades.
People with shitty lines / living in shithole get to play on servers with people like them.
I miss autokick feature for anyone above a certain ping threshold.
>>340784916
>Overwatch
>too fast
This guy
>>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
YEAH BECAUSE 99,92% OF ALL GAMES ARE PLAYED ON QUICK PLAY OR BRAWL AND NOT ON CUSTOM GAMES YOU FILTHY FUCKING FAGGOT
HOW THE FUCK IS THIS EVEN AN ARGUMENT?
>>340786954
Doesn't matter if it's an argument or not, Blizzdrones will still eat it up
>>340760474
>>The other thing that we did, after that video, is we actually added what is called a 'high bandwidth option' to our custom games, that allows players to play at a 60Hz update rate. It's kind of ironic that they're demanding it, it's in the game and playable, and right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
jesus christ. neo-/v/eddit needs to kill itself for shitting on blizzard when this exists.
>>340760474
>b-but you don't understand
>all those other games with higher tickrate that perform better don't count!
Blizzard damage control is especially funny to watch because it's so pathetic.
>>340787561
>when this exists.
When what exists? Proof from the developer's mouth that they don't even understand that most games are being played through matchmaking and not custom games?
>is we actually added what is called a 'high bandwidth option' to our custom games
>right now we're seeing about 0.08 per cent of all matches that take place in Overwatch are actually using the feature.
Yeah no shit, when you try it the server keeps crashing.
it'd be great if when I made a custom game, regular people would join my game with quick play
>>340787864
this right here, holy fuck
nobody is making a custom server and fucking around, everyone hits "go" and goes
>>340760474
>>340778797
Shit post and totally wrong.
>>340760474
>implement a way to play with 60tick
>bury it in custom games so you need to invite 11 other people to play
>not having a choice alongside quickplay, brawl, etc that is essentially 60tick quickplay testing
>>340760474
20 clientside tick rate means no matter how good your reaction time is you will still be hit if someone shoots even near you
it lowers the skill cap casual trash
