Summary

Title:Lucid cloth always respects vertex selection
Category:Workflow
Status:Open
Posted By:michaelwbell ( Michael Wentworth-Bell )
Date Created:6 January 2016

Problem

Description:

Hi Marsel, 

I have come across one issue when trying to use the Lucid Cloths and the modifier stack. 

I have attache da video to demonstrate. Sorry if it is a bit confusing, I didn't have access to a microphone at the time. Sorry for the wall of text below:

In summary:

Lucid Cloth will always respect the vertex selection even if the user is not passing the vertex selection up the modifier stack. In 3ds max if a user continually clicks on a selection modifier (edit poly in my case), they can toggle wether or not the selection passes up the stack. In the video this is shown as the icon of the 3 'vertices' travelling up the modifier stack. 

In the video you can see that even when the vertex selection is not active, the cloth object will still respect that selection. 

 

I came across this error when trying to simulate a scene with many different objects. I could not work out why a particular set of objects would not simulate at all. Infact they were "not simulating at all" because earlier in the modifier stack I had selected all vertices. But I did not have vertex selection active. 

 

In the video I try to show what I mean. First I am using a Rigid body and toggling vertex selection on/off. I then do the same with the Cloth preset. 

Steps to Reproduce:

See video

 

Attached Files:

>ClothStackSelectionInvisible.mp4 (3548130 bytes),

I didn't think this was an issue. Cloth selection is passed up the stack regardless of the sub-selection mode which Max currently uses so Lucid adopts it. Does Max's native cloth only respect vertex selection when in vertex sub-object mode? What if there was some other modifier selecting vertices, like a scripted modifier that doesn't have sub-selection. Would that mean it wouldn't be able to specify fixed vertices for cloth?

Doesn't seem like a bug to me.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

The only issue I see is that it is not clear to the user that the stack selection is being used by lucid. 

In the image above it is clear that 'mesh select' has an active selection (vertices in this case) and that selection is going up the stack to 'taper'. 

A user could click the 'mesh select' text in the modifer stack and the selection icon will disappear - the stack selection is no longer being passed up the modified stack. 

 

With lucid, lucid always recieves the stack selection, even when the user has 'toggled' the selection to be off. By that I mean users don't see the icon of the stack selection (3 vertices in the image above) being passed up the stack anymore yet lucid still takes it. I thought it should only do that when the stack selection is deliberately set. I will test max cloth and other modifiers but I haven't seen another modifier that receives the stack selection without having that stack selection icon. 

Michael Wentworth-Bell

--

Test system for Lucid:
i7-4790k
GTX 780 6GB
32GB Ram
Windows 7 Pro
3ds Max 2016 EXT2

--

Portfolio - http://thelode.com.au
Facebook - https://www.facebook.com/DigitalLode