Add configuration option for Power Prompts to bypass stabilizeInputsOutputs() #281
Conversation
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
…utputs() enabling all outputs by default for better compatibility with Anything Everywhere
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I've been doing lots of editing my workflows and I consistently run into the issue that I cannot connect conditioning/model outputs from the Power Prompt nodes when the model/clip inputs are attached via Anything Everywhere nodes. I'm not sure what is going on in code that is causing these connections to not be treated as connected nodes, something to do with how Anything Everywhere broadcasting works I assume, but I did not wish to dig into so much code to resolve it. Instead I offer this configuration settings to bypass the problem with balancing behavior that occurs due to this incompatibility.