NAI Detection Combine Loader

You've found the deprecated twin. NAIDetectorCombineLoaderTest shows up in the node menu as "NAI Detection Combine Loader" - the same label as the current node - and its schema is byte-for-byte identical, because it is the current node. In the pack's __init__.py it's a subclass with a flag:

class NAIDetectorCombineLoaderTest(NAIDetectionCombineLoader):
    DEPRECATED = True

It exists so that the pack's 2.8.0-era prototype workflows and previously saved API prompts still resolve. There's no test variant of the logic, no experimental path, nothing to compare against. If you're building a new workflow, use NAIDetectionCombineLoader.

What it does, since you'll meet it anyway

Four dropdowns and one output. face_segm_model is the primary region selector and defaults to segm/Anzhc Face seg 640 v2 y8n.pt; the other three (face_bbox_model, sam_model, eye_bbox_model) sit behind show_optional_models and are only relevant when SEGM is set to OFF. SEGM wins whenever it's selected - BBOX and SAM aren't just skipped, they're never downloaded or loaded, which is the point of having the priority rule in the first place.

Bundling models/ultralytics/segm plus models/ultralytics/bbox plus models/sams into one panel makes the detectors a swappable input rather than a wiring project. The only thing you get out is detectors, a NAI_DETECTION_BUNDLE that the pack's detailer nodes consume directly. It's not SEGS, and it won't plug into Impact Pack's own detailers.

Install

Same pack, same steps, and this node is inert without its collaborators:

cd ComfyUI/custom_nodes
git clone https://github.com/raspie10032/ComfyUI_RS_NAI_API_Request.git
python -m pip install -r ComfyUI_RS_NAI_API_Request/requirements.txt

ComfyUI-Impact-Pack and ComfyUI-Impact-Subpack provide the actual YOLO and SAM providers this node wraps, and the pack's requirements add segment-anything for the SAM path. Restart ComfyUI after installing or updating.

The one thing to watch

Migrated 2.8.0 workflows keep working, and quiet compatibility is exactly why this alias is here. But the prototype-era detailer carried a preview_only flag that let you preview detection and matching without spending anything. That control is gone from the current node, and it no longer suppresses a correction request on a migrated graph. Loading a workflow is safe. Queueing it corrects the image, subject to its saved Anlas protection.

Practically: if you open an old workflow and find a loader whose class name ends in Test, don't fix it - swap it for NAIDetectionCombineLoader. Same sockets, same output, no migration to think about later. The label on the canvas will look identical either way, so check the class name in the saved workflow JSON if you care which one you're running.