SP_SupirSampler_DPMPP2M

If you're running SP_Supir, this is one of the two nodes you actually need to touch before it (the other is your model/checkpoint loaders). It's small on purpose - two settings, one job.

What it does

SP_SupirSampler_DPMPP2M builds a sampler configuration for SUPIR's DPM++2M sampling path and outputs it as a single supir_sampler bundle (typed SP_SupirSampler), ready to plug straight into SP_Supir's own supir_sampler input. It takes exactly two inputs: dpmpp_eta (a float, default 0.1, range 0 to 10) and tiled (a boolean, default off).

dpmpp_eta controls how much stochastic noise the sampler re-injects at each step - the same eta concept you'll recognize from other DPM++ samplers elsewhere in the ecosystem. Lower values (closer to 0) behave more deterministically, closer to a pure ODE solve; push it higher and each step re-introduces more randomness, which can add variation but also instability if you go too far. The default of 0.1 is a mild, sensible starting point - you generally won't need to move it far from there unless you're chasing a specific look.

tiled does what it says: switches the sampler into tiled mode, processing the image in chunks instead of all at once. This is your VRAM lever specifically for the sampling step - it's the sibling setting to sampler_tile_size over on SP_Supir itself, which controls the actual tile dimensions once tiling is on.

When you'd use this over the alternative

SP_SupirSampler's article (the "unpacker" node in this pack) notes that SUPIR's own implementation actually supports two sampler families - DPM++2M and EDM - and this node is the DPM++2M one. If you're not sure which to reach for: DPM++2M is the simpler, more commonly used default in SUPIR workflows, and it's the one this pack ships a dedicated builder node for. Unless you have a specific reason to want the EDM path's extra knobs (edm_s_churn, a separate restore_cfg), this is the one to start with.

Installing it

Part of the SP-Nodes pack:

• ComfyUI Manager: search "SP-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, restart ComfyUI.

No extra models - it's a config builder, not a model-loading node. The actual SUPIR checkpoint requirement lives on SP_Supir, not here.

Troubleshooting

If SP_Supir seems to ignore this node entirely, double check the wire actually goes into SP_Supir's supir_sampler input and not left dangling - since the type is a bundle unique to this pack (SP_SupirSampler), ComfyUI won't let you accidentally plug it in somewhere else, but it's easy to build the node and forget the connection. Beyond that, if VRAM is your constraint and turning tiled on here alone doesn't seem to help enough, remember it's only the sampler's own tiling - pair it with sampler_tile_size (and vae_tile_size for the VAE decode step) on the SP_Supir node itself, since tiling one stage without the other still leaves the other stage processing the full image at once.