00:42 — Locate the comfyui installation directory
01:02 — Clone the repository from github which introduces the missing node
01:12 — Switch into that newly cloned repo with the cd (change directory) command
01:24 — Locate the location where ComfyUI stores all of it's shit that is not part of the installation itself
01:49 — Activate the environment ComfyUI isolates itself in to keep dependencies working and updated for one thing without breaking shit for some other thing
01:58 — Entering the following command AFTER activating the environment to install dependencies for newly cloned repo: pip install -r requirements.txt -U
02:05 — Use the same python.exe (we use python to invoke the pip module since we can't upgrade pip if we're using pip, thus the reason we don't treat it like every other thing we install with pip) from the same directory as where we found the environment's activate.bat along with the following arguments: -m pip install --upgrade pip
03:14 — Close ComfyUI so it can load the newly cloned repository to introduce the new/missing nodes.
03:32 — Observe that the once missing node (rgthree) is no longer indicated to be missing.
Again.
03:45 — finding the repo which has the missing node.
04:01 — Opening a terminal from within the ComfyUI's python environment's scripts folder which contains the batch file to activate said environment.
04:07 — Edited out an interruption but you've missed nothing of interest, simply navigating to the installation location's custom_nodes directory to proceed cloning the next repo, checking it's contents, and installing the observed reqs files
04:54 — Begin organic troubleshooting to find out why the cloned and installed repo doesn't provide the missing node. Starting with opening the workflow from the file once more, because (as you'll see later) sometimes ComfyUI doesn't notice that newly installed nodes exist which are part of custom node groups so the custom group remains missing (is my theory anyway, I have no credible insight into why this occurs)
05:26 — Open file explorer and rename the folder to lowercase which might help depending on how specifically the script is trying to locate something. Linux knows that ./This and ./this are two different directories, but Windows will see .\This and .\this as the same thing.
YouShouldKnow: in all operating systems that I know of, a single period/full stop "." used programmatically stands to represent the current working directory a.k.a. the directory the command is being executed from, and two of them ".." refers to the parent directory of that which you're currently in. For example is you're in C:\ComfyUI\models and you do cd .. you will change directories and now be in C:\ComfyUI
06:14 — open built-in terminal to observe outputs. COMMAND LINE IS NOT SCARY, it conveys information as simply and as clearly as possible. A few seconds later I highlight that we can see that it's trying to call a module which isn't installed.
06:34 — Attempt simplest manual retrieval/installation of missing python module with: pip install <insert module>
06:54 — Observe the python file failing to make the call for a module which is missing, just to see if it's doing so in a weird or unconventional manner, even if you don't know how to write code, you know how to read and knowledge is power.
07:14 — attempt a couple different things, like putting "py" in front of the missing module's name as is sometimes the case for something being added to PyPi (Python Package Index). Also try un→reinstalling the module which claims py pip to be installed by the workflow to be missing.
08:23 — Copy the root cause of the issue, which shall be inputted into the most powerful tool of all...
08:47 — Seeing what others are experiencing and how they're remedying their issues if indeed anyone has, but rest assured you're not the first one to do anything in life, so errors will most often be resolved by people who care more than you do to make shit work, so one requires only the mere will to READ as a form of consuming information which will be the most efficient manner to learn constructive knowledge.
09:07 — Check multiple sources.
09:22 — /u/agx3x2 has the insight we needed!
09:44 — Observe in the background the script running updates for the comfyui manager's front end, which is sometimes required for our attempts to be able to be aware of and make use of shit which is newly updated or recently released. This is also why we had to upgrade pip a little bit ago.
09:50 — ComfyUI fails to load UI. (to the devs, this occurrs a handful of times, so maybe interesting to you to stick around)
10:27 — Open the workflow from file again.
Again.
10:53 — WindowsKey+r brings up Windows' run dialog. %USERPROFILE% is to Windows as $USER is to Linux.
11:34 — I don't know who needs to hear this, but the Del key on a standard keyboard removes things that are in front of the cursor, as opposed to backspace key which removes things that are behind the cursor.
11:51 — Activate the environment.
12:40 — Install the deps.
13:53 — Attempt manual installation of missing module.
14:20 — The LEAST you could do...
16:27 — See if the manager can help (Admittedly I may have recommended this sooner if this wasn't all in an effort to make you more self reliant).
17:21 — ComfyUI again fails to load UI after having updated manager's front end.
17:46 — Open the workflow again from file.
AGAIN.
18:05 — Find it.
18:18 — Install it.
18:30 — Satisfy it.
AGAIN!
18:55 — THE SITE DOESN'T SHOW THE NODE!?!?!?!
19:04 — Check the other one, maybe they were both part of the same repo
19:25 — Make sure the last thing worked before focusing on the next thing.
19:49 — Wrapping google search terms "in quotes" makes google return results that contain that which the quotes contain EXACTLY as it appears within the quotes.
20:00 — From the top, the first and the fourth things this repo lists in the "Features" section are those which we are missing. Rejoice!
20:02 — Clone the repo into the installation directory's custom_nodes folder.
20:16 — Satisfy the repo's dependencies.
20:40 — Kill it.
20:45 — Rebirth.
21:09 — I noticed the missing package in the background of the loading splash...
21:11 — No dice.
21:17 — Manager manages.
21:47 — Consistently fails to load UI without killing the process after updating front end.
22:09 — Once more, with feeling!
22:19 — Eureka! Go forth now and exert your newfound competence unto fearful repositories who once thought themselves safe in the obscurity of dependency hell, for now hell has frozen over!