วีดีโอ

what did crysis use?

Man universities have fallen so far. This kind of rendering is really slow and incapable of anything that compute can do. Yea lets make the pipeline even bigger and add even more draw calls lmao.

forward rendering looked cleaner and sharper, defered just looks blurred

Thank you! :)

I just tried forward rendering in unreal engine with MSAA and I feel like I am born again without needing glasses, who decided it was such a great idea to go crazy with the AA smudge tools.

"this will change in the near future" Nope, we just get games with worse and worse fps! Thanks for the great video

Thanks for video!

why do you repeat "moving the g-buffer" ? It doesn't need to move. It's only ever allocated once. It is written once for each frame. Once it has been written, it is read-only. I do not understand. Do we transfer its contents between RAM and VRAM frequently or something?

7:25 In webgpu, the vertex and fragment shader code is provided to the pipeline. This means that a pipeline can only execute 1 fragment shader. So to render the scene we wouldn't just have the nested loops: lights>objects, but rather materials>lights>objectsWithThisMaterial, and for each material set a different pipeline. Am I missing something here? is that pipeline-per-material, the intended way to draw the objects for this case? 19:30 In WGSL it doesn't seem to be possible to use some samplers inside branching code. Is there a way around that?

Thank you so much for sharing your knowledge sir, I learned a lot from your presentation!

But surely you just put your lights into a GPU buffer and then you can sample the buffer whilst drawing meshes. That makes it just M draw calls for M meshes, with sampling into the buffer for N lights which is really not any different from deferred, other than that deferred avoids redrawing fragments - but even a depth prepass on forward solves that issue.

So that's how the pattern of my socks was made..

where is the "messed up" part ?

Can't wait for the return of MSAA and sharp graphics again!

Definitely still a heady topic for me, but thank you for explaining it. Specially for the emerging trends and outlook in the end, definitely interesting.

Amazing explanation, I could finally grasp the pros and cons of each technique

excellent

Shrek?? no way 😅 that’s great. Awesome talk, thanks

Unbelievably good explanation. I cannot thank you enough!

Thanks mate

Memory Bandwidth > Shader Complexity Memory bandwith is way more important than shader complexity, you can see this in games like Zelda TOTK where the only reason why lag spikes exist is because of memory bandwidth only, I would highly advise you to look into it you can learn so much from that

Deferred rendering has the advantage of calculating lights per block and not per pixel, decreasing the GPU overload, so it doesn’t matter how many lights cross your blocks because it won’t affect performance. If I’m not mistaken, Apple has TBDR Patents and has been using it on the iPhone since 2017.

How do you make this can you please make a tutorial

Thanks a lot. Saved a lot of time and effort.

Can't believe such a perfect digestion of high level information into actionable mental models exist. Thank you!

Is curious how everybody who illustrates a depth buffer always use the reverse depth approach, where white is closer and black is farther, more curious is that the reverse depth buffer distributes the depth precision much better than the original, 'forward' depth buffer, where closer objects have a depth close to 0 and far objects have a depth closer to 1 😊

best video to explain them, from the history , hardware to gpu pipeline work , thank you. looking forward more tutorial with this way .

have you checked out the "clustered forward renderer" in bevy? Looks pretty nice. Don't know if any downsides. Says unlimited lights

Very good video!

And this is why you're at Cambridge University <3

Hmm, I thought the PowerVR/Dreamcast was the first tile based deffered renderer?

谢谢你

Excellent. Best video about this topic I've found. Thank you.

why is forward always portrayed as lights x meshes. i have never written a forward renderer like that. just put the lights in a buffer and then send the lights affecting a mesh as indices. gives you 1 uniform branch for the loop but that should be fine and way faster than multiple draw calls lol

Thanks for the video, i had a lot of questions on the topic and this was an absolute clear explanation of the differences

"If you cannot explain something in simple terms, you don't understand it." This video really shows how deep an understanding you have on the shader topic. Thanks so much!

Thanks a lot for sharing, didn't expect a dive into the current state of things in games. It was a very pleasant surprise :)

Excellent talk. I did a little research and found out that you are just a young lad. Wish you all the best and thanks for such a great talk.

This is gold content, watched several videos on the topic, this is the one that actually makes me understand.

very well explained, loved it

Hands down the best, most straightforward explanation of forward vs. reverse rendering I have seen!

This is such a helpful video!

Should also mention all lighting in doom eternal is dynamic. The "pre-processing" that is being done is called clustered forward rendering, in which a culling stage reduces the lights sampled in a specific part of the scene.

thank you shrek

Thank you! Been going back and forth between defferred and forward as it's a lot more effort using forward shading - requiring much more planning and optimising. I plan to force myself to use Forward rendering during development and commit to a much more optimised game rather than go for dynamic lighting.

very useful ! thanks a lot

😍😍😍😍 my favourite youtuber

What’s up?! Great content. Have you ever thought about using smzeus . c o m to promote your videos?!