11000+款5星资源

8.5万+用户参与评分

10万+社区成员鼎力支持

每款资源都经过 Unity 审核

首页

此内容由第三方提供商托管，该第三方提供商在未接受Targeting Cookies的情况下不允许观看视频。如果您想观看来自这些提供商的视频，请将“Targeting Cookie”的Cookie偏好设置为“是”。

1/6

概述资源包内容版本评论 Publisher info 资源质量

Vissity lets you visualize PTV Vissim traffic and PTV Viswalk pedestrians in Unity. Import network objects, simulated vehicle and pedestrian traffic, and signal timings.

可编程渲染管线（SRP）兼容性

Unity可编程渲染管线（SRP）是让您能够通过C#脚本控制渲染的一个功能。SRP是支撑通用渲染管线（URP）和高清渲染管线（HDRP）的底层技术。

Unity版本	内置渲染管线	通用渲染管线（URP）	高清渲染管线（HDRP）
6000.0.40f1	兼容	兼容	兼容

描述

Vissity lets you visualize PTV Vissim traffic and PTV Viswalk pedestrians in Unity. Import network objects from a network file (.inpx), simulated vehicle traffic from a vehicle record file (.fzp), simulated pedestrian traffic from a pedestrian record file (.pp), and signal timings from a signal changes protocol file (.lsa). With Vissity, you can create highly realistic animations, visualizations, and immersive experiences with your simulated traffic.

Please read the technical details section in its entirety to determine if Vissity is right for your project.

Demos:

WebGL Demo: Signalized Crosswalk

This demonstration shows a "skeleton" build of a signalized crosswalk. (In this context, a skeleton build means that the links, signal heads, and vehicles are primitive GameObjects.) The purpose of this demonstration is to exemplify the synchronicity between the Traffic Manager and Signal Changes Manager. In this example, there are two Traffic Managers: one spawns vehicles that follow trajectories in a vehicle record file (.fzp) and the other spawns pedestrians that follow trajectories in a pedestrian record file (.pp). The Signal Changes Manager reads a signal changes protocol file (.lsa) with a signal controller of type VAP and is responsible for changing the signals.

Use "+" and "-" on your keyboard to increase and decrease the simulation speed factor by 1, respectively. Reversing time is possible.

This example is included in the Vissity package.

技术细节

Key Features:

• The Time Controller component allows you to speed up, slow down, pause, and reverse the simulation.

• The Network Importer component parses a network file (.inpx) and imports PTV Vissim network objects as primitive GameObjects in Edit Mode. Currently, the following network objects can be imported: link segments, desired speed decisions, priority rules (stop lines), stop signs, and signal heads.

Note: Because link segments are imported as primitive cubes, there will be gaps between the segments. Vissity does not include a functionality that fills in these gaps. The intended use of the Network Importer component is to import the network objects into Unity to more easily align the traffic model in the game environment and use them as a reference when building the scene. Typically, roadway geometry is imported into Unity from another source or is created with a road creation tool.

• A Materials List is a data container that is assigned to a Network Importer component. It defines which materials the Network Importer should apply to the PTV Vissim network objects when they are imported in Edit Mode.

• The Traffic Manager component reads trajectory data from a vehicle record file (.fzp) or a pedestrian record file (.pp) and facilitates the smooth animation of traffic in Play Mode.

• A Traffic Assets List is a data container that is assigned to a Traffic Manager component. It defines which prefabs the Traffic Manager should spawn for the PTV Vissim vehicle types or PTV Viswalk pedestrian types in Play Mode.

• The Signal Changes Manager component reads a signal changes protocol file (.lsa), loads traffic signal timings for each signal group from all signal controllers, and creates a field for each signal state. Each field can be assigned one or more mesh renderers in Edit Mode. In Play Mode, this component activates and deactivates the mesh renderers to animate traffic signal changes. This component supports a variety of signal controller types: Fixed Time, Built-in, VAP, Ring Barrier Controller (RBC), and more.

Setup:

LTS Unity versions are recommended for stability (2019.4.x or 2020.3.x). In a Unity project, import the Vissity package. Navigate to GameObject > Caelo Labs > Vissity. Alternatively, right-click in the Hierarchy and select Caelo Labs > Vissity. A GameObject named Vissity is created with a Quick Start Guide component attached. Four child GameObjects are additionally created, each with a correspondingly named component attached: (1) TimeController, (2) Network Importer, (3) Traffic Manager, and (4) Signal Changes Manager.

Vissity takes advantage of custom inspectors wherever possible, which provide clear instructions every step of the way.

Project Settings Requirements:

• API Compatibility Level .Net 4.x

Support, Feedback, and Community:

If you need support, have feedback, or would like to engage with an active community of Vissity users, join our Discord server. For details, see the last page of the documentation or the Quick Start Guide component.

Disclaimer:

• Vissity does not include source code.

• Vissity does not include game ready assets (vehicles, traffic elements, etc.). The Prefabs folder contains vehicles and a pedestrian created with primitive GameObjects to demonstrate how vehicles and pedestrians should be set up to work with Vissity. The Unity Asset Store has a large number of assets, some of which are free, that can be used in conjunction with Vissity.

• Vissity does not include a license for PTV Vissim or PTV Viswalk.

• Vissity does not offer a co-simulation feature with PTV Vissim or PTV Viswalk.

• End user is responsible for ensuring that no license agreements are violated in their use of Vissity.