r/TechnicalArtist • • 6m ago

Fluid Art Generator

Thumbnail gallery
1 Upvotes

r/TechnicalArtist • • 14h ago

Pipeline generator

Post image
1 Upvotes

Hey everyone! How's it going?

I've been working on a little tool on and off for a while and thought I'd share it here to get some feedback.

It's basically a simple pipeline generator for post-production workflows (compositing, 3D, AI, etc.). It creates a folder structure based on the type of project and also generates the corresponding project files with some basic settings already configured.

It also includes a small project/shot manager, kind of a very simplified ShotGrid, where you can review shots, add notes, open them, render and manage deliveries, all in one place.

It's still very much a work in progress, and I'm sure there are plenty of tools out there that already do this much better, but I wanted to build something lightweight and flexible that could work across different types of projects.

It's a standalone executable, so there's no installation needed. Just point it to your working directory and you're good to go.

I'd love to hear what you think, what might be useful, what doesn't make sense, or what could be improved. It's also open to anyone who wants to contribute or suggest ideas.

Thanks!

https://github.com/cfieiras/post-project-manager


r/TechnicalArtist • • 18h ago

Other I built my portfolio as an explorable 3D bedroom where the PC boots into a Windows XP desktopne

Thumbnail gallery
0 Upvotes

Sharing a project and the pipeline behind it, since the technical side might be more useful than the portfolio itself. It's a bedroom scene where you click a CRT, the camera pushes into the screen, and a live XP-style desktop runs on the glass (Three.js, no bundler).

Live: https://kayzee-room.vercel.app/hi/reddit-h6m

The problem: I wanted Cycles-quality lighting (fur, dusk colour, soft lamp shadows) in a browser, at a few MB, and with a camera move that never glitches.

What I tried, in order

  1. Baked lightmaps. Cheap, but materials looked flat and clay-like.
  2. Camera projection. I rendered the scene in Cycles from two cameras (a seat view and a close-up in front of the CRT), then projected those renders onto the real geometry in three.js, with a per-projector depth test to stop ghosting. That kept the Cycles look for about 3 MB total. The close-up is 96° at 2800 px. The parked camera sits exactly on the render's position and frames the glass by changing the FOV, so any window shape shows an untouched render.
  3. Still glitchy mid-zoom. Blending between projectors painted things twice. Narrowing the blend range helped, but didn't fix it.
  4. What shipped: a pre-rendered film. I rendered the push-in as 48 frames along the exact chair-to-monitor path, with the same easing and lens interpolation the runtime uses, and encoded it to about 2.3 MB of x264. It plays on a fullscreen quad. The three.js camera syncs to each video frame with requestVideoFrameCallback, and the room meshes render depth-only, so the live layers (CRT screen, sticky notes, dust, glow) stay registered. If the video isn't ready, it falls back to projection.

Gotchas that cost me time

  • VideoTexture in a custom ShaderMaterial isn't sRGB-decoded, so you decode it in the shader or it looks washed out.
  • The iframe over the glass has to be sized before it loads, or the page picks its phone layout.
  • On phones the glass is tiny, so the iframe runs at a virtual 1024 px width and is CSS-scaled onto the tube.
  • Cycles on the GPU kept failing with "insufficient memory" until I noticed leftover headless Chrome test browsers holding GPU memory.

Performance: the desktop world uses 260k instanced grass blades, so the speed comes from elsewhere: skipping the 3D world behind maximised windows, half frame rate when idle, and an adaptive resolution ladder gated by real GPU timing, so throttled background tabs don't trigger it.

The Blender side is a procedural scene driven headless from Python scripts, and Claude Code wrote most of the scripts and the three.js. Happy to go deeper on any of this. I'd also like to hear how it performs on your hardware, and whether you'd have solved the zoom differently.