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.

LOD/mip blur -- any, dynamic radius; fixed sample count regardless. On a quest for faster realtime rendering. > Render texture aside, it's a single pass.

Mirza Beig

28,994 subscribers

88,300 views • 3 months 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

$Unity includes a tool for baking SDF textures: 🧊 I made this experimental shader for fully volumetric glass shaped to any object using a 3D distance texture. Handles layered self-refraction in a single pass (look at the ears, when the model is rotated), + explicit backface rendering via another camera -> texture pass. I don't have clear plans to add this to PRISM, but it's something I wanted to try out as a morning experiment (R&D, rendering/optics, performance -- for later).$

Unity includes a tool for baking SDF textures: 🧊 I made this experimental shader for fully volumetric glass shaped to any object using a 3D distance texture. Handles layered self-refraction in a single pass (look at the ears, when the model is rotated), + explicit backface rendering via another camera -> texture pass. I don't have clear plans to add this to PRISM, but it's something I wanted to try out as a morning experiment (R&D, rendering/optics, performance -- for later).

Mirza Beig

65,799 views • 3 months ago

AERO 1.7 is now live on the Unity asset store: adding support for light cookies [texture masks], which can be animated and coloured, from any light + a new rolling fog dynamic/animated texture example is included. 🔗 It's free, download it here:

AERO 1.7 is now live on the Unity asset store: adding support for light cookies [texture masks], which can be animated and coloured, from any light + a new rolling fog dynamic/animated texture example is included. 🔗 It's free, download it here:

Mirza Beig

20,612 views • 24 days ago

some progress on SSGI > GBuffer pass with normals and albedo > mipmaps for depth and irradiance (so we can lod sample farther pixels) > horizon based AO and GI (6 rays per pixel, 12 steps) next step is fixing the temporal and spatial noise

some progress on SSGI > GBuffer pass with normals and albedo > mipmaps for depth and irradiance (so we can lod sample farther pixels) > horizon based AO and GI (6 rays per pixel, 12 steps) next step is fixing the temporal and spatial noise

Gabriel Dechichi

42,795 views • 5 months ago

Looking for a fast method to render your large-scale game components? Our lastest High-Perf Graphics paper allows to render terrains, oceans and even entire planets in realtime on any modern GPU using compute shaders. Fun fact: we use a Concurrent Binary Tree as a GPU memory manager.

Looking for a fast method to render your large-scale game components? Our lastest High-Perf Graphics paper allows to render terrains, oceans and even entire planets in realtime on any modern GPU using compute shaders. Fun fact: we use a Concurrent Binary Tree as a GPU memory manager.

Anis Benyoub

50,581 views • 1 year ago

Btw I'm working on window blur in niri! Both xray and regular. Xray always "shows through" to the background. This allows it to be very efficient: compute blurred texture only once, then just draw that texture (very cheap). Not a single blur recomputation in this video! #niri

Btw I'm working on window blur in niri! Both xray and regular. Xray always "shows through" to the background. This allows it to be very efficient: compute blurred texture only once, then just draw that texture (very cheap). Not a single blur recomputation in this video! #niri

YaLTeR

42,705 views • 5 months ago

#rendering id Software moved to #Deferred rendering for Id Tech 8 as it proved more performant than their #Forward+ solution. About 26% faster opaque pass #gdc #gamesev

#rendering id Software moved to #Deferred rendering for Id Tech 8 as it proved more performant than their #Forward+ solution. About 26% faster opaque pass #gdc #gamesev

TheRedPixel

17,422 views • 3 months ago

Not quite #screenshotsaturday Finally figured out realtime POINTINESS SHADER! No texture baking or raytracing, just a whole bunch of precomputed vertex values and crazy shader math. Works instantly on any mesh. Pointiness -> edge highlight + wear + occlusion and even bevel!🤓

Not quite #screenshotsaturday Finally figured out realtime POINTINESS SHADER! No texture baking or raytracing, just a whole bunch of precomputed vertex values and crazy shader math. Works instantly on any mesh. Pointiness -> edge highlight + wear + occlusion and even bevel!🤓

Aleksei Abramenko

52,770 views • 1 year ago

Running the server on x30 so the AI can test it's strategies faster (realtime screen recording)

Running the server on x30 so the AI can test it's strategies faster (realtime screen recording)

max

80,438 views • 4 months ago

