Virtual World Dynamics F.A.Q (Last Updated: 2024 Nov 05 5:09 pm)
@Surody: This error message appears only when you use very complex hair (or clothes)? How many seconds before the message appears?
@grinch2901: Excuse me to reply so late. My current problem is that I need to work on other projects because the sales of VWD are almost ZERO since the starting of DForce. My question concerns three problems :
Currently, I would like to generate some free clothes which could be used as tests. I just want to ask you if some of you would accept to make these tests.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
VirtualWorldDynamics posted at 3:15PM Sun, 03 December 2017 - #4319238
@Surody: This error message appears only when you use very complex hair (or clothes)? How many seconds before the message appears?
@grinch2901: Excuse me to reply so late. My current problem is that I need to work on other projects because the sales of VWD are almost ZERO since the starting of DForce. My question concerns three problems :
- Currently, I cannot work so much on a project without any incomes (even if, in some months, I will be probably able to work for nothing... I hope).
- I want to define one or two meshing methods which would allow to define repeatable behaviors. (I worked a lot on meshes generation in the past).
- I could make some cheap clothes with a very precise meshing with their .RIP files. This could be a method to continue the project.
Currently, I would like to generate some free clothes which could be used as tests. I just want to ask you if some of you would accept to make these tests.
I happens inbetween creating the mesh and adding the shaders. The error appears shortly before the shaders are getting added at the end.
[grinch2901]
Well I've done many more sims since I wrote that and I will say that it really doesn't seem slower at all. Just that one item, which was pretty dense mesh so probably just because of that. It does behave a little differently than before. Specifically before if you changed the materials in the original clothing item, it changed them on the VWD item too. It seems it doesn't now, which is not a big deal. It was also the case that the VWD item would lost materials when you saved the scene and reloaded it, I don't think it does anymore. Essentially it seems the VWD and the original item are not really coupled as tightly as they were, and personally I think that's probably better (a matter of opinion, others may disagree).
Bottom line, your quick and dirty workaround seems to work like a charm. I see no reason why it can't just stay the official method moving forward if you are so inclined. Nice work and thanks for getting it done so quickly.
Wanted to correct something I said here. The workaround is via a script that replaces the bridge as downloaded from the store. In the instances where materials weren't coming across as expected I was actually using the old bridge script, the one 4.10 broke. When I've used the proper one philemot provided in this thread, it works perfectly, all materials work fine. So it was operator error on my part. Sorry for any confusion I caused.
A little more feedback, I've been working now in Daz Studio 4.10 with both VWD and dForce. I was hoping that for quick and easy items like a simple skirt I could just dForce it and save the complex items for VWD. What I've found is that either I am incompetent at dForce or it's pretty unstable. Basically 90% of the items I try to use dForce on either explode during sim or cause the sim to crash and you have to restart Studio if you want to try dForce again. I've really had very little success with it. On the other hand, all these same garments came right into VWD and worked perfectly well.
I do mostly still render so one thing I like to do is with a dress is select the verts above the waist and make them fixed, simulating only the skirt. That's dead simple in VWD even if the materials aren't set up that way because you can select verts directly. In dForce to keep an item out of the sim I have tried to select the surface (if there is one) and make it's sim contribution strength zero. Maybe that's why things explode so often. But the alternative is to sim the whole garment and then I run into making it hold share and the like by playing around with settings.
Like I said with VWD my favorite tricks are to import with vertices extension so the small bits and peices don't fall off, then make the upper body verts fixed, put a little inflate on the skirt, also add some stiffness to the skirt and then sim it. Then when I sim I can just tweak gravity an inflation until I get the skirt to drape the way I like. dForce is going to require a completely different workflow but since it crashes all the time I haven't really found a good one for me yet. So for the time being I am sticking with VWD, with ony the occasional experiment in dForce.
It looks like Daz has fixed the OBJ export issue with it's latest release Ver. 4.10.0.123 (12/10/17) Because I was having texture issues in VWD with Daz 4.10.0.107 Ver. But now it seems to be working again. I'm going to test it further. If I notice any thing I'll report it here.
I'm using VWD Ver. V1.1.522.3630 and Daz Studio Bridge 2 (I'm not sure if I'm using the latest VWD version) I sent an email to Gerald to verify but have not heard back. And I can't download it from my Rendo library because I was one of the first ones to buy it from him directly before it was released officially.
Glad to see it's working. I decided to move over to Daz from Poser recently. And when I fired up VWD in Daz for the first time recently I was immediately having texture issues with hair (Daz "Spring Hair" and "PH Timeless" in particular. Although I do get insufficient memory when trying to use OOT hair or something heavy on polys).
I'm relieved it's seems to be working now, because I am seriously relying on VWD for all my animation projects.
Like one poster said, Gerald and Phill should add A Pay Pal Donation link In their videos or something secure like that somewhere here or elsewhere, so we can tip you guys, (with lunch at least.) Because we know you are working hard on these programs and are a great help to us.
Excuse me if I take many many time to reply to your questions.
The VWD Ver. V1.1.522.3630 is the latest version. The GPU version begins to work but it is not stable enough to start an update. I resolved many problems on this version even if the Self-collision don't work at all. Certainly a very simple error.
For the Pay Pal Donation link, perhaps it is a good idea. I will send a mail to Philippe to ask him. This will help us to use more time to work on the programs.
I use a bit of time to work on a cloth generation. Sorry for going so slowly. I want to give you the geometries with the clothes. This would allow you to generate the mesh with another size. When I will be ready, I will post a video tutorial to show the method. (Using a free mesher).
Currently, I am in relocation. This takes also a lot of time. I will be more productive from the beginning of the new year. Sorry.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
I'd like to add my thanks to Philemot for the fix, which got VWD working again for me in 4.10.0.107. It's good to hear that MrFiddles22 has had success with VWD in 4.10.0.123 - Any others had the same? Now 4.10.0.123 is on general release, is the advice to remove the fix, or leave it in place? I'd be happy to make a small donation to support Philemot and/or Gérald if there was an opportunity through paypal.
I am using Daz Studio 4.10.0.123 (general release, not a beta) and VWD works like a champ in it using the original bridge script. I kept the workaround script that Philemot provided as a backup since .. why not? But I am using the "official" bridge and it works perfectly.
As a side note, the release of dForce has actually made me use VWD more. In part because I wanted to test the workaround script, in part because I wanted to compare to dForce (VWD is better) and in part because my interest was just rejuvenated. Go figure.
I quote myself: "I get really often "file of the object doesn't exist" error and the VWD file afterwards is useless because of that. Especially with more complex hair it seems to appear."
Forget about that. It seemed to be a problem with that alternative solution. I upgraded to the newest public build of Daz and use VWD without it and now it works. But I would like to ask if the memory stash can be increased? 1200MB seems not that much for very complex mesh.
@Surody: This size corresponds to the max size for the memory. I don't why it is not possible to increase this value. If I increase this size, the message will come from Windows. This would not allow to keep the hand. The memory consuming comes from the springs generation. The GPU version will perhaps allow to generate more springs. In all cases, the best solution will be to compile the program in 64 bits. This should be possible with a new version of the library. This certainly will ask a lot of tests. My current priority is the generate a Usable GPU version. I know I ask you to be patient. I am sorry to that but sometimes, all is not so simple.
The new version of Daz Studio 4.10.0.123 seems to work perfectly. A great news.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
@Surody: Thank you for your support. I will send a mail to Philippe to ask him how to proceed.
Someone asked me to make a video with the head at 90°. I just made a tutorial to explain a method. Perhaps, not the only one. This method don't work correctly for a classic hair simulation.
Sorry the tutorial has no sound because I lost my microphone during my relocation. I will redo this tutorial in some days. Here is the link : https://youtu.be/U0OSIV-gRT8
This video allows to see the speed of the simulation with the GPU processing. It progresses everyday.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
Sorry for the video with sound. As I'm moving out, I really have no time to work on the program and the tutorials.
The new year will let me more time and I will restart the project.
I wish a very good Christmas day and a very good new year to everyone.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
MrFiddles22 posted at 2:28PM Sat, 30 December 2017 - #4319837
Update: I am experiencing a crash when I close VWD. Daz crashes after I click the dialog box "Yes, Do you want close VWD" Then I have to restart Daz.
Use the script to STOP VWD first, this usually prevents it.
But Software crashes, save often.
Hello Writers_Block,
In fact, I just restarted the VWD development since this night. I will open a new thread to explain this.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
@Surody: I will create a new thread in the VWD forum tomorrow. There are still so many things to do.
____________________________________________
Follow me on Twitter : @VWDynamics
Watch demo videos on Youtube
Writers_Block posted at 3:45PM Mon, 12 February 2018 - #4321243
MrFiddles22 posted at 2:28PM Sat, 30 December 2017 - #4319837
Update: I am experiencing a crash when I close VWD. Daz crashes after I click the dialog box "Yes, Do you want close VWD" Then I have to restart Daz.
Use the script to STOP VWD first, this usually prevents it.
But Software crashes, save often.
I noticed I am missing that button. I will have to try installing it again...Thanks
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I get really often "file of the object doesn't exist" error and the VWD file afterwards is useless because of that. Especially with more complex hair it seems to appear.