Oh my god, I had a comp game a while back where the enemy team just randomly won before capping the 3rd point. Now I can finally retire knowing that this mystery, the source of so many sleepless nights has been solved. Thank you
@@Marblr You obviously don't have to but it might be nice if you'd add people that helped you in the video description. I mean who doesn't like being appreaciated, right?
I saw it happen once in my comp match, on last point of Numbani. It kinda remained uncaptured, but the sides swapped right after (?) I was starting to think its just a visual bug on match proggress bar
@@focusprxand that knowledge is impressive. While we have some tools to peek into the game a bit, like Workshop, a lot of it is left to speculation unless you're really into it.
Due to how difficult this is to replicate and there have been seemingly no changes to affect how payloads work, it's possible, and even likely, this has been in since OW2's release, maybe even OW1. The fact that it's been there for at least a year and is only just now discovered highlights how insanely rare it is.
I think this happened a couple times in some matches that I was in. It's extremely rare, but it is blizzard so I'm not surprised they let a bug like that slip through the cracks.
@@kid10249595 to be fair it's a bug one can't normally test for, and due to its rarity and lack of big content creator calling it out it probably went unnoticed
Imagine having a shit losing streak and on your “final” game of the night where things are finally going greatly, this glitch just pulls up and shatters your hopes
I do believe it happened once during a multi-streamer event in France back in 2018-19. On a custom competitive game on Hollywood, the gate after the 1st point didn't open. They had to redo the game. If i recall this event correctly, then this bug is present in the game since Overwatch 1, so your theory about the infinite number of games seems pretty solid x)
Heya! Just wondering if there is there a way to visualize how close to the cart you need to be to push it? I've noticed it is easy to c9 the cart on Dorado on the back side, yet on the front you trigger it from pretty far away, it feels like the model and the zone to trigger a push are misaligned
@@philogl the push volume is a sphere centered on the payload's origin point (the dot shown at 0:39). I believe the Dorado payload's origin is toward the front of it, so a sphere would extend much further in front of the cart than behind it. I don't know what the radius of this sphere is offhand.
I think i actually had this happen once before and was wondering why the payload clipped through eichen's castle doors before the animation had a chance to play. Very interesting lmao
That's odd. Someone else in the comments saw a similar thing happen with the gate doors in Hollywood. But instead of clipping through the doors, the car got stuck in the doors
Had to watch multiple times to understand the competitive desync, the imagery really really helped, especially the gray dot that's representing the goal Awesome work as always
My guess as to the fact that you have to push it right as it starts rolling backwards is likely logic to prevent nodes from being re-triggered in error by the payload moving backwards. IE if the junkertown payload moves back over the gate closing node, it will not attempt to close the gate again, since it detects the payload is moving backwards. And thus this applies to checkpoints, for a single tick, the checkpoint is detecting that the payload is moving backwards so it doesnt activate that checkpoint node
That would mean that nodes would get triggered again if you let the payload roll back and then over the node again though (in a normal situation without the glitch)
@@SoWhom No, what I meant is, in a normal game, if you got CP1, then the payload went backwards to before CP1 then went over it again, you'd get the extra time again That doesnt happen
6:56 "Perhaps given an infinite number of Overwatch matches, every possible bug is bound to happen eventually." Man, I hope I end up in the Overwatch match where the "lucio gets buffed" bug happens
just wanna say that although I don't have any plans on playing OW2 again - these videos are still super fascinating and are so well put together. Keep it up, love the content. :)
I don't even play Overwatch anymore, but I continue to come back to your videos. Your prose and straightforward editing style makes each video a really enjoyable experience.
idk this is so rare and i've literally never seen it happen in 1k+ hours. It might have even existed in ow1 tbh. They might not even know about it or its so obscure its not a priority
@@Zen-db5pp It stands for Player Vs Everything. He's referencing the gamemode that blizzard promised would be coming with Overwatch 2 but the executives scrapped the entire thing which was 4 years of work.
The infinite monkey theorem states that a monkey hitting keys at random on a typewriter keyboard for an infinite amount of time will almost surely type any given text, including the complete works of William Shakespeare.
Your videos always remind me of one match I’ll never forget where I was playing Zarya on Dorado. We were fighting on that 2nd checkpoint where the gate opens, and both teams were contesting point for extremely long. All our stats were so high, we really contested point for so damn long. Eventually we died to a junkrat ult. 😢One of the funnest matches ever.
Oh god, this is a fun one. Aside from not being able to win, it's worth pointing out the the spawn room not changing **combined with** no extra time being added makes for a truly uphill battle.
Blizzard should look at all of Marblr’s RUclips vids like this, it shows such an amazing tutorial on the bug, a good intro, good editing and explanations. Like someone give this man a raise ffs.
I know im a year late to the party, but I have a pretty good guess as to why this is. The logic for this moment likely looks something like this: if payloadDistance equals checkpointDistance; checkpoint = captured; When the first line should be: if payloadDistance >= checkpointDistance; This code is likely only run when the payload is actively being pushed. In other words, in order for the checkpoint to be captured, it must be actively pushed, and have its distance equal the checkpoint distance, which works fine in most cases. But, depending on the exact order of operations, what ends up happening is this: Tick 1: payload is being pushed Between Tick 1 & 2: payload stops being pushed (game will not register this until Tick 2) Tick 2: payload reaches checkpoint, and is no longer being pushed, so checkpoint is not registered Tick 3: Payload is being pushed, but distance no longer equals checkpoint distance, so it is skipped (because the payload has started moving) The fix in this case being that the checkpoint should be recieved if the position is >= the checkpoint distance, or alternatively have it collect the checkpoint regardless of whether its being pushed or not
@@jessicastjames6202 Now I'm wondering what happens if on a payload map the first team were to do this glitch and make it to the end with zero points, like once they make it to the very end they just forfeit the rest of the round. Like does the other team win as soon as they reach the first checkpoint and score a point? Or would they have to make it to the end while also using the glitch? Since the distance is x meters away from the last checkpoint, I think the second team wouldn't be able to win (purely based on distance rather than points) if they hit the checkpoints, since the first team has the distance of the whole map while the second team would keep resetting their distance and only have 1/3 at most of the first team's.
this explains all the times that we're near the 3rd checkpoint and I'm spawning at the default and having to pin across the entire map, losing a whole minute as tank
this looks easy to fix. The progress is still registered even if the checkpoint is missed. The game logic should define if the checkpoint was reached by checking the distance the payload traveled, if it is greater then the distance from the checkpoint to the beggining of the path, then the payload reached the checkpoint.
My theory for this is that the payload point travels beyond the checkpoint in one frame, thus bypassing it. Pushing the payload from its reversal state might "kickstart" the payload forward, making it travel further than it normally would in one frame so thats why you need pixel perfect timings.
You and nobody else knew about this glitch until marbler uploaded this video. Are you really surprised or are you just pretending to be to justify your absurdist anger against a video game company?
@@conceptualization.6617 is it though? The group think consensus was that blizzard couldn’t find their ass with two hands and a map yet all you put your immutable faith in them because what Jeff made promises and left not even a year in? And then because communities are often harbingers of their own doom they continued to work on the fools errand why? Because they knew that if they stopped working on the stupid damn campaign exactly what’s happing now would happen. Jeff put overwatch updates on hold for nearly 4 years because he wanted to make a stupid fucken campaign that nobody but streamers and lore nerds wanted.
If I had to have a *guess* at the reasoning I would imagine the logic is something like this Is Payload at Node? Yes. -> Node type check. Node = Checkpoint -> Is payload velocity >0 (i.e. is it moving forward). No. -> Do not change checkpoint captured flag. So on the single server tick that pixel occurs, the information taken is that the payload still is moving backwards (especially if referenced from the previous server tick), and the game thinks, oh it's just rolling backwards, don't do anything
![5,000,000 Damage Mitigated [PATCHED]](http://i.ytimg.com/vi/i88R8MEV8AE/mqdefault.jpg)
Turn payload maps into push maps with this one simple trick! Non-mobile heroes hate it!
LMAO
xD
casual push players:
the Doomfist with top 500 level rollouts:
@@sakucelty the chadfist
SHH DON’T GIVE THEM IDEAS!!!!
"Perhaps given an infinite number of Overwatch games, every possible bug is bound to happen"
-Ow2 hot fix motto
"And thats why we are cancelling PVE, we need to focus on bugfixes!!1!"
It's like the monkey with a typewriter thought experiment
@@lnemf I mean, yeah. "Within infinity, everything"
@@lnemf no the idea is that the monkey actually does something
@@beybladetunada5697 they were stripped of their resources and were expected to make the same game, what did you expect?
Oh my god, I had a comp game a while back where the enemy team just randomly won before capping the 3rd point. Now I can finally retire knowing that this mystery, the source of so many sleepless nights has been solved. Thank you
I want this to happen in OWL so bad
For Real
Would they reset the march if it actually happened?
@@miguelcruz7826 yeah absolutely they'd replay the map
@@phil1500 probably ban everyone and then declare it a draw for existing near a bug
event organizers should orchestrate this so OWL is actually somewhat interesting
Imagine staying up until 4am brute forcing locations for this, couldn't be me
Smile
@@spookiboys :)
I can't believe you managed to replicate this one tbh. Actually insane
It's... fairly easy to replicate. In custom games, I mean.
@@SethJV figuring out how it happens is the reason why it would be difficult
I had some help from other users -- namely Coathar!
@@Marblr You obviously don't have to but it might be nice if you'd add people that helped you in the video description. I mean who doesn't like being appreaciated, right?
I saw it happen once in my comp match, on last point of Numbani. It kinda remained uncaptured, but the sides swapped right after (?) I was starting to think its just a visual bug on match proggress bar
imagine being a blizzard dev and finding out your tasks through Marblr
Marblr should be hired by Team 4 since he clearly knows this game better than the devs
imagine being a blizzard dev PERIOD
lmao
“hm ok let’s see uh nothing to do today. um. hrm. oh Marblr uploaded, i guess i’ll watch it, might not fix it if it’s too complicated.”
Don't think it's uncommon for game devs to find bugs through social media.
It's truly amazing how you find these and the reasons. Keep up the overwatch science
He gets them sent to him but the way he finds out why is impressive
when you know the games mechanics it’s easy to replicate bugs like these
@@focusprxand that knowledge is impressive. While we have some tools to peek into the game a bit, like Workshop, a lot of it is left to speculation unless you're really into it.
Due to how difficult this is to replicate and there have been seemingly no changes to affect how payloads work, it's possible, and even likely, this has been in since OW2's release, maybe even OW1. The fact that it's been there for at least a year and is only just now discovered highlights how insanely rare it is.
Been there since day 1. It happened to me at least twice and I only played Ow1.
@@fidel_soto oh yeah it happened to me 5 times and i played overwatch one time
Sometimes things exist for a while but nobody knows until somebody popular covers it
I think this happened a couple times in some matches that I was in. It's extremely rare, but it is blizzard so I'm not surprised they let a bug like that slip through the cracks.
@@kid10249595 to be fair it's a bug one can't normally test for, and due to its rarity and lack of big content creator calling it out it probably went unnoticed
Imagine having a shit losing streak and on your “final” game of the night where things are finally going greatly, this glitch just pulls up and shatters your hopes
I do believe it happened once during a multi-streamer event in France back in 2018-19. On a custom competitive game on Hollywood, the gate after the 1st point didn't open. They had to redo the game. If i recall this event correctly, then this bug is present in the game since Overwatch 1, so your theory about the infinite number of games seems pretty solid x)
link? :3
I'll be looking at this bug on stream if you want to ask questions or just hang out: www.twitch.tv/marblr :)
Hello. Do u plan on expanding your content to other games eventually?
@@marzman4 There are a couple other games I'd love to explore!
Heya! Just wondering if there is there a way to visualize how close to the cart you need to be to push it? I've noticed it is easy to c9 the cart on Dorado on the back side, yet on the front you trigger it from pretty far away, it feels like the model and the zone to trigger a push are misaligned
@@philogl i have the same issue too on dorado .
@@philogl the push volume is a sphere centered on the payload's origin point (the dot shown at 0:39). I believe the Dorado payload's origin is toward the front of it, so a sphere would extend much further in front of the cart than behind it. I don't know what the radius of this sphere is offhand.
I think i actually had this happen once before and was wondering why the payload clipped through eichen's castle doors before the animation had a chance to play. Very interesting lmao
That's got to be the most common place for it to happen tbh, I've not seen a bigger clusterfuck of a checkpoint ever
That's odd. Someone else in the comments saw a similar thing happen with the gate doors in Hollywood. But instead of clipping through the doors, the car got stuck in the doors
“You’ll have to walk a marathon to get to the payload”. Devs saw this and thought it was actually a good idea. Thus push maps were born.
And flashpoint
Hey we heard u like 2cp and holdingW from spawn so we made 5cp with walking element of push. Heres flashpoint, enjoy
Had to watch multiple times to understand the competitive desync, the imagery really really helped, especially the gray dot that's representing the goal
Awesome work as always
Man that point skipped harder than the OW2 developing team skipped PvE
These are literally my favorite OW videos, i love this stuff.
My guess as to the fact that you have to push it right as it starts rolling backwards is likely logic to prevent nodes from being re-triggered in error by the payload moving backwards. IE if the junkertown payload moves back over the gate closing node, it will not attempt to close the gate again, since it detects the payload is moving backwards. And thus this applies to checkpoints, for a single tick, the checkpoint is detecting that the payload is moving backwards so it doesnt activate that checkpoint node
That would mean that nodes would get triggered again if you let the payload roll back and then over the node again though (in a normal situation without the glitch)
@@talymenombrenuit3659 that is what happens as demonstrated in the video
@@SoWhom No, what I meant is, in a normal game, if you got CP1, then the payload went backwards to before CP1 then went over it again, you'd get the extra time again
That doesnt happen
6:56 "Perhaps given an infinite number of Overwatch matches, every possible bug is bound to happen eventually." Man, I hope I end up in the Overwatch match where the "lucio gets buffed" bug happens
I completely purged myself from anything OW related, except for this channel, these videos are great.
My favorite overwatch content! It's interesting seeing how the game works behind the scenes.
Apart from ability to find and reproduce bugs of any complexity, I've always been delighted with your video editing skills
just wanna say that although I don't have any plans on playing OW2 again - these videos are still super fascinating and are so well put together. Keep it up, love the content. :)
It's all good, the developers are really busy working on PVE so these bugs are bound to happen.
DOES HE KNOW?
Any day now pve will be released perks and all. I cant wait
no one tell him
@@georgerice6488 I love the part where Mei cryofreezed all over the place and froze PVE progress forever.
May it rest in peace.
@@crangejo Probably, that comment is dripping with sarcasm
I was always about to ask “well what if….” And then you answered it. Great job!
3:00 hey look, it turned into the push gamemode!
I don't even play Overwatch anymore, but I continue to come back to your videos. Your prose and straightforward editing style makes each video a really enjoyable experience.
“Escort, Hybrid, and Push are temporarily disabled. Only Control maps are available in Competitive.”
lmao
fr?
Hey Marblr, really missing the videos, always loved watching your style of videos. Hope you make a new one soon!
Marblr putting more time in ow than devs themself
Pve
@@veretxnerd983 What pve?
nah the devs put they life into this shit. u should be mad at blizzard executives
idk this is so rare and i've literally never seen it happen in 1k+ hours. It might have even existed in ow1 tbh. They might not even know about it or its so obscure its not a priority
@@Zen-db5pp It stands for Player Vs Everything. He's referencing the gamemode that blizzard promised would be coming with Overwatch 2 but the executives scrapped the entire thing which was 4 years of work.
National Marblr Upload day!
The visuals came in clutch. Especially with the Comp Desync cos I didn't understand at all without it 😅
This is the first bug of yours ive actually experienced in game, and its a rare one too
The infinite monkey theorem states that a monkey hitting keys at random on a typewriter keyboard for an infinite amount of time will almost surely type any given text, including the complete works of William Shakespeare.
Your videos always remind me of one match I’ll never forget where I was playing Zarya on Dorado. We were fighting on that 2nd checkpoint where the gate opens, and both teams were contesting point for extremely long. All our stats were so high, we really contested point for so damn long. Eventually we died to a junkrat ult. 😢One of the funnest matches ever.
Oh god, this is a fun one. Aside from not being able to win, it's worth pointing out the the spawn room not changing **combined with** no extra time being added makes for a truly uphill battle.
"Perhaps given an infinite number of Overwatch matches, every possible bug is bound to happen eventually." (Marblr's ergodic hypothesis)
Why and how do u know that word
@@sjshdjdjesj5628 I do physics
5:06 I'm floored by the efficacy of that animation in explaining what's going on
Marblr is giving us better content than dev team itself lol
Great, high quality video!
Blizzard should look at all of Marblr’s RUclips vids like this, it shows such an amazing tutorial on the bug, a good intro, good editing and explanations. Like someone give this man a raise ffs.
honestly love your content, thank you
Wake up babe, marblr posted
Dude your voice is so soothing. I could listen to you explain game bugs all day
as someone who has done lots of editing with the sm64 castle theme as background music seeing the ending sync was a treat
this is so well edited for a payload glitch 😂
Very well produced video, explanation and easy to hear voice. Well done!
production hero is unreal! Very well done
0:04 I can't believe you pulled a Hazy Maze Cave. Triggered my fight or flight with that one.
I know im a year late to the party, but I have a pretty good guess as to why this is.
The logic for this moment likely looks something like this:
if payloadDistance equals checkpointDistance;
checkpoint = captured;
When the first line should be:
if payloadDistance >= checkpointDistance;
This code is likely only run when the payload is actively being pushed.
In other words, in order for the checkpoint to be captured, it must be actively pushed, and have its distance equal the checkpoint distance, which works fine in most cases. But, depending on the exact order of operations, what ends up happening is this:
Tick 1: payload is being pushed
Between Tick 1 & 2: payload stops being pushed (game will not register this until Tick 2)
Tick 2: payload reaches checkpoint, and is no longer being pushed, so checkpoint is not registered
Tick 3: Payload is being pushed, but distance no longer equals checkpoint distance, so it is skipped (because the payload has started moving)
The fix in this case being that the checkpoint should be recieved if the position is >= the checkpoint distance, or alternatively have it collect the checkpoint regardless of whether its being pushed or not
holy fricking heck I have seen the junker town gate happen, and not just one bu a few tiems so THIS is why D:
Wealth over here in TF2 we don't need to worry about people doing that as a bug
I love this RUclipsr
imagine a game where this happens, and they reach the end without winning… will it just be overtime til the attackers c9?
Imagine in Total Mayhem, the attackers wouldbe so tilted
@@jessicastjames6202 🤓
@@dikiyhuybruh
@@jessicastjames6202 Now I'm wondering what happens if on a payload map the first team were to do this glitch and make it to the end with zero points, like once they make it to the very end they just forfeit the rest of the round. Like does the other team win as soon as they reach the first checkpoint and score a point? Or would they have to make it to the end while also using the glitch? Since the distance is x meters away from the last checkpoint, I think the second team wouldn't be able to win (purely based on distance rather than points) if they hit the checkpoints, since the first team has the distance of the whole map while the second team would keep resetting their distance and only have 1/3 at most of the first team's.
@@wargex Considering that the attackers would have far spawns, yeah that's never happening for a long enough time
I lost a comp match to this. I even still have the clip saved on Xbox and shared it to the subreddit and they just understood it to be a bug
this explains all the times that we're near the 3rd checkpoint and I'm spawning at the default and having to pin across the entire map, losing a whole minute as tank
Meanwhile in tf2 you gotta make the payload go 100+ mph for desynchs, and more
Nothing better than Marblr uploading
im throwing all my comp games like this now thank you!
WAKE UP BABY, MARBLR RELEASED A VIDEO.
I could listen to you explain Overwatch bugs forever
Best OW2 new content is the bugs we can't comprehend how the devs created them
High quality content yet again! Keep it up!
Payload just phasing through the door on Eichenwalde as the crusaders watch in horror
Blizzard should be paying this man for doing a lot of their work for them
this looks easy to fix. The progress is still registered even if the checkpoint is missed. The game logic should define if the checkpoint was reached by checking the distance the payload traveled, if it is greater then the distance from the checkpoint to the beggining of the path, then the payload reached the checkpoint.
love the content.
i sure hope blizzard can fix this quickly since they are focusing more on PvP. best company fr!
They need that manpower for the shop 💪😎
Excellent music choice
Blizzard hire this man
"Perhaps given an infinite number of Overwatch games, every possible bug is bound to happen" - this is an actual testing strategy called 'fuzzing'.
The gate trick in dorado happened to me once in competitive, we were all confused as heck
Cool vid! Also I played in a game w you earlier on emonggs stream. Had so much fun! -screamyposum
Great game, Blizz.
Game itself don't work but the shop works just fine!
The Vandiril of overwatch 😂
So glad Icould be in this video, what a cameo
thanks for the heads up marblr
the timed hazey maze theme on the intro is a 10/10
Daddy Marblr is back with another banger
ah yes, OW2, a great game with no bugs and an amazing PVE that exceeded everyone's expectations
My theory for this is that the payload point travels beyond the checkpoint in one frame, thus bypassing it. Pushing the payload from its reversal state might "kickstart" the payload forward, making it travel further than it normally would in one frame so thats why you need pixel perfect timings.
The timing sounds so precise on this one it has to be one of the rarest bug, but losing a ranked game because of it would drive me crazy
00:01 me in driving school
I love your work, please keep it up !
new marblr video lets gooooo
Are we surprised of these glitches existing anymore with the recent actions of blizzard
weird correlation, but yes blizzard has some spaghetti-like code.
You and nobody else knew about this glitch until marbler uploaded this video. Are you really surprised or are you just pretending to be to justify your absurdist anger against a video game company?
@@thedude4840 this bug and blizzard's inability to respect their consumers aren't related, but being angry at them is justified regardless
@@conceptualization.6617 is it though? The group think consensus was that blizzard couldn’t find their ass with two hands and a map yet all you put your immutable faith in them because what Jeff made promises and left not even a year in? And then because communities are often harbingers of their own doom they continued to work on the fools errand why? Because they knew that if they stopped working on the stupid damn campaign exactly what’s happing now would happen. Jeff put overwatch updates on hold for nearly 4 years because he wanted to make a stupid fucken campaign that nobody but streamers and lore nerds wanted.
@@conceptualization.6617and you still play lmfao
Love the ssbm music you use.
I was 0.01 meters away from winning an escort comp game yesterday and this just gave me bad memories
cool little rare bug. thanks maxor.
Marblr the king of finding bugs and being the reason they get patched🤣
Thanks for the awesome content and great videos!!
Lets go new Marblr video!
Now think of how many times this happened in a real game without anybody noticing.
This man is the way
If I had to have a *guess* at the reasoning I would imagine the logic is something like this
Is Payload at Node? Yes.
-> Node type check. Node = Checkpoint
-> Is payload velocity >0 (i.e. is it moving forward). No.
-> Do not change checkpoint captured flag.
So on the single server tick that pixel occurs, the information taken is that the payload still is moving backwards (especially if referenced from the previous server tick), and the game thinks, oh it's just rolling backwards, don't do anything
If it used this logic, then maybe a potential fix would be to wait for the next server tick and re-check the velocity
Your videos are so good bro
Great stuff as usual
ik the PvE news is devastating but you're like the best OW content creator pls dont leave 😭😭
Melee music is so good
This definitely feels like a Shounic video within the first 20 seconds.
This happened to me when I was on defense, but it happened on an overtime.
Now I know why we won and I feel bad for the Ana that deserved her win 😔