ArchAi3D_Qwen_Interior_View_Control

There's a reason real-estate photography leans on the corner shot: it shows two walls, the floor, the ceiling and the sightline in one frame. ArchAi3D_Qwen_Interior_View_Control defaults to corner_front_left for exactly that reason - the author calls corner views the most common in real-estate work, and it's the node you reach for when you want to re-shoot a room from a set of classic angles instead of typing camera directions yourself.

Mechanically it's the sibling of the pack's other interior camera nodes: a prompt-builder for Qwen-Image-Edit that turns a preset (or a custom angle description) into a "change the view to…" instruction plus a system prompt that tells the model it's an interior photographer who must preserve every fixture, wall feature, flooring detail and spatial relationship. Where it stands apart from Interior Focus and Interior Navigation is that it's view - not distance or travel - so it's the one to pick when you're hunting for a composition rather than a move.

What's different about this node

Two extra inputs make it interesting, both born from the pack's Qwen prompt research:

• target_description - tell the model what's actually on the wall you're pointing at ("that has refrigerator", "with large window", "no molding"). The author's research found that naming the target object materially improves whether Qwen actually shows it. It's optional but it's the difference between "a wall" and "the wall with the window."
• preservation_preset - a constraint clause to force layout consistency during the camera change. It defaults to none, and there's a custom slot if you want to write your own ("keep refrigerator visible in frame"). If you're doing a series of view variants for a client, this is the input that keeps each shot looking like the same room.

Otherwise you get the standard inputs: preset (viewing angle presets, corner_front_left default), scene_context (the room description), a free-text custom_angle for when none of the presets fit, and debug_mode to print what it's building.

Outputs: prompt (your encoder's user text), view_description, and system_prompt (wire to the encoder's system_prompt input - on this node the preservation language lives there, so connect it).

Installing it

Part of the ComfyUI-ArchAi3d-Qwen pack by Amir Ferdos (ArchAi3d), installed like every node in it:

# ComfyUI Manager: search "ArchAi3d Qwen"
cd ComfyUI/custom_nodes
git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
cd ComfyUI-ArchAi3d-Qwen
pip install -r requirements.txt   # PyYAML core; heavy deps are optional

Restart, then load a Qwen-Image-Edit model (2509/2511, GGUF-quantized unless you own a data center) - the pack bundles no checkpoints.

Common issues

• The room rearranges itself. Qwen-Edit re-emits the whole frame, so unasked-for pixels move. The preservation clause is your lever here; crank it to custom and pin the objects that must stay put.
• Angles are approximate. Research-consistent, not exact. Direction is reliable, degree fidelity isn't - don't iterate on a single degree of rotation and expect a difference.
• People break it. If a person is in the shot, the model will happily rotate them instead of the camera. This node is for rooms; use the Person category nodes for people.

The honest summary: it's a template library for interior viewpoints, and for the corner-angle default alone it saves you the fiddliest part of writing Qwen camera prompts by hand.