Gourieff / comfyui-reactor-node

Fast and Simple Face Swap Extension Node for ComfyUI
GNU General Public License v3.0
1.09k stars 114 forks source link

Can't seem to get the sams and ultralytics directories to populate, or be recognized #279

Closed HotHams closed 2 months ago

HotHams commented 2 months ago

First, confirm

What happened?

I've updated ComfyUI, gotten latest on everything here, and I've followed the readme closely, but can't get the ultralytics and sams directories to get recognized where the directions tells me they should be. Upon install, those don't populate, so I manually created them, as I don't know whether I'm supposed to populate them through some other method. The readme doesn't mention this if so, but mentions to "put it into the 'ComfyUI\models\ultralytics\bbox' directory" so this implies the sams and ultralytics directories should be there already, and identifiable. Since they're not, I guessed that manually creating the folders and placing the files within would work, considering the new hotfix points to the corresponding paths. Any help with regard to getting my system to recognize these so I can use this set of nodes correctly would be appreciated. Thank you!

Steps to reproduce the problem

Preceding this, I was getting an issue nearly identical to this. What made it stop bugging me about ultralytics, though, was having Comfy install the pip package for ultralytics. It stopped bothering me about ultralytics, but beyond that, it didn't solve anything. It did not create a directory for it nor sams, and when I searched for "ultralytics" nothing comes up in my ComfyUI folder. Reactor can't find the path where we're supposed to place the face_yolov8m.pt model or the sam_vit_b_01ec64.pth model.

Sysinfo

Win11 4090 Just a simple Reactor setup for fastfaceswap on ComfyUI Windows Portable.

Relevant console log

This isn't really code-related, so much as it is an inability for my system to find the paths directed by reactor.

Additional information

No response

HotHams commented 2 months ago

I ensured I got the ultralytics path via other packages that call for it, and came to the conclusion this seemed likely due to user error somewhere along the way. I hope I didn't waste anyone's time!