Namespace mobisim.Traffic
Namespaces
mobisim.Traffic.Editormobisim.Traffic.TimelineClasses
Reactive gap-keeping process that halts a vehicle whenever another vehicle enters its forward
sensor arc within stopDistance, then clears itself once the leading car moves away.
A TrafficProcess that halts a traffic actor when a non-vehicle obstacle (such as a pedestrian or a stationary mine) enters the actor's sensor arc.
A TrafficProcess that models real-world intersection dwell behaviour: the traffic actor decelerates to a full stop at a designated stopline and waits for a configurable dwell time before being allowed to proceed.
CollisionDataLogA serialisable container for all collision events captured during one data-collection interval.
A MonoBehaviour that accumulates collision events and exposes them to the data-collection pipeline via IDataLoggable.
Serialisable distance thresholds that govern when an actor begins decelerating and when it comes to a full stop relative to a detected obstacle.
NumericValueDisplayDisplays a formatted numeric value in a TextMeshPro UI element and controls its visibility.
Specialises TrafficBehaviour for pedestrian actors by routing each sensor detection event to the appropriate TrafficProcess subclass.
Loosely-typed parameter bag passed to ProcessData) so that concrete processes can receive heterogeneous configuration without a custom constructor per subclass.
SensorPhysics-based proximity sensor that fires a OnDetected event for every collider that enters its configurable arc- or cone-shaped detection volume.
Extends ContactStruct with a minimum dwell time at stoplines, used by traffic-signal compliance processes to model realistic intersection behaviour.
TimeStampedCollisionAn immutable snapshot of a single collision event, timestamped to the simulation clock.
TrafficBehaviourAbstract MonoBehaviour that translates sensor collision events into active TrafficProcess instances, driving autonomous actor behaviour such as gap-keeping, stopline compliance, and pedestrian avoidance.
TrafficProcessAbstract base class for a single reactive traffic behaviour — gap-keeping, stopline compliance, or collision avoidance — that runs for a bounded duration and then removes itself from the active list.
The traffic signal controller controls the runtime visual state of a traffic light by updating material shader keywords. This component is responsible for displaying the correct light color (Red, Yellow, Green), as well as enabling or disabling a flashing effect when required.
Extends TrafficBehaviour with vehicle-specific process dispatch (Car vs Pedestrian vs Stopline layers) and dynamically steers sensors toward the next waypoint so that detection stays aligned with the vehicle's intended path on curved roads.
Enums
Rules governing how many instances of the same process type may be active simultaneously on a single actor, preventing over-braking from redundant sensor triggers.
Defines the geometric mode used for detection.
TrafficSignalEnumerates the possible visual states of a simulation traffic light.