Other files

*.u3dm

Proprietary 3D model file

Files for 3D vehicle models are stored in the proprietary *.u3dm file format. Exporting and processing these files further is not permitted (Supported file formats for 2D/3D models).

*.fbx

Autodesk Filmbox format

3D model file for vehicles, pedestrians or static objects (Using 2D/3D models), (Using static 3D models) A *.fbx model file may include movement statuses that are relevant for animation of the model, e.g. for the opening and closing of doors or the pedaling movement of a cyclist. If the 3D model should include the positions of axles, drawbars and couplings, define these attributes in the FBX file before adding them (Presetting vehicle attributes in FBX 3D model file).

*.fds

Fire Dynamics Simulator file

The Fire Dynamics Simulator (FDS) program can simulate a fire event and save the results in an *.fds file (Fire event based on an FDS file).

*.layx

Layout settings file

Initializes the Vissim session with position and size of the screen windows and settings of the display options (Saving and importing a layout of the user interface)

*.inpx

Input: Network file (input file)

Description of the entire Vissim traffic network with all elements which belong to it

*.inp

Input: Network file (input file)

File format of network file until Vissim 5.40. *.inp network files saved in Vissim 5.40 can also be opened in Vissim from version 6 and above. Network files from older versions cannot be opened in Vissim version 6 or above.

Vissim can no longer open an *.inp network file saved with version 5.40 or an older version as of version 2023. To continue using such a network file in Vissim 2023 open the file in a Vissim version between Vissim 6 and Vissim 2022 and save it as an *.inpx network file. This *.inpx network file can be read into Vissim 2023.

*.inp0

Network backup copy

Automatically generated copy of the input file

*.q

Plot3D file

As a result of the FDS simulation covering the entire FDS mesh, Plot3D Quantities can be stored in a Plot3D file *.q (Fire event based on an FDS file).

*.pua

Interstages (ASCII)

Output file of Vissig/CROSSIG/P2, input file for a VAP control logic with stages and interstages (Exporting data from the signal controller editor), (Add-on module Traffic-dependent VAP Programming).

Avoid special characters and accent marks in names and identifiers, for example in the name of a signal group. For additional information, refer to the VAP manual (Identifiers section), which by default is saved to the ..\Doc\<language ID> directory of your Vissim installation.

*.pw1

Parameter file

VS-PLUS parameter settings (Add-on module VS-Plus)

*.rcf

Input file in *.xml format. Visum file for Vissim route import (coordinates) (Importing routes). The file contains the following route data:

• Numbers of the zones in which routes begin and end
• Coordinates of the link polygons
• Volume
• Vehicle types
• Projection information

*.sig

Supply file of the fixed time controllers in XML format (Opening and using the signal controller editor), (Using signal controller type Fixed time) until Vissim 2021.

From Vissim 2022, the supply data are stored in the signal controller attribute Internal supply data. If you open an *.inpx file of a Vissim version prior to 2022 that contains a reference to a *.sig file, Vissim will read the supply data from this file and convert the data. When you save the *.inpx file, the supply data is also saved to it. You can then delete the *.sig file.

*.trax

File to which the modification changes are saved (Editing the project structure)

*.v3d

Vissim 3D file

Up to Vissim version 2023.00-01: 3D model file for vehicles, pedestrians or static objects (Using 2D/3D models), (Using static 3D models) A *.v3d file may include movement statuses that are relevant for animation of the model, e.g. for the opening and closing of doors or the pedaling movement of a cyclist.

As of Vissim version 2023.00-01 the file extension .v3d is replaced by the extension .fbx. Vissim adjusts the references of model files with the extension .v3d the .fbx extension when you open a network file saved before Vissim version 2023.00-01, which contains files with the extension *.v3d. Vissim stores information about these adjustments in the log file vissim_msgs.txt. For *.v3d files of static 3D models, for which these adjustments are not possible when opening the network file, a window opens where you can select howVissim should proceed with the file:

• Copy model file: Copies the *.v3d file to the directory of the network file. This means that the *.v3d file is still used and not an *.fbx file.
• Delete static 3D model: Removes the 3D model from the network file. You can add a 3D model file .fbx instead (Defining static 3D models).
• Do not adjust: The reference to the *.v3d file is preserved, but the 3D model is no longer displayed because *.v3d files are no longer stored in the directories under ..\3DModels and the *.v3d file is not copied to the directory of the network file.

*.vap

VAP logic

File with signal control program logic of a VAP controller (Add-on module Traffic-dependent VAP Programming)

*.vce

VS-PLUS C format

VS-PLUS parameter settings in C format (Add-on module VS-Plus)

*.wtt

Value type table

Internal interface description of data types and their formats transferred by an external control procedure in the Signal Times Table window and/or the Signal controller detector record (Defining signal controllers and signal control procedures), (Using signal controller type Fixed time)

*.vxb

Binary supply file for the TRENDS control procedure (Using add-on module TRENDS)

*.zip

Data container of a Vissim model archive

In the context of Vissim , a *.zip file can be a data container of an archive file that contains the network file and all related relevant files (Exporting network files and corresponding files to model archive)

*.vissimpdb

Vissim project file

Binary project file for scenario management (Scenario management)

*.vissimpdb_SQLITE_backup: Backup copy of the binary project file

When you save the base network or a scenario in Scenario Management, Vissim automatically saves a copy of the .*vissimpdb file in the Backups directory of the Scenario Management project.