Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work with Get/Set KJNodes #213

Open
M1kep opened this issue Aug 18, 2024 · 2 comments
Open

Doesn't work with Get/Set KJNodes #213

M1kep opened this issue Aug 18, 2024 · 2 comments
Labels
compatibility working with other nodes
Milestone

Comments

@M1kep
Copy link

M1kep commented Aug 18, 2024

I'm not sure which extensions bug this is, but when I try to use the AE? node in combination with Get/Set KJNodes, something breaks with the links.

got prompt
Failed to validate prompt for output 14:
* CLIPTextEncode 9:
  - Exception when validating inner node: '2'

workflow(2)

@chrisgoringe
Copy link
Owner

Why would you use them both together ?!

@M1kep
Copy link
Author

M1kep commented Aug 18, 2024

😅😅

I was organizing my "globals" into a section where I pass the get results into a bunch of UEs with varying RegEx's to allow me to determine all node inputs by the groups they are in.

This let me keep the "set" areas clean by just having a small collapsed node next to the load checkpoint, or clip text encode.

I'll upload a pic in a few hours

My thinking is this wouldn't be too hard for somebody who's more familiar with the node graph and linking structure. I think the UEs are setting the input on the matching nodes to the virtual Get node's ID, rather than the Set nodes ID. I could definitely be wrong though, as I've only put about 30 min into this so far.

If you aren't able to take a look, I would appreciate if you could share some info about which functions in your code would probably be the best place to start looking. Also could you explain what upstream and downstream represent, I'd assumed they were the inputs and matched targets, but thought I was seeing the UE node ids as a downstream, but it's also possible I was getting nodeID and array indexes mixed up in the debugger 😭

@chrisgoringe chrisgoringe added the compatibility working with other nodes label Sep 6, 2024
@chrisgoringe chrisgoringe added this to the 5.2 milestone Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compatibility working with other nodes
Projects
None yet
Development

No branches or pull requests

2 participants