DAC Data Scale 988

Every node in the DaC pipeline runs on a little dict called dac_data - the upscaled dimensions, tile size, overlap and grid that Divide Image Select and Combine Tiles read to do their jobs. DAC Data Scale 988 is a pure utility that rescales every dimension in that dict at once: width, height, tile size and overlap all multiplied by a single multiplier, with the grid layout and tile order left untouched.

It exists because of a workflow problem that has nothing to do with image quality: you planned a tiling run at 1024px tiles, and then you realized your card can't handle 1024px tiles in the processing pass, or you want to increase the resolution of the tile processing without re-planning the whole grid. Rather than re-running DaC Algorithm with new inputs and re-checking the info every time, you drop this node between the algorithm and the rest of the pipeline and rescale the plan in one move.

The inputs

Only two, and neither needs much explanation:

• dac_data - the plan from DaC Algorithm 988 (or 988 v2).
• multiplier (default 1.0, range 0.25–16, step 0.25) - scales every dimension. 0.5 shrinks tiles to half size for a VRAM-light processing pass; 2.0 doubles everything for a higher-res pass.

The grid (grid_x/grid_y) and tile_order are explicitly preserved - that's the whole point. The node is intentionally dumb: it scales numbers, it doesn't re-solve geometry. If you shrink tiles but keep the grid, your overlap shrinks proportionally too, and if you shrink it far enough the tiles stop overlapping at all - at which point you're back to seam city and you should probably re-run the algorithm instead.

Outputs

• dac_data - the scaled plan, to be fed onward to Divide Image Select and Combine Tiles.
• info - a summary showing each dimension before/after, plus the grid, which is preserved. That's the line you want to read: it tells you the geometry is still sane.

When to reach for it

Honestly, this is the kind of node you use once you've hit the mismatch once. The moment you're tuning "which tile size can my card actually process" across a few runs, being able to halve the whole plan instead of editing four fields in the algorithm is the kind of small QoL win the plumbing layer is full of. It's also handy for scaling a plan from a source image you want to preview cheaply - plan big, scale the geometry down for a test run.

Install

Part of ComfyUI-988: Manager (search "ComfyUI-988") or:

cd ComfyUI/custom_nodes
git clone https://github.com/kajan988/ComfyUI-988
cd ComfyUI-988
pip install -r requirements.txt

Then restart. It's pure math - no models, no downloads, nothing to configure beyond the two inputs.