So there is gonna be a Soft 2015 at least ;)

Had this problem before - I think what I did was abusing the 'reference to string' node together with 'find in array' to find the object name string in the array of strings of the group member names.

Very nice - will be sure to add it to my arsenal. Thanks!

I've owned a license from the beginning of V3 and giving up on working with it.
Texturing performance is below horrible (filling a layer with a color takes about 3-5 minutes on an 8k map) and the workflow is very convoluted.

Btw Eugen I use your curve tools all the time here at work - they are awesome!
For extrusions I still sometimes have to resort to Maya -_-

You probably have to delete that simulation marker.

The thing is it is already there - just tested it with the unsupported environment variable and this is what I am looking for. It is just buggy and crashes a lot but it is there....

Yet it only works for a single compound which makes this method a total slowdown.

No I don't think so - working on a single ICETree which affects multiple objects would be so much more intuitive and speed up working. There already is an unsupported ICE Branch Mode which can be enabled through an environment variable. Haven't tried it yet - heard on the mailing list that it crashe...

There are also several limitations to remapping keys (impossible to remap camera navigation, modifiers, etc..) I have the "S" camera Navigation shortcut in Maya 2010 (and other shortcuts) like I'm used to in Softimage, see the link: http://forums.cgsociety.org/showpost.php?p=1928175&p...

In danger of repeating myself over and over again: Setting ICE data on groups / ICETree branch mode. I recently had to apply a deformer ICETree to 250 meshes at once - the only thing possible was to export the whole tree as a compound, script the application of the compound to the meshes and link th...

The only things I (still) really want are improved performance with many objects (this totally destroys Softimage - Maya is easily up to more than a thousand times faster) and the ability to set data on group members (ICETree branch mode would be great).

I heard the conversion of shaders is pretty slow (someone talked about 10+ minutes for more complex scenes) - is it at least multithreaded?

While the features are few in this release it is not as disappointing as it seems. Lots of stuff has been fixed users have been complaining about. Just two days ago I was cursing that I wasn't able to immediately override settings in ICETrees. The only disappointing thing is that the HQV seems to be...

I think the problem with ICE is how it was/is implemented. Not as Lego pieces with a design for universal nodes that can be used in 99% of situations but instead it has several nodes that only work in some circumstances. This is what kills ICE for most people. You need to sleep with ICE to get buil...

God I hate Autodesk...