Has anyone ever succesfully used:
meshop.setVDataValue or polyop.setVDataValue
or
meshop.setVSelectWeight[font=Courier New] [/font]
…?
The corresponding get functions work fine. The set functions return ok and all but the actual soft selection weight is never changed.
[font=Verdana]Any other known way of affecting the soft selection?[/font]
Thanks,
Rog.
I can’t find a way to affect soft selection weights on individual vertices either. I’m seeing the same results as you with the setVSelectWeight[font=Courier New] [/font] method. Perhaps this is something that max uses for its soft selection functionality that isn’t supposed to be changed independently of that. If that’s the case, though… I don’t understand why the setVSelectWeight[font=Courier New] [/font] method is exposed through maxscript and isn’t just an internal API call. Can anyone else shed some light on this?
There are the methods that deal with changing the soft selection parameters (falloff, pinch, etc). These work, but I’m not sure they’re what you want.
meshop.[b][b]setFalloff[/b][/b]
meshop.[b][b]setBubble
[/b][/b]meshop.[b][b]setPinch
[/b][/b]
I am understanding it a bit better now. Not that it’s a great help…
The SetVdataValue for channel 1 (soft selection) does work on an a mesh object.
This mesh can be the mesh of an Editable Poly Node. However as soon as you try to visualize a change in these values you would need to go into vertex subselection mode + soft selection.
As soon as you do that the editable poly/mesh base object or modifier will overwrite the values in the channel with what it calculates itself by taking the “hard” selection and the falloff parameters etc. I figured this out by going through te code of the Select Poly modifier.
So, in the end, I can still see not much use of exposing this API.
Rog.