Daryl Dunlap

Daryl Dunlap

About Me

Expertise
Freelancer
Location
Not Specified
Website

Connect

My Tutorials

obj-image Intermediate
Redshift4H | Instancing | Intermediate
obj-image Beginner
Redshift4H | Instancing | Beginner

Recent Forum Posts

CopyToPoints vs Instance OBJ node with High Point counts Nov. 6, 2018, 9:42 a.m.

Thanks so much Sean - this mystery has been solved. I was hoping I was missing something, and indeed it was that option on the ForEach EndBlock (which should be enabled by default!).

CopyToPoints vs Instance OBJ node with High Point counts Nov. 6, 2018, 12:52 a.m.

Thanks for chiming in, but, I still dont get it.

Are you saying that Instance OBJ node doesn't have to do those steps?

CopyToPoints vs Instance OBJ node with High Point counts Nov. 5, 2018, 8:50 a.m.

There was a kinda lengthy debate on FB on this topic, and I wanted to see if a SideFX employee could chime in…

As Users started to dive into the PackedPrim Instancing support added to Redshift, what the community discovered ( as stated by Tim ), was that for high Point counts ( >= 100k ), CopyToPoints was severely slower than the Instance OBJ node when performing the same tasks ( packing geo and then varying the geo that is instanced onto points )…..we even wrapped the CopyToPoints in a Compile Block and it was still much slower.

The performance gap we're discussing here is Cook time only.

Bonus Question: How do you use a SubNet with the Instance OBJ node (specifically, using a SubNet as the Instance Source via the Instance OBJ node parameter)? I couldnt even get that to work at all.