Can't you force it to belong to the mesh with ice?

Edit Oh I see what you mean I think . The transform array in fabric isn't the same order as si. That's always going to be the case from whatever dcc isn't it?

This is not going to work because you will have to work with two dimensional arrays. I am afraid this is only possible in code for now. Essentially you will have a an array of arrays of weights and indices for the deformers. So you will have to move your experiment to code. Sorry! I'm just going by...

Its harder than I anticipated. I forget that "per-point context" in ICE, is dealt with as just an array in Fabric, so you've used up one array dimension just on that. Thats so locked into my way of thinking, that its hard to get my head around the fact that a simple ICE array is in fact a ...

Wouldn't a pointcloud be the same as a mesh? Sure;y yoU just end Up with an array of positions either way..

Why can't you store it as an ICE attribute and use crate to embed it in the alembic file?

Or if you don't want to deal with 2d arrays, split the second dimension into separate attributes.

This is looking more and more accessible with each new update. This one significantly advances fabric for deforms.my area of interest.
Great work.

Thanks Eric. I look forward to fiddling around with your tool.
Hold on. That didn't sound right.

This is your second lesson in vectors.

https://vimeo.com/156686656

I'll be giving you some homework soon

here it is.. Look inside it, as you'll see that it is very simple.


https://dl.dropboxusercontent.com/u/822 ... sicompound

right click save as..


and watch this video I made for you to understand vectors

https://vimeo.com/156559211

Sorry, yes of course. I meant that it's easily achieved. Obviously that's if you know how to manipulate vectors.
If you have trouble I'm happy to make you a compound.

You can easily make a compound to grow the hair after the cache.

You'd need to multiply the strand position in relation to the point position.

thanks Myara.. that worked a treat.

The thing I noticed first from Fabric is how it's generic and isn't designed to read any softimage specific data. only generic data. It's like the difference between an Obj as opposed to a softimage object. You realise how much isn't there and now it's just the fundamentals. It made me realise how m...

Hi Eric,

Thanks.

It was my understanding that whatever variable triggered the loop was fixed until the loop ended. Obviously that's wrong. So it's good to know.

You make some shapes.. select them and its meant to make Objects from them that store the Blendshape in point positions.. So it works but only on the first.. Can anyone see why? xsi = Application lm = LogMessage from win32com.client import constants as c sel = xsi.Selection grab = sel(0) cls = grab....

Looks very useful, thanks. I have a few compounds where those Fcurves overpower everything

Yes I'm going to do some more ICE ones.. I'm working on a "how to make Fur dynamics" one at the moment. To me, its all the same kind of stuff. Anything learnt in ICE is applicable to Fabric. and at the moment far faster for me. I'm liking Fabric, but its more work to get the same results. ...