List of improvements for dForce
IsaacNewton
Posts: 1,300
On the offchance that the devs of dForce are NOT all-knowing, it might be an idea to make a list of improvements the we, the users, would like to see in the next release.
I would start off with a couple of items:
1) A one click button to convert the simulation shape in the current frame to a morph.
2)The possibility to run a simulation on two objects at the same time, so that they can interact naturally together. eg a shirt and a skirt.
Please feel free to add to this list, perhaps the devs will see it eventually.
Comments
2) should already be possible using the layer setting. 1) could probably be handled already, with a script.
The proper way to makerequests is via a support ticket, though there's nothing wrong with discussing the ideas in the forum first.
Is there a web site with the sort of cloth & material variables and cofficients we should be using with dForce? I know they will be inaccurate and need adjusting according to model mesh density and topology but it would be nice to have some table of ballpark restraints to use, i.e. silk cloth is less stiff than denim. That is so completely vague though. Seems like a table of ratios or percentages for the dForce parameters is needed. Or is this sort of thing with 3D modeled cloth properties in 3D physics simulations 100% new to DAZ Studio?
The parameter names are mostly similar to those in Marvellous Designer, so you might see how values for that worked - but of course same name doesn't mean same behaviour.
Thanks, I'll look.
Richard, do you know of a tutorial which might explain how to achieve this (step 2)? When I try to follow one simulation with another, the first simulation is wiped. (Example: simulate two pieces of clothing on two different characters in the same scene.)
I have to admit that writing a script to do this is probably beyond my limited programing skills. Moreover, the idea of having to write a program (a script) to run a program seems a bit crazy when the original program could easily have the "script program" incorportated in it by the professional programmers.
You said at the same time - so that would be giving the top item a higher layer value (in the Surfaces pane). If you want to run sequentially you can select the item you simulated first and in the Parameters pane select Freeze Simulation.
There are many "little" functions that would be nice to have, and however easy this one may be (and not having tried to script it I don't know that it would be, it just looked possible on the face of it) they would rapidly swamp the developers. Where they are simple, and scriptable, then leaving them to the community is probably the most effective approach. Maybe, since we are in Product Suggestions, a PA will see this thread and write the script.
So, how do the developers decide which feature to work on out of the many which could be added; unless we, the clients, give them a list of our favourites? Or do they just work on the features they find interesting?
I imagine they weigh many lists - though it wouldn't usually be the developers as such actually making the decisions.
Again, how can they (whoever makes the decisions) weigh the wishes of clients if they never hear from the clients? Or doesn't it really matter much what the clients want?
I'm not aware of any suggestion that they don't want feedback - if you want to make a feature request do so. I was merely pointing out that even if you are right about your request being "easy" there are a lot of potentially useful, perhaps easy feature requests and they won't all be addressed.