Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

For those running the -enablereplays command for debug replays, the next beta update adds debug replay takeover. 😱 Press SELECT to pause at a moment in a replay and take over controls for P1 or P2 and see what you could have done differently!

Liam

2,299 subscribers

69,410 views • 2 years ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Bonus Prompt: I wanted to see what else Lovart could do so I asked it to create plushies for the "greggle Family" and then create a marketing banner for them. It did an awesome job and you will probably see these in WalMart within the next year Here’s the replay:

Bonus Prompt: I wanted to see what else Lovart could do so I asked it to create plushies for the "greggle Family" and then create a marketing banner for them. It did an awesome job and you will probably see these in WalMart within the next year Here’s the replay:

greg

22,021 views • 1 year ago

Toxic British Press, don’t panic! The Prince is probably looking at the score or a replay. He’s not looking for ways to take over the British Monarchy. You’re safe. 🤭 💳 Panqueque Real 🥞 #PrinceHarry #NBAFinals #Spurs #Knicks #AdamSilver #InvictusBirmingham27

Toxic British Press, don’t panic! The Prince is probably looking at the score or a replay. He’s not looking for ways to take over the British Monarchy. You’re safe. 🤭 💳 Panqueque Real 🥞 #PrinceHarry #NBAFinals #Spurs #Knicks #AdamSilver #InvictusBirmingham27

Nelly

17,708 views • 19 days ago

new replay update! now you can select what type of frame you want to help compose stuff :) been loving the love they've been putting into replay mode 😁

new replay update! now you can select what type of frame you want to help compose stuff :) been loving the love they've been putting into replay mode 😁

cam

62,629 views • 1 year ago

you're allowed to demonstrably remonstrate and point at the replay, if you play for Collingwood #AFLPiesLions

you're allowed to demonstrably remonstrate and point at the replay, if you play for Collingwood #AFLPiesLions

outbreezy

62,729 views • 11 months ago

What a SAVE by Ronwen Williams for the Sundowns! Watch live and replay on 🔥

What a SAVE by Ronwen Williams for the Sundowns! Watch live and replay on 🔥

afl_africa

34,657 views • 2 years ago

WE HAVE A MONSTER DEBUT TODAY 🚨 Catcher Joe Mack is getting the call for the Marlins, and I remember seeing this in person and immediately going to Twitter to see a replay of what tf I just saw One of the fastest poptimes EVER at 1.75

WE HAVE A MONSTER DEBUT TODAY 🚨 Catcher Joe Mack is getting the call for the Marlins, and I remember seeing this in person and immediately going to Twitter to see a replay of what tf I just saw One of the fastest poptimes EVER at 1.75

Fuzzy

356,110 views • 1 month ago

These small, clumsy robots at the marathon arecompeting on a different track. They're easier to debug, safer around humans, and far more practical for labs and classrooms. And yes-they're oddly charming in motion!

These small, clumsy robots at the marathon arecompeting on a different track. They're easier to debug, safer around humans, and far more practical for labs and classrooms. And yes-they're oddly charming in motion!

Sinical

2,857,832 views • 2 months ago

Pause to see what a fantastic journey awaits you at the expo! Comment and share with your screenshot, server and ingame UID, Ai-chan will select 20 participating Captains to gift Flame-Chaser standees~ Kudos to Captain Tigera for the fanart! #honkaiimpact3rd #homusummer

Pause to see what a fantastic journey awaits you at the expo! Comment and share with your screenshot, server and ingame UID, Ai-chan will select 20 participating Captains to gift Flame-Chaser standees~ Kudos to Captain Tigera for the fanart! #honkaiimpact3rd #homusummer

Honkai Impact 3rd

161,279 views • 2 years ago

For those at the game that didn’t get to see the endless replays for Cheltenhams goal …… there’s a push in there somewhere but you might not see it (like the ref) Thankfully not a turning point in the game. Onto Saturday! 🖤🤍

For those at the game that didn’t get to see the endless replays for Cheltenhams goal …… there’s a push in there somewhere but you might not see it (like the ref) Thankfully not a turning point in the game. Onto Saturday! 🖤🤍

Notts County History

12,710 views • 7 months ago

Deadlock practicing Corner Boost Using Debugging Type the debug command "citadel_wall_detection_debug 1" into the console, slow down time in the sandbox panel, and you'll now be able to see the direction you'll be pushed in when jumping off a wall

Deadlock practicing Corner Boost Using Debugging Type the debug command "citadel_wall_detection_debug 1" into the console, slow down time in the sandbox panel, and you'll now be able to see the direction you'll be pushed in when jumping off a wall

DEADLOCK PROJECT 8

98,030 views • 2 months ago

my proudest creation in ryOS is... the window resizers 🤌 just gave them an upgrade and a debug mode to see them!

my proudest creation in ryOS is... the window resizers 🤌 just gave them an upgrade and a debug mode to see them!

Ryo Lu

89,024 views • 1 year ago

Every big moment deserves a replay. Get more streaming time with the Buffet Bundle. 4hrs for N250 | 10hrs for N600 Dial the code in the video to subscribe. MTNYouTubeBuffet

Every big moment deserves a replay. Get more streaming time with the Buffet Bundle. 4hrs for N250 | 10hrs for N600 Dial the code in the video to subscribe. MTNYouTubeBuffet

MTN Nigeria

677,010 views • 8 months ago

I'm trying to make a modern debug bar for Laravel. It's a super early concept, I have innovative ideas to try that will make the debug bar a true coding companion. I'd love to share more later if anyone is interested. For now, I'm just trying to improve the UI by reimplementing the basic features everyone, no matter their level, needs.

