IntersectionAnalysis: Collected Attributes don't make sens? {[SOLVED]}

   1242   2   0
User Avatar
Member
1114 posts
Joined: 4月 2017
Offline
Hi!

I connected 2 polygonal geos (not curves) to the IntersectionAnalysis sop:

input 0: 428108 primitives
input 1: 24494 primitives

I toggled Input Number and Primitive Number but when I look at the geo Spreadsheet, it says one of the hit from input 0 is primitive number 496294. The problem is I don't even have that many primitives in input 0. How can I get that result?

...is that sop only meant to be used with curves.. ?!

-Olivier
Edited by olivierth - 2023年7月6日 17:31:32

Attachments:
Houdini_IntersectionAnalysis_bad_attibs.JPG (128.0 KB)

User Avatar
Member
9124 posts
Joined: 7月 2007
Offline
Can't check right now, but I believe intersection analysis expects triangulated geo, and if it's not then it triangulates internally

Therefore the numbers may refer to the triangulated prims

(There is a warning on your node which probably says something along those lines)

So try adding Divide SOP to triangulate before and see if the numbers match
Tomas Slancik
CG Supervisor
Framestore, NY
User Avatar
Member
1114 posts
Joined: 4月 2017
Offline
Arg, yes, I forgot to read the warning:

A triangle and curve mesh is required on the input for correct attribute output.A triangle and curve mesh is required on the input for correct attribute output.

I ended up using another method that did not require those attributes.

-Olivier
  • Quick Links