There is a pdf user manual that comes with VWD (it's about 50 pages long), and is by default stored in the same folder as the plugin script itself (not the bridge, the actual VWD script folder).
Biscuits has done some excellent video tutorials (There are five or so; I downloaded them all) explaining how to use it. I only found one on Renderosity just now when I looked; the others might be on youtube.
Videotutorial VWDCloth&Hair STATIC HAIR SIM
Sickleyield also has one specifically for the DAZ bridge which I just found by searching for "vwd cloth and hair" on youtube...
The DAZ plugin does occasionally crash if you try to load in too much geometry in a simulation. My most recent crash was with the "Marionette Outfit" for G3F. the polygon count was over 2 million, I think. I have the Decimator plugin for Studio, though, so if an item fails because it is too big, I just decimate it, and then the sim works just fine. I have noticed problems too if you try loading new items into the scene and then refreshing the "Host List". I also always load the figures into the sim using their "base" resolution with "zero" subdivisions. That really helps with sim speed as well.
DS conforming items now load by default as parented probably to keep your scene tab less messy if you are loading a million props into the scene as well. I have to admit that generally I like it, but sometimes it does make it a pain. You can always just un-parent the items once they're conformed. They still work...
Usually if the plugin does crash, I get an error message in French, which doesn't help me much (not the French aspect - the text of the message itself...). It just tells me that there is an access violation and the script has stopped working. Not knowing what the access code violation number stands for, I have no idea how to fix it. Usually I just exit the plugin, stop it, re-open it, and then try to do different whatever it was that made the script crash the previous time.
When the plug-in loads a "cloth" or "hair" object for a sim, it creates an obj file of your original hair or cloth figure, and loads that into the scene. By default, it also makes your original source figure invisible, replacing it with an obj clone, which the script re-textures to match your original figure. With the newest update to Studio that came out, I get the standard "export" and "import" pop-up menu for each item, but I have discovered through trial and error that by leaving the settings the way they first appear in the pop-up, everything loads just fine without a glitch. You just have to click "ok" twice more than necessary... When the simulation is finished, you hit the "send pose to host" button. This applies the simulation data to the cloned object, not the original figure. If you apply an animated drape, it loads as a morph numbered to correspond to each frame, and then a different morph is keyframe dialed for each frame (automatically, thank goodness!)
If the script crashes after you try loading it the first time, you have to delete any cloth or hair clones that you tried to make last time, or the script won't run properly. I believe that hidden items don't show up in the "Host List" either, but that might just be bad memory.
I also systematically delete all of the memory files that the script saves for each simulation. Once the simulation is run and the pose is sent to the host, the clone object geometry is saved with the DAZ scene file, so you no longer need the simulation data. Supposedly, you can reload it and still tweak things by keeping the simulation files, but I haven't worked out how to do that yet, and the memory files kept by the sim are quite large...
The little yellow dot that shows up is in fact what you use to alter the sim. It only grabs one vertex, but it drags all the neighboring vertices around with it. Usually when I first drag, I yank it way further than I want it to move, and then let it go while the sim is running, and everything jumps back into place.
If you want me to find a thread, though, better tell me, because I'm not very good at randomly trolling forums. I found this thread through the weekly newsletter...
