@AmethystPendant: Thank you for your comment. What bothers me now is that feeling of hair crossing through. I made tests of hair generations of using both stiffening methods to generate larger strands, but the adjustment is difficult. Regarding your mistake, I am annoyed really because it's a mistake I never had and I can not seem to generate. Your test by putting a very high value in the sleep is interesting. It proves that the problem is not there. You speak of a disk K :, is it a network drive or an external drive? The amount of information flowing between Poser and VWD is very important and it is better to work with a fast disk. Do you look if you have all the rights to the directory where you installed the program? Could you tell me if you can import any item (eg V4) or if the program disallows any dialogue with Poser. If you can import a collision member, can you import the animation by pressing the "Record" button, once the imported item to see if the dialogue runs or stops. I ask you some work, it should solve the problem as quickly as possible.

@tomyee: The commercial party is not my strong point. A solution that integrates directly VWD into Poser would be much easier for me. I have just written to Nerd3d to see if, already, he would be interested in the program and if so, whether he would agree to integrate it into the version under development. By against, I can already see Carrara users to react because they would not have, in this case, VWD in their favorite program. The problem is not easy. Personally, I'd rather an independent program which remains flexible and integrated with different software. We just need to find a distribution method.

The important thing in this situation is that the program continues to evolve. The rest will come by itself. The fortuity does not exist.

I just released a new video. I did a test with realistic hair (Lucia hair by StudioArtVartanian). This hair give very good renderings results. The difficulty is to find the right parameters for the link of the hair strands. The result is good but is far from perfect. Tell me what you think of it.

Thank to Ooseven for his animation. The simulation of the skirt "Atardecer" is really perfect. I hope you're going to see his video.

I will publish a new version of Demo before the week-end. This version finally corrects the overruns memory errors that required to restart the program. For now, I have a little memory loss but it does not bother, I will try to correct. In addition to correcting some bugs, this new version will eliminate a collision actor or a dynamic player. It will also allow to reset the simulation.

@fivecat : Thank you thank you for great images and thank also to Biscuits for her beautiful long hair that will make much (virtual) ink.

@AmethystPendant and @NolosQuinn : I thought the problem was gone. Are you using the latest demo version? In all cases, it should be checked whether the file "StartVWD.py" does contain a line "Sleep 0.1" and not "Sleep 0.01" which corresponded to earlier versions. This means that my message loop between VWD and Poser was far too fast. If the value is 0.1, the problem remains. I know that some people have had this concern, as Wimvdb for example, but I thought it solved with a longer sleep ;-)). This error corresponds to a file that we are trying to achieve and that is still used by another application. Does this problem occurs only during the simulations also during the loading of the OBJ files? As VWD does not know the animation of the collision objects, he needs, at every frame, to request deformations to Poser. It seems that the problem is at that time. Could you make a screenshot at the time of the crash. Have you tried to record the animation before running the simulation by using the "Record" button in the "Collision Parameters" tab after being loaded. Does the problem appear at each simulation or some simulations work properly? I am particularly annoyed with that error, because I am unable to reproduce it. I tried the program on 5 machines and the problem has never occurred to me. Another idea, personally, I use a short directory name like : "C: VWD" to install the program. Could you make a test with this type of application path. I ask you some work, but I think this is the only solution for this problem. Thank you in advance.

My eye goes well, I started working on the error portion of memory size. In the next version, it will be possible to reconfigure a coat or hair after a memory error without leaving the program. It will also be possible to delete a collision member or a dynamic element. It will also be possible to reset a simulation.

The distribution of VWD has still not found a solution. This is not really a waste of time because the program still requires some corrections.

I saw that there were quite a few messages. Please excuse me, but I will put some time to respond. My operation has been well done, but there is a certain visual fatigue which will disappear with time. I will use those moments to work on the management principle for memory errors and how to reset the simulation or delete a dynamic object. I would answer the messages in a few days so as not to stay too long in front of the screen for now.

@Biscuits: Your long hair is really fantastic.

@MacSavers : I just do tests and, in fact, I said some silly things. The clothroom Poser does not remove the spaces, it uses the internal name of Poser, which generally does not contain spaces. This internal name may still contains spaces. What I said, is completely false. Initially, there have been several problems naming and the spaces appeared to be part of these problems. I think this problem is now solved. Going back to your import problem, I wonder if the problem is not in Unix (Mac version) which does not like spaces in file names. Have you been able to experiment without spaces? In VWD, I will modify the exchange file names to conform to the naming of Unix. This should solve all problems.

