图像分区 · 分块参数档位

If you've ever hand-wired max_pixels, context_pixels, and grow values into a tiling workflow, you know it's a knuckle-dragging exercise in arithmetic. RegionEditTileControlPreset is the pack's answer: one node that centralizes all the tile sizing decisions behind named presets, so "my 8GB card can't handle this" becomes a dropdown instead of a spreadsheet.

The core is tile_profile, with four named tiers straight from the source: 保守（小块） conservative/small, 标准 standard, 大块（高显存） big (high VRAM), and 超大块（慢速） extra-large (slow). These map to concrete geometry - conservative is 1024×768 max at ~786K pixels, standard is 1536×1024 at ~1.57M pixels, big is 2048×1536 at ~3.1M, and extra-large is 2816×2816 at 8.4M. You pick based on VRAM: if you OOM, drop a tier; if you've got headroom, raise one for fewer, larger tiles. The tooltip says it plainly: "显存不足时选小块，显存充足时可选大块."

Then default_grow (the reconstruction extent outside the target mask - choices from 8 to 192 pixels) and default_blur (composite edge softness - from hard 0 to very soft 64) are each their own named dropdown, because the pack is emphatic that grow and blur are independent: grow decides how much context gets rebuilt, blur decides how soft the seam is, and neither should auto-scale with the other. For per-tile exceptions, tile_grow_overrides and tile_blur_overrides take strings like 2=16,5=64 (tile numbers matching the plan preview, starting at 1; empty = uniform).

The last input is edit_instruction - the node also carries your edit text ("移除选中内容，保持其他内容不变。" by default, with a tooltip explaining it goes straight into the FLUX.2 Klein edit flow), so your instruction travels with the sizing config down the same wire. That's the "control" in the name: one node is the single source of truth for "what are we editing, at what size, with how much context."

The nine outputs are exactly the values the tile planner and batch-prepare nodes want: max_long_side, max_short_side, max_pixels, context_pixels, default_grow, tile_grow_overrides, default_blur, tile_blur_overrides, and edit_instruction. There's a nice safety detail in the source: context_pixels is silently bumped up to guarantee it's at least max_grow + SAFE_TILE_MARGIN and SEAM_GUARD_PIXELS + SAFE_TILE_MARGIN, so even if you crank grow to 192, the crop context stays large enough that neither the reconstruction area nor the fixed seam guard can reach a VAE crop edge. You can't accidentally build a plan that chops its own context - that's a real design nicety.

Install: ComfyUI Manager → Region Edit Toolkit (native-region-tile-planner-merge), or git clone https://github.com/Liu-Bot24/ComfyUI-Region-Edit-Toolkit.git into custom_nodes, pip-install requirements.txt into ComfyUI's actual Python, restart.

The honest take: this is the node that makes the whole tiling chain usable, and the extra-large "slow" tier is aptly named - 8.4M-pixel tiles are for people with genuinely big VRAM and patience. Start at standard, let labeled_preview_images from the batch-prepare node show you the plan, and only then decide whether the extra-large tier is worth the wait. This pack is too new for community tuning threads, so treat the presets as the author's own baseline - they're sensible baselines.