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

[FEATURE REQUEST] - ComfyUI v3.10 compatibility #108

Open
fafayqa opened this issue Jan 1, 2025 · 2 comments
Open

[FEATURE REQUEST] - ComfyUI v3.10 compatibility #108

fafayqa opened this issue Jan 1, 2025 · 2 comments
Labels
question Further information is requested

Comments

@fafayqa
Copy link

fafayqa commented Jan 1, 2025

Summary

I would request that this node is doing what it supposed to do also in the latest ComfyUI, cos at the moment it does absolutely nothing...speaking about the SD PROMPT READER: regardless of image I use - be it my own generated previously with the ComfyUI or some other taken from the Civitai website - it doe snot show any info at all!

2025-01-01 17 16 10

Basic Example

Want it to work as your example here. :-)

screenshot_v130

Reference Issues.

No response

@fafayqa fafayqa added the question Further information is requested label Jan 1, 2025
@MMykolyshyn
Copy link

MMykolyshyn commented Jan 2, 2025

I am also seeing loss of features on CUI v3.10-11. For SD Saver I am seeing the following:
image

NOW @fafayqa there appears to be a workaround. The nodes that are in the sample workflows provided (in the Workflows folder) appear to have the correct features and structure. I tested and the node does work. to do so:

  1. Open one of the sample workflows, then save it as one of your saved workflows.
  2. Then insert the workflow into any of your active workflows. Then attach what you need.

I would also recommend (deepening how long this bug persists) to build out a custom workflow that just collects all of your needed nodes, then just insert and attach what you want.

Additionally @receyuki I believe this also lends a clue on how to repair this issue long term. I am not a pro at all but I would assume the Nodes in the example workflows and the nodes we add in are not the same. So somewhere the call to bring in a node is not pointed to the right place. So finding out why this is (Node ID or whatever is used to link to the node object) will be a first step.

@fafayqa
Copy link
Author

fafayqa commented Jan 16, 2025

yes, that seems to work, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants