Pillar 3 · RAY-L
What RAY-L is
RAY-L connects Blender and ComfyUI. It passes the geometry of a Blender scene to an AI image model as an edge structure, via ControlNet Canny — keeping composition, perspective, and object placement exactly intact while the AI interprets materials, light, and atmosphere.
That's the technical description. The real question is a different one: why is this even necessary?
What RAY-L is not: another way to produce impressive AI images. There are already plenty of those, and most of them are the result of negotiating with a system that has its own ideas — sometimes surprisingly good, sometimes surprisingly bad, never really predictable. For hobbyists and quick ideation, that's often enough. For professional image production, it isn't.
What RAY-L is: a way to integrate AI image generation into a workflow that holds up to professional requirements. Not through ever more precise prompts — that approach tries to turn a stochastic system into a deterministic one, taking away exactly what makes the AI strong. Instead, through a deliberate division: what has to be fixed exactly, and what's allowed to be interpreted.
The division RAY-L implements technically
This division isn't a new invention — it's the core principle laid out in detail in the Concept section of this site. RAY-L is the technical implementation of that principle:
Blender determines: camera, perspective, geometry, object placement, spatial relationships. Everything that has to stay exactly the same on repetition — today, in six months, with a different material or a different mood.
The AI interprets: material feel, lighting mood, atmosphere, surface detail. Everything that's allowed to vary from image to image without losing the image's core statement.
RAY-L is the bridge between the two — a Blender add-on that prepares the geometry of the active scene and hands it to ComfyUI, where a diffusion model with ControlNet Canny generates the final image from it.
Why ControlNet Canny
ControlNet Canny transmits edge data exclusively — no light color, no mood, no material information. That exact limitation is why it's the right choice for RAY-L: it gives the AI a binding spatial structure without simultaneously dictating how it visually elaborates that structure.
What sits compositionally correct in Blender sits correct in the result. A weak composition can be compensated atmospherically by the AI — but compensated is not corrected. For an atmospheric image without strict requirements, the AI can save a lot. For a product photo that needs an exact position in the frame, a specific size, and a defined perspective, there's no substitute for that.
Exactly how ControlNet Canny works — and why this variant specifically, rather than another — follows in its own article.
Who RAY-L is for
RAY-L is for anyone already used to constructing and controlling images systematically: product visualizers, advertising photographers, architectural visualizers, designers, art directors. For people whose question isn't "which model delivers the most impressive random results," but: "how do I produce the same image tomorrow with a different product, in a different mood — reliably, not approximately."
No expert knowledge is required, but a basic understanding of both worlds helps: how Blender works as a composition tool is described in the 3D & Blender section. How diffusion models work and what ControlNet does, in the AI section.
License and responsibility
RAY-L is a bridge, not a model provider. Which AI model is used within RAY-L — and under what license — is the user's own responsibility. More on this in the article on licensing in the AI section.
Current status
RAY-L is being developed primarily for Windows with Nvidia hardware, the typical platform for ComfyUI workflows. The Windows version is close to completion. On macOS with Apple Silicon, RAY-L already runs stably, via a purpose-built adaptation path.
Currently reliably supported: SDXL and Flux.1 dev, with working ControlNet Canny. Further models — including Flux.2 dev, and Ideogram 4 — will be added once the respective ControlNet support becomes available. More on this in the AI section, in the article on model types.
What's coming here next
This section will keep growing over the coming weeks — from how ControlNet Canny works in detail, through the complete workflow from Blender to finished image, installation and setup, to model-specific guides for Flux.1 dev and, further out, additional models.
To keep up with the current status and new content: the homepage always shows the most recently updated sections.
RAY-L Beta