Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Octahedral impostors (WebGL) Single quad, 1024x1024 texture resolution The intention, of course, is to serve as an LoD and not to be viewed up-close The bake happens in-engine and is fully runtime capable. Bake includes full G-buffer: normals, ORM, albedo, depth Bake parameters: atlas texture resolution - how big...

34,304 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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 Aufrufe • vor 1 Jahr

Working on Sparse Volumetric Light-maps. Thanks to CynicatPro🎃 for pointing me at Unreal's version. In a nutshell it's just another sparse voxel data structure. My implementation is, no doubt, different from Epic Games Store's own. I'm using 4x4x4 probe grid with intermediate nodes having very wide branching factor of 64 as well (4x4x4). I liked the parameters that Unreal is using, of limiting both total memory as well as the lowest level of detail, which is common in sparse grid implementations. Here's Bistro scene with just 1Mb limit. This is roughly equivalent to a 512x512 lightmap texture in 2d, except surface light maps require unique UVs and you typically get very little detail out of 512 resolution texture with a lot of light leaking. There is also no directional response. My implementation encodes second-order spherical harmonics for each probe (9 coefficients), encoding RGB channels as RGBE9995 (4 bytes). So far only worked on the structure, actual bake is yet to come. I've been eyeing sparse voxel structures for a while now, and have been studying them roughly since the GigaVoxel paper by Cyril Crassin but never really implemented anything for the GPU before. I was always the BVH-kind of guy. It's a fascinating topic. --- Stats for the scene: --- Total memory usage: 1.000 MB Node count: 609 Unique probe count: 24,025 Probe reuse: 38.36 % Unexpanded nodes: 15,714 --- Again, note that there is no GI going on here, only the structure of the probe tree and the algorithm for building it from a given scene.

Alex Goldring

11,519 Aufrufe • vor 5 Monaten

Wuthering Waves PS5 Performance Test • Test Setup PS5 Slim (brand new, clean, no dust) Room temperature: 22°C with AC • Map Issue Yes, it's real. The new map is locked to around 2 FPS when opened from the menu, making it extremely laggy. • Stuttering Problems The game has severe stuttering. In some areas, it even freezes for 4–5 seconds, making the experience frustrating. • My Observation From my testing, the game appears to be running at a very high internal resolution on PS5 instead of relying on aggressive upscaling. For example, DLSS Quality at 1440p renders the game internally at approximately 1707×960 before upscaling it to 2560×1440. On PS5, however, it looks like the game is rendering at or near 2560×1440 internally and then upscaling to 4K. If that's true, it's an extremely demanding target for a base PS5. • Is This Fixable? Yes. If the game is indeed using such a high internal resolution, lowering it and using better reconstruction or dynamic resolution scaling could significantly improve performance. Running at such a high internal resolution on a base PS5 doesn't make much sense, and the game has suffered from performance issues for nearly 12 months. • Final Thoughts Kuro Games needs to address this. At this point, we can't keep blaming players, their hardware, or the engine. If the high internal resolution is the cause, it should be adjusted. If it isn't, then something else in the game's optimization is seriously wrong. #WutheringWaves #Gacha

Kaito

46,945 Aufrufe • vor 4 Tagen

2026 = The end of upscaling? One of generative AI's biggest drawbacks was the resolution, and I'm not talking about the output resolution as 1080p would be enough for most of the projects. I'm talking about the "internal" resolution of how these models work, that makes small faces distorted in your generations, the ones that will make a wide-shot impossible because the small details will morph and of course with some models text rendering is not possible. Upscaling with AI was always a strange case, local upscalers sometimes lacked the quality compared to the closed source competitors, but those can be pretty pricey and the results are sometimes way too "creative". So I was very, very interested when Kling AI announced native, not upscaled 4K generation but wanted to have a good method test it. Again, I never missed the 4K output resolution with genAI, but I missed the nuanced detail rendering of the engines and the lack of that made it impossible to create for example very wide shots with tiny details. So I fired up some image models to generate stills inspired by Morocco and see how Kling behaves, now in 4K. Some notable moments: 00:22 - Skin and eye texture, the movements, the little coins in the headdress 01:18 - The reflection in the water 01:39 - The reflection in the eye, and the scarf textures 02:10 - Check all the details on the rails 02:20 - Water particles and leaves 02:29 - The rendering of the rusty parts of the rail 02:50 - How the waves change the reflection in the foreground 02:55 - The cloud movement in the background

László Gaál

17,514 Aufrufe • vor 2 Monaten