Priority tweak for Impact Sensor

TheBeardyMan 16. Februar 2022 09:05

We use Impact Sensors to trigger effects when objects collide with each other, and some of those effects are only supposed to occur once for each collision. For collisions between objects of two different kinds, we can ensure that a once per collision effect really only occurs once per collision by giving only one of those kinds of objects an Impact Sensor wired up to trigger the effect. But sooner or later, two objects of the same kind are going to collide. If they both have an Impact Sensor wired up to trigger a once per collision effect, how are they going to agree which of them is responsible for the effect?

A priority tweak on the Impact Sensor gadget could solve this problem. The priority tweak would be a number, with one out of band value - possibly represented as infinity in the UI - reserved for disabling priority and making the Impact Sensor register all collisions regardless of priority. When two objects collide, and their Impact Sensors would both register the collision according to their label tweaks, and neither Impact Sensor has the out of band priority value, only the Impact Sensor with the higher priority value would register the collision. For Impact Sensors triggering once per collision effects, other logic could be used to give each Impact Sensor's priority tweak a unique value. When two objects with Impact Sensors uniquely tweaked in this way collide, only one Impact Sensor will register the collision, thus ensuring that once per collision effects are only triggered once.

• 

  TAPgiles

  • 17. Februar 2022 08:21

  

  This would make things a lot easier. Though needing unique priorities per impact sensor would still be a bit of a nightmare. Something along these lines to enable the "one object per collision makes a signal" thing would be good though.

  0

  Diesen Beitrag melden

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.