I'd say the deletion delay looks to be tied to how long the death particles should stay around. Riptire and immortality field are pretty small, so they disappear and nobody notices. Mecha and turret leave behind big chunks though, so it makes sense to wait a bit more until those go away
That would also explain bob's weird 10.2 seconds thing, since normally he would do the jump animation to leave the battlefield right on the 10 seconds mark and then dissapear for good, he's probably scripted to be deleted after the 10.2 seconds (ult duration + jump animation) regardless of his current state, even if he died, wonder if inmortality and tire also behave like that if you somehow avoid their extremely quick death animations
@@LuigixD Bob's entry is deleted 0.2 seconds after ult ends as he leaps out of the map. For player he doesn't exist anymore, therefore it can be deleted at an instant when he finishes his jump out animation without long delay. For 7.5 seconds after death - idk, maybe to make it similar to players' respawn timer cuz he is big major threat and autonomous separate character with vulnerabilities and hit boxes similar to normal heroes
Knowing the way the team colors work behind the scenes makes me wish there was a way to always show your team as blue in replays. It’s so counter-intuitive to see your own team as “the enemy” when watching a game back
Does anyone know in those replays how the red and blue teams are chosen in modes like Control and Push, when you have the same neutral area to be taken by either team?
@@ccricers I would guess that it has to do with the order in which each team is populated. The match maker selects the first person, and then places that person into team 1. Then the match maker runs its algorithm to decide which players out of the pool will be that players teammates and enemies. Which group is on team one or team two likely also decides which is attacking or defending. Obviously I don’t know for sure, but I would guess this is how it would work since it is irrelevant which players are on which team, but it would still make sense to index the first player selected as team one (basically the first player is in the first element of array one aka team one). Then again, I am looking at this from a data engineer perspective, I’m not a game dev and I don’t know how good or bad overwatch’s data structure practices are.
As a workaround you could use the color blind filter to set colors correctly, if your team is red, just switch it out. Just remember to reset them before going into game again lol
I think it happens when the person that got killed leaves the game while the killfeed is still active, so maybe bc their data gets deleted or something?
yes, this also happens when player entities are deleted. I showcase this at 2:26 by manually deleting winton via the workshop. I had trouble getting it to occur "naturally" by leaving a server, but it's good to know that it is sometimes possible.
I've had this happen with echo dupe where an ally killed an enemy echo dupe and said ally turned red in the killfeed. I don't even want to imagine the hellish spaghetti code that results in this glitch.
I'm so happy this channel exists and you're doing such a great job. I've always had these super specific questions nobody ever answered online and you're out here answering them in such an intuitive and we'll constructed and edited way!
I’ve had this happen in deathmatch to players while waiting in queue, pretty minor but it’s still pretty wacky since this wasn’t in ow1 to my knowledge.
it must occur when a player finds a game after getting a kill/being killed -- they are taken out of the server and their entity is deleted. I tried to reproduce this manually by leaving a game myself via the pause menu, but couldn't get it to work. thanks for the info!
@@Marblr i've seen it happening in queue deathmatch since OW2 launch, if right after you kill someone they get put into a game their killfeed icon changes to blue from red
@@Marblr well you can consider 2 things maybe 1 the entity data isn't deleted until that space on the team is filled by a new player, or 2 that entity data is linked to players specifically and not just in the one match so when they join a new match their entity data is taken with them. That's why it occurs when they find a match and not when they just go back to the menu.
I noticed this too and it's been bugging me. Same thing happens when someone leaves in Deathmatch, or in hero gauntlet, when they kill someone and automatically switch to another character. Also I've noticed that whenever someone use the "I'm with you command", it will Always display your name but with the incorrect character "Orisa (Player name)" even tho you're DPS/support.
no way, I've seen this a few times and just thought it was one of those weird quirks I'd never understand but Marblr is here to save the day again. Keep up these videos, they're so informative and well made.
I really want to know what could’ve possibly happened for the overwatch team to update the game and make the payload timer say “unspecified” at the end of payload maps since it wasn’t a thing before season 2
Hey Marblr, just wondering about the bug that turns the target select from red to blue. I've noticed that some times on Zen and Echo, Zen's discord orb target select goes from red to blue, and so does Echo's when she has ult. Just wondering if there's a similar explanation or if it's black magic.
there is something even stranger going on with the targeting UI color, since it changes back and forth between the friendly color and the enemy color for both teams. perhaps related to this, but it definitely does not share the same characteristics.
just adding that I also have experience the UI color change on Zen! It changes to blue for enemy targets and every time causes me to take a second a look at who I'm discording!
I absolutely love this channel. Just straight to the point info with insane production quality! and it combines two of my favorite things, overwatch and spaghetti code
I don't know if this is something that only happened to me, but in the Practice Range, there is an specific spot in which you don't die when falling off map, specifically behind the practice characters
Yes! I thought I'm the only one. I don't know exactly WHY I got there, but I used Echo's Flying ability and didn't die in that spot. Only if you move a mm to the side, you die.
There are a lot of places like that in the Practice Range, I've spent a lot of hours with my friends with Pharah trying to find all of them. (Mei's wall and Sym's teleporter could help too)
Nice explanation, one thing I also noticed that helps explain this is that when playing torb if you hit the air where your turret used to be with your hammer, it will continue to make the metal noise until the color changes at the top right. nice video
Int endorsement; Int pEndorsement; Void AfterMatch() { If (GainedEndorsment()) pEndorsement = endorsement++; If (endorsement ‰ 20) LevelUp(); If (pEndorsment == endorsement) endorsement--; }
They've kept the system a highly guarded secret. Regardless, I lose endorsement levels when 5 stacked, when I literally can't get endorsements. So I dont think they bothered to fix it for OW2.
It doesn't matter because if you use endorsement to track anything in Overwatch then you are part of the problem of overwatch. The endorsement system is only for getting extra XP of you want it
@@GummyDinosaursify for generations, the dreaming city housed one of the awoken's most closely guarded secrets. it is known as the endorsement system, the endorsement system of a thousand voices
I noticed a very interesting bug that could be a topic for the next video: I was playing QP (so, no deathmatch) when an enemy Orisa threw a javelin, hit someone with it (don't remember who), and the javelin knockback threw them off the map. The killfeed did not display the javelin icon, but it displayed the icon for Halt! Why do you think this is?
I’ve also seen player icons also change colors if they leave the game immediately after being killed. Plenty of times have I high nooned behind a team, killed a solo zen and they promptly alt-f4, therefore causing the player icon in the killfeed change colors.
I have a hunch that there's a draw call for the killfeed, which is constantly trying to access that entity's team color, instead of caching it like everything else. Why this change occurred may have something to do with an attempt to try and conserve memory. If "performance boost" is ever mentioned in the patch notes, that might be it.
Funny thing, I have actualyl seen this bug again with the new Battle For Olympus game mode where after a bit of time one of the killed enemies was suddenly turning blue, sadly couldn't take a screenshot in time
I literally noticed this during some gameplay the other day and was thinking if you were gonna make a video on this- Guess I didn't have to wait very long :)
I have noticed this happen in Deathmatch. At the end of a match, when everyone's final score is displayed after the POTG, anyone who has left the match between when the match is over and the server closes will have their part of the scoreboard turn blue.
Great video, I also noticed sometimes the game chat will say the wrong hero name for you, for example it'll say username(kiriko) says hello to username2(junkrat) even though username2 is someone completely different
My guess for why only the colour changes is that each entry in the killfeed holds a copy of the data for name and icon, since that information is global and tied entirely to that entry. However, because the colour is dependent on each player's team, the entry instead stores a reference to the entity that made the kill and the one that was destroyed.
the same thing (sorta) happens if a player leaves the game during a pre game deathmatch (the "while you're waiting" one) immediately after you kill them, their color changing from enemy to team in the killfeed
If you Rez as Mercy then swap your character you suddenly become red for no reason in particular. This was observed from an outside same team perspective.
The delay before deletion happens because of the destruction effects for objects. The object is parented to them and deleting them would also delete the effect immediately. Evidently you can see, everything that falls apart, the rubble will disappear exactly when the color change happens
I did an Echo ult today where I died right after I killed people with an Orisa ult, and it showed the deaths in the enemy team color, like they killed themselves. It was weird. I was wondering about it, and very strange of youtube to present this to me like 20 minutes after I saw that.
My partner had a game the other day where both teams had a player with the same name, and he was getting this bug and having such a difficult time understanding what was happening.
impressive that you made a video about a bug. i wonder how this gets past design... and even QA lmao. maybe they should add a NOTEAM tag for deleted objects
Makes you wonder how this bug got created in the first place, if it was working perfectly fine at launch. What kind of changes are they making for the future where they'd need to look at this code and accidentally introduce this bug? Something related to PvE? Or just a pure dev error?
You're probably onto something with it being related to PvE, I can imagine when the number of entities starts getting really high the dev's start putting in more effort to optimise memory use for and deleting all data from associated entities probably helps that. This sorta thing seems like it'd be really easy to fix so I'm guessing (entirely conjecture) it slipped through without someone noticing and then instead of just fixing it right away they're having a more thorough look at how they handle this sorta data retention thing to stop easy oversights related to it happening again.
I have suspicions that at least some of the newer OW2 bugs are related to PvE changes. Tracer's broken damage falloff could have been a falloff talent upgrade that adversely affected PvP. even if PvP and PvE are completely separate branches, it is entirely possible that things not meant to be shipped end up in the retail build (such as the NDA warning shown during the Halloween event).
I love your videos! Truly high quality information discussed clearly, with aesthetically pleasing graphics and realistic yet digestible in-game recreations. It gives of @ScruffyMusic vibes occasionally! Great in-depth information on games, and I love how nerdy it is haha. I recommend both his and these videos to all my friends.
something cute i noticed is that riptire gets deleted and the color change glitch happens (seemingly) as soon as junkrat is back in control after his ult is destroyed. i think a similar case is true for torb's turret where the deletion period happens the moment that torb would be able to throw his turret again if it wasnt destroyed
Thank you! I wondered and even spoke about this in team chat: "Look at the feed. How did I get killed by MY team's junk tire? I got killed by a BLUE tire!" The fix, of course, is to not free objects until they scroll off the killfeed. Simple!
That explains why the killfeed looks a bit weird sometimes, good to know. I guess the easiest way to fix this would be to make it so the object doesn't get deleted from memory until after its off the kill feed? I don't think that'd cause too many problems unless both teams use pet heavy heroes and use a lot of excess memory at once, but if things only last 20 - 30 seconds longer so they get cleared off the feed first, I'd think it'd almost take an intentional effort to make this cause problems.
This seems like a pretty huge oversight. Why would they tie what is supposed to be a static display (the killfeed) to dynamically changing data? They could just pass in the state of the entity when it is killed to the killfeed UI.
I think the delay between death and deletion is somehow related to the object's functions. For example, I think Rip Tire is deleted 1 second after death to allow for the camera to remain there for a short period like it does instead of instantly snapping back to Junkrat after detonation, which might have been too disorienting.
I have that problem in all my games. Something else that happens is that when a teammate says hello to me (or any form of communication) it'll wright my name, but also wright another teammate's hero, not mine. Example: Flats (Mercy) to Inklow (Echo): Hello!". The problem is that I'm not playing Echo, I'm playing Genji.
This bug hapens when a player leaves match, 4 exemple in skirmish. This means, that player data is deleted after leaveing, and this is the reason, that your stats and ult charge reset after rejoining a comp game.
I noticed recently in a video with a sigma mirror match that whenever you stun the opposing sigma with rock, the text that appears says "Sigma (your name) stunned by Accretion". It doesn't happen every time however, as later in the video it said the opposing sigma's name instead I doubt it's caused by the same issue but it's definitely in the same vein as this.
![เขามัทรี - เอ็กซ์ ศุภกฤต - จอนนี่มิวสิค [ Official MV ]](http://i.ytimg.com/vi/AS9ufKuQIVs/mqdefault.jpg)
![Kiriko can Teleport to (0, 0, 0) [PATCHED]](/img/n.gif)
I'd say the deletion delay looks to be tied to how long the death particles should stay around. Riptire and immortality field are pretty small, so they disappear and nobody notices. Mecha and turret leave behind big chunks though, so it makes sense to wait a bit more until those go away
True. Deletion would happen only after the animation/particles of the character/object ends
@@TheSodaWave that makes a lot of sense
Can anyone confirm if that happens with Bob?
That would also explain bob's weird 10.2 seconds thing, since normally he would do the jump animation to leave the battlefield right on the 10 seconds mark and then dissapear for good, he's probably scripted to be deleted after the 10.2 seconds (ult duration + jump animation) regardless of his current state, even if he died, wonder if inmortality and tire also behave like that if you somehow avoid their extremely quick death animations
@@LuigixD Bob's entry is deleted 0.2 seconds after ult ends as he leaps out of the map. For player he doesn't exist anymore, therefore it can be deleted at an instant when he finishes his jump out animation without long delay. For 7.5 seconds after death - idk, maybe to make it similar to players' respawn timer cuz he is big major threat and autonomous separate character with vulnerabilities and hit boxes similar to normal heroes
Amogus tracer is a real one
😔🙏
Got to love the tiny amount of silliness in a very professional video.
Winton
Winton 🦍
@@OrigamiAhsoka why do I keep seeing you in comment sections💀
Knowing the way the team colors work behind the scenes makes me wish there was a way to always show your team as blue in replays. It’s so counter-intuitive to see your own team as “the enemy” when watching a game back
Agreed. People have been asking for this pretty much since replays debuted.
Does anyone know in those replays how the red and blue teams are chosen in modes like Control and Push, when you have the same neutral area to be taken by either team?
@@ccricers I would guess that it has to do with the order in which each team is populated. The match maker selects the first person, and then places that person into team 1. Then the match maker runs its algorithm to decide which players out of the pool will be that players teammates and enemies. Which group is on team one or team two likely also decides which is attacking or defending.
Obviously I don’t know for sure, but I would guess this is how it would work since it is irrelevant which players are on which team, but it would still make sense to index the first player selected as team one (basically the first player is in the first element of array one aka team one). Then again, I am looking at this from a data engineer perspective, I’m not a game dev and I don’t know how good or bad overwatch’s data structure practices are.
As a workaround you could use the color blind filter to set colors correctly, if your team is red, just switch it out. Just remember to reset them before going into game again lol
THIS HAPPENED TO ME AND I WAS SO CONFUSED THANK YOU AGAIN MARBLR THE GOAT
This also happens with hero icons in some occasions
I think it happens when the person that got killed leaves the game while the killfeed is still active, so maybe bc their data gets deleted or something?
yes, this also happens when player entities are deleted. I showcase this at 2:26 by manually deleting winton via the workshop. I had trouble getting it to occur "naturally" by leaving a server, but it's good to know that it is sometimes possible.
Ah, this explains why all of the player entries on the leaderboard start turning blue at the end of an FFA match.
winton
I've had this happen with echo dupe where an ally killed an enemy echo dupe and said ally turned red in the killfeed. I don't even want to imagine the hellish spaghetti code that results in this glitch.
Someone on Team 4 forgot to wrap the killfeed HUD Text with EvaluateOnce() 💀
I'm so happy this channel exists and you're doing such a great job. I've always had these super specific questions nobody ever answered online and you're out here answering them in such an intuitive and we'll constructed and edited way!
Same here
I on the other hand dont play as much ow2 to notice these details, but i love how he goes detective mode on all those bugs
I’ve had this happen in deathmatch to players while waiting in queue, pretty minor but it’s still pretty wacky since this wasn’t in ow1 to my knowledge.
it must occur when a player finds a game after getting a kill/being killed -- they are taken out of the server and their entity is deleted. I tried to reproduce this manually by leaving a game myself via the pause menu, but couldn't get it to work. thanks for the info!
@@Marblr i've seen it happening in queue deathmatch since OW2 launch, if right after you kill someone they get put into a game their killfeed icon changes to blue from red
@@Marblr well you can consider 2 things maybe 1 the entity data isn't deleted until that space on the team is filled by a new player, or 2 that entity data is linked to players specifically and not just in the one match so when they join a new match their entity data is taken with them. That's why it occurs when they find a match and not when they just go back to the menu.
@@Marblr It happens very reliably for me in the final FFA deathmatch screen after POTG. Everyone who leaves then turns blue.
It also happens if the player that died changed heroes
Which is why this bug happens all the time in mystery heroes mode
I noticed this too and it's been bugging me.
Same thing happens when someone leaves in Deathmatch, or in hero gauntlet, when they kill someone and automatically switch to another character.
Also I've noticed that whenever someone use the "I'm with you command", it will Always display your name but with the incorrect character "Orisa (Player name)" even tho you're DPS/support.
Definitely not patched, still happens consistently, especially with Torb turrets and Dva mech
これずっと謎だったから解明してかつ解説までしてくれるのほんと助かる…！
no way, I've seen this a few times and just thought it was one of those weird quirks I'd never understand but Marblr is here to save the day again. Keep up these videos, they're so informative and well made.
I really want to know what could’ve possibly happened for the overwatch team to update the game and make the payload timer say “unspecified” at the end of payload maps since it wasn’t a thing before season 2
Hey Marblr, just wondering about the bug that turns the target select from red to blue. I've noticed that some times on Zen and Echo, Zen's discord orb target select goes from red to blue, and so does Echo's when she has ult. Just wondering if there's a similar explanation or if it's black magic.
there is something even stranger going on with the targeting UI color, since it changes back and forth between the friendly color and the enemy color for both teams. perhaps related to this, but it definitely does not share the same characteristics.
just adding that I also have experience the UI color change on Zen! It changes to blue for enemy targets and every time causes me to take a second a look at who I'm discording!
That has happened to me a few times, thought I was going crazh
Indie devs you guys
I absolutely love this channel. Just straight to the point info with insane production quality! and it combines two of my favorite things, overwatch and spaghetti code
This also happens when players leave most games right after they get killed. Their color changes to the team of the player who killed them.
I don't know if this is something that only happened to me, but in the Practice Range, there is an specific spot in which you don't die when falling off map, specifically behind the practice characters
Yes! I thought I'm the only one. I don't know exactly WHY I got there, but I used Echo's Flying ability and didn't die in that spot. Only if you move a mm to the side, you die.
Always been there 🗿
thats been in the game since ow1's release
Yep. If you boop practice Tracer off the map there as Brig, she'll just sit there on the rocks mocking you.
There are a lot of places like that in the Practice Range, I've spent a lot of hours with my friends with Pharah trying to find all of them. (Mei's wall and Sym's teleporter could help too)
Clicked on this instantly, I love your videos man. Keep it up :)
Nice explanation, one thing I also noticed that helps explain this is that when playing torb if you hit the air where your turret used to be with your hammer, it will continue to make the metal noise until the color changes at the top right. nice video
Yes, this is what I was looking for. Thanks
You could make a video about how the endorsement system works, for example how many votes you need each level and how it decays.
Int endorsement;
Int pEndorsement;
Void AfterMatch()
{
If (GainedEndorsment())
pEndorsement = endorsement++;
If (endorsement ‰ 20)
LevelUp();
If (pEndorsment == endorsement)
endorsement--;
}
They've kept the system a highly guarded secret. Regardless, I lose endorsement levels when 5 stacked, when I literally can't get endorsements. So I dont think they bothered to fix it for OW2.
It doesn't matter because if you use endorsement to track anything in Overwatch then you are part of the problem of overwatch. The endorsement system is only for getting extra XP of you want it
@@SuperLifestream It was fun to endorse the enemy team after a match to make em less salty
@@GummyDinosaursify for generations, the dreaming city housed one of the awoken's most closely guarded secrets. it is known as the endorsement system, the endorsement system of a thousand voices
Man these videos are so well produced, love the structure and visuals
I noticed a very interesting bug that could be a topic for the next video: I was playing QP (so, no deathmatch) when an enemy Orisa threw a javelin, hit someone with it (don't remember who), and the javelin knockback threw them off the map. The killfeed did not display the javelin icon, but it displayed the icon for Halt! Why do you think this is?
Did they hit a wall before falling?
@@laststanding9998 No, I don't think so. It's hard to remember.
I love that you made a video for this, it's been bothering me a ton but it's so minor some people don't even notice it!
These videos are very well made, and I love the behind-the-scenes explanations!
I’ve also seen player icons also change colors if they leave the game immediately after being killed. Plenty of times have I high nooned behind a team, killed a solo zen and they promptly alt-f4, therefore causing the player icon in the killfeed change colors.
I’m having more fun watching these videos than playing the actual game
I have a hunch that there's a draw call for the killfeed, which is constantly trying to access that entity's team color, instead of caching it like everything else. Why this change occurred may have something to do with an attempt to try and conserve memory. If "performance boost" is ever mentioned in the patch notes, that might be it.
Funny thing, I have actualyl seen this bug again with the new Battle For Olympus game mode where after a bit of time one of the killed enemies was suddenly turning blue, sadly couldn't take a screenshot in time
I literally noticed this during some gameplay the other day and was thinking if you were gonna make a video on this-
Guess I didn't have to wait very long :)
Damn I was just thinking about this bug and you uploaded a video about it, nice.
It feels like bugs are cropping up more and more in ow recently
wake up babe new marblr vid just dropped
I have noticed this happen in Deathmatch. At the end of a match, when everyone's final score is displayed after the POTG, anyone who has left the match between when the match is over and the server closes will have their part of the scoreboard turn blue.
The thing still exists in the small messages you get on the bottom, but I think only with the sym turrets
Imagine being the developer who changed a single line of code thinking no one would notice it.
But Marblr exposes you anyway.
thanks for the detailed explanations as always.
Great video, I also noticed sometimes the game chat will say the wrong hero name for you, for example it'll say username(kiriko) says hello to username2(junkrat) even though username2 is someone completely different
Was coping from their being no new upload by binge watching all the older ones I haven't watched, and you post right after I'm done lol
chill and educational content , good stuff
My guess for why only the colour changes is that each entry in the killfeed holds a copy of the data for name and icon, since that information is global and tied entirely to that entry. However, because the colour is dependent on each player's team, the entry instead stores a reference to the entity that made the kill and the one that was destroyed.
the same thing (sorta) happens if a player leaves the game during a pre game deathmatch (the "while you're waiting" one) immediately after you kill them, their color changing from enemy to team in the killfeed
dude i’m literally in love with ur channel where have u been my entire life
Just sign this man blizzard. This is the most in depth bugreport / analysis i have ever seen. Great Job, very informativ!
Oh I’ve been wondering when I’d see your video on this! :P
Man, I was waiting for this video.
Amazing video as always
Overwatch should hire you to do videos like this!
If you Rez as Mercy then swap your character you suddenly become red for no reason in particular. This was observed from an outside same team perspective.
The amount of attention to detail of using the correct numbering for the TF2 teams because Team 1 is Spectator. Bravo, Marblr!
The delay before deletion happens because of the destruction effects for objects. The object is parented to them and deleting them would also delete the effect immediately. Evidently you can see, everything that falls apart, the rubble will disappear exactly when the color change happens
your videos are really neat and informative and entertaining, keep up the great work man
5:15 I just realized Ashe has voice lines or bob elimination
Honestly love this channel everything is so well informed and the commentary is perfect
I did an Echo ult today where I died right after I killed people with an Orisa ult, and it showed the deaths in the enemy team color, like they killed themselves. It was weird. I was wondering about it, and very strange of youtube to present this to me like 20 minutes after I saw that.
I swear this is rhe most fun ow channel
I saw this happen in a game and immediately thought of you making a video on it XD
I was waiting for this one! This has been happening all the time
I saw this for the first time yesterday and you post the video 😍
I’ve been waiting for this one!
brah the editing is on point
My partner had a game the other day where both teams had a player with the same name, and he was getting this bug and having such a difficult time understanding what was happening.
impressive that you made a video about a bug. i wonder how this gets past design... and even QA lmao. maybe they should add a NOTEAM tag for deleted objects
Makes you wonder how this bug got created in the first place, if it was working perfectly fine at launch. What kind of changes are they making for the future where they'd need to look at this code and accidentally introduce this bug? Something related to PvE? Or just a pure dev error?
You're probably onto something with it being related to PvE, I can imagine when the number of entities starts getting really high the dev's start putting in more effort to optimise memory use for and deleting all data from associated entities probably helps that. This sorta thing seems like it'd be really easy to fix so I'm guessing (entirely conjecture) it slipped through without someone noticing and then instead of just fixing it right away they're having a more thorough look at how they handle this sorta data retention thing to stop easy oversights related to it happening again.
I have suspicions that at least some of the newer OW2 bugs are related to PvE changes. Tracer's broken damage falloff could have been a falloff talent upgrade that adversely affected PvP. even if PvP and PvE are completely separate branches, it is entirely possible that things not meant to be shipped end up in the retail build (such as the NDA warning shown during the Halloween event).
Doesn’t Tracer’s pulse bomb have a similar effect when eaten by say, DVA, or Sigma?
Great video as always
I would also like to state, this happens sometimes with Zenyatta discord targets. Sometimes the reticle will appear blue when aiming at an enemy
honey, wake up, new Marblr video!
The developers watch these to help them understand the game better
I love your videos! Truly high quality information discussed clearly, with aesthetically pleasing graphics and realistic yet digestible in-game recreations. It gives of @ScruffyMusic vibes occasionally! Great in-depth information on games, and I love how nerdy it is haha. I recommend both his and these videos to all my friends.
This is a really interesting video. 😊 Reminds me of a Smash fact video. 😊 Bonus points for the SMB music. 😊
This happens all the time and I was so curious as to why. Thank you for this.
GREAT VIDEO I LOVE YOUR WORK KEEP GOING BROTHER
This man's content is so good I still watch it after permanently quitting overwatch
something cute i noticed is that riptire gets deleted and the color change glitch happens (seemingly) as soon as junkrat is back in control after his ult is destroyed. i think a similar case is true for torb's turret where the deletion period happens the moment that torb would be able to throw his turret again if it wasnt destroyed
Thank you! I wondered and even spoke about this in team chat: "Look at the feed. How did I get killed by MY team's junk tire? I got killed by a BLUE tire!" The fix, of course, is to not free objects until they scroll off the killfeed. Simple!
monkey ball music in the background is giving me flashbacks..
@ 5:35 look mom, I'm famous! It's me! That's great
Thx Echo
That explains why the killfeed looks a bit weird sometimes, good to know. I guess the easiest way to fix this would be to make it so the object doesn't get deleted from memory until after its off the kill feed? I don't think that'd cause too many problems unless both teams use pet heavy heroes and use a lot of excess memory at once, but if things only last 20 - 30 seconds longer so they get cleared off the feed first, I'd think it'd almost take an intentional effort to make this cause problems.
This seems like a pretty huge oversight. Why would they tie what is supposed to be a static display (the killfeed) to dynamically changing data? They could just pass in the state of the entity when it is killed to the killfeed UI.
Monkey Ball makes for some really nice background music.
I think the delay between death and deletion is somehow related to the object's functions. For example, I think Rip Tire is deleted 1 second after death to allow for the camera to remain there for a short period like it does instead of instantly snapping back to Junkrat after detonation, which might have been too disorienting.
Love the super monkey ball music, amazing taste
Amazing video like always.
Same thing happens in deathmatch when someone leaves while they're in the kill feed, it attributes ownership to you
Just found this guy recently but god damn it is he one of my favorites
i noticed this too but i thought i was trippin, glad to know i wasn’t imagining it
insane quality good job
I’ve noticed when talking to certain players it’ll think you are the wrong character. And it’s so confusing
I'm pretty sure this happens in hero gauntlet aswell when someone gets a kill as a character and immediately switches to the next one
I have that problem in all my games. Something else that happens is that when a teammate says hello to me (or any form of communication) it'll wright my name, but also wright another teammate's hero, not mine. Example: Flats (Mercy) to Inklow (Echo): Hello!". The problem is that I'm not playing Echo, I'm playing Genji.
Dude just casually doing Blizzard's QA work for them, right down to explaining exactly how it works.
This channel is the savior owl direly needs and they don’t even realize why
I noticed this when season 2 dropped but never saw anyone bring it up
*Dev who will have to work on holidays to fix this*: -Happy holidays to you too!
Overwatch spaghetti code is starting to rival Tf2 spaghetti code.
I do not care for Overwatch these days but I still love to watch your videos. Especially thanks to the subtitles :)
This bug hapens when a player leaves match, 4 exemple in skirmish. This means, that player data is deleted after leaveing, and this is the reason, that your stats and ult charge reset after rejoining a comp game.
3:18 this was so clean i love it
I noticed recently in a video with a sigma mirror match that whenever you stun the opposing sigma with rock, the text that appears says "Sigma (your name) stunned by Accretion". It doesn't happen every time however, as later in the video it said the opposing sigma's name instead
I doubt it's caused by the same issue but it's definitely in the same vein as this.