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 have searched the existing issues and checked the recent builds/commits
What would your feature do ?When I was a new user. Knowing which folder to put Upscalers, Ultralytics models etc etc. Was confusing and also at times unknown since for example I was following along with a youtuber who was doing a tutorial. Told you what node to use. Put a link to a model in the description but completely glossed over where it needed to be placed. I would love an option or some toggle for users who want to use it where if there is a node that is referencing... well anything that requires a drop down where files are placed. The feature simply examines what folder that particular drop down is referenced to and pops it open so you can put the model file in there.
Proposed workflowPicture this... You are a new user. You are watching a youtube video about "Face Detailer" You maybe install the custom node the way the youtuber said. You downloaded the Yolo model from the link in the description. But the youtuber completely missed telling you where to actually put the file. So you add the Ultralytics node. But you are a new user and have no idea where you need to put that yolo file. So next to the dropdown for the ultralytics model dropdown is a little button to pop up the folder where those models are stored. And you can then just drag the model in there. Close the windows explorer window and go back to comfy. "Refresh" and the model shows up.
And this could work for anything where files need to be placed in specific folders. New users trying FLUX who have downloaded Clip or Unet models but have no idea where they go just click the little button and the folder pops up for them. Or they use an upscaler node and again they can pop up the folder. In essence all the feature does is look at what target folder is being referenced by that particular drop down and pops up an explorer window to that folder.
Is there an existing issue for this?
What would your feature do ?When I was a new user. Knowing which folder to put Upscalers, Ultralytics models etc etc. Was confusing and also at times unknown since for example I was following along with a youtuber who was doing a tutorial. Told you what node to use. Put a link to a model in the description but completely glossed over where it needed to be placed. I would love an option or some toggle for users who want to use it where if there is a node that is referencing... well anything that requires a drop down where files are placed. The feature simply examines what folder that particular drop down is referenced to and pops it open so you can put the model file in there.
Proposed workflowPicture this... You are a new user. You are watching a youtube video about "Face Detailer" You maybe install the custom node the way the youtuber said. You downloaded the Yolo model from the link in the description. But the youtuber completely missed telling you where to actually put the file. So you add the Ultralytics node. But you are a new user and have no idea where you need to put that yolo file. So next to the dropdown for the ultralytics model dropdown is a little button to pop up the folder where those models are stored. And you can then just drag the model in there. Close the windows explorer window and go back to comfy. "Refresh" and the model shows up.
And this could work for anything where files need to be placed in specific folders. New users trying FLUX who have downloaded Clip or Unet models but have no idea where they go just click the little button and the folder pops up for them. Or they use an upscaler node and again they can pop up the folder. In essence all the feature does is look at what target folder is being referenced by that particular drop down and pops up an explorer window to that folder.
But I feel like this could be a time saver
┆Issue is synchronized with this Notion page by Unito
The text was updated successfully, but these errors were encountered: