VRGDG Storyboard Builder UI

Before you render a single frame of an AI music video, you need a storyboard: a scene-by-scene plan of what each clip will show, which lyric it covers, and what the camera does. Doing that planning inside the node graph is miserable - you end up with a wall of text nodes that all need editing in place. VRGDG Storyboard Builder UI is the pack's answer: a dedicated planning UI that organizes your scene prompts before image or video creation, so the graph stays clean and the plan lives somewhere you can actually review it.

It slots into the VRGameDevGirl Video Builder workflow at the "planning" stage - the README's quick start is explicit about the order: create a project, build a storyboard, then generate images and render. This is the node from that list that does the planning. It's the friendlier sibling of the browser-AI storyboard launcher: that one generates start images with your browser as the brain; this one is a full project-aware planning surface.

What it needs

The single required input is project_folder - the path to a Video Builder project. It reads and writes that folder's plan, so a scene you sketch here is the same scene the Video Editor and the Remake Clip Queue will later load. It echoes the path back out as its only output, which is mostly so you can chain the folder into whatever UI node comes next without guessing the path. Set it, wire it, and open the node to get the actual storyboard interface.

That project-aware bit is what makes this worth using instead of a text node and a prayer: because it writes into the same project structure the rest of the pack uses, your scene prompts, timings, and references survive the trip from planning to generation. You're not copying text around; you're filling in one plan that the pipeline reads.

How it fits the workflow

The classic mistake this node exists to prevent is prompt drift. If you write scene prompts ad hoc at generation time, every scene ends up with different character descriptions, inconsistent locations, and no continuity. A storyboard forces the decisions up front - who's in the scene, where they are, what the camera's doing - and then every downstream render pulls from the same source of truth. For multi-scene projects like music videos, that consistency is the difference between a "music video" and a slideshow of unrelated clips.

Install and the usual suspects

Standard pack install: ComfyUI Manager → search vrgamedev → install → restart → hard refresh the browser. The refresh is non-negotiable with these UI nodes; the JavaScript that renders the storyboard interface won't load on a cached page, and "node installed but opens blank" is almost always that.

If you open the UI and it looks empty, check that project_folder points at a real project - the node isn't magic, it needs a folder to read and write. And as with the whole Video Builder, the author's guidance applies: save often, use Branch Project or Export Shareable Project ZIP before big experiments, and start with a short project before committing to a long one. A plan is only useful if it survives until the render finishes.