Hy3D Diffusers Scheduler Config

If you've ever wished you could just pick "Euler A" or "DPM++" for the delight or paint stage of a Hunyuan3D workflow, this is the node that lets you. Hy3DDiffusersSchedulerConfig builds a diffusers scheduler from the pipeline's own config and hands it out as a NOISESCHEDULER that Hy3DDelightImage and Hy3DSampleMultiView both accept.

It's a config node, so it has no model and no GPU cost - it reads the pipeline's scheduler config, swaps in the sampler you picked, and returns a scheduler object. The heavy lifting (the actual sampling) happens in whatever node you feed it to.

Inputs

• pipeline - a HY3DDIFFUSERSPIPE. It only needs to exist to provide the base scheduler config; wire it from DownloadAndLoadHy3DDelightModel or DownloadAndLoadHy3DPaintModel.
• scheduler - the sampler. Eleven options: DPM++, DPM++SDE, Euler, Euler A (default), PNDM, DDIM, SASolver, UniPC, Heun, DEIS, and LCM. If you know the sampler from image generation, the names mean the same things here. Euler A is a good default for these pipelines; DPM++ tends to give slightly crisper detail at similar step counts; LCM is only useful if you're trying to cut steps dramatically.
• sigmas - default, karras, exponential, or beta noise schedules. Karras is the community's usual quality pick; default keeps whatever the model shipped with.

Output: diffusers_scheduler (NOISESCHEDULER) → the scheduler socket on Hy3DDelightImage or Hy3DSampleMultiView.

The part that's easy to miss

The scheduler you build is derived from the pipeline's config, so it inherits the right parameters for the model automatically - you're only choosing the algorithm family, not hand-tuning noise schedules. That's the whole point: it's the "I want this sampler" switch without the research project.

One honest limitation: most Hunyuan3D workflows never touch this node, because the defaults (Euler A on the paint model) are already sane, and the delight stage barely benefits from sampler swaps. Reach for it when you want to experiment with quality per-step, or when a workflow someone shared specifies a particular sampler. It's also the natural place to look if a shared workflow references a scheduler you can't find - the "missing node" is usually this one.

Install

It ships with the pack, so it arrives with ComfyUI Manager (search "Hunyuan3DWrapper") or a clone into custom_nodes. No extra dependencies beyond the pack's own requirements.txt. There's a copy of this node on each branch of the example workflow - one feeding the delight stage, one feeding the paint stage - because each pipeline gets its own scheduler config.