You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using both Fooocus kSampler from both Fooocus_Nodes and from comfyui-art-venture:
As far as i understand, they are both defined as "FooocusKSampler" by ComfyScript:
For example;
"_, img_out = FooocusKSampler(pipe3, "Preview", "ComfyUI", model)["result"]"
How do we choose FooocusKSampler defined from Fooocus_Nodes in our comfyscript output?
Additional comment:
I guess it is FooocusKSampler_ node but If I run that I am facing the following error:
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_group_norm)
It should be FooocusKSampler_. You can check its type stub. Conflicting names (nodes/types) will be suffixed with underscores. This is sometimes misleading but I havn't found a better way that is also short.
That error is probably caused by the same problem as in #94?
Although it is the same error, this time it may not be caused because of threading. I get the error sometimes even in the web ui. Also getting the same error by just running at the first execution
Activity
cihangoksu commentedon Feb 24, 2025
Additional comment:
I guess it is FooocusKSampler_ node but If I run that I am facing the following error:
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument weight in method wrapper_CUDA__native_group_norm)
Chaoses-Ib commentedon Feb 24, 2025
It should be
FooocusKSampler_. You can check its type stub. Conflicting names (nodes/types) will be suffixed with underscores. This is sometimes misleading but I havn't found a better way that is also short.That error is probably caused by the same problem as in #94?
cihangoksu commentedon Feb 24, 2025
Although it is the same error, this time it may not be caused because of threading. I get the error sometimes even in the web ui. Also getting the same error by just running at the first execution
Chaoses-Ib commentedon Feb 24, 2025
Then it's probably the node itself's problem. Maybe you can report to the author? Though it looks a bit unmaintained...