Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

DOCTOR DOOM FULL MID-SCREEN COMBO Heard y'all needed some sauce? This character does mad damage for very little resources #MarvelTokon

98,117 Aufrufe • vor 8 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

i spent 4 dollars to make this post Akali 3H single routing structure with positioning optimizations these range from bnb territory to psychotic, but mainly putting together as an example for combo limits / optimization adjustments on the fly. You can always 2 hit walljump / do single hit jM to reduce some length and maintain the routing if combo time is a concern. For the third and fourth combos, there are 2 versions - one that optimizes for limit strike damage / combo time, and one that sends in extra air normals for 5s2 oki. Just posted both as an example, but routing like this also helps bridge the gap on 5s2 damage if you'd like to use that. Notes: 1) Corner to corner, keep in mind extra normals will increase the pushback and leave you closer to corner by the end, reducing frame adv from the tumble. 2) Nearing corner (starting about 75% of the stage away) adjustment on the ender for when the tumble has less frame adv, just cram in more air normals and save your double jump. 3) Here's where you'll start to see corner adjustments - round start position, this ends up being the starter for max damage midscreen, but if you were to reach the corner after the apex of your second jump loop arc, you can squeeze in extra minimum damage for a notable increase. Fortunately also maximizes corner carry while pushing damage. 4) In corner route. Stupid hard wrt combo time, just posting as an example of combo limits. you can probably just opt for above, but it does get an extra min damage source in. Alternatively, learn an easier combo lol. Have similarly structured stuff for 2H, will probably get to it later.

SKD

20,215 Aufrufe • vor 4 Monaten

As a graphics engine coder I think when you look at a flickering bug like this one in the video below it’s not immediately obvious what is going on. The key here is observation - to study this flickering/bugged render carefully - what do we see? Firstly for me it was very obvious that nearly all of the scene shadows were flashing on and off - but (but!) there was a secondary issue where some buildings and parts of the sky were also flashing purple. Hmmmm. Interesting. I initially thought then this might be two separate bugs - but because the sky purple element could only based on full screen post fx and not 3D rendering I looked at this first with a few GPU captures to step through all our post processing to find the rendering stage which made these pixels turn purple: When I did this I found the colour 3D texture LUT grading that makes our different biomes have unique colour palettes was going very wrong - colours near 0 or 1 were wrapping and making the purple elements that we see in the said sky and base parts. The only way this could happen was if the texture was corrupt (which it was not) or if the 3D texture sampling was wrapping and not clamped as intended. That was the Eureka moment - because if the post fx had the wrong texture sampler then the disappearing shadows which also require an exact texture sampler for comparing depth might be also wrong because of the same kind of texture sampling issue! So with this idea that the engine was using the wrong texture samplers, but only in very high draw call scenes like the big base here I the looked at some engine limits and found the bug very quickly - a circular dx12 descriptor buffer for samplers running out over multiple frames, reusing the wrong data for new scenes inflight. Hence the flickering, as the GPU randomly got wrong samplers for some post textures or shadow depth. Easy to fix with triple limits for future expansion and also adding an assert/debug spam in case this limit is ever reached again - QA testers would see this message and report if they ever saw a flicker with this style of bug. My bug and my bad from 2017 porting NMS to DX12 without foreseeing how massively complex bases and our game would grow.

Martin Griffiths

72,828 Aufrufe • vor 1 Jahr