@MacSavers : For your static simulation, as say Biscuits, you have to nail the cloth on the character. For your dynamic simulation, I am a little bored by the end of the simulation where the cloth seems to be abnormally deformed. Have you this result at every time? I have set the gravity to 1.0 as you said. This is perhaps more simple for users.

I have not added a node mass at the level of the dynamic object generation. I will say something that will seem strange to you, but changing the mass of all the nodes of a dynamic object, does not change significantly the simulation. Remember the experience on the moon where a feather and a steel ball fell at the same speed. On Earth, the steel ball arrives on floor before the feather only because there is a air resistance. However, I have added a modification of the node mass using a selection. During the simulation, a node with a great mass will influence the simulation more that a node having a small mass. This solution allows to give some effects to the cloth or the hair. It is necessary to be carefull to not too increase this value under penalty of having abnormal results.

@MacSavers : could you publish some videos to show the result of your simulations. I have made many simulations with these values with all kind of clothes and hair and i never had the results you say have. I would like really see how behave the cloth.

@Biscuits : have you tried to modify the rigidity of the cloth or the hair to avoid to change the gravity?

I have made some modifications in the program about the gravity and the node masses. I have put the gravity to 10 for conforming it to the Earth gravity. In the computations, the Gravity value is multiplied by 4. I have added a node mass at the moment of the creation of a dynamics object. This value is set to 1.0 by default. I also have added a mass modification by vertices. This feature allows to use different masses for the nodes in the same cloth. This corresponds to the reality when a cloth is made with different matérials. I accelerate the computation of the elastic function which was very slow.

I see that my documentation is incomplete and I didn't made enough videos to show the functionnalities of VWD. I know that the program has to be improved but I feel that many functions are not well understood. My next goal is to make demo videos showing the capabilities of VWD and how to use it. You will have to listen my horrible accent. ;-))

@MacSavers : I asked me the question to set the Earth gravity in VWD. This valeur is 9.81 m/s2. In fact, I would have put this value to 10. This value is an acceleration. it depends of the time(s) and of the size(m). All the simulations are not made using the same gravity because it depends of the timestep used in the simulation. It depends also of the scale used for the simulation. Poser and Daz Studio use different scales to import their characters, if you want to be conform the the earth gravity, you have to use different gravities in these software. The value of 40 used in VWD generates simultations that give correct results compared to the reality. I can put this value to 10, but I will have to multiply this value to 4 to be conform to the reality.

I have sent a new demo version to the Renderosity's freestuff. This version allows to import dynamic actors having big meshes. These meshes generated errors in the old versions. The one solution was to reduce the rigidity distance to a value lower than 1.0 for the clothes and lower to 0.5 for the hair. The obtained results was often not realistic. It is now possible to keep this value that gives very good results and apply a minimun distance for the springs that allows to reduce the numbers of springs without change the behaviour of the cloth or the hair. This version corrects some bugs integrated in the last version concerning the Added rigidity by neighborhood.

I have received a message from Jenn who actually wants to send VWD. I have to explain how we can work to realize this action. It is me who have to be sufficiently clear. I thank her for her patience.

@estherau: You can find the last demo version at https://www.renderosity.com/mod/freestuff/?item_id=75748.

I will post a new version this week for the correction of the bug that I have found concerning the stiffening by vertices.

@estherau : I suppose you have made some tests with the demo version. The final version is not different of the demo version, there are only a few functions that were deleted. If the demo version works correctly and you can generate a personal code in the "About" tab, everything should work the same way. This test would be very interesting for all the Mac users.

@NolosQuinn : I just sent a message to Jenn Blake and Eric VanDycke asking them to tell me whether or not there is a possibility of selling VWD on their respective sites. I await the end of the next week and, if there is no response, I begin to sell the program myself.

Making some tests for creating a video, I realized that I had introduced a bug in the latest version of the program. This bug makes the stiffening by vertices ineffective. Early in the week I will make a new version that corrects this error. This version will also introduce a minimum size in the springs generation for simulating very complex objects easily.

@MacSavers : VWD is a simple program. In Windows, I can start the program and close it simply. The problem you have, comes from the emulator.

I added a min distance for the importation of dynamic elements. This allows to import clothes or hair that I could not import before without loosing any rigidity. I think it is a great progress for importing all kind of conforming clothes and hair, even if they are very complex and have a great quantity of vertices.

No reply!!!!!!!!!!!!!

@MacSavers : Excuse me, I don't understand what I can do for you. Under Windows, the program closes normally and I can't see what I can do else. If you have an idea about how I can help you, please tell it to me.

@fivecat, Thank you for this video. It is always a great pleasure to see simulations made with VWD.

No reply, no reply, no reply !!!! Generally, we are tired when we have too many replies. Personnaly, I am tired because I have no reply.

I should really like to say you that the selling process goes on, but to do that, I would need to have at least some informations and I have nothing. Sorry.

@moogal : Thank you for your comments and I can assure you that I am as frustrated as you to see the slowness about the distribution of VWD. It is true that I use a particular form of protection and I want to keep it. For now, I have not thought to a principle of storing simulation settings associated with a dress or hair. Ideally, a cloth that must be simulated with VWD would see his settings assigned automatically during importation. We can think about it.

@shedofjoy : Today I posted a new demo version. If you want to test VWD, it is important to download this version because it corrects all errors listed above. It is true that our phones have a power higher than the computers with whom I started working and which needed in a room of 500 m2. Personally, I think that manipulate Poser with my big fingers on a 5-inch screen will definitely surreal. ;-)). Still expect the next releases !!!

