chena

@rokuz7 @CorporateShark I'm looking forward to reading it.

@chena_cpp @CorporateShark I should probably do a proper write-up. Anyway, I plan to open-source it so you can play with it. In a nutshell: I built a voxel grid and cluster lights by “importance” - the 8 most important light source indices per cluster, with all the rest “tail” stored as a SH decomposition.

My modest attempt at clustered lighting with irradiance volumes. Fully GPU-driven Vulkan powered by @CorporateShark’s LVK. Insanely fast! 256 light sources at 0.43ms per frame.

@_3Leon @AhomiGoi How to process the volume boundary？If a person half in volume, half outside.

Normal density volumes does not work the same. It does not place probes right at the edge of the volume either but has to be grid locked - this means that it can still leak lighting. It also does not work for the normal GPU lightmass, only works on cpu lightmass My system is local, so if someone is inside one volume, they physically can’t reach light that is baked outside the volume, meaning if I place a volume inside a room, it can not leak if I am close to a wall no matter the cell size due to the fact that it can’t look at lighting outside the volume. To handle blending between them there is a fade slider as well. The probes are also not placed to a global grid that needs to subdivide, they are also local and are placed at the volumes bounds and only cares about the volumes size. So another difference is that it is not some overarching brick system only allowing 3 mip levels, mine has how many cells as you want per volume and not tied to a world coordinate grid. Sorry for the wall of text, just wanted to explain a bit in detail 💪

Nearing completion on my custom UE5 volumetric lightmap probe system that is volume based (for baked environments). Uses GPU lightmass as base and then a custom per volume probe system - Completely eliminates light bleeding due to per area control. Allows for blending between volumes and custom resolutions in custom areas. Will see if i can make this into a plugin - currently this is a full engine fork so i am unsure if i can make it happen! Still some things left before i can call it feature complete but currently its working exactly as intended! Fully artist controlled both visually and optimization speaking, no more auto probe placement that is affecting the whole level 💫 #UnrealEngine5 #UE5 #GameDev

@rokuz7 @CorporateShark What is the density of the irradiance volumes probe？With so many dynamic lights, how do you achieve such a fast rendering speed?

@chena_cpp @CorporateShark Dynamic like that:

@Toyojiro3619 The grass animation looks so natural. How did you make it?

もう少し回顧録。Interactable grass material です。Material function paratemer で風の向きや速度、メッシュの曲げ具合を調整出来ます。頂点データにピボット座標を仕込んだり、Render Target で風強度マップを生成したり、結構苦労した。 #UnrealEngine5 #UE5 #GameDev #IndieDev #ゲーム制作

@Cody_J_Bennett What is ARC coefficients？

WIP atmosphere implementation of "Production Ready Atmosphere Rendering" (Hillaire 2020) with ARC coefficients using Slang & WebGPU. On the ground, an RGBA16F 200x100 sky-view LUT is sampled, but in space, I raymarch for per-pixel transmittance at higher precision.

@PS_Leoluch @ostromfanclub @damdeuce 3 texture sample triplanar, How? Thanks.

But they do pretty dense meshes, use a lot of unique geometry and do pipelines which will make a lot of people very upset . And their shaders are not complicated - it is pretty smart packing and good use of tech 3 texture sample triplanar with 4 material blend is opposite of that . And that's my point

One of the most dumb decisions I see - going low poly and making complex material layering and a lot of high res textures. Going with dense geometry is the easiest way to do high fidelity realistic content. It is not important how many polys you have if each of them are expensive to render

@HDRgameAnalysis @HeavyMetalRMN Thanks, that's a smart workaround.

@chena_cpp @HeavyMetalRMN I use a PC with a capture card and a video player, that works with Reshade. See how here.

