request: expand index list on Collision One|Many [ColOM]

Would be nice to have not just the first object, but all colliding in the index output. I assume the information is there already anyhow. Or is this a different method from intersection?

Replies to This Discussion

Permalink Reply by Andrew Heumann on May 22, 2013 at 9:09am

seconded...

Permalink Reply by David Rutten on May 22, 2013 at 9:44am

It's not there because I stop colliding as soon as I find a collision. I could of course keep on testing to generate this data, but it will slow down the component somewhat. Anyway, I'll put it on the list of things to do.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Balázs Hegedus on September 23, 2015 at 1:47pm

HI David,

I have the same problem as Philp wrote in 2013. I also need to know all colliding object....Is there any progress on this? Or is there any workaround to solve this issue? Thanks for reply in advance.

Permalink Reply by Balázs Hegedus on September 24, 2015 at 1:33am

An idea for extending the functionality, and the speed problem.

An input integer parameter which controls how many collision object is calculated from the first one. Zero would mean all.

In my situation, I would be happy with the first 10.

Permalink Reply by David Rutten on September 24, 2015 at 3:18am

Not a bad idea, the problem is changing the behaviour of the component is a breaking change, but I suppose I can do what I normally do, replace it with a newer one while hiding (but keeping) the old one...

Permalink Reply by Balázs Hegedus on September 24, 2015 at 5:48am

David, If you don't want to change the behavior why not introducing a new component like Collision Pro for example? :)

Permalink Reply by phillip on September 24, 2015 at 3:40am