Dynamic Gi
VIArts
Posts: 1,499
Anyone with the dynamic martial arts gi for M4 or knowledge of dynamic cloth, SAVE ME!
I have the jacket set to collide with everything but a couple of hidden parts of a chair I want H4 to sit on. When I drape, the slack vof the belt keeps disappearing into the front.
Yes, I have it layered on top of the pants. And yes, I'm doing 30 frames from the T pose to the sitting pose. And YES, it's Fit To H4. AND NO, it won't be animated.
Any idea what's up?
EDIT: Oh yeah, I also draped the pants first.
Post edited by VIArts on
Comments
The belt is a particular hard piece to keep in position specially for a more advanced pose like sitting on a chair. I suggest setting the clothes to collide with a primitive and animate the primitive as a helper to keep the belt from sinking, other wise you might have to postwork it. In Michael 4 the gi conforms (although with pokethru) and on a sitting pose the belt might stay over the gi good enough so you can have a usable render for postwork in an image editor. Granted a little stiff as all conforming clothes are.
I wish DAZ and Optitex would develop more this plugin so we could have other options like a live simulation where one can just pull the belt up with the mouse and the physics engine corrects the simulation.
I haven't tried anything else yet, but... The conforming belt from the non-dynamic gi is just as annoying. Doesn't anyone think martial artist needs to sit down? :D
did you freeze the simulation on the pants first?
I find this helps
then do the next item, in this case belt, to collide with pants
after freezing that, under geometry add a smoothing modifier and set it to collide with pants.
That sounds interesting, got to try it myself next time I work with this item. Thanks Wendy.
One of the gotchas with Optitex dynamics is that the cloth will frequently fall through the collision object if its mesh resolution is too low. E.g. if the front part of the chair you're having problems with is straight, with edges at either end but none or only a few in the middle, your sash will fall between the chair front edges and sink into the mesh. It's these mesh edges that Optitex cloth collides with.
This will also bite you if you use a primitive helper as SimonWM suggested — don't use a minimum number of divisions, bump up the number a bit or the sash will fall through the primitive as well.
FWIW, I seem to get my best collision results if the mesh density of the cloth is roughly similar to the mesh density of the collision object. (Does anyone know if that's actually true, or have I just been lucky in selecting my test objects?)
Well, it's not falling through the chair, rather itr failils trhrough the top of the pants or the bottom of the jacket (i'm visually impaired)). I'm juyst now getting a cxhance to try again. So I'll let you know.i
And how do i know how many polys it is?
Up at the top of the Viewport is the dropdown list that shows which camera you're looking through. Beside it is another dropdown that lets you select how to view the objects in the scene. Usually this is at "Texture Shaded". Switch it to "Wire Shaded" and you'll see your scene with no textures applied, and the mesh visible. (It does show Diffuse Color, though, so most things, but not everything, will be white.)
When you drape dynamic cloth, what happens is the lines in the cloth colliding with the lines in the collision object. If a thin object like the sash falls between two lines in the chair (or other clothes), it'll just fall right through.
Don't forget to switch back to "Texture Shaded" — it won't affect the render if you don't, but it does almost always make it more difficult to see what you're doing when you continue manipulating the scene.
One final thought, go back and double-check the dynamics tab Collide With settings. I've been using the Optitex stuff since it first came out, and it's still a bit of a coin-toss whether I get those ticks in the right boxes first time. :red:
Yup, it just falls right through trhe jacket. Afnd it really isn't a separate mesh from the jacket. It has material groups, but no controllable nodes. Wendty's thing didn't work. Alil the right colliion boxes are checked too
Here's a couple before and after drape snips in Wire texture shaded mode.i
Now that I see your screenshots... drat, you only have the basic dynamics plugin. The full paid-for version has four sub-tabs, not two, and the Preferences one has a tickbox for "Self Intersection" which I think might solve your problem. As the name suggests, it makes the dynamic cloth collide with itself. That's annoying, I thought that was part of the basic plugin.
I tried it in the paid version, and the belt still falls through the jacket with Self Intersection ticked.
That's weird. Anyone else got any ideas? That was my last one.
If I read this correctly, the belt isn't dynamic, so it isn't affected by the dynamics parameters. Do the belt ends have bones, morphs, or handles for posing?
The belt's dynamic, all right (I don't think Optitex cloth can support part-dynamic part-conforming items like Poser does). I can get it to behave, but the slightest off-perfect setting makes it bounce about and take maybe several drape runs to settle down. I'm not sure what's happening here, though.
As noted above, a Invisible helper like a High Ploy Torus from a primitive or two set to END at the proper position of the final drape would HOLD the belt into place. Many of the dynamic sets now come with helpers as part of the package. You set the Item to Collide with the Helpers as well and if they have enough verts they HOLD the item where you want it.
I did a test. Didn't use any helper and the belt stay over the jacket. The jacket goes first on the Garment list and I see you have set this correctly. I made the jacket collide with the pants and M4 from the thighs up and the pants collide just with Michael 4 from the abdomen down. Do not make the pants collide with the jacket, just the jacket with the pants.
Also if you are using Hiro 4, being a Generation 4 figure you can make a static drape, might be easier than an animated drape. Animated drapes are necessary only if the clothes are rigged for generation 4 and are being used with Genesis 1 and 2 since the rig structure changed.
And here is Hiro 4 sitting. No problem with the belt. Now that I remember I think pretty much was the untied version of the jacket that had a bit of difficulty with the belt staying on top, the closed version which is the one you show should work without the need of primitive helpers..
I do not have the item so could not check. Helpers appear to not be needed if done your way. TY for the test.
Hmm... All I really did was start a new scene. I don't know what I did wrong last time.
It's a little pokey though.
Sometimes DAZ Studio just needs a swift kick in the re-boot, IF/WHEN things that SHOULD work don't. Close the bugger, and start it again. If that does not work do a PC Re-Boot. If the Stack pointers get a bit iffy (often the case) only a Re-Boot will clear them all from your OS. Then things should work properly again.
I think it has more to do wih the file because I'd been opening and closing DS and rebooting my PC.
If you save a file and it saves with bad data nothing is going to fix that file. That is the reason I always save at least 4 saves of all my work. If one save has a error in it it is very rare that all will. UNLESS the item in use (some older stuff) causes the error. Also Saving over the same file multi times in one Use of DAZ Studio can/has caused bad data on my system before. Not often but often enough I now will close DAZ Studio after a set of Saves, take a short break and then go back to my work again.
Most of these errors are not caused by DAZ Studio by the way, but by the OS doing things in the background. Even just getting a YOU have Updates waiting message for Windows at the wrong time can cause a file to write to disk bad. And those can only be stopped by dropping the NET fully. If you get a Auto Update for anything while working in DAZ Studio SAVE as fast as possible and EXIT DAZ until the Update and a re-boot sets your registry again. That is a fast way to lose all your work, a Auto Update.