Short HDR setup guide for #Pragmata on PS5 and PS5 Pro. PC gamers should use the RenoDX HDR mod. Max Brightness: This is what the game will output in max brightness at different settings on the max brightness slider. Set it to what your display can do on a 2-10% window. 5 clicks: 325 nits 6 clicks: 400 nits 7 clicks: 400 nits (545 nits) 8 clicks: 700 nits 9 clicks: 700 nits (795 nits) 10 clicks: 865 nits 11 clicks: 900 nits 12 clicks: 940 nits 13 clicks: 940 nits 20 clicks: 940 nits You can only get 545 nits at 7 clicks and 795 nits at 9 clicks if you also move the min brightness slider from left to right and back again. Or the game simply will output 400 or 700 nits. Its a strange error. Black levels: Everyone should set the min brightness slider all the way to the left. Paper White (brightness): The brightness slider is adjusting the overall brightness of the game, also called paper white. Start by setting to minus 5 from neutral. Then the game will output 203 nits paper white. That is what most probably will prefer for 700-940 nits max brightness. If minus 5 is too dim for you, then use neutral. Here the game will output 230 nits paper white. Don't go lower than minus 5 on displays capable of 400-700 nits. Here the game will decrease paper white down to 185 nits (at 400 nits max). Probably to make room for highlights above the midtones. But ultimately set paper white (brightness) to what looks most natural to you.

@HDRgameAnalysis @HeavyMetalRMN How did you check the luminance? PS 5 don't like PC, can't capture the frame. Thanks.

@HeavyMetalRMN I don’t know why its 940 nits. I only look at what the game outputs. How its all done by the game engine is something I know very little about and I can’t go into the code and check.

@andkalysh This seems to require modifying the engine source code. Is it possible to release it as a plugin?

More experiments with #UE5 - Custom Render class. Decided against changing Shading Path as it has deep dependencies, this is easier for now. #UnrealEngine5 #gamedev

@FilippoTarpini How to do it? Thanks.

Perspective Correction (lens distortion) off vs on. It has a huge impact in ultrawide, but helps a lot with 16:9 too. Screenshots don't do it justice, but browsing the world in FP feels much more natural. This specific matrix doesn't emulate cameras distortion, but is designed for perception. The implementation is borrowed from the brilliant Fubax.

If you weren't aware, a few years ago I mage a gigantic mod for Prey that kickstarted the Luma Framework project! Mod adds HDR, DLSS/FSR, GTAO, improves SSR and shadow, perspective correction, 8k & Ultrawide support and a billion other things 🙂. Digital Foundry worthy video from JDSP here: youtube.com/watch?v=15c1SK…

@andkalysh How did you perform the interpolation for the SH3 coefficients?

Coming in UEX 2.6: - ZH3(Activison) Improvements for LPV SH - LPV for forward rendering - Rendering module overhaul. - Small fixes Image below UEX2.5.8 compiled for PS5 with LPV on forward rendering path. #UE5 #UnrealEngine5 #gamedev

@MR3Dev The vistas are great and the clouds look solid but a bit blurry, while the assets and lighting aren't very high quality

Anyone who thinks Crimson Desert has amazing visuals has not played a game since the launch of PS4

@topotoylabs "each tile is self-contained with all the information it needs about itself and its neighbors", cool, how?

Geo-morphing in my engine is designed so each tile is self-contained with all the information it needs about itself and its neighbors. No cross-tile lookups at boundaries.

I finally fixed all the cracks at tile boundaries in my terrain engine + I started experimenting with run-time procedural fine detail over the GIS data #indiedev #gamedev #computergraphics #procedural #terrain #rendering

@SebAaltonen @dkharms_ It seems to be just reducing the permutation explosion caused by state changes, but most permutation explosion is caused by shader static condition branch, state don't change.

@dkharms_ I have some ideas in my blog post: sebastianaaltonen.com/blog/no-graphi…

The PSO explosion has grown so much that today we need massive cloud servers to deliver the PSOs. Each vendor has their own solutions. We should fix the root cause instead of building this massive infrastructure. tomshardware.com/pc-components/…

@panoskarabelas Did you use aftermath? breadcrumbs seems can't get more detailed info.

If you have no GPU breadcrumbs, implement them, yesterday.

@SoftEngineer Did any of the talks mention shadow culling? Thanks.

Doom Etarnal and its predecessor were ultra-optimized towards light counts. There are great presentations for both from SIGGRAPH. Elernal more-so. Makes sense that the team would push it as far as it goes. As for TDA - I guess part of it is the open-world(-ish) nature of the game. Unless your game is super-duper dark, it's actually really hard to make good use of local lighting in outdoor scenes. If you take a good-looking open-world game, they typically find ways to cover up the sky to create good environment for varied lighting. Such as a dense forest with occasional clearings and tall brush. Other games lean into making the landscape look beautiful, but that's not a lighting thing anymore. If you have walls and a ceiling - it gives you so many options for lighting fixtures. As humans we know that the sun is really freaking bright, so any light sources outside can't be too bright or they will look fake. Sad times. So yeah, you have to tone down main directional light source and make it overcast, push towards twilight and night as far as possible. Most games that have a day/night cycle cheat by making sunrise and sunset last several times longer proportionally than in real-life, because lighting is more interesting during those times.

@FilippoTarpini Which decompiler did you use? I can't find a decompiler support dxil.

@chena_cpp Yes. There's a few decompiler around for multiple shader model versions. Plus, as I said, Musa has reverse engineered the previous games. Pragmata wasn't much different.

How does Resident Evil Requiem, and more generally the latest RE Engine games, handle HDR? Here’s a technical breakdown of the defects we think it has. Obviously the game has HDR grading so that's already great in itself, and the on final screen results are good. For context: I’m a big RE fan, so this is not meant as hate or criticism; just a technical analysis! @MusaRenoDX, a fellow modder and collaborator, has been making mods to improve HDR and grading most of their games, and did for this one too (REverse engineering and replacing game shaders). They are pretty popular in the PC gaming community! Biggest problems: - Wrong transfer function used for SDR, which shifts the look unintentionally in SDR only, this gets baked into the default look of the game and assets, and is not transposed in HDR, hence HDR has a very different look on shadow (more raised). - HDR LUTs are pre tonemapped to 1k nits, and then re-tonemapped to your display peak. This means that if you set it to 1k nits, you actually get less as it tonemaps twice. This also means you can't get more than ~1k nits. - Improper paper white scaling. The user brightness is scaled in the wrong place, which skews all the colors sampled from the LUT. For example if the LUT tinted shadow red and midtones blue, if you double you brightness setting, shadow will start to be tinted blue, which breaks the game intended look. Minor problems: - They use separate LUT files for SDR and HDR, including one for each SDR gamma/OETF settings. The SDR one bakes in tonemapping, while the HDR one does display mapping after. A IMO simpler and more reliable workflow would be to have a single HDR LUT and neutrally compress to SDR or HDR at the end. - Setting the Gamma/OETF to Rec.709 apparently causes major banding. Either way it shouldn't be used if as it's not a transfer function used by displays. - LUTs input is in the AP0 (ACES storage) color space which means much of the input range is wasted as the game renders in Rec.709, a much smaller gamut. - There's no separate control for UI brightness which isn't ideal for UI visibility or OLED in general. - UI transparency blending looks a bit different between SDR and HDR which makes it unreliable from an artistic point of view, but it's not bad here. Previous games used SDR LUTs all the way and stretched them to HDR with sub optimal math, hence in HDR you'd have some weird hue shifts on shadow and broken gradients. They recently improved on that. The tonemapper here seems to be ACES (per channel + hue shifts) but we can't confirm as it's within LUTs. I really wish I could reach out to CAPCOM :D! SDR vs HDR pics.

@eclmist Hi, how to use dx12 RT in wpf? Thanks.

Last weekend I decided to write an editor for my DX12 renderer. I started a WPF project, but was immediately disappointed by the lack of a built-in window docking system. So I wrote one in🙂