Max Liani
@maxliani.bsky.social
Tracing rays at NVIDIA. Former lighting artist, working on computer graphics rendering tech for all humans and robots alike. I mostly post stuff about light transport simulation, and my hobby project Workbench.
TinyBVH has just been 𝘂𝗽𝗱𝗮𝘁𝗲𝗱 𝘁𝗼 𝟭.𝟴.𝟬. For CPU ray tracing, it is now the fastest option in most cases - Outperforming Intel Embree and Madmann91 for BVH build time and single-ray performance. On GPU, performance exceeds 4B rays per second - 4 rays per pixel at 4k/120Hz. github.com/jbikker/tiny...
People who bought SpaceX thinking what they bought is an aerospace company 🤦🏻♂️ What they got instead is a tiny share of xAI, and a minuscule one of aerospace sector.
Do they need to have tried and failed? To qualify, I mean… Does music education at school count? My literature teacher told me many times I will never write anything in my life. I guess the music teacher thought that too.
Hey now, that's an unfair characterization, I never even tried to be a musician. Instead, I became a software engineer because I was bad at drawing.
That sink is every AI vibe coded application, if you review the code. Hey, it passes all unit tests though…
I'm not a plumber. But I'm pretty sure that's not how sinks work.
Maybe I see this in rosy retrospection, but I feel that the work I did many years ago to create the Glimpse production renderer still feels to me the most insane project I ever started.
I always had some envy about people who can read books, novels before going to sleep. If I read something I find myself immersed in, goodby sleep, I won’t be able to sleep at all.
About 3.5 years ago I did some experiment to improve the behavior of microfacet normals at glancing angles. Many surfaces become highly reflective even though having high roughness. Check the discussion in the thread. Here is my implementation reusing equations you already have:
There's a neat short paper from Eurographics this year that evaluates how well microfacet shading models actually predict measured reflectance. The answer is: not nearly as well as one would hope! (1/3) ssteinberg.xyz/2026_surface...
Cut tool. It does more or less what you'd expect from a cut tool. Snap to points and edges, fractional placement, cut across faces, slice. No support for edge loops yet.
Add Polygon second pass: "predictive snap points" and numerical input to finetune distance and direction of the current point position in respect to previous.
I need to revamp my modeling operators, especially those that require user interaction. Here is first attempt at the Add Polygon operator. It's a first pass; it needs some work, but I feel it's not a bad start.
Alright, I made some further improvements to the tree view, which now draws in constant time (in respect to the scene complexity). Here is a test with 16 million transform nodes viewable in the scroll area. Without screen recording, the whole app renders at 8kHz.
I played a bit with the UX of interacting with the tree view. The common operations are selection and re-parent. I want to control both with the same gesture. So, if the drag&drop is mostly vertical -> reparent. If it widens to the side, it becomes marquee selection. Yes, no?
I am not sure why I am doing this, but I optimized further the scene tree view as it was getting a bit slow and clunky to operate when I had many nodes expanded. It's not cheap, it's still the most expensive part of the program to draw.
A long time ago in a galaxy far away (circa 2011) I came up with a distant rect light for my lighting crew. I can't remember how I did it, but I am trying to recreate it. Here is a test for the light sample distribution in the hemispherical domain.
After how many years? I added code for distant area lights. Some call it "directional". The control "scale compensation" is meant to preserve the light power (radiant flux), so as the emissive area increases, the intensity decreases.
I cut down startup time by deferring DLSS initialization. The first second of images rendered are noisy, until DLSS init is complete, at which point I accept a one off 40ms hiccup to allocate buffer resources and begin denoising. I'd say it's decent enough!
DLSS in workbench. The quality of 1spp rendering is way higher compared to the other built-in denoisers, and for half the cost. The comparison changes at higher spps.
I am trying to add DLSS-RR mode to Workbench. In theory I already have most things from the renderer, exception made for the specific pixel jitter and the motion vectors… It shouldn’t be too hard for me to add either of those. I am curios to compare DLSS with the other denoisers
Last weekend I refined the scene tree view in Workbench. I used the drag & drop support in dear imgui to implement DAG reordering and reparenting, plus renaming. Custom behavior and drop region draw to show where the node would be inserted, and display where and why it cannot.
100,000 fuzz iterations. I'd say this part of the system works :)
Oh boy, I am letting Cursor run automated mutation testing in Workbench... 🍿
I have just spent 7 hours straight, barely leaving my desk looking at the wrong problem. I thought I was lost in reindexing hell, but the complex data structure I just made works just fine, the problem was in the incomplete input data all along. How is your day?
Finally, I came around at implementing DOF and wiring it to the camera manipulator system. Click and drag to samples the scene to estimate the focus distance, while scroll to modulate the aperture.