psychedelicious
commented
7 months ago This node is an internal implementation detail, designed for programmatic use in the UI. We got requests for it to be made visible in the UI so we un-hid it, but this node should have a big asterisk on it.
In v4, this node changes, and these inputs are nonfunctional:
And these inputs have "incorrect" types:
- rand device
- scheduler
- init image
- hrf method
- refiner scheduler
These inputs have field/data types that are used only for metadata in the linear UI's internal graph building logic. I don't plan to create all the additional logic and UI for those field types.
Is there an existing issue for this problem?
Operating system
macOS
GPU vendor
Apple Silicon (MPS)
GPU model
M1 Max
GPU VRAM
64 GB
Version number
3.7.0
Browser
Chrome 121.0.6167.184
Python dependencies
No response
What happened
In the workflow editor, I added the Core Metadata node and went to select the model. I was using an SDXL model but the list only displayed SD 1.x models
What you expected to happen
I expected to see all available models in the list (or, a list limited by the Generation Mode)
How to reproduce the problem
Open workflow editor, add Core Metadata node, select models in dropdown. (On a system with both SD 1.x and SDXL models installed.)
Additional context
This may be related to https://github.com/invoke-ai/InvokeAI/issues/4959 https://github.com/invoke-ai/InvokeAI/pull/4686#discussion_r1366447763
Only somewhat related: The core metadata node could also benefit from passthrough/output values (could use its fields as inputs for linear workflow UI and then pass fields out to the graph from there). Or alternatively the Denoise Latents node could pass out values that could be piped into core metadata. Would make workflow layout simpler.
Discord username
No response