Seems like VWD works fine with the release version of Daz until you exit. As soon as VWD closes, Daz Studio crashes. Anyone else experiencing this?

To work around it, you can save your scene in Daz before the crash occurs. Tedious but it helps.

Same problem. Tried the workaround, but in my case I lose all surface materials of the VWD’d object during the save/reload process. I have opened a case with DAZ. Anybody else have a better idea?

Sorry, didn't give the full workaround. Surface materials is a separate issue that existed with 4.10, so I do it by habit. Here's the full workaround to help with both:

1. Edit > Duplicate > Duplicate Node (the duplicate never has surface material issues).
2. Save Scene.
3. Close VWD. Daz crashes. Reopen Daz and delete the original VWD object (which lacks materials). Your dupe should be fine.

I agree it seems like a Daz issue since it's dying in QTScript.dll. If I had access to Phil's bridge source code, I might be able to find some way to exit differently to avoid the crash. Or I think the new release of VWD is going to avoid using the bridge, which may also resolve the issue.

I made a quick test with Dazstudio 4.11.0.383 and VWD: 2.1.820.5830 without any problem

Excellent. In reading a few posts, it appears your newer version of VWD might be available in Sept.

I suppose I'll use the workarounds till then.

Hello zanth77 and knigge64,

Thanks to Smaker1 for the tests. The material issue comes from DS. The problem don't exist if you affect manually a material to the VWD item. Now, in the Utilities, there is a way to restore the Daz materials on one click. Not perfect but useful.

zanth77 posted at 11:58PM Tue, 18 June 2019 - #4353349

Sorry, didn't give the full workaround. Surface materials is a separate issue that existed with 4.10, so I do it by habit. Here's the full workaround to help with both:

1. Edit > Duplicate > Duplicate Node (the duplicate never has surface material issues).
2. Save Scene.
3. Close VWD. Daz crashes. Reopen Daz and delete the original VWD object (which lacks materials). Your dupe should be fine.

I agree it seems like a Daz issue since it's dying in QTScript.dll. If I had access to Phil's bridge source code, I might be able to find some way to exit differently to avoid the crash. Or I think the new release of VWD is going to avoid using the bridge, which may also resolve the issue.

Yup, was having the same issue. You are a lifesaver... thank you....

zanth77 posted at 12:00AM Wed, 19 June 2019 - #4353370

Excellent. In reading a few posts, it appears your newer version of VWD might be available in Sept.

I suppose I'll use the workarounds till then.

Hey, so do you save it seconds before VWD finishes???

VirtualWorldDynamics posted at 4:57AM Wed, 19 June 2019 - #4353387

Hello zanth77 and knigge64,

Thanks to Smaker1 for the tests. The material issue comes from DS. The problem don't exist if you affect manually a material to the VWD item. Now, in the Utilities, there is a way to restore the Daz materials on one click. Not perfect but useful.

I must be doing something wrong. I did everything above from edit to finish, but all that happens is a static hair, no animation, and I see only the duplicate figure with no clothes on...???

Here is a screenshot of the issue!

Sepiasiren posted at 7:15AM Wed, 19 June 2019 - #4353437

zanth77 posted at 12:00AM Wed, 19 June 2019 - #4353370

Excellent. In reading a few posts, it appears your newer version of VWD might be available in Sept.

I suppose I'll use the workarounds till then.

Hey, so do you save it seconds before VWD finishes???

I let VWD finish entirely then 'send pose to host' in vwd, click Scene Viewer to minimize VWD to the right of my screen so I can see daz, Duplicate the VWD object (which is usually selected), Save Scene, close VWD (and let Daz crash), then reopen Daz.

I haven't done an animation since moving to 4.11 but I'd imagine it'd be the same, using 'send animation to host' in place of 'send pose to host'.

Your screen shot looks strange. It seems like you duplicated the entire figure. I'd never do that. The figure is usually just the collision object. I only duplicate the vwd object (usually cloth or hair).

zanth77 posted at 1:40PM Wed, 19 June 2019 - #4353457

Sepiasiren posted at 7:15AM Wed, 19 June 2019 - #4353437

zanth77 posted at 12:00AM Wed, 19 June 2019 - #4353370

Excellent. In reading a few posts, it appears your newer version of VWD might be available in Sept.

I suppose I'll use the workarounds till then.

Hey, so do you save it seconds before VWD finishes???

I let VWD finish entirely then 'send pose to host' in vwd, click Scene Viewer to minimize VWD to the right of my screen so I can see daz, Duplicate the VWD object (which is usually selected), Save Scene, close VWD (and let Daz crash), then reopen Daz.

I haven't done an animation since moving to 4.11 but I'd imagine it'd be the same, using 'send animation to host' in place of 'send pose to host'.

Your screenshot looks strange. It seems like you duplicated the entire figure. I'd never do that. The figure is usually just the collision object. I only duplicate the vwd object (usually cloth or hair).

Oh okay, I didn't know you had to click on just the object, I thought you were duplicating the entire scene.

I find that when I hit "send animation to host" it won't let me save until the animation is done, which of course when it is done, it crashes.

Hello,

Just a question, do you use the bridge or the direct transfer? I use the program a lot of times every days and Daz never crashes. In the current version, the animation is transfered to DS immediatly and can be played without waiting.

By 'direct transfer' do you mean VWD version 2? As far as I'm aware, the daz bridge is the only option for the VWD currently available on renderosity.

