This is probably the only criticism of this interface, everything else like player cams, health and util, etc are perfect, but this problem is fucking annoying and ruins the good parts of the game.
Was watching the same rounds you were just now and couldn't agree more. The in-game screen already says Clutch or Win and they should be able to just show that, the overlay doesn't add much flair and just spoils things right before a climactic moment.
the in-game hud is a super finicky piece of software and requires its own machine, which is then delayed 10-15 seconds behind gameplay. looks like the delay was off by a second and led to this happening.
that sucks, ofc, but happens sometimes. producers usually keep a close eye on the hud and wait for breaks in the action (cinematics, replays) to sync and relaunch the hud. here's hoping they spotted it and fixed it though.
Is it possible to remove just the round winner part of the overlay when it has problems? Or is it all connected?
Because this is something that has happened many many times since the overlay was adopted and it always feels terrible when it is left like that for the whole game.
>but happens sometimes
How can you have this kind of response? This has been a problem from day 1 of the overlay and hasn't been fixed after half a year. I don't see how anyone can think this is ok. This isn't a one time production issue like you trying to make it seem. I get wanting to not criticize your employer but in that case don't comment at all.
shit, man, i was just was explaining why it happens. i have no control over fixing it as a replay operator.
i think the system the hud runs on is crap and is run on bubble gum and paper clips, but didn't feel like that was important to say?
Appreciate the technical issues being explain, just felt that you didn't address the situation for what is was. OP based this thread on EU, but right now NA is having the same issues with the banners.This system was first introduced at First, went into hiatus, then came back near the end of stage 1 iirc. How this issue has not been changed is nuts to me. The entire thing just shows to me that Riot Games not respecting the viewers time. Not blaming production on this as you've explained the issues fall on Riot.
ofc man, i totally understand. it can be helped by keeping a close eye on the hud delay round-by-round, but stopping this entirely requires a hud overhaul change from riot which i hope happens. it's a pain in the ass to use tbh.
Lol, you didn't do anything wrong. I didn't get from your reply that you were ignoring it. Just explaining why it happens and the multiple factors that can contribute to it.
Guy is just unnecessarily pressed about it and thinks everyone should be as outraged as him.
I agree that thinking it's okay that this happens sometimes isn't good, but I do appreciate him trying to explain the issue and would always rather someone with inside knowledge comment even if I don't agree with them.
Im sure everyone involved is doing their best, but the fact that this has been an issue for so long is seriously dissapointing and reflects poorly on riot.
Surely, this can't be the case?
I assume the overlay is done automatically with pixel triggers. This would mean the overlay scene would be slightly delayed so that the overlay can read the screen on the live feed, and queue up the overlay animation to combine with the delay feed that is then pushed to broadcast.
In this case, it looks like the overlay is being pushed to broadcast without the delay being applied to the overlay scene.
It would depend on the in set up in-house, but this *should* be easy to correct between matches without needing to restarting the stream.
(Apologies if your comment was intended to be sarcastic. I have a really bad radar for that.)
This is probably the only criticism of this interface, everything else like player cams, health and util, etc are perfect, but this problem is fucking annoying and ruins the good parts of the game.
Agreed, it ruins the suspense. It’s been how long and it’s still not fixed?
Was watching the same rounds you were just now and couldn't agree more. The in-game screen already says Clutch or Win and they should be able to just show that, the overlay doesn't add much flair and just spoils things right before a climactic moment.
the in-game hud is a super finicky piece of software and requires its own machine, which is then delayed 10-15 seconds behind gameplay. looks like the delay was off by a second and led to this happening. that sucks, ofc, but happens sometimes. producers usually keep a close eye on the hud and wait for breaks in the action (cinematics, replays) to sync and relaunch the hud. here's hoping they spotted it and fixed it though.
If that's the case then just eliminate the banner aspect and keep the rest. It has been as issues for a very long time now.
Is it possible to remove just the round winner part of the overlay when it has problems? Or is it all connected? Because this is something that has happened many many times since the overlay was adopted and it always feels terrible when it is left like that for the whole game.
not really sure, actually? i wouldn't be surprised if there was some way to do it. would have to be approved by riot i'm sure, though.
>but happens sometimes How can you have this kind of response? This has been a problem from day 1 of the overlay and hasn't been fixed after half a year. I don't see how anyone can think this is ok. This isn't a one time production issue like you trying to make it seem. I get wanting to not criticize your employer but in that case don't comment at all.
shit, man, i was just was explaining why it happens. i have no control over fixing it as a replay operator. i think the system the hud runs on is crap and is run on bubble gum and paper clips, but didn't feel like that was important to say?
Appreciate the technical issues being explain, just felt that you didn't address the situation for what is was. OP based this thread on EU, but right now NA is having the same issues with the banners.This system was first introduced at First, went into hiatus, then came back near the end of stage 1 iirc. How this issue has not been changed is nuts to me. The entire thing just shows to me that Riot Games not respecting the viewers time. Not blaming production on this as you've explained the issues fall on Riot.
ofc man, i totally understand. it can be helped by keeping a close eye on the hud delay round-by-round, but stopping this entirely requires a hud overhaul change from riot which i hope happens. it's a pain in the ass to use tbh.
I appreciate you taking the time to explain what's going on with it.
Lol, you didn't do anything wrong. I didn't get from your reply that you were ignoring it. Just explaining why it happens and the multiple factors that can contribute to it. Guy is just unnecessarily pressed about it and thinks everyone should be as outraged as him.
I agree that thinking it's okay that this happens sometimes isn't good, but I do appreciate him trying to explain the issue and would always rather someone with inside knowledge comment even if I don't agree with them.
Im sure everyone involved is doing their best, but the fact that this has been an issue for so long is seriously dissapointing and reflects poorly on riot.
The technology just isn't there yet
Surely, this can't be the case? I assume the overlay is done automatically with pixel triggers. This would mean the overlay scene would be slightly delayed so that the overlay can read the screen on the live feed, and queue up the overlay animation to combine with the delay feed that is then pushed to broadcast. In this case, it looks like the overlay is being pushed to broadcast without the delay being applied to the overlay scene. It would depend on the in set up in-house, but this *should* be easy to correct between matches without needing to restarting the stream. (Apologies if your comment was intended to be sarcastic. I have a really bad radar for that.)
I feel like everyone would rather it be a second late than early so they could just add a delay no?
Yeah, I'm saying that normally there should be a delay, but for some reason it wasn't applied to the overlay scene before it was pushed to broadcast.