@MacSavers : I think I have this cloth and I'll make a try. Biscuits was right to make you this proposal because we have had, for a while, naming problems. What surprises me in your error, is precisely the space that should not be there. Let me explain, for animation, I use the Poser clothroom (for .dyn files). You can try, but the Poser clothroom removes spaces when it imports object names. To comply with this naming, the first thing I do, in terms of import, is to delete the spaces in file names. Looks like the Python program is not running correctly. I am going to experiment with this dress and I give you the answer tomorrow. Could you make a test with a cloth without spaces in its name to see if the problem persists.

@ErickL88 : The "Restore All" button does not work perfectly. Its purpose, as stated Fivecat, is to delete all the _VWD files from Poser and redisplay the original files. However, this redisplay only works for characters and not for props. I want to make this change, but I have not taken the time to do so. You say you got in trouble with the hair generation, could you tell me what seem you complicated in this generation? I think I already have simplified this generation using Windvb advice, but I feel that the interface is not perfect on this subject.

Thank you for all the renderings you put on the thread, it is a great pleasure for me to see these images.

In the latest version of the program, the documentation has not changed. I want to thank Ooseven that helps me to create a better documentation. In order to not work on the two versions in paralelle, which quickly would generate an unmanageable problem. We will coordinate us to work both on the integration of new functions and improved translation.

I have not yet incorporate all the changes recommended by Winvdb, I will list those that remain to be implemented.

The latest version still contains errors. By doing tests, I have found that the vertices selection by materials does not work with the hair. This is fixed.

I feel that the necessity to close and then reopen the program in case of error, is a serious problem of usability. I began to think about the fact you can delete the last action with CtrlZ and you can delete a simulation element. The first tests seem satisfactory. As regards the reconfiguration of functions, it is possible but in some time. In relation to this, I wondered if an editing window of .RIP files would not be a better option. Tell me what you think about that.

Bad news, especially for me .-( , I have to be operated on one eye Wednesday. Apart from the fact that there is no reason that things do not go well, I'll probably slower for the response to messages for some days.

@estherau and @MacSavers : I am aware that all artistic fields are areas where the Mac is very often used. At home and in my work, I work on Windows and Linux. I acknowledge that I do not know the compilation on Mac. But I have friends who see only through this system. I am pleased that my product interests a lot of people, but I currently have a priority to complete the program for Poser and Windows. I do not reject any possibility of extension and I'm sure that Mac compilation is one. To have tried virtual machines, I know that the results are often extremely disappointing. You, however, would it be possible to make a test ... to see.

I posted a new demo version. This version takes into account many of the suggestions made by Wimvdb. There's still some changes to which will come in future versions.

This version should resolve the naming error problem. It should also correct the errors workflow, especially for hair. Help bubbles are positioned above each element of the interface. Keyboard shortcuts "F" to follow, "L" for lasso can facilitate the use of the program.

Tell me what you think of these improvements.

@MacSavers : thank you for the revolution, whatever I am wary of the revolutions which, by definition, returns to their starting point ;-)). It is true that I have often been extremely disappointed with dress and hair animations even in quality productions. If I can bring my little stone, it is with pleasure. In the future, I would like to interface VWD in several software, among these, there are DAZ3D and Carrara. For cons, I'm sorry to disappoint you, but I can not write the program for Mac. I could write much of the interface, but the graphics library that I use does not work with Mac. If I ask you to work with Poser in Windows, I feel you are going to hate me. ;-)) again.

I'm ready to send a new demo version. This version will take into account numerous comments made by Wimvdb which will aim to make reliable the program and improve its workflow. I take this opportunity to renew to Wimdvb a huge thanks for its test work. This version will be on the Renderosity site, Wednesday. I continue to dialogue with Jenn about the distribution of VWD in Renderosity. Even though I'm really optimistic, it is necessary to find a way to combine the constraints.

I Thank Biscuits, Fivecat and Wimvdb for their renderings and their videos.

@Morkonan : There is indeed a hardware protection.

@Ooseven: Thank you for your comment. To defend Glitterati3D, I understand that when we were cheated once, we are suspicious. It's totally normal. I hope that the message below, will reassure her.

I personally have quite a lot of software that use hardware protections and I never had a problem.

Renderosity wants to be able at any time to distribute a product that a person has bought, automatically. This is quite normal and I think this solution ensures that your product will always be available whether you have a problem on your machine or you decide to use another machine. That is the goal of the 3 keys. I made a proposal to Jenn for VWD can be distributed by Renderosity. This causes that Renderosity can at any time generate the program for each user. I think the fact that it is Renderosity that manages the program should reassure those who are afraid of losing the use of the program.

About the program, I did not give much news. It's not because I do not do anything, the opposite. I make the corrections that will improve the reliability of the program and workflow management that was not necessarily obvious, especially for hair. I do this work thanks to the fabulous work done by Winvdb who participates in the private beta and has listed all bugs and workflow errors in program functions.

I want to thank a lot Biscuits who has made fabulous renderings that show the possibilities of the program. We must not forget that the program is not enough and that such renderings and models, in particular the hair, are related to her talent.

