Again a GameObject will only appear once in the list, even if it has multipleĬolliders. This will produce a different list if the colliders are on child GameObjects to theirĪttached RigidBody components. If the sensor is in 'RigidBodies' mode then the detected objects will be the attached RigidBody GameObjects forĪll the sensed colliders. IfĪ GameObject has multiple colliders it will still only be detected once. If the sensor is in 'Colliders' mode then the detected objects will be the collider GameObjects as expected.
Each sensor has two detection modes: Colliders or RigidBodies. In this example you could disable automatic pulsing on the bullet's sensor and manually call Pulse() when needed.Įach of the sensors detect GameObjects by their colliders, but that doesn't mean the collider itself will appear in the sensors list of detected objects. Sometimes however you may want precise control over when a sensor is pulsed, for example a bullet may want to pulse its sensor just before it determines whether it has hit anything.
Each of the sensors can be configured to automatically pulse themselves at fixed intervals or every frame. This will cause the sensor to perform its 'sensing' routine that adds and removes GameObjects from its list of detected objects. Sensors update their list of detected GameObjects by being pulsed, that is by having their Pulse() method called. If (sensor.GetNearestByName("Player") != null) GetNearestByName returns the nearest detected GameObject with the specified name, or null if there is none detected. RaySensor, RangeSensor and TriggerSensor all extend Sensor This sensor could be placed at the end of a maze to check if the player has reached the last room and escaped. Here's how you might write a MonoBehaviour that uses a sensor. This simple range sensor setup allows the worker to see the piles of bricks around him.
0 kommentar(er)
