fix(ui): improve DyPE field ordering and add 'On' preset option#8793
Merged
lstein merged 22 commits intoinvoke-ai:mainfrom Jan 30, 2026
Merged
fix(ui): improve DyPE field ordering and add 'On' preset option#8793lstein merged 22 commits intoinvoke-ai:mainfrom
lstein merged 22 commits intoinvoke-ai:mainfrom
Conversation
- Add ui_order to DyPE fields (100, 101, 102) to group them at bottom of node - Change DyPEPreset from Enum to Literal type for proper frontend dropdown support - Add ui_choice_labels for human-readable dropdown options - Add new 'On' preset to enable DyPE regardless of resolution - Fix frontend input field sorting to respect ui_order (unordered first, then ordered) - Bump flux_denoise node version to 4.4.0
JPPhoto
requested changes
Jan 27, 2026
Collaborator
JPPhoto
left a comment
There was a problem hiding this comment.
I'm getting this error when I use the node.
DyPEPreset is now a Literal type (string) instead of an Enum, so .value is no longer needed.
Update test imports and assertions to use string constants instead of Enum attributes since DyPEPreset is now a Literal type.
- Add dype_scale (λs) and dype_exponent (λt) sliders to generation settings - Add Zod schemas and parameter types for DyPE scale/exponent - Pass custom values from Linear UI to flux_denoise node - Fix bug where DyPE was enabled even when preset was "off" - Add enhanced logging showing all DyPE parameters when enabled
- Fix DyPE scale and exponent parameters not being applied in frequency computation (compute_vision_yarn_freqs, compute_yarn_freqs now call get_timestep_mscale) - Add metadata handlers for dype_scale and dype_exponent to enable recall from generated images - Add i18n translations referencing existing parameter labels
- Fix DyPE scale and exponent parameters not being applied in frequency computation (compute_vision_yarn_freqs, compute_yarn_freqs now call get_timestep_mscale) - Add metadata handlers for dype_scale and dype_exponent to enable recall from generated images - Add i18n translations referencing existing parameter labels
…sack/InvokeAI into fix/dype-ui-ordering
- Hide scale/exponent controls in UI when preset is not "on" - Only parse/recall scale/exponent from metadata when preset is "on" - Prevents confusion where custom values override preset behavior
Presets (auto, 4k) now use their predefined values and ignore any custom_scale/custom_exponent parameters. Only the 'on' preset allows manual override of these values. This matches the frontend UI behavior where the scale/exponent fields are only shown when 'On' is selected.
Rename the 'on' DyPE preset to 'manual' to better reflect its purpose: allowing users to manually configure scale and exponent values. Updated in: - Backend presets (DYPE_PRESET_ON -> DYPE_PRESET_MANUAL) - Frontend UI labels and options - Redux slice type definitions - Zod schema validation - Tests
Rename the 'on' DyPE preset to 'manual' to better reflect its purpose: allowing users to manually configure scale and exponent values. Updated in: - Backend presets (DYPE_PRESET_ON -> DYPE_PRESET_MANUAL) - Frontend UI labels and options - Redux slice type definitions - Zod schema validation - Tests
…sack/InvokeAI into fix/dype-ui-ordering
JPPhoto
requested changes
Jan 29, 2026
Collaborator
JPPhoto
left a comment
There was a problem hiding this comment.
Hopefully these are all quick changes.
invokeai/frontend/web/src/features/nodes/util/graph/generation/buildFLUXGraph.ts
Show resolved
Hide resolved
…sack/InvokeAI into fix/dype-ui-ordering
- Update docstrings, comments, and error messages to use 'manual' preset name - Simplify FLUX graph builder to always send dype_scale/dype_exponent - Fix UI condition to show DyPE controls for 'manual' preset
JPPhoto
approved these changes
Jan 29, 2026
Collaborator
JPPhoto
left a comment
There was a problem hiding this comment.
Things are great! If there are any outstanding issues, I'm sure people will catch them in rc2.
dunkeroni
pushed a commit
to dunkeroni/InvokeAI
that referenced
this pull request
Feb 2, 2026
…ke-ai#8793) * fix(ui): improve DyPE field ordering and add 'On' preset option - Add ui_order to DyPE fields (100, 101, 102) to group them at bottom of node - Change DyPEPreset from Enum to Literal type for proper frontend dropdown support - Add ui_choice_labels for human-readable dropdown options - Add new 'On' preset to enable DyPE regardless of resolution - Fix frontend input field sorting to respect ui_order (unordered first, then ordered) - Bump flux_denoise node version to 4.4.0 * Chore Ruff check fix * fix(flux): remove .value from dype_preset logging DyPEPreset is now a Literal type (string) instead of an Enum, so .value is no longer needed. * fix(tests): update DyPE tests for Literal type change Update test imports and assertions to use string constants instead of Enum attributes since DyPEPreset is now a Literal type. * feat(flux): add DyPE scale and exponent controls to Linear UI - Add dype_scale (λs) and dype_exponent (λt) sliders to generation settings - Add Zod schemas and parameter types for DyPE scale/exponent - Pass custom values from Linear UI to flux_denoise node - Fix bug where DyPE was enabled even when preset was "off" - Add enhanced logging showing all DyPE parameters when enabled * fix(flux): apply DyPE scale/exponent and add metadata recall - Fix DyPE scale and exponent parameters not being applied in frequency computation (compute_vision_yarn_freqs, compute_yarn_freqs now call get_timestep_mscale) - Add metadata handlers for dype_scale and dype_exponent to enable recall from generated images - Add i18n translations referencing existing parameter labels * fix(flux): apply DyPE scale/exponent and add metadata recall - Fix DyPE scale and exponent parameters not being applied in frequency computation (compute_vision_yarn_freqs, compute_yarn_freqs now call get_timestep_mscale) - Add metadata handlers for dype_scale and dype_exponent to enable recall from generated images - Add i18n translations referencing existing parameter labels * feat(ui): show DyPE scale/exponent only when preset is "on" - Hide scale/exponent controls in UI when preset is not "on" - Only parse/recall scale/exponent from metadata when preset is "on" - Prevents confusion where custom values override preset behavior * fix(dype): only allow custom scale/exponent with 'on' preset Presets (auto, 4k) now use their predefined values and ignore any custom_scale/custom_exponent parameters. Only the 'on' preset allows manual override of these values. This matches the frontend UI behavior where the scale/exponent fields are only shown when 'On' is selected. * refactor(dype): rename 'on' preset to 'manual' Rename the 'on' DyPE preset to 'manual' to better reflect its purpose: allowing users to manually configure scale and exponent values. Updated in: - Backend presets (DYPE_PRESET_ON -> DYPE_PRESET_MANUAL) - Frontend UI labels and options - Redux slice type definitions - Zod schema validation - Tests * refactor(dype): rename 'on' preset to 'manual' Rename the 'on' DyPE preset to 'manual' to better reflect its purpose: allowing users to manually configure scale and exponent values. Updated in: - Backend presets (DYPE_PRESET_ON -> DYPE_PRESET_MANUAL) - Frontend UI labels and options - Redux slice type definitions - Zod schema validation - Tests * fix(dype): update remaining 'on' references to 'manual' - Update docstrings, comments, and error messages to use 'manual' preset name - Simplify FLUX graph builder to always send dype_scale/dype_exponent - Fix UI condition to show DyPE controls for 'manual' preset --------- Co-authored-by: Jonathan <34005131+JPPhoto@users.noreply.github.com> Co-authored-by: Lincoln Stein <lincoln.stein@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ui_orderto DyPE fields (100, 101, 102) to group them at bottom of nodeDyPEPresetfrom Enum to Literal type for proper frontend dropdown supportui_choice_labelsfor human-readable dropdown optionsui_order(unordered first, then ordered)flux_denoisenode version to 4.4.0Related Issues / Discussions
Fixes DyPE fields being scattered throughout the FLUX Denoise node UI instead of grouped together.
QA Instructions
Merge Plan
Standard merge, no special considerations.
Checklist
What's Newcopy (if doing a release after this PR)