array1 step increment

Let me save you five minutes: array1 step increment and array1 step from this same pack are the same node wearing a different label. Same three inputs (start, step, increment), same single array output, and the same math under the hood. The author ships both, and the code confirms it - both produce [start, start+increment, start+2*increment, ...]. You only ever need one, and which one you use is pure taste.

So what does it actually do? It generates an arithmetic sequence. The confusing part is the parameter naming, which is worth repeating loudly: step here is the number of values to generate, not the spacing. increment is the spacing. start=10, step=4, increment=5 gives you [10, 15, 20, 25] - four values, spaced 5 apart. If you set step=1, you get a list with just start in it, because the loop runs zero times. If increment is 0, every value after start is identical.

Where does this fit? These array generators exist to drive batch and camera work - sweep a camera elevation from 0 to 30 in steps, generate N frame indices, produce a list of orbit radii for a multi-view render. Feed the output array into anything in the pack that eats a LIST, like the camera-pose converter or a batch loop, and you've turned one typed number into a whole sequence without hardcoding.

One behavior to respect: there's no guard on start interacting badly with a negative increment, so a step count of 5 with increment=-2 gives you [10, 8, 6, 4, 2] - fine if you meant it, surprising if you didn't. Check the output list in the UI before you rely on it. It's a cheap sanity check and it saves a confusing render later.

This is part of 807502278/ComfyUI-3D-MeshTool, a one-developer 3D utility pack. Pure Python, no models. Install via ComfyUI Manager (search "ComfyUI-3D-MeshTool") and restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/807502278/ComfyUI-3D-MeshTool
cd ComfyUI-3D-MeshTool
pip install -r requirements.txt

Pack-wide heads-up that applies here: the author renames nodes between releases and old instances go red in saved workflows. When that happens, recreate the node and reconnect - and now you know you can just grab whichever twin is present.