I want to distribute a new version of Demo next week. I agree on the fact that I fell again. I assure you that there are many changes and especially increased reliability. This version certainly will not contain all the corrections listed by Windvb, but this version will be directed bug fixes and workflow corrections. I hope by then I will have a positive response from Jenn and I would finally start the distribution of the final version.

In the next four days, I would not be able to respond to messages. Do not worry, I will reply as soon as I could.

I start to be confident about the distribution of the program by the Renderosity marketplace, despite of my method of protection.

Thank you for your patience.

VWD

@Glitterati3D : I do not want to maintain a controversy that does not happen to exist. I confess that your message did not make me so happy. I am truly sorry that your computer has been struck by lightning. I am really sorry that the company that sold you this software $ 200 refuses to give you a new key, despite your explanations. I just want to say that I have nothing to do. You are tarnishing my image in a forum while I never have sold you anything. You have not even mentioned the person or company that has deceived you. If you lay a charge, do it on the right person. Give the name of this company and stop to tarnish the image of those who have done nothing against you. Please.

I thank those who supported me. Of course, I continue. I do not remember it has happened something negative.

@Glitterati3D : I explained how I intended to work, each person will have bought three keys. If I make an update, I send the 3 keys. If the 3 keys are already used, I ask to the person, what key is to remove. This solution allows a person to have 3 computers that can use the program. This is the number of computers used by many people who works with computers. I personally do not see the connection with a theft. Of course, if you ask me every week to replace an old code, it might be me who would start having doubts. I'm sorry you thought I had a moment to think of stealing anyone. I am someone who creates and it is very rare that a creator is a thief.

I published three videos that show simulation results made with VWD.

I hope you do not think all like Glitterati3D because I stop everything immediately.

VWD

@PepBoy : Tell me if I'm wrong, but the programs you mention, uses wires for animating hair. For the renderings, it is necessary to use special shaders. I know a little "Fur and Hair" which is in 3D Studio Max. VWD never works on wired hair, but always on meshed hair. The animations made with hair correspond to a mesh deformation just like a cloth. He long ago, I wrote a script that converted Poser hair in 3dsmax with, however, some restrictions. Is it really that you need?

I really, really, thank, Winvdb who did a phenomenal job on the program. It gives me all the information about the bugs and the workflow errors in the interface. I also thank Ooseven which has offered to help me in the writing of documentation. I have no reply from Jenn, I would have tendeance to consider this as a refusal, even if the adage says "who says nothing consents". The choice is now made to work on improving the program into a more user-friendly program, the time to find a way for its distribution. I will publish regular demo versions including new features and changes.

@Vestmann : This is a topic that had already been asked.
I thought I would sell my product 50 Euros or 56 Dollars.
This price corresponds to that of a direct sale.
On Renderosity, I think, for the programs, the commission is 30 percent. This is 56 / 0.7 = 80 Dollars. I find this price too expensive, so on Renderosity, I'd sell my product 40 Euros or 44.5 Dollars. This is 44.5 / 0.7 = 63.5 Dollars.
To sum up, my product will be to:

• 56 Dollars on my site when created,
• 63.5 Dollars on Renderosity if Renderosity agrees to use my system for the protection and distribution.
  It's lots of explanations for a single price, but I wanted to clearly explain my approach.

I received an answer from Jenn Blake for the distribution of VWD. I feel that Renderosity uses a method with keys but without hardware key protection system. I spent a lot of time writing my protection system and I want to distribute my program by using it.
When I do an update, the generation of executables and sending them by mail to all buyers is done by pressing 2 buttons. I think I try to make the protection as transparent as possible for users.

Being almost ready for program distribution, but with no opportunity to do so now, I started to open a private beta test.

I asked, for the moment, to 4 people to test the final version by giving me ergonomic defaults and simply bugs that still exist, unfortunately.

The first results allow me to make corrections.

I will publish this weekend a new demo version. This version has some new features but is also the result of the first interface corrections related to the beta test.

I therefore look forward to a response from Jenn Blake, hoping Renderosity accepts the use of my method of protection.

I'm really sorry again for this against-time.

VWD

Hello,

I received today a first message from Jenn about the distribution of my program on the marketplace of Renderosity. Unfortunately, I do not know if it will be possible to do so because of my method of protection.

Tomorrow I'll post a message that will give more details on this subject.

The new demo version will be ready for the weekend. This should correct the naming problem you may have encountered, maybe. It will make a selection of vertices using the materials and will add a new possibility of self-collision. Some keyboard shortcuts have been added to facilitate the use of the program.

This version will probably be the one that will be the first official final version, even if there will be further changes to come.

I will definitely work on the generation of a site that will distribute it.

Sorry to all those against time.

VWD