Part of the time needed to export a mesh from Studio or Carrara is welding duplicate vertices. For hair, it takes a very long time because most of the edges have to be inspected. Maybe I could add the option to skip that part?

I'm finishing my current project and I'll soon have more time to work on this subject. Just to be sure, will this script be called from VWD? (Meaning they will have to go through the python translator?). Will they be available for Carrara and Poser?

Hi MikeO,

Sorry I didin't see your post before. Could you send me your .Car file so I can have a look? Is the "merge vertices" checked before sending the subdivided mesh to VWD ? It may take time and it doesn't look necessary looking at your mesh. Do you use the import static pose in VWD or do you import an animation? The process is slightly different in the Carrara bridge.

It looks like the model imported from VWD has creased edges (I don't know why and I would like to investigate). I think you can solve the lumps by opening the VWD mesh in the vertex editor, selecting everything and applying the command "smooth edges".

I keep a computer with 4.8 installed just for that purpose. As long as this computer is working and studio doesn't go in a version incompatible with it, it should be all right.

grinch2901 posted at 10:11AM Mon, 27 November 2017 - #4318641

Just weighing in to say I risked installing 4.10 and ran VWD using the new script in this thread and it worked perfectly. OBJ export seemed to take a little longer than typical but ut was a dense mesh so might just be that. simulation ran perfectly and transfer back to studio was flawless, all materials there and textured properly. I'm very happy, thanks for the effort to let us stay current with studio and still use VWD!

Yes, I think it would take longer. I've programmed it in script and not C++ and it shows. Remember, it was just a workaround while Daz move the bug correction from beta to production and it didn't seem worthwhile to invest in plugin development.

markht posted at 9:53AM Fri, 24 November 2017 - #4318589

philemot posted at 1:50PM Thu, 23 November 2017 - #4318586

By chance, would the material in the genitalia have the same name that materials in the figure. If so, try to rename them, it might get you through.

The Genesis 1 and 2 female genitalia surfaces have the same name as the main figure, because they do not need a special texture. You just apply the skin materials for the main character to the genitalia. With Genesis 3 they changed the genitalia to require different material and it has different surface names.

Just removing the genitalia to run VWD seems like a better work around than renaming the surface.

Didn't dare suggesting it

Glad you're not blocked

I didn't change anything for collision objects because I thought the export bug didn't impact collision. Maybe I was wrong.

By chance, would the material in the genitalia have the same name that materials in the figure. If so, try to rename them, it might get you through.

I've created a VWDPython script exclusively for Studio 4.10

It can be downloaded here. Just download in your computer and place near the regular VWDPython.dse file. Click on the new file (VWDPython4-10) instead of VWDPython

Tests are good for me, but I'd rather have other test as well. Could anyone try this script, it would be very helpful.

Custom OBJ exporter is written. Tests are starting today. If all goes right, I'll release a quick fix specifically for 4.10 to allow users to use VWD in 4.10 awaiting repairs from DAZ. It's not a perfect solution because this custom exporter will have to be reviewed a every new Studio release for changes in the internal model. I'd rather use Daz exporter when it works. This export problem is also an issue for other uses of Studio (export to blender or octane for instance) and I think Daz will eventually solve it. Stay tuned for more news

After trying everything I could think of (and even other), I've been unable to go around this bug. There are also no news from Daz for the ticket submitted by other Daz users. So I decided to tackle the issue and write my own OBJ exporter. I hope to give you some more news soon.

I now have the answer for the crash. The second export is defective. It exports facets referencing vertices not exported. I'm not surprised the OBJ importer in VWD crashes as it's not supposed to happen. Any script developper can reproduce the error. Using silent OBJ export and import examples from the Daz doc center, You can try to export a mesh, import it back and export again the imported mesh, all in a sequence in the same script.

If you think you can help, I've no qualm sending you the sources. I just have to warn you that some of the code is dynamically generated by translating Python into javascript and executed afterwards, so debugging is not always simple. But the import and export code are in the script (and they are mostly cut and paste from Daz examples).

zanth77 posted at 11:52AM Tue, 07 November 2017 - #4317486

Hi I noticed that the bridge no longer maintains surfaces when importing cloth to VWD from Daz, after the upgrade from Daz Studio 4.9 to 4.10. All the surface zones get combine into a single default zone which makes it difficult to use when you have cloth with differing surface settings/textures per zone.

I can work around the problem because I have an old Beta version of Daz but was curious if it's something simple to fix in the bridge? Thanks!

I'm working on it, but it's not easy. There is a dedicated thread on the subject in this forum.

Thank you for the support. I must say it's a hard nut to crack. To be more precise, when you import an obj file, you have to stop the script before you can re-export it. Studio does something when the script is stopped that validate the imported mesh. I haven't found how to reproduce it (and I tried a lot of thing). I'm constrained because the script acts within commands from VWD and it's not easy to change global behaviour.

I think I owe you a detailed explanation of the error: When creating a cloth or hair object, VWD export as an obj file the mesh selected. This export has a "Weld seams" option, import it back to create the cloth mesh then export it again. The studio bridge add a further export import after merging duplicate vertices. After the first import, all further exports lack materials, which is new to 4.10 version. I've tried everything to force that export but nothing do. I also tried to remove the additional export-import phase, but then VWD crashes. I'll keep on trying but, if it fails, I have two options. Wait for Daz to correct the bugs (there is a ticket open) or write a new obj exporter (not very difficult, I had to do that for Carrara). whatever the solution is, I'm afraid it will take some time. I'm really sorry about that.

I think it's related. After forcing one property, i can have at least one material correct instead of one named "default". I've checked all other parameters exposed and there are identical. It doesn't mean anything because a new parameter introduced in 4.9 is not exposed either. The export through the export menu must set this value and it's why surfaces are preserved.

I continue to look into it.