I'm trying to make a modern debug bar for Laravel. It's a super early concept, I have innovative ideas to try that will make the debug bar a true coding companion. I'd love to share more later if anyone is interested. For now, I'm just trying to improve the UI by reimplementing the basic features everyone, no matter their level, needs.

Benjamin Crozat

21,310 views • 1 year ago

You have placed the guidewire for a CVC, you view the vessel below and see the wire in the lumen, How did this occur and what is your next step? Take the full challenge here--> NephroPOCUS

You have placed the guidewire for a CVC, you view the vessel below and see the wire in the lumen, How did this occur and what is your next step? Take the full challenge here--> NephroPOCUS

Pulmonary-POCUS

10,735 views • 1 month ago

Not only have we launched the most accurate Valorant replay tool, but we’ll also be updating it frequently. One of the newest features lets you play multiple rounds simultaneously and select specific players to analyse or view certain patterns ‼️ What other features would you like to see?

Not only have we launched the most accurate Valorant replay tool, but we’ll also be updating it frequently. One of the newest features lets you play multiple rounds simultaneously and select specific players to analyse or view certain patterns ‼️ What other features would you like to see?

light

48,798 views • 9 months ago

I'm sorry, SpongeBob. I endlessly repent and you always forgive me for what I've done. You have accepted the fact that you must keep dying at my hands no matter what form you take - soap or not. Killing you over and over and over again is as easy as breathing.

I'm sorry, SpongeBob. I endlessly repent and you always forgive me for what I've done. You have accepted the fact that you must keep dying at my hands no matter what form you take - soap or not. Killing you over and over and over again is as easy as breathing.

soap of the day

78,965 views • 9 months ago

Everyone's pestering Chris Buescher and tagging him in replays of the 2024 Kansas Speedway finish so I'm gonna do him a solid and tag him in a replay of the 2024 Watkins Glen International finish where he beat road-course master SVG for the win

Everyone's pestering Chris Buescher and tagging him in replays of the 2024 Kansas Speedway finish so I'm gonna do him a solid and tag him in a replay of the 2024 Watkins Glen International finish where he beat road-course master SVG for the win

nascarcasm

74,316 views • 2 months ago

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot *resume* the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which *would've* hit the breakpoint, *if* it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because *generally* you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) *cannot apply* to some module's debug info - more quickly than doing a *full* PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume *knowing* that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Huge upgrade to loading speeds coming soon, especially with DLL-heavy codebases like UE! The primary reason PDB -> RDI conversion (or PDB parsing in debuggers more generally) is a big bottleneck in startup time is because they must be converted/parsed/loaded _serially_. This may seem surprising, since intuitively it'd seem like they can be converted/parsed/loaded/etc. in parallel. This is not true in the general case due to breakpoints, and how they relate to an API like `LoadLibrary`, and how it translates into debug events. When a debuggee runs `LoadLibrary`, the debugger will receive a debug event informing the debugger that the associated module was loaded. Any time a debug event is sent to the debugger, the debuggee stops running entirely. This is so that the debugger can make decisions about how the debuggee should proceed. For example, if I have a breakpoint on `foo.c:123`, that file name and line number can only be correctly interpreted (meaning resolved into code addresses) using debug information. The debugger only knows about that debug information from the PDB - without it, that file/line combo is meaningless. But importantly, the debugger cannot resume the debuggee until it has resolved that breakpoint - otherwise the debuggee may execute code which would've hit the breakpoint, if it were resolved in time. So, the debugger needs to ensure that all breakpoints are fully resolved before resuming. This is a correctness detail that everyone has to pay for, basically because `LoadLibrary`s are received one-at-a-time. Obviously, if it were instead an API like `LoadLibraries`, then the debugger could prepare all of the debug info in one batch before resuming - but it doesn't know what that batch would be, given just an initial `LoadLibrary`. This is unfortunate, because generally you are not debugging the code loading a bunch of DLLs, but the debugger can't really know that. (It is probably a good idea to provide a `raddbg_load_libraries` API at some point, so that we can resolve this issue on the debuggee side). In any case, RADDBG now resolves breakpoints much more quickly by avoiding 99% of debug info conversion work to do a common case of breakpoint resolution - you might call this "breakpoint disqualification". Basically, if a breakpoint is set, and we can quickly determine that that breakpoint's information (file location, expression, condition, etc.) cannot apply to some module's debug info - more quickly than doing a full PDB -> RDI conversion (which entails a full parse & a bunch of work) - then we can simplify the very common case in DLL-heavy cases: you put a breakpoint on `foo.c:123`, when 99% of the DLLs do not have any line info for that file, so the debugger can resume knowing that breakpoint will not resolve within that file. In this demo video, you can see I place a breakpoint that only resolves within the executable's debug info - it does not resolve within any of the 100 DLLs that are loaded serially. Within the `Modules` tab, you can see that as I run the target, most of the debug info is not loaded initially, even though the debuggee is running. That debug info is loading in parallel, as the debugger knows it does not need to wait for that debug info to be prepared for this breakpoint.

Ryan Fleury

17,527 views • 1 year ago

So the first replay maybe u could kinda say offensive foul, but the second replay shows an egregious flop for Jokic’s 5th. Bam shouldn’t be rewarded for this

So the first replay maybe u could kinda say offensive foul, but the second replay shows an egregious flop for Jokic’s 5th. Bam shouldn’t be rewarded for this

BBALLBREAKDOWN

636,390 views • 3 years ago