ArchAi3D_Qwen_Camera_View_Selector

Somewhere between "front view" and "dutch angle" there are exactly 22 views that professional photography keeps reaching for, and this node is a dropdown of all of them. ArchAi3D_Qwen_Camera_View_Selector is the pack's quick-pick: you don't describe a camera move, you just name the view - three-quarter, isometric, section, aerial, corner, ceiling, overhead, ground level - and it hands you a prompt plus a system prompt that keeps the model honest about maintaining that view.

What's on the panel

• camera_view - the 22-view dropdown. Six orthographic (front, back, left, right, top, bottom), five portrait angles (eye level, high, low, bird's eye, worm's eye), four architectural (section, aerial, street level, entrance), three interior (corner, entrance, ceiling), and four cinematic (three-quarter, isometric, dutch angle, overhead, ground level).
• subject - what you're photographing: "the building", "the product", "the room". Leave it empty and it defaults to "the scene".
• scene_context - an optional description ("modern architectural exterior with glass facade") that improves consistency so the model doesn't invent a new building while changing the view.
• debug_mode - prints the generated prompt to the console.

Outputs

Three strings: prompt (ready for a Qwen Edit 2509 workflow), view_description (a plain-language description of the view you picked), and - the one the tooltip is excited about - system_prompt. That's the v4.0 addition: a per-view system prompt ("You are an architectural photographer. Maintain section cut perspective...") that goes into your encoder's system_prompt input and is most of why the results hold together.

How it works

The node keeps a curated dictionary of views, each with a prompt template and a specialist system prompt. Pick a view, give it a subject, and it composes something like "modern architectural exterior, change the view to a three-quarter view of the building showing both the front and side." The research note baked into the code is the interesting bit: Qwen works better with named viewpoints ("front view", "top-down view") than with abstract camera movement descriptions, which is exactly the kind of thing that separates a reliable node from a dice roll.

When to reach for it

The README's example workflow sums it up: quick viewpoint changes for architectural elevations, product e-commerce shots, and interior plan views. It's the fastest of the pack's camera nodes to drive - one dropdown, one subject, done. For a straight angle swap it beats the heavyweight focus cameras (V5/V7) because it doesn't ask you a dozen questions first.

Install

Pack install, once for everything:

cd ComfyUI/custom_nodes
git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
cd ComfyUI-ArchAi3d-Qwen && pip install -r requirements.txt

Or search "ArchAi3d Qwen" in ComfyUI Manager. Restart, then it's under ArchAi3d/Qwen/Camera. You need Qwen-Image-Edit weights (quantized on consumer cards) plus an encoder from this pack to actually run the prompt.

Gotchas

The views that sound similar are not interchangeable - bird's eye (straight down from high) vs. aerial (~45° site overview) vs. overhead (90° directly above the subject) produce different compositions. And as with every node in this family, direction is reliable but exact angle is approximate; a "dutch angle" may come out at 10° when you wanted 20°, and that's the model, not you.