In feature film VFX, our lighting teams spend a lot of time shaving off as much render time as possible. Even 1 minute saved per frame adds up. For a 5 second shot, 1 minute less per frame saves you 2 hours of rendering per shot. Our shots are usually a lot heavier than this and our teams usually get a lot more optimization for render times than 1 minute per frame. Some shots can be rendering for up to 30 hours per frame depending on complexity. Large studios have a plethora of optimization tools which shave off a lot of render time from our shots. Rendering technology is always improving, bringing render times down and increasing physical accuracy. Video is of Hyperion with interactive rendering with Pixar's RenderMan XPU renderer, which is up to 5x faster than their older RIS architecture.

In feature film VFX, our lighting teams spend a lot of time shaving off as much render time as possible. Even 1 minute saved per frame adds up. For a 5 second shot, 1 minute less per frame saves you 2 hours of rendering per shot. Our shots are usually a lot heavier than this and our teams usually get a lot more optimization for render times than 1 minute per frame. Some shots can be rendering for up to 30 hours per frame depending on complexity. Large studios have a plethora of optimization tools which shave off a lot of render time from our shots. Rendering technology is always improving, bringing render times down and increasing physical accuracy. Video is of Hyperion with interactive rendering with Pixar's RenderMan XPU renderer, which is up to 5x faster than their older RIS architecture.

Rassoul Edji

16,128 views • 1 year ago

my texture brushes for rendering and creating ethereal art

my texture brushes for rendering and creating ethereal art

nika lynas

116,884 views • 2 months ago

Boston Dynamic just unveiled their newest Atlas robot. This is not a render. Oh my god It's giving "call an ambulance... but not for me"

Boston Dynamic just unveiled their newest Atlas robot. This is not a render. Oh my god It's giving "call an ambulance... but not for me"

Marques Brownlee

7,091,212 views • 2 years ago

Dynamic frosted glass and blur for Unity (URP). > Similar to Doom and Deus Ex: MD (2016).

Dynamic frosted glass and blur for Unity (URP). > Similar to Doom and Deus Ex: MD (2016).

Mirza Beig

94,318 views • 3 months ago

MAGE uses a custom engine to drive 120 FPS physics with dynamic shadows and "hundreds of high fidelity dynamic props" on Quest 3 & Quest 3S. Details here:

MAGE uses a custom engine to drive 120 FPS physics with dynamic shadows and "hundreds of high fidelity dynamic props" on Quest 3 & Quest 3S. Details here:

UploadVR

14,049 views • 1 year ago

Added dynamic drag radius and improved gradients. Here’s a live version:

Added dynamic drag radius and improved gradients. Here’s a live version:

Toni Lijic

100,371 views • 1 year ago

Greedy_Evening shared a GPU-driven quadtree terrain mesh with dynamic LOD, culling, and stitching handled directly on the GPU 🌍 See more:

Greedy_Evening shared a GPU-driven quadtree terrain mesh with dynamic LOD, culling, and stitching handled directly on the GPU 🌍 See more:

Jettelly Inc.

25,948 views • 5 months ago

#shader test for MAN-BAT : it's a challenge to #render all the short film with Blender 🔶 in #RealTime 👁️🦇😎 #brush #blenderartist #3d #batman #project #animation #manbat Blood Snow

#shader test for MAN-BAT : it's a challenge to #render all the short film with Blender 🔶 in #RealTime 👁️🦇😎 #brush #blenderartist #3d #batman #project #animation #manbat Blood Snow

julien_chery

49,710 views • 1 year ago

"Assassin’s Creed: Odyssey" map of Greece on a single 32,768 x 32,768 texture in the Browser. Virtual Texture tech in WebGL 2.0 The source is a 804 Mb PNG. Without Virtual Texture tech you'd need to download that and wait for a few seconds for your browser to decode it before you could use it. Your browser would then crash when it tries to upload it to the GPU :) If we imagine that the upload to the GPU would succeed - it would take 4Gb of VRAM. Virtual Texture loads immediately, because the image is split into small fixed-sized tiles with full LoD chain (mips) and uses 2048x2048, which is just 16 Mb of VRAM. Article:

"Assassin’s Creed: Odyssey" map of Greece on a single 32,768 x 32,768 texture in the Browser. Virtual Texture tech in WebGL 2.0 The source is a 804 Mb PNG. Without Virtual Texture tech you'd need to download that and wait for a few seconds for your browser to decode it before you could use it. Your browser would then crash when it tries to upload it to the GPU :) If we imagine that the upload to the GPU would succeed - it would take 4Gb of VRAM. Virtual Texture loads immediately, because the image is split into small fixed-sized tiles with full LoD chain (mips) and uses 2048x2048, which is just 16 Mb of VRAM. Article:

Alex Goldring

188,343 views • 5 months ago