BTW if you're looking for more folks to help test version 2, I'd be happy to do so (as long as it doesn't overlay version 1 which I currently use quite a bit).

Just tried this and not able to get the animation into Daz without Daz crashing. How are you saving the scene before Daz crashes? When I press "send animation to host" (after simulation has completed), I am unable to save the scene in Daz. Daz is busy receiving the simulation from VWD and I am unable to give Daz any commands. I have no way of saving the scene before Daz crashes. I can only save before, but the simulation has not been sent to Daz.

Not sure how you are saving before Daz crashes after sending simulation to Daz from VWD.

I think I'm misunderstanding something?

Note: using Dazstudio 4.11.0.383

Hi Asiel, My workaround was only for 'send pose to host' (i.e., for static renders). I hadn't tested animations. I just tested animation, and you're correct. The release version of VWD (1.1) does indeed crash as soon as you attempt to send the animation, therefore not allowing a save.

That's too bad since I use animation from time to time. The good news is that the 'current version' of VWD seems to fix these problems as mentioned above. Curious to know how to get a pre-release version of it (since I assume it's not released quite yet).

VirtualWorldDynamics posted at 7:28PM Wed, 19 June 2019 - #4353516

Hello,

Just a question, do you use the bridge or the direct transfer? I use the program a lot of times every days and Daz never crashes. In the current version, the animation is transfered to DS immediatly and can be played without waiting.

I use the DAZ bridge--not sure how to use WVD without the bridge...

zanth77 posted at 7:30PM Wed, 19 June 2019 - #4353522

By 'direct transfer' do you mean VWD version 2? As far as I'm aware, the daz bridge is the only option for the VWD currently available on renderosity.

BTW if you're looking for more folks to help test version 2, I'd be happy to do so (as long as it doesn't overlay version 1 which I currently use quite a bit).

Indeed, I have no way to use WVD or DAZ without the bridge.

zanth77 posted at 7:30PM Wed, 19 June 2019 - #4353533

Hi Asiel, My workaround was only for 'send pose to host' (i.e., for static renders). I hadn't tested animations. I just tested animation, and you're correct. The release version of VWD (1.1) does indeed crash as soon as you attempt to send the animation, therefore not allowing a save.

That's too bad since I use animation from time to time. The good news is that the 'current version' of VWD seems to fix these problems as mentioned above. Curious to know how to get a pre-release version of it (since I assume it's not released quite yet).

IKR -- I dug up a Daz 4.9 version to use but it is kinda buggy as well...

Thanks all. Was really hoping to get animations. I need to find an older version of Daz.

Asiel posted at 10:05PM Wed, 19 June 2019 - #4353537

Thanks all. Was really hoping to get animations. I need to find an older version of Daz.

I had one in my downloads--it is hard to find one online after a newer version comes out.

FYI,

This update surprise is a bummer for all of us and we are actively formulating a good fallback solution to this DS 4.11 issue as we look for the 'correct' technical solutions mentioned above. We hope the delay isn't causing any notable problems for any of you (let us know if so! support@virtualworlddynamics.net). We'll let you know when we have more information and the pest possible solution.

VWD_dan

VWD_dan posted at 3:19AM Sat, 22 June 2019 - #4353788

FYI,

This update surprise is a bummer for all of us and we are actively formulating a good fallback solution to this DS 4.11 issue as we look for the 'correct' technical solutions mentioned above. We hope the delay isn't causing any notable problems for any of you (let us know if so! support@virtualworlddynamics.net). We'll let you know when we have more information and the pest possible solution.

VWD_dan

You rawk dan, thank you looking forward to updates! :-)

Hello,

I do all what is possible to generate a full beta version in the weekend.

  Gérald

Wow, thank you!

Hey Gérald, I finally got to test the new pre-release version with a new install of DS4.11 on a brand new drive and like Smaker1, I am not seeing any issues on Windows7_x64.

I noticed you have a path setup for Gmsh. Are you sending to Gmsh and back for the new remeshing now, and is it automatic or is there input parameters. I haven't set it up yet, so I haven't tried it yet.

Also, since VWD is still x86, do I need to link to a x86 Gmsh, or will a native x64 Gmsh on my x64 PC work? Which one should I install and link to?

EDIT: I forgot that I had one more question; Did you separate VWD for DS and Poser -- This seems to be only for DS, but I am sure I can use the previous Poser script setup which will link to the new VWD version. I am just wondering about it auto-bridging to Poser as the previous version did.

Hello DaremoK3,

It is well if the beta version works fine now.

You can use the GMSH version that you want. Personally, I use a 64 bits version. I didn't use the volumic meshing since a while. Tell me if you have any issue.

The new version works for Poser and Daz Studio. These are 2 different dialogs depending on the host you use.

Hi all,

Kind of a 'bump' for this thread:

If you have a problem with your VWD version and DAZ Studio 4.11 w/ Philemot's great DS/VWD bridge product, we're offering a time-limited V2.x beta version that runs through November 30, and works with DAZ Studio 4.11 natively. While it is a beta and missing updated Documentation, etc. it does everything V1 did and has our new features to play with (and test) as well: Wind, body dynamics, hair and cloth assistants and GPU calculation.

If you wish to 'play' or at least get VWD working in your DAZ Studio 4.11 environment, just send us an email at 'support@virtualworlddynamics.net' or PM us here at Renderosity and we'll get you access to this full V2.x version that runs through November 2019. This date was picked based on our expectation to have a complete V2.x version release available here at Renderosity in September 2019.

Because this is not a full program update, nor is it a traditional freebie, it doesn't meet the criteria for a customer broadcast letter at Renderosity, so they recommended that we notify you all though these forums. Please pass on the word!

cheers,

VWD_dan