Mon, Jun 3, 5:50 AM CDT

Welcome to the Virtual World Dynamics Forum

Virtual World Dynamics F.A.Q (Last Updated: 2024 Jun 02 9:59 am)




Subject: VWD is saying my cloth item "does not exist"


MikeO ( ) posted Mon, 24 June 2019 at 7:09 PM · edited Fri, 24 May 2024 at 3:17 PM

Hello again!

I successfully selected my figure as the Collision item. But when I select the item for the Cloth, not only do I get a pop-up telling me the item "does not exist", it adds a ".obj" to the file name, in the pop-up window message, where there is no such designation for my item.

I've been using VWD for a number of years and this is the first time this has happened.

Can anyone provide insight?

These are my own created models.

Thanks!


VirtualWorldDynamics ( ) posted Tue, 25 June 2019 at 8:08 AM

Hello MikeO,

This message appears when the time-out is reached during the importation. Generally, this message appears when the actor is hidden in the scene or if the actor is enormous and takes too much time to import. Please, tell me if this helps you to resolve your problem.

____________________________________________

Follow me on Twitter : @VWDynamics

Watch demo videos on Youtube


zanth77 ( ) posted Tue, 25 June 2019 at 9:34 AM

Often you can fix it in Daz by selecting the item > parameters > mesh resolution > set to Base. Subdivision greatly increases an object's geometry so it can time out before VWD can import it. Returning to Base resolution helps avoid this timeout.


MikeO ( ) posted Tue, 25 June 2019 at 3:56 PM

VirtualWorldDynamics posted at 3:49PM Tue, 25 June 2019 - #4354635

Hello MikeO,

This message appears when the time-out is reached during the importation. Generally, this message appears when the actor is hidden in the scene or if the actor is enormous and takes too much time to import. Please, tell me if this helps you to resolve your problem.

Thanks for the reply!

Hmm... My cloth item is about 2000 polygons and it is not hidden. I tried to import a new instance but the problem persists.

I just cannot find a reason for this item to be so troublesome!

I am using version 1.1.522.3630 with the Carrara Bridge.


MikeO ( ) posted Tue, 25 June 2019 at 3:59 PM

zanth77 posted at 3:57PM Tue, 25 June 2019 - #4354655

Often you can fix it in Daz by selecting the item > parameters > mesh resolution > set to Base. Subdivision greatly increases an object's geometry so it can time out before VWD can import it. Returning to Base resolution helps avoid this timeout.

Thanks for your suggestions!

I am using Carrara, but I do not have the item subdivided. It's about 2000 polygons.


VWD_dan ( ) posted Tue, 25 June 2019 at 5:20 PM

Could this be related to the name of the node/item? Maybe spaces, '&', or some other 'special' character(s) are causing an internal conflict?

Maybe rename your item and/or re-import it? (guessing here)

VWD_dan


VWD website: https://www.virtualworlddynamics.net  -  VWD support: support@virtualworlddynamics.net

Current VWD Versions:   Release: V1.1.522.3630 – 2017/05/18 11:52,    Beta: V2.2.908.6404 beta – 2019/11/24 9:34 (exp 2019/12/28)

Qualifier: Yes, I'm helping Gérald with VWD, No, I'm not yet an expert on its use!


MikeO ( ) posted Tue, 25 June 2019 at 7:50 PM

VWD_dan posted at 6:55PM Tue, 25 June 2019 - #4354748

Could this be related to the name of the node/item? Maybe spaces, '&', or some other 'special' character(s) are causing an internal conflict?

Maybe rename your item and/or re-import it? (guessing here)

VWD_dan

I think I found the problem and it is rather mundane! A "d'oh!" moment!

Turns out when I opened VWD I had the "weld duplicate vertices" box checked. Once I unticked that option, I was able to advance to the next step.

I knew it would be something simple, but I just couldn't put my finger on it! 😄

Thanks for the advice!


Privacy Notice

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.