So I need one Relative Proximity Sensor Prototype for each pair of objects I want to check collisinos for, right?<br><br>Thus, if I want to check collisions among N objects, I would need N xN Relative Proximity Sensors?<br>
<br>Thanks for the feedback!<br><br><div class="gmail_quote">El 22 de agosto de 2009 07:23, Don Brutzman <span dir="ltr"><<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>></span> escribió:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Collision node is for viewpoint-to-object collision detection only,<br>
not object-to-object collision detection.<br>
<br>
We've got a prototype in the Savage library that may be suitable<br>
for what you want to do.<br>
<br>
<a href="https://savage.nps.edu/Savage/Tools/Animation" target="_blank">https://savage.nps.edu/Savage/Tools/Animation</a><br>
<br>
Relative Proximity Sensor Prototype<br>
Paired object-to-object proximity sensor design pattern<br>
implemented as a reusable prototype node.<br>
<br>
Relative Proximity Sensor Example<br>
RelativeProximitySensor design pattern: example use.<br>
<br>
essentially you ROUTE the same values to the prototype that you are<br>
using to translate two objects. The prototype then sends notification<br>
events if the two objects are sufficiently close to each other.<br>
<br>
all the best, Don<br><font color="#888888">
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270 MOVES Institute, Monterey CA 93943-5000 USA work +1.831.656.2149<br>
X3D, virtual worlds, underwater robots, XMSF <a href="http://web.nps.navy.mil/%7Ebrutzman" target="_blank">http://web.nps.navy.mil/~brutzman</a><br>
<br>
</font></blockquote></div><br>