Derp Slider V2 Editor
Style Your Sliders Before They Touch a Workflow
Here's the honest pitch: the Derp Slider V2 Editor does nothing to your generation. No inputs, no outputs, no data flowing through the graph. It's a pure design-time tool - a sandbox where you tune how a Derp Slider looks, then save that look as a reusable style file. If you've never cared what a slider widget looks like, you can skip it entirely. If you're building a control surface you'll stare at all day, this is where the polish happens.
What it actually is
It ships in xcp_derp-UI-Release (comfy.icu knows it as "xcp_derp-UI"), the pack from lordwedggie that layers custom layouts, themes, docking and "wireless" signal routing on top of a normal ComfyUI graph. Its whole point is replacing the default control nodes with ones that look intentional instead of like a spaghetti incident. The Slider V2 is the pack's second-generation slider widget, and this editor is its fitting room.
The Python side is one line of truth: the node class is a pure virtual shell whose function is literally do_nothing and returns an empty tuple. Everything you see is front-end. That's a pattern worth knowing - a handful of derp-UI nodes are exactly this: UI-only surfaces that the backend registers so they exist in the node menu, but they never touch the inference pipeline.
How it works
The editor renders a live preview slider on the node face (a float from 0 to 1, step 0.01) plus a row of style controls. When you save, it packages the current style into a JSON file and POSTs it to the pack's /xcp/save/sliderV2Styles route; the load dropdown pulls files back through /xcp/load/sliderV2Styles. Saved styles live in ComfyUI/user/derpNodes/sliderV2Styles/ - plain JSON you can back up, hand to a friend, or wipe without touching your workflows.
The controls that matter, all on the face:
- Style preset dropdown - the base look (the built-in presets like the "knob" style).
- Canvas vs HTML render path - the same style can render two ways; HTML is the fancier painter path, and this is a global toggle, not per-slider.
- btnLR and Round knob toggles - button-style left/right arrows, and (for knob styles) whether the knob is round.
- Fill height and knob geometry (width scale, offsets) - the fine detail that separates a custom control from a default one.
- The style name field plus load / save / refresh buttons for style files.
Installing it
Same story as the whole pack - there's no separate install:
cd ComfyUI/custom_nodes
git clone https://github.com/lordwedggie/xcp_derp-UI-Release
Restart ComfyUI. Or open ComfyUI Manager β Custom Nodes Manager and search "xcp_derp-UI-Release" - same result. There's no requirements.txt and no model downloads: it's JS plus a thin Python shell that only uses ComfyUI's bundled environment. That's the good news for a pack this UI-heavy.
Where people trip
- It's not per-node styling. The editor tunes a style file that other sliders reference; it doesn't restyle the node you're looking at in place. Adjust, save, then point your slider at that style.
- The render path is global, so if your canvas-rendered slider and your HTML-rendered slider don't match, that's why - it's a pack-wide setting, not per-node.
- Empty style dropdown? Hit the refresh button; files live under
user/derpNodes/sliderV2Stylesand the list is fetched on demand. - Weirdly broken face after an update - hard-refresh the browser (Ctrl+Shift+R). This pack ships a lot of front-end code and stale cached JS is the classic culprit.
One honest caveat: this is a young, niche pack with basically no community footprint yet. The editor is fiddly, and if you only need a slider, the plain Derp Slider is fine. Reach for the editor when the difference between "default widget" and "custom control surface" is the whole reason you installed the pack.
Inputs (0)
No inputs
Outputs (0)
No outputs