From my current experience as well, some lora work better on certain art styles. Such as anime vs realistic. Sometimes using only a high with no low can fix out the details before generation.

(Even bumping the strength to 2 or even 3.)

I have had some lora completely change my image and i found some new ones that just perform better on the art style at times.

I usually will do short test (2 seconds) to save time to make sure the adjustments made for my workflow are working as intended or there is no major changes to the desired output.

I dont have much experience using faceid so i'm afraid i cant help much on that. But there good resources on youtube that can help something like the faceid.

I am to also understand that comfyui has some safeguards now to make it harder to use faces, in a nefarious sort of deal using certain nodes.

All the lora files themselves will still go to the lora directory and you will be loading 2 loras. Usually on the model page for them has a tab for a high and a low. If there is no low. Then you will only load it into the high side and load no pairing lownoise.

The group on the left in the box for High noise is for the Loras, most will be set at a strength of 0.8 to 1.0, then the box for Low Noise will be the secondary Loras for Wan2.2 usually the same strength of 0.8 to 1.0 as well.

The powerlora loader is what you can use to make it easier to switch and toggle loras easier. Reconnect the high noise on the left to the model workflow, which will be the loras on the bottom in high and for the same for the low.

Connect the top model to the left side of the high noise box, then take the output of powerlora model back down to the blue tab reroute on the left of that then select and delete loras under the tab reroute. Repeat for the low as well.

If you are not using the powerlora. The loras in boxes are set in the workflow. If you use more loras you will have to attach them in the column for each side. The purple is in bypass node mode, select and hit CTRL+B to remove the bypass to enable them.

If you get garbled messed as your output you may have changed the Ksampler, they need to be set to what i have in the image/workflow. The only thing you should really be messing with in the ksampler is the steps which will give a crisper result, but will take longer, ( i dont go past 12 really) and you will make those changes to both ksamplers. Changing the start steps and end steps in the ksamplers can cause the garbled mess. They are confusing to me on the results they make if changed too much. I haven't messed with it much though.

You should only change the steps and not CFG. I would not recommend going higher then 12 steps due to time it takes to run. I would also not recommend really changing anything in the ksampler other than the steps.

Use the modelsamplingsd3 above the ksampler instead.

@HeavenSword It looks like it is the way you are prompting. The Wan model uses a more natural language when prompting.

Example for yours:

"The woman in the video takes her shirt off and is completely nude revealing her naked form, her breast and tits are visable. She is smiling at the viewer as she takes her shirt off. She takes her pants off after she reveals her breast to show her pussy. She changes her expression to a more content and sensual expression as she removes her pants while looking at the viewer. The scene is vivid, full of emotional expression, with smooth animation and excessive jiggle physics. The scene is high quality. The camera is steady."

You could also specify underwear color after removal and then a action after as well. Or the beast details after the removal prompt part. (You may also want to remove the jiggle part for your breast sizes)

Not all seed numbers will give the desired results, but it's more about prompting. I tested this prompt and it worked for the results you are looking for i think.

I had the nsfw lora on at 1.0 in both high and low noise. And the lightning speedup lora. (The NSFW could possibly need to be lowered in strength)

Recommend to also include the lora SmoothMix Animations XXX. (Linked in description) this lora can cause a bunch of movement at times, sometimes it needs to have a 0.3 strength in both high and low.

In addition. You want a specific scenery, you would build the scene first then the person. Like, "the scenery is an old tavern..." then describe the tavern details you would want, such as lighting, materials that make up the tavern, such as is it stone or wood walls, is there people there and so on.

There are limitations to the model itself based on training data it has in it, since GGUF is a smaller stripped model, things may look weird in detail if it wasn't really trained on the data or if the model has been merged to include the data, like a lora that is trained.

@HeavenSword most Lora's, your high noise one and the low noise one will have the same setting strength, make sure they are in the correct loaded sides to corresponding sides, wan 2.2 trained Lora's will usually have 2 loras that need to be downloaded and put in the lora location, if there is only a high noise, you will load it on the high side only at 1.0 (you can load wan 2.1 lora this way and it supports them usually, but not always) Most of the time you can set them to 1.0, but some recommend other strengths, such as the smoothanimation xxx recommends 0.3.

generally they need to be between 0.8 and up to 1.0.

Changing the modelsamplingsd3 to high values, such as 12 to even 20 (or higher even) will cause more movement but can cause bad results without extra steps in the ksampler.

And sometimes loading to many Loras will damage the final results too. It has various degrees, sometimes dropping strengths on them as you load more can fix those issues, but may also cause results to not take place such as a action will be minor or even not happen properly.

Good to hear that it works well for you.

I actually think I am going to put up a new workflow soon up in a week or so (maybe sooner?)

It has 3 prompt fields that are stitched together - making a 18 second clip with better transitions and flow. (Also takes more time obviously as well) But I have been testing it and it seems to be holding up well for about anything you put in it. It is a matter of the use is to flipping a switch and setting a number for that switch and clicking run.

The longest part will be loading all the loras into it for a person to use it. (Which i will try to link to downloads for in it)

It could be due to the version I made the workflow in (older now) try rightclick on the integer node, about 5 down should be a option "reload node". It may unlink though and will need reconnected.

Alternative is to delete the integer node itself and manually set the value, i just had it there to make changes a little easier.

Another option is to double click a empty space and type in "int" and select integer and manually recreate the node that way.