Загрузка видео...

Не удалось загрузить видео

На главную

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___O's profile picture

Liam

2,299 subscribers

69,410 просмотров • 2 лет назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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:
0:16

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 просмотров • 1 год назад

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
0:16

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 просмотров • 15 дней назад

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 😁
0:13

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 просмотров • 1 год назад

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

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

outbreezy

62,729 просмотров • 11 месяцев назад

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

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

afl_africa

34,657 просмотров • 2 лет назад

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
0:18

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 просмотров • 1 месяц назад

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!
0:11

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 просмотров • 2 месяцев назад

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
0:12

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,230 просмотров • 2 лет назад

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! 🖤🤍
0:17

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 просмотров • 7 месяцев назад

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
0:10

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 просмотров • 2 месяцев назад

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

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 просмотров • 1 год назад

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
0:10

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,006 просмотров • 8 месяцев назад

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.
0:15

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 просмотров • 1 год назад

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
0:14

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 просмотров • 1 месяц назад

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.
0:11

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 просмотров • 9 месяцев назад

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?
0:18

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 просмотров • 9 месяцев назад

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
0:16

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 просмотров • 2 месяцев назад

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.
0:18

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 просмотров • 1 год назад

United players and staff crouched over to have a look at their monitor. Terrifically take by Maguire but first replay showed he’d strayed marginally offside #mufc
0:15

United players and staff crouched over to have a look at their monitor. Terrifically take by Maguire but first replay showed he’d strayed marginally offside #mufc

Samuel Luckhurst

611,865 просмотров • 1 год назад