Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Day 23 of how I vibe code my game engine in Cursor: Unit Sprites Like I mentioned in my buildings post: units hit the same wall once the animation steps outside the sprite’s inner silhouette. That’s where the pain starts: pixel bleeding, halos, and PBR maps becoming impossible to...

121,234 Aufrufe • vor 6 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

I built a clone of the Yeezy store with Next.js. This was a fun challenge — the site has some smooth animations and feels very fast. But it was bothering me that I couldn't use the browser back button. Can we do better? So I rebuilt the site with v0 and Motion. Here's how it works: 1. When you click on a product, Motion is able to animate the original position of the product in the grid, to the zoomed in product detail page. 2. During this transition, we also shallow update the URL with the `/p/slug` route for the page. 3. If you press the back button in the navbar, or use the browser back button, or press escape — all options will take you back to the main product listing page. 4. If you reload the page while looking at a product, or someone sends you a link to a specific product, it still works! This is the best parts of a SPA and MPA mixed together. In the future, I can make this even better with View Transitions (I wasn't able to get the product animation just right, but if you can I'd love to see it!). I also took some creative liberties from the original design. The whole 1/2/3 size thing, where you needed to click the "?" to see SM/MD/LG was strange, so I just went directly to those sizes. Similarly, I prefered the more traditional style sheet/modal with the background color change, versus the full screen takeover. If you wanted to actually hook this up to Shopify now, you can swap the cart implementation with Next.js Commerce, which has all the APIs you need + optimistic writes 🔥 Should I make a video walking through the code?

Lee Robinson

148,937 Aufrufe • vor 1 Jahr

(Yes i know the movement is exaggerated, its just to show the motion, it also doeant move like jello when in vr) -Left is before, Right is after- Ok wall of text time for the nerds Literally everything is the same on both sides except the position of 1 bone (made sure that even after adjusting, the collider would still be in the same spot) The reason for this change is because she wanted to be able to clap her ass in vr, and last time i did this all i did was add a toggle for a hidden bone that moved, and its angle would trigger the sound. Which was because that with my previous position, the cheeks could never really meet in the middle when in motion unless you just pushed them together with your hands, and i wanted to just have the sound actually be triggered by them colliding with each other This is also the first time ive used endbones to help drive the movement, so now thanks to that and all my previous experimenting with squishing as well, I can now get bones to move exactly how i want them to move when in natural motion. And i know a lot of people are gonna ask me to teach them how or explain my thought process but i literally just go off feeling lmao. Like, i just kinda visualize in my head how i want the motion to look, and then i just kinda know where to put everything, so im not even sure how to even start explaining rip. I have the things that artist want where they can just make the shit in their head exactly how they envisioned it lol I have a few more ideas i want to try, so we'll see if theyre good enough to get a tweet lol Thank you for coming to my ted talk

Pixel

27,240 Aufrufe • vor 1 Jahr