$Great question! 🤔 How do you simulate *multiple* layers of glass/refraction in video games? In the last breakdown, I discussed how to create a glass shader in Unity URP. In essence, we were taking the render of the scene from the camera without any transparent objects. This is available in URP as the global _CameraOpaqueTexture. This is good enough for most use-cases, and more or less the classic way of doing it. 🔍 What is _CameraOpaqueTexture? As the name implies, there are no transparent objects rendered into this texture, so it's not possible by default to have something like a transparent-type ocean material/shader rendered through a refractive glass shader (which samples and distorts this texture to render on its surface, as if it's transparent). ⚠️ Why it’s tricky: It's much easier to sort without much further setup if you don't have refraction, and only a transparent material, because in that case you're not simulating the transparency yourself via sampling the rendered scene texture. But for refraction, it's required-- unless you want to go down the ray/path tracing route. You could simulate accurate, real dispersion... and that's about as expensive as it sounds, and it requires a rework of your entire rendering. --> 🚫 It's not a viable suggestion to offer. 📚 There are well-known terms regarding transparency sorting you can search up, but as you've specifically asked for refractive boxes, I'll discuss briefly about that. 🧱 Simulating layers of refraction: For this kind of rendering, you need some way to render the backfaces before rendering the front. And the backfaces that are rendered may contain whatever data you'd like for additional processing in the layer front-facing mesh render. 🧪 Examples: You could render the back face as a glass shader of its own, as an intermediate step after _CameraOpaqueTexture. Then you sample this texture instead and you end up with multi-layered refraction, "just like that". You can also render the back normals only, via a fully opaque shader, and use that to manually account for that during the front render. You could even bake in data needed for thickness in realtime. 🛠️ Without making it complicated for yourself, the most straightforward method is via render textures, and you can easily set some fractional resolution. Cameras in Unity have an open slot for target textures to render to. You can use custom render textures to process _SelfTexture2D. ⏱️ It's great to do low-resolution processing for more complex tasks, like blurring and caustics. You can get massive performance boosts, considering the square law and number of pixels/fragments that need calculations (quadratic scaling). 🚧 I've not fully exploited the possibilities myself, but research/development with PRISM is ongoing!$

Great question! 🤔 How do you simulate multiple layers of glass/refraction in video games? In the last breakdown, I discussed how to create a glass shader in Unity URP. In essence, we were taking the render of the scene from the camera without any transparent objects. This is available in URP as the global _CameraOpaqueTexture. This is good enough for most use-cases, and more or less the classic way of doing it. 🔍 What is _CameraOpaqueTexture? As the name implies, there are no transparent objects rendered into this texture, so it's not possible by default to have something like a transparent-type ocean material/shader rendered through a refractive glass shader (which samples and distorts this texture to render on its surface, as if it's transparent). ⚠️ Why it’s tricky: It's much easier to sort without much further setup if you don't have refraction, and only a transparent material, because in that case you're not simulating the transparency yourself via sampling the rendered scene texture. But for refraction, it's required-- unless you want to go down the ray/path tracing route. You could simulate accurate, real dispersion... and that's about as expensive as it sounds, and it requires a rework of your entire rendering. --> 🚫 It's not a viable suggestion to offer. 📚 There are well-known terms regarding transparency sorting you can search up, but as you've specifically asked for refractive boxes, I'll discuss briefly about that. 🧱 Simulating layers of refraction: For this kind of rendering, you need some way to render the backfaces before rendering the front. And the backfaces that are rendered may contain whatever data you'd like for additional processing in the layer front-facing mesh render. 🧪 Examples: You could render the back face as a glass shader of its own, as an intermediate step after _CameraOpaqueTexture. Then you sample this texture instead and you end up with multi-layered refraction, "just like that". You can also render the back normals only, via a fully opaque shader, and use that to manually account for that during the front render. You could even bake in data needed for thickness in realtime. 🛠️ Without making it complicated for yourself, the most straightforward method is via render textures, and you can easily set some fractional resolution. Cameras in Unity have an open slot for target textures to render to. You can use custom render textures to process _SelfTexture2D. ⏱️ It's great to do low-resolution processing for more complex tasks, like blurring and caustics. You can get massive performance boosts, considering the square law and number of pixels/fragments that need calculations (quadratic scaling). 🚧 I've not fully exploited the possibilities myself, but research/development with PRISM is ongoing!

Mirza Beig

51,429 views • 11 months ago

Gaussian splatting as part of the UI – a lot went into making this as performant as possible – for example, for the frosting effect I track the card in screen-space and only render to and sample the pixels touched by the blur

Gaussian splatting as part of the UI – a lot went into making this as performant as possible – for example, for the frosting effect I track the card in screen-space and only render to and sample the pixels touched by the blur

🌈 George Corney

51,942 views • 3 months ago