MiniMax H3 R42 · Native Safety Checkpoint

Every delivery route in the R42 universal system needs one thing in common: a saved, verified copy of the native H3 take with its audio, before any finishing route touches it. IAMCCS_MiniMaxH3UniversalNativeCheckpointR42 is that shared safety net - the node that always saves the native frames and audio to disk, and then makes one smart decision about whether to keep the render going.

The smart decision is the "queue owner" problem, and it's worth understanding because it's the heart of R42's multi-route design. A long multi-segment render auto-queues each next segment. But who is allowed to do that depends on the delivery route, because some routes need to wait for the complete native film. If a master route (the LTX one-film path) is selected, this checkpoint queues every segment and merges them all - LTX gets handed the whole programme, never a lone final chunk. If a per-segment route is selected instead, the checkpoint does not own the queue; the per-segment delivery node downstream does, and it re-queues as it finishes each piece.

So the node's job splits in two: the saving part is unconditional (native frames + audio always get checkpointed - that's the "safety" in the name), and the queueing part is conditional on the route. Read the code and you'll see it: for master routes it forces merge_segments = True and arms the legacy-master editor policy; otherwise it just saves and lets the delivery layer handle continuation.

Inputs and outputs

The required inputs are the raw material and the choreography: images and audio (the native take), current_segment/total_segments, fps, and trim_head_frames. Optional sockets cover the plumbing - bridge_images for continuity, resolved_render_id, filename_prefix (default IAMCCS/MiniMaxH3/segment), merge_segments, keep_segments, render_id, queue_next_segment, stage_label, plus sampled_latent, motion_context, motion_state and cine_linx for state handoff, and editor_delivery_policy. Outputs: native_frames, native_audio, resolved_render_id, and report.

For a beginner, the ones that matter are images/audio in, cine_linx in (so it knows the route), and the resolved_render_id/report/native_frames/native_audio out - those downstream delivery branches are the consumers.

The honest take

This node is the R42 replacement for the older plain native checkpoint: it saves exactly the same thing, but it participates in route-aware queueing so a master run can't accidentally start LTX on segment 1 while H3 is still generating segment 12. The failure mode it prevents - a master film built from an incomplete native programme - is the kind of bug that wastes an entire evening of rendering. That's why every other R42 delivery node checks native_saved_report and refuses to run without it: the checkpoint is the contract that everything else trusts.

Where people trip: if you bypass this node and feed a delivery route directly, the delivery node will correctly refuse - "must run after the native safety checkpoint." That error is R42 working as intended, not a bug. Keep the checkpoint in the graph and route everything through it.

Install

It's part of IAMCCS-nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes

or via ComfyUI Manager (search "IAMCCS"), then restart. It needs the H3 stack - current ComfyUI (≥ 3.x) with native MiniMax H3, Python ≥ 3.12, PyTorch ≥ 2.8, the ~42 GB H3 weights and its video/audio VAEs. And the licence reminder applies as always: H3's community terms exclude the US, EU, UK and Korea.