If you ICE experts out there had to recommend the top 5 (first) things to learn about ICE what would they be? I'm looking for cornerstone/pedestal type foundation items. I'm going to put some time into really learning ICE and I'd like to know what the most valuable concepts are.
Cheers
gray
P.S. More seriously:
1. Context
2. Locations, getting data at locations, etc.
3. Reference frames, i.e. knowing which data is local to the object with the tree and which data is not
4. Arrays and array manipulation
5. Transformations and 3D math in general, e.g., knowing the difference between multiplying a vector or a position by a matrix.
6. Simulated versus unsimulated trees and how it all fits with the operator stack
- Data flow in an ICE tree
- Data context, structure, and type
- ICE trees, the operator stack, and evaluation (eg simulation versus modeling)
- Attributes
- Transforms, matrices, vectors, and coordinate systems
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Simon Van de Lagemaat
Sent: December-15-11 1:08 PM
To: soft...@listproc.autodesk.com
Subject: Top 5 things to learn about ICE?
For arrays, I guess it depends on whether or not you do any programming.
If you do, then arrays aren't that hard to grasp.
I don't program at all. But I'm sure if I bang my head up against that wall enough it will crumble!
Thanks for all these tips guys, this will really help.
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Stephen Blair
Sent: December-15-11 10:56 AM
To: soft...@listproc.autodesk.com
Subject: RE: Top 5 things to learn about ICE?
Graham is right, locations is good thing to understand.
I’d replace “attributes” in my list with “locations”…
For arrays, I guess it depends on whether or not you do any programming.
If you do, then arrays aren’t that hard to grasp.
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Stephen Blair
Sent: December-15-11 1:33 PM
To: soft...@listproc.autodesk.com
Subject: RE: Top 5 things to learn about ICE?
Here’s 5 things off the top of my head…
In other words, learn to be a programmer.
Matt
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Fabricio Chamon
Sent: Thursday, December 15, 2011 9:33 PM
To: soft...@listproc.autodesk.com
Ya that's the sticky part :-)
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Matt Lind
Sent: December-16-11 10:30 AM
To: soft...@listproc.autodesk.com
No. ICE is a framework for creating operators which abstracts the low level details away from the user so he/she can focus on the task at hand as it relates to 3D. In order to make effective operators, the user needs to be knowledgeable in the area of what ICE is doing at a high level so he/she can use the available resources properly. Just like with scripting you can be functional without that knowledge, but you’ll be far from efficient - or as a friend of mine would always say, “know just enough to be dangerous”.
To use an analogy, just because you know how to speak French doesn’t make you a French poet. Knowing the language is not enough. You have to understand the inner workings of all the pieces to know how to put them together in a cohesive manner. In the case of ICE, that means getting more versed in topics of computer science, and possibly mathematics and/or physics depending on what you’re doing.
�If ever there was a way of scaring animators away from ICE, Matt, your comment is it! What we need is for everyone to play with ice and not even think about the maths side of it. How far they get will be down to their own ability. I really don't regard myself as someone who understands the maths side of things, but I get by because of the way ice works. It bridges the gap between artist and coder, but also allows coders to dig deeper.
Just because I'm not a French Poet doesn't mean I can't kick some serious ICE butt!! ;-)
>
> To use an analogy, just because you know how to speak French doesn�t make you a French poet.� Knowing the language is not enough.� You have to understand the inner workings of all the pieces to know how to put them together in a cohesive manner.� In the case of ICE, that means getting more versed in topics of computer science, and possibly mathematics and/or physics depending on what you�re doing.�
>
> Matt
�
AMEN!
Am 22/12/2011 09:48, schrieb Chris Marshall:
If ever there was a way of scaring animators away from ICE, Matt, your comment is it! What we need is for everyone to play with ice and not even think about the maths side of it. How far they get will be down to their own ability. I really don't regard myself as someone who understands the maths side of things, but I get by because of the way ice works. It bridges the gap between artist and coder, but also allows coders to dig deeper.
Just because I'm not a French Poet doesn't mean I can't kick some serious ICE butt!! ;-)
>
> To use an analogy, just because you know how to speak French doesn’t make you a French poet. Knowing the language is not enough. You have to understand the inner workings of all the pieces to know how to put them together in a cohesive manner. In the case of ICE, that means getting more versed in topics of computer science, and possibly mathematics and/or physics depending on what you’re doing.
>
> Matt
--
Chris Marshall
Mint Motion Limited
Not everyone learns the same way.
You can learn how to play a piano by first learning how to read music, doing scales and variations, music theory etc.
Or, you can just sit down and start tapping keys, and learn to associate tones with finger positions.
The important point is, the piano *makes a sound* when you press a key, despite how much music theory you know.
Many people learned to play piano by ear first, as kids, then went on to eventually learn the theory and become virtuosos.
--
The beauty of ICE is, you can just sit down and start tapping keys, and it *makes a sound.*
Basically what I said is that to use something effectively you have to learn something about it. If that concept scares you then you definitely should not be touching ICE, because when people with that approach touch technical things in a production pipeline, it scares TDs in the same way an exuberant child with a fork in extended hand heading towards an electrical outlet scares the parents.
Like I said before, you can ignore all the details and be functional (which seems to be the approach you prefer), but don’t be surprised when it doesn’t work and/or creates problems.
Matt
From: softimag...@listproc.autodesk.com [mailto:softimag...@listproc.autodesk.com] On Behalf Of Chris Marshall
Sent: Thursday, December 22, 2011 12:48 AM
To: soft...@listproc.autodesk.com
Subject: Re: Top 5 things to learn about ICE?
If ever there was a way of scaring animators away from ICE, Matt, your comment is it! What we need is for everyone to play with ice and not even think about the maths side of it. How far they get will be down to their own ability. I really don't regard myself as someone who understands the maths side of things, but I get by because of the way ice works. It bridges the gap between artist and coder, but also allows coders to dig deeper.