@Biscuits : Today, I also published several videos on YouTube. One of them simulates your sinfull dress which is a dress with a double layer. As I say in the video, I made a change to this dress because I removed a layer and I inserted a dual face material. I continue to work on the double layer original dress, but the simulation without any interpenetrations is difficult to obtain.

The current version works really properly. It will be improved and modified at the interface level. However, I think the most important is to rework now on documentation with the assistance of Ooseven who helps me for the translation. I even start to take oral English classes in order to make my videos in English. I think it is these videos that could best explain how works VWD. VWD is not just another cloth simulator, it's more a general simulator that could actually simulate things other than clothes or hair.

@moogal and @MacSavers : I am aware that there will be work to do in the interface. Colors may indeed have some significance. The interface recommended by MacSavers allows to know the actors on which the program has already worked. This interface seems perfectly effective and I will inspire of it at the time of the definition of this new interface. However, for now, I am more interested in substance than in form. There were a number of issues that were resolved in this thread and I think improving the program must go through there. I'll put on Renderosity a new version of VWD. This version corrects all errors that remained in the interface. I need to receive many feedbacks of all people who test the program to consider this version as a true 1.0 version.

@0oseven: I know I'm late with respect to the documentation and I beg you to forgive me. I had to juggle the time I could spend at my computer and the desire to see the program working properly. Now, the documentation will become my priority.

@Biscuits: I am sorry I can not give news because they are missing to me too. What I can say is that there are currently two places that are interested in the distribution of VWD (including Renderosity). The terms are not so easy to set up, but everything works in the right direction.

It took some time to answer because I have a little forced on my eye that reminded me to order. I had to reduce the time spend at the computer. However, i have worked on two animations, one of which caused me problems. I will publish them in the week. In fact, simulations and renderings are consumers of computer time, but not so much human time.

@MacSavers and @0oseven : This interface is really an interesting example.

When I started working on VWD, I thought that the interface should be as narrow as possible so as to take up less space on the Poser interface.

With a little experience, I realized that the size of the interface is not very important because once the program has started, there is no reason to act in Poser.

The narrowness of the interface required to compact the components that comprise it.

My priority now is to finish securing and optimizing the program.

I will launch myself into writing a new interface just after.

I have good news, because I think the solution is finally found for the distribution of VWD. I hope to say a little more in a few days.

@Biscuits and @fivecat : I think Fivecat is right, we should start a collect for her in the forum. Just a small technical explanation: the hair must be within V4 over half of the character. The hair want to get out of the character by searching the nearest vertices. I think all the hair out by the navel because it is this part of the mesh that penetrates most in character and were thus closest to the hair vertices. Thank you for this image, Biscuits.

@MacSavers : I think the two errors come from the same problem. I'm working on it and I think send quickly a correction for this error. I hope that working with MacOS will not generate a slowdown in the exchanges that could become blocking.

Thank you for all the images and videos published on the forum. Some of them show difficulties and others, encouraging results. In all cases, they help to advance the program.

@AmethystPendant : Your information regarding the correct operation of the program by VWD in the "C:VWD" directory is very important. I will ask all the people who work with Windows 10 and who have this error I / O 32 to test using this new directory. This is not an acceptable final solution, but it allows to continue to perform simulations. I got a Windows 10 today and I'll start doing tests with this system tomorrow. I hope this problem will be resolved quickly. As for integration into other software, you are right, the method of creating a DLL is a good method. However, the program can only function by using all the vertices selection functions and all springs generation methods. These functions could be called from the DLL, but in the host software, it would be necessary to create an interface that would resemble so much as the existing one. It is for this reason that I decided to create my interface fully with all its possibilities, even if it could be designed differently. The actual method allows to easily interface VWD with another software by using only few script functions. In all the cases, nothing is always fixed and the possibility you mention is very interessant.

@piersyf : In fact, I talked about finances more than money, though the two are related, unfortunately. I think the developers of Carrara who see their software that might escape them, could say the same. I think that all work deserves salary whatever the nature of that salary. By against, I did not want to only focus on VWD, it was a more comprehensive reflection. I do not want myself to lament. It's not my mindset.

I take this message to thank all the people who support my project.

@tomyee : You are right, actually, I had not thought of. It is true that there is no reason not to coincide an integrated version for Poser and a standalone version that could be integrated with other software. The integration into a software should not be too difficult to do because the communication simply asks importing Obj files and exporting cache file format readable by the host software, that's all. These functions must be present in the script functions of all the software in the market.

When we see the latest posts on the thread, it is clear that whether you are a developer, designer or user, we are all driven by finance. I can say with certainty that my main priority, when I started to work on VWD was not financial and it is now seen that the decisions depend more on finance than other reasons. Personally, I find this really regrettable. In this adventure, my greatest pleasure will be to see animations made with VWD.

I put a new version on the Renderosity's FreeStuff.

This release fixes a number of bugs.

The main achievement of this version is not to block the program in case of memory overflow. Currently, there is a small memory loss that I will try to correct.

This version also allows you to delete a dynamic object or a collision object. It also resets the simulation. Incidentally, I noticed a bug: If a simulation is complete and you want to completely redo the reset does not affect the button "Start Dynamic Simulation" which prevents the restart. it is already fixed for the next release. This works for a long simulation which can be seen at the outset that it is not good.