For those who can't see the attachments (and everybody else for that matter), I've uploaded them to si-community:
http://www.si-community.com/community/viewtopic.php?f=19&t=3588
gray
From:
softimag...@listproc.autodesk.com [mailto:
softimag...@listproc.autodesk.com] On Behalf Of Guillaume Laforge
Sent: Monday, April 01, 2013 09:49 AM
To:
soft...@listproc.autodesk.com
Subject: Re: ICE Topo Clone from group of objects onto Particles?
> How can i use CPU Fully?
You can't :). When building one mesh, it is very hard to use all your CPU resources. ICE Array nodes (like Build Array from Set or Merge Topo Array) will use one CPU core most of the time (same for the classic merge mesh operator). Maybe there are some faster ways to do this instance to mesh conversion, but not by generating one final mesh.
For example, for N instance shapes, we could generate N meshes. Those meshes would merge shapes using the same topology. Or we could generate one mesh from every particles. This is the perfect scenario for parallel computing :). Unfortunately we can't do such thing from ICE (generating new 3D objects) and creating tones of objects in the scene could slow down interaction a lot...
For info, Creation Platform use the concept of slices per Nodes, where we you can abstract several similar operations into one single node. This is how geometries can be generated so quickly for apps like Flora, Stage or Horde. Such feature in ICE would help a lot ! When I was working on ICE Topology and CrowdFX, I asked several times for the possibility to "unlock the ICE context". For example, being able to do polygon mesh operations not per particle (it would be nice also) but per custom context. For the Instance to Mesh operation, you could create a custom context based on the number of instance shapes and ICE would process each "instance shape clusters" in parallel. I didn't have the skills to implement such feature on an little program like Softimage :), but it would be a nice (and big) feature for sure!
Guillaume Laforge
On Mon, Apr 1, 2013 at 1:27 AM, Byungchul Kang <
ka...@cgndev.com<mailto:
ka...@cgndev.com>> wrote:
Thanks Vincent!
Here.. modified Ice graph.. how about it?
but It is too slow why CPU usage around 15%. How can i use CPU Fully?
2013/3/30 Vincent Ullmann <
vincent...@googlemail.com<mailto:
vincent...@googlemail.com>>
In Thunderbird i cant see any attatchments, what is quite annoying... becouse thats my usual email-checking tool.
Wenn i view the mails via
mail.google.com<
http://mail.google.com> i see these attatchments.
Am 29.03.2013 23:39, schrieb Ahmidou Lyazidi:
I can see the attachment too!
-----------------------------------------------
Ahmidou Lyazidi
Director | TD | CG artist
http://vimeo.com/ahmidou/videos
2013/3/29 Dan Yargici <
danya...@gmail.com<mailto:
danya...@gmail.com>>
I can see them (Gmail)
DAN
On Fri, Mar 29, 2013 at 1:32 PM, Stephen Blair <
stephe...@gmail.com<mailto:
stephe...@gmail.com>> wrote:
Hi Gray
I don't see any attachments.
This happened last time you posted a screenshot too. I couldn't find the attachments
On 28/03/2013 6:46 PM, Grahame Fuller wrote:
Do these compounds help? I've posted before but for some reason the attachments don't seem to make it into the archives.
They were designed to copy particle instances to real topology, but obviously you don't actually need instances but just an integer for the object index in the group.
Usage notes:
To use, put Convert Instances to Mesh in an ICE tree on an empty mesh. It works only with the "self" object. You also need to store the shape index on the point cloud and reference it in the compound's ppg. To transfer attributes, attach one of the Transfer compounds to the Execute port - there's one for each component type.
If you transfer the MaterialIDs, then you can use the Copy Materials checkbox. This works only if all objects in the group have identical Materials arrays.
The transfer is based on finding locations on the group geometry, so it's best to move the instance masters apart if they overlap.
It uses the 2013 version of Build Array from Set which supports topology-type attributes. To use it with Softimage v2012, you'll need to replace it with Build Array from Per Point Data.
gray