It doesn't matter which file you use to open the project. The *.inpx file contains the base network and a reference to the *.vissimpdb file. The *.vissimpdb file is binary coded and contains all data (modifications,...) from scenario management.
Click File > Scenario Management > Project Structure, tab Scenarios, select a scenario in the list, and click the button 'export selected scenarios' (floppy disk with the red arrow). This will export a standalone network file of the scenario (as an *.inpx). For more information, click Help > PTV Vissim Help and refer to the section 'Editing the project structure'.
1) Open Windows Explorer.
2) Navigate to %appdata%\PTV Vision\
3) Open your PTV Vissim version folder (e.g. ..\PTV Vissim 11\).
4) Delete the file 'licenses.data'.
5) Relaunch PTV Vissim.
After achieving convergence, if you want to continue using the same paths, change the following settings:
- In the Dynamic Assignment: Parameters window (Files tab), deselect 'Store paths (and volumes)'.
- In the Dynamic Assignment: Parameters window (Search tab), deselect 'Search new paths'.
- In the Dynamic Assignment: Parameters window (Choice tab), under Path choice model, select 'Use volume (old)'.
Here are two general tips for facilitating convergence.
1) Click Traffic > Dynamic Assignment > Parameters.
- On the Files tab, scale the total volume to e.g. 20%.
- On the Choice tab, activate 'Avoid long detours' and 'Limit number of paths', and for the max. number of paths per parking lot relation, decrease the default value of 999 to a value that make sense for the spatial scope of your network.
2) Click Simulation > Parameters.
- The random seed increment should be set to 0 for convergence runs. If the model has already converged and only evaluations are performed, the random seed increment should be > 0.
- Change the dynamic assignment volume increment to e.g. 5%. For more information on the dynamic assignment volume increment, click Help > PTV Vissim Help and refer to the section 'Defining simulation parameters'.
Other useful tips:
- Select only one of the three convergence criteria; preferably, choose 'Travel time on paths'.
- If you select multiple convergence criteria, there is a chance that convergence will never be reached due to the increasing requirements the convergence criteria could become too strict.
- If you select the convergence criterion 'Volume on edges', there is a chance that convergence will never be reached because the absolute number of vehicles on the highest volume links fluctuate more than on links with less volume although the percentage deviation is the same.
- Use longer evaluation intervals (>= 15 minutes): A path is converged if it converges in all time intervals.
- The default setting for convergence criterion is 95%, but depending on the network and especially the frequency of low path volumes (per interval), lower values may be necessary to meet the condition. Longer time intervals usually allow for higher percentages.
- Heavily overloaded networks typically never converge. Therefore, it may be reasonable to assume that the paths and distribution achieved from convergence runs at 70% traffic volume is similar to those at 100% traffic volume. Rather than assigning 100% of demand and never achieving convergence in a congested network, the paths could be developed using incremental increases in demand up to, for example, 70%. At this point, the demand could be fixed at 70% for convergence runs. Assuming that convergence is achieved and the paths are reviewed for suitability, the demand could be increased back up to 100% for evaluation runs.
ShrConvPathTT is the share of the paths in percent that has met the convergence criterion if the convergence criterion 'Travel time on paths' has been selected. The percentage weighted by volume is specified in parentheses: Total volume (across all time intervals) of all converged paths / total volume of all paths used.
ShrConvEdgeTT is the share of the edges in percent that has met the convergence criterion if the convergence criterion 'Travel time of edges' has been selected. The percentage weighted by volume is specified in parentheses: Total volume (across all time intervals) of all converged paths / total volume of all paths used.
Note: A path is converged if the convergence criterion is met in all time intervals. From the *.cva file, you cannot recognize if the paths that converged in one time interval are the same that converged in another. However, you can open the Paths list in PTV Vissim (Traffic > Dynamic Assignment > Paths), and if you add the attribute Converged (Conv) to this list, then you can see if the path is converged or not.
For more information, click Help > PTV Vissim Help and refer to the section 'Saving data about the convergence of the dynamic assignment to a file'.
1) Open the network and select 'Parking lot' from the toolbar.
2) Choose 'Edit - Auto Route Selection...' from the menu.
3) Select the desired zone combination. All routes found so far are shown in the list.
4) Choose an item in the list box to show the corresponding route in the network.
You may assign the same zone number to more than one parking lot and set the proportion factor within each one of them.
A generalized cost function is used instead of merely travel time. The link cost is the weighted sum of travel time, distance and link specific costs. The user has control over the weights that are used for each particular vehicle type.
The traffic volume originating from this zone will be split evenly (on average) between the two parking lots.
Please check the following points:
- Is the evaluation period long enough to catch all of them? If the simulation runs for e.g. 3600 seconds and you do aggregate at the end of the same period, there will almost certainly be vehicles not yet arrived at their destination parking lot.
- Are there errors in the network topology reported to the messages file? You might find out that some vehicles cannot reach their destination because there aren't any possible routes between their origin and their destination.
- Make sure that after a modification to the network topology you delete the *.bew and *.weg files before running the simulation again.
There is no implicit unit for the generalized cost, so you can freely choose it. You only need to consider that travel time is measured in seconds, distance is measured in meters and that the link cost has no implicit unit. So you need to choose the coefficients both as a weight and conversion factor to convert from one unit to your chosen unit.
Example: You choose $ as cost unit.
Now you need to determine the worth of one second of travel time in $ and also the worth of 1 meter in $ (if you want to include the distance in your calculation).
If you use any link cost, you would define these as cost in $.
There is a matrix correction tool in PTV Vissim. For more information, click Help > PTV Vissim Help and refer to the sections 'Correcting demand matrices' and 'Defining and performing Matrix correction'.
It is also possible to export the PTV Vissim network to PTV Visum, which provides a more sophisticated handling of matrices and traffic demand.
This problem usually occurs when nodes are missing in the network. In such cases, there are too many possible paths/edges, and PTV Vissim cannot build the abstract network graph. Add the necessary nodes; one node per intersection generally works.
For more information on how to properly code nodes for dynamic assignment, in PTV Vissim, click Help > PTV Vissim Help and refer to the section 'Building an Abstract Network Graph' and its subsections.
The problem occurs because for traffic from matrices it is required that the destination parking lot at the time of departure has still open for the whole simulation period (not only for the remaining simulation period). That means a opening time of 99.999 seconds is not enough for a simulation period of 86.400 simulation seconds from a departure time 13599,1.
Please define a opening time of 999.999 for all parking lots, then it will work.
If you have modified your Vissim network and still want to continue to use an old path file, the option ''Check Edges'' in the Dynamic Assignment window must be enabled.
Then the following errors might occur:
'The abstract graph (edge structure) in file *.WEG isn't identical with the current one. Error messages are written to the Messages window.'
'Old abstract graph in *.WEG: The edge 726 cannot be mapped to any edge in the current network graph.'
'One or more paths in file *.WEG are not used anymore. Error messages are written to the Messages window.'
'No edge turn in the node 10 from node 9 to node 14 could be found.'
Either one of these errors means that the old structure (of the path file) cannot be safely matched with the modified Vissim network. You either need to modify your network or you need to delete the path file and let Vissim build a new one.
'If the message looks like this:
''No path from parking lot 23 to parking lot 1594 can be used because of the following connector closures: 11880, for the following vehicle types: 100''
it is just a warning. It does not mean that vehicles are not placed into the network unless there is another message which states:
''No parking lot found from zone 19 with at least one path to destination zone 14. Vehicles of type 100 from the matrix 1 could not be placed in the network.'''
You need to have a SCATS®/SCOOT® system running on your computer (this is independent of Vissim and is not distributed by PTV).
For SCATS®, several files incl. WinTraff and ScatSim are needed from the 'Roads and Traffic Authority' NSW, Australia.
When an intersection is changed, it is necessary to update its geometry. PTV Vissim needs to find a location where the new part of the network is connected to the old part of the network. Therefore, PTV Vissim cuts the links between the new intersection and the old ones very close to the old intersections. This is not random; PTV Vissim tries to save as much of the old network as is possible. For example, items located on the edges next to the updated intersection will generally be restored.
This warning message originates from Excel® and may come up, if the command 'RunContinuous' is used. Choose one of the following solutions to avoid this message:
Use 'RunSingleStep' instead of 'RunContinuous' in the following way:
for i = 0 to simulation.Period * simulation.Resolution simulation.RunSingleStep DoEvents
Switch off all Excel® warnings using the VBA command:
Application.DisplayAlerts = False
Use a different programming environment.
The recommended option is included in the standard Vissim installation at '..\Examples\Training\SpecialModeling\Incident'. The following technique is used:
1.Create a mini connector (ca. 1m long) inside the same link connecting all lanes that are still available during the incident.
2.Create a partial routing decision that includes the newly created connector and define it for the time period where the incident should occur.
3.In addition, if you want to model the incident vehicle, create a parking lot on the blocked lane.
4.Make sure that the routing decision for the parking lot is only active as long as needed to let one vehicle park.
5.Assign a dwell time to the parking lot that matches with the time period of the partial route.
This method reflects the most fluent lane changing behavior.
Please note that this modeling technique is not possible in combination with Dynamic Assignment.
A merging area should be modelled as a single link with as many lanes as the main road plus the merging lane(s). Make sure to only use a single connector at the end of a merging area to connect with the remaining lanes.
On motorways, use the 'free lane change' option for the links involved in order to increase capacity.
The train cannot stop because its deceleration capability is limited and thus it needs a longer look-ahead distance than normal traffic to see the stop in time. If it is unable to stop in time, it leaves its route and the train is removed from the network (this event is logged in messages).
To fix this, in the driving behavior parameters used for the train, increase the maximum look-ahead distance.
Show time label in the Network Editor or exported *.avi video:
Network editor > Edit basic graphic parameters > Show simulation time label
Show simulation seconds:
View > Simulation Time > Simulation Second
Show time in the time format hh:mm:ss:
View > Simulation Time > Time of Day
Set the start time of the simulation:
Simulation > Parameters > Start time
Since gap acceptance can vary from location to location, this variable is considered an 'engineering input', meaning the modeler should use engineering knowledge or location-specific field data when setting up priority rules.
Even if you draw links crossing each other, the program will not recognize this as an intersection unless you model connectors or any type of junction control (signal control, conflict areas, and/or priority rules).
For 3D mode you may enter a height value to any link/connector to show the different levels.
For a network with three simple, 4-leg junctions the geometric model will be finished within a few hours. Coding an existing signal control depends heavily on the control logic: A few minutes for a fixed time control, several hours for modeling a complex vehicle-actuated control with public transport priority.
Any junction geometry can be modeled (signal-controlled intersections, priority junctions, merges including any type of roundabout) in Vissim.
The basic element of Vissim networks is a link (stretch of road) with one or more lanes. Links can be modeled exactly according to the geometry of the real junction with a precision down to one millimeter. Based on the link structure, network elements such as signal heads, conflict areas, priority rules etc. can be defined.
Check if the lane where the HGV wants to change to, is closed to HGVs (button 'Lane Closure...' in the link/connector window) or if the lane change to this lane is banned for HGV (button 'No lane change...' in the link/connector window).
Vissim uses vehicle-driver-units. There are practically no limits on the number of vehicle and driver types. By default, the vehicle types Car, HGV, Bus, Tram, Pedestrian and Bike are included. Along with all their default specifications VISSIM provides a quick project start.
Yes, it is possible.
Definition one: group of cars (known as a 'platoon') the size of which is defined by the signal times.
These platooning effects can be generated by:
- modelling the adjacent junctions (platoons formed by signals)
- lengthening incoming links (platoons formed by car-following and different desired speeds).
Definition two: Grouping vehicles into platoons is a method of increasing the capacity of roads. An automated highway system is a proposed technology for doing this.
This ca be simulated using scripts, see the example Platooning.inpx in ...Examples Training\Autonomous Vehicles (AV)\Platooning.COM (since Vissim 9). In the future PTV Vissim version also integrated funcionality may be inplemented (without the need for scripts).
In order for a vehicle to react in a conflict area it has to see the end of the conflict area.
- Raise the attribute value 'Observed vehicles in front': Base Data > Driving Behaviors.
For long conflict areas it may happen that the defined number of 'Observed vehicles in front' is too low to accomodate for all vehicles (the conflict area is internally counted as vehicle as well).
- Raise the attribute value 'Look ahead distance (minimum)': Base Data > Driving Behaviors.
This ensures that vehicles see the end of the conflict area, independently of the number of 'Observed vehicles in front'. We recommend to apply this driving behavior only to those links/connectors where it is required in order to keep the simulation speed as fast as possible.
- Use the network object 'Priority Rules'.
Conflict areas seem sometimes being ignored by vehicles, e.g. because other vehicles keep waiting because of another Conflict area. With a Priority Rule you can model to keep an intersection clear.
(Re.f: Manual 18.104.22.168 It is better to use conflict areas than priority rules to model driving behavior.)
Yes. For a short section (e.g. 20m) in front of the stop lines, apply the 'No lane change...' flag in the link/connector attributes to all lanes and all vehicle classes (you may need to split a link in order to get a suitable section).
Caution: A gridlock situation may appear in that section as no lane changes are possible - not even necessary lane changes because of a route.
The largest Vissim license has no built-in limit. Therefore the network size is limited only by computer resources. Apart from the hardware, the major factors that determine the simulation speed are number of vehicles simultaneously in the network, number of signal controls and number of possible paths (Dynamic Assignment).
Yes, by using stop signs with an optional time distribution.
Yellow boxes can be modeled using conflict areas or priority rules. For details on priority rules please refer to the PTV Vissim help > 'Creating and editing a network' > 'Modeling right-of-way without SC' > 'Modeling priority rules' > 'Examples of priority rules' > 'Priority rule Example 2: Avoiding tailbacks at a junction'.
Visualization of the yellow box can be done if you include it in a background graphics file. You can also load multiple background files simultaneously.
In the Network Editor, you can view the attributes of a network object in a text box and position the text box.
1) On the Network Objects toolbar, in the row of the desired network object type, click the Edit graphic parameters button.
The list with the graphic parameters of the network object type opens.
2) Make sure that the option is selected for the 'Label visibility' attribute.
3) Click the button next to the 'Label attribute'.
The list of attributes opens.
4) Select the desired entry.
5) Confirm with 'OK'.
6) Click next to the list with the graphic parameters.
The label is shown in the network object.
For more information, click Help > PTV Vissim Help and refer to the section 'Viewing and positioning label of a network object'.
Please refer to the PTV Vissim Help (https://cgi.ptvgroup.com/vision-help/VISSIM_11_ENG/) > 'Creating and editing a network' > 'Modeling right-of-way without SC' > 'Modeling stop signs and toll counters' > 'Using stop signs for right turning vehicles even if red'.
These are the options for the use of the network element Parking Lot:
1. For the use of static routes:
Modelling roadside parking and pick-up/drop-off lanes.
Any orientation, e.g parallel, diagonal and perpendicular parking lots can be modelled.
2. For Dynamic Assignment:
Modelling origins and destinations of trips. A Logit-based parking lot choice model is implemented in Vissim. Details can be found in the Vissim user manual.
Vissim has separate models for urban traffic and for motorways (car following models - Wiedemann 74 and Wiedemann 99). Motorway junctions can be modelled using the standard network elements. Merging areas have been tested and proved against HCM standards.
PTV Vissim does not use any map projection and does not take into account any map projection of background files. Instead, PTV Vissim uses an own local, metric coordinate system defining a flat surface.
PTV Vissim does neither provide any coordinate transformations, but since PTV Vissim 10 an example is provided, using formulas in User-Defined Attributes to determine coordinates in 'Sphere Mercator'/Mercator (sphere)':
c:\Users\Public\Documents\PTV Vision\PTV Vissim 10\Examples Training\Evaluation\WGS Coordinates.UDA
Any background files created in CAD or GIS systems should adopt this local coordinate system: Match the coordinate values of some central point in the network, for example a node or the Reference point: Base Data > Network Settings > Display > Background maps > Reference point in network
Regarding the use of background images, refer to the Manual: 22.214.171.124 Loading image file as background image.
To change the coordinate system in AutoCAD Map 3D refer to:
Yes, it is possible to model overtaking into oncoming traffic lanes. Please have a look to the example: '..\Examples Training\Overtaking In The Opposing Lane\Interurban' and the PTV Vissim Help.
Public transport is modelled as trams and/or buses in high detail with fixed routes. Stops and timetables are modelled as well. Waiting times at stops depend on the timetable and on a user-defined random distribution for the passenger interchange times. Optionally the dwell time calculation method can be chosen which uses real passenger flows to determine waiting times. Priority on signal control junctions can be modelled completely with detection and control logic using a vehicle actuated signal controller.
No, a new static route will be considered by a vehicle only if the existing one has been completed (the green bar passed). However, partial, parking lot and managed lane routes are considered by vehicles traveling on a static route.
Route choice can be determined by the user (static routing) or computed iteratively with the optional Dynamic Assignment module. Routes can also be imported from the travel demand modelling software PTV Visum.
If you define a negative height to a link, the link will be displayed below the 0-plain and thus is not visible in 3D mode initially. However, vehicles will still travel on such a link and you can look below the 0-plain in 3D mode. You can also shift the entire network (excluding background files) to a different height using the z direction in 'Edit - Translate Network'.
From Vissim 6.00 it is also possible using levels
When using static routes, a movement is banned if there is no route assigned to that movement (if routes do exist for at least one other movement). Routes are dependent on vehicle classes thus allowing banned turns for a certain class only.
When using Dynamic Assignment, connectors may be closed to certain vehicle classes.
Since the model is microscopic, shock waves and blocking back are modelled inherently.
Local knowledge can be modelled in Dynamic Assignment by defining different vehicle classes and allowing rat runs only for these classes.
Lane drops and gains can be modelled easily using the link parameters.
VMS and other types of traffic control can be modeled using the VAP or COM interfaces.
See also the '..\Examples' directory on your standard VISSIM installation for examples on these topics.
Yes, since PTV Vissim 10, vehicles are able to reverse out of parking lots. Please see the examples in '..\Examples Training\COM\Car Park Display.VBS' and the PTV Vissim help for more information.
The 2D visualization during a simulation run can be slow on Windows 7® if a desktop theme with Aero (translucent glass design) is selected. If a basic theme without Aero is selected (in Control Panel - Appearance and Personalization - Personalization - Theme), the 2D visualization can be up to 9 times faster.
In PTV Vissim, click Edit > User Preferences. In the navigator tree, choose GUI > Graphics and click the button Compression. This will open the Video Compression window, where you can select a default compression program for AVI recording.
Please follow the workarounds in the FAQ below:
No, it is not possible. Vissim has no user defined WMSs. In Vistro and Vissim it is only possible to use our predified WMSs. The feature is already on our Vissim wish list.
We recommend NVIDIA graphics cards since PTV Vissim 10 DirectX can be used in addition to OpenGL. NVIDIA GeForce graphics cards with Fermi or Kepler architecture (400 or later, such as GeForce GTX 750) are sufficient. For desktop computers, the GeForce GTX1060, for example, is powerful and still relatively cheap. If certified drivers are required, cards from the Quadro series can of course also be used. The performance is similar to the graphics cards of the GeForce series. For notebooks, it is important that they have a dedicated graphics card, not just an on-board graphics card. To reiterate, we recommend graphics cards from NVIDIA as they have better drivers and can be switched on for an application like PTV Vissim or PTV Visum.
You should always use the latest graphic card driver. You can find the driver either on the website of the manufacturer of your computer or laptop or on the website of the graphic card manufacturer, examples:
Consider the use of a tool offered by the manufacturer to automatically detect and update the driver.
Yes, among several bitmap formats (e.g. jpg, tif, bmp) also vector formats (e.g. wmf, dxf/dwg, shp, Mr. Sid) can be used for background graphics.
Please note that few vector formats currently are supported by the 32-bit version of Vissim only.
For this task you need an animated pedestrian model and V3DM. Follow the steps listed below:
- Create a 3D pedestrian model in a professional 3D modeling application (such as Autodesk 3ds Max) that can be animated or moved.
- Divide a flow of movement into 20 parts to export 20 different 3D models, each showing a different state of the model.
- Export each state to a DWF file.
- In addition to the other 20 states, export the model to a DWF file at standstill.
- In V3DM you create a new project of the type 'vehicle'.
- Import the model in standstill position as state 0.
- For each exported DWF file, create a new state within V3DM and import the associated DWF file.
- After importing all 21 DWF files, assign the corresponding 'vehicle' properties: 4 different colors (shirt, hair, pants, shoes), positions of the front and rear axle.
- Export the V3DM file to v3d format.
- Create a new 2D / 3D model distribution with the exported v3d format and map it to a pedestrian type.
Yes, any background graphics that are loaded in 2D are also visible in 3D. Static 3D objects in V3D format (Vissim 3D) may be placed anywhere in the network. From Vissim 5.20 onwards, it is also possible to place Sketchup® files (*.SKP) directly in 3D mode as static object (Vissim 32-bit editions only).
Several vehicle and static 3D models are included with the standard Vissim installation in V3D format. Many additional models in V3D format are available to download through our service area webpage (login required).
Customized models can be created/converted using V3DM (Vissim 3D Modeler - additional module, see also FAQ http://vision-traffic.ptvgroup.com/en-uk/training-support/support/ptv-vissim/faqs/visfaq/show/VIS19264/).
On computers with both an on-board graphics card and a dedicated graphics card, the graphics mode needs to be explicitely switched to the dedicated card for best PTV Vissim performance. This can be done in the Nvidia Control Panel or AMD Catalyst Control Center, which can be accessed from the system tray in the Windows taskbar or from the advanced settings in the display settings from the Windows Control Panel.
If a computer has Nvidia Optimus, PTV Vissim is usually executed by default on the on-board graphics. To assign Vissim to the dedicated graphics chip, the graphics settings need to be modified as above.
V3DM is short for 'Vissim 3D Modeler' and is an additional Vissim module to
- convert 3D objects from DWF, 3DS and SKP (Sketchup®) format to the Vissim V3D format
- create simple 3D objects (such as houses, simple vehicles etc.) including textures
If you would like to create more complex 3D objects you need professional 3D modeling tools such as 3ds Max. For including your own pedestrian models in Vissim, please check FAQ http://vision-traffic.ptvgroup.com/en-uk/training-support/support/ptv-vissim/faqs/visfaq/show/VIS19311/.
In PTV Vissim, static 3D objects (V3D format) can be inserted in 3D mode by right click.
Another option is to export PTV Vissim data to 3ds Max in order to create a high-end presentation of the simulation entirely inside 3ds Max.
There are two potential solutions:
Video compression codec: Find a good balance between quality and file size using a current codec (see also FAQ http://vision-traffic.ptvgroup.com/en-uk/training-support/support/ptv-vissim/faqs/visfaq/show/VIS19291/).
Vissim window size: Decrease the size of the Vissim application window to reduce the output size of the AVI video.
We recommend the x264 codec, which creates quality AVI videos with smaller file sizes (https://sourceforge.net/projects/x264vfw/).
The video codecs are part of the operating system and therefore PTV Vissim has no influence over which codecs are available. Make sure that the desired codec(s) are installed on your computer before starting PTV Vissim.
For successful playback, you need to ensure that the codec used for recording is also installed on the computer system where it is played back.
Please note that for x264 there is a 32-bit and a 64-bit edition available. Choose the edition that complies with the application for recording/playback (e.g. x264 32-bit for PTV Vissim 32-bit). If you are unsure, you may also install both editions.
As an alternative for playback, you may use a media player with built-in codecs such as VLC media player.
(Please note that using these codecs and other software is entirely at your own risk and is outside the scope of PTV Support.)
Yes. You can import Sketchup® files as static 3D objects and (from PTV Vissim 10 onwards) also as vehicle models. You can find a large library of Sketchup® models incl. buildings and landmarks on the Internet.
Update all your graphic card drivers manually. Windows often indicates that the the graphic card driver was updated automatically, but that does not always cover the latest, current version.
We recommend visiting the website of the manufacturer to download and install the latest driver.
Consider the use of a tool offered by the manufacturer to automatically detect and update the driver.
When this does not solve the issue, change the following setting in PTV Vissim:
Edit > User Preferences > GUI > Graphics > 3D Mode > Graphics driver: Change 'OpenGL 3.0' to 'DirectX11'
For recommendations on which graphic cards to use: http://vision-traffic.ptvgroup.com/en-uk/training-support/support/ptv-vissim/faqs/visfaq/show/VIS19126/
Yes, using the node evaluation. For further information, in PTV Vissim click Help > PTV Vissim Help online help and refer to the section 'Evaluating nodes'.
PTV Group maintains a contract with Microsoft to use Bing Maps as a live background map in PTV Vissim, PTV Vistro, PTV Visum, and PTV Viswalk, from which customers with an active maintenance contract benefit.
If this applies to you, and your license in the dialog
Help > License > Bing Maps (until ...)
is listed as not activated, please contact
together with a screenshot of this dialog.
- If none of the background maps can be displayed, refer to:
- If you like to renew your maintenance contract, contact email@example.com or your local distributor.
- If your maintenance contract was already renewed, activate the latest license ticket you received by e-mail from PTV through
Contact your license administrator in case you are not responsible for managing the licenses.
Due to licensing restrictions, Google Maps cannot be used as the interactive live map provider in PTV Vissim.
The available map providers currently are Bing Maps and OpenStreetMap.
You could take a series of screenshots from any map service and add and manually tile them in the Network Editor as Background Images.
For more information on using background images, refer to the following help page: https://cgi.ptvgroup.com/vision-help/VISSIM_11_ENG/#5_Netzbearbeiten/Hintergrundgrafiken_einfuegen.htm.
If you are using PTV Vissim 10 in combination with the Windows 7 operating system, your graphics card driver could cause a crash during its startup, often resulting in the error message VISSIM100.exe - Application Error: The application was unable to start correctly (0x0000005). This issue has been fixed in PTV Vissim 10.00-07. In the release notes of this version, please search for ID 12843 for a detailed description of the patch.
To resolve this issue, upgrade to the latest service pack of PTV Vissim 10. The installation file for the latest service pack can be downloaded here: http://cgi.ptvgroup.com/cgi-bin/en/traffic/vissim_download.pl.
AutoCAD® DWG files allow to store multiple layouts within the same file. In PTV Vissim always that layout is used which in AutoCAD® was actived last.
Yes. The PTV Vissim Viewer can be used without any license. For more information please refer to the PTV Vissim Help > 'Introduction' > 'Using PTV Vissim Viewer'.
To update the Viewer to a new service pack, please check
You receive this warning when a vehicle passes the start of a travel time measurement twice.
This can happen if you have intersection-by-intersection static routing and/or U-turns. Then it is probable (given the random assignment of turning movements) that some vehicles are routed around the block and pass the same travel time measurement twice. There is no way to prevent this behavior other than defining longer static routes through the network or using Dynamic assignment.
The aggregated values are displayed only on links where 'Link Evaluation' is enabled. If you would like it to be enabled for the entire network, go to multi-select mode, select the entire network and enable 'Link Evaluation'.
In a saturated network, minor changes may lead to big consequences. For instance, due to a slight variation of green time, the number of vehicles passing through may be one vehicle less per cycle. This vehicle might be the critical one which leads to a queue that builds up continuously during the simulation whereas in the other case, the green time was just sufficient to accommodate the entire demand. These effects can also be seen on the field, where normal day-to-day changes may lead to different traffic situations.
A minor change (e.g. in lane change) can also lead to different results within the typical statistical boundaries. Generally speaking, a network which is not operating at capacity will react less to changes of the random seed.
Currently we are not aware of different results on different hardware. If you use the same PTV Vissim installation with the same simulation files on different computers and still get different results, please report these effects in detail to PTV Support.
There is no general rule to this as it depends on the PTV Vissim application:
- In a 10-km stretch of highway with low traffic volume simulated for one hour, travel times will be very stable and depend only on the distribution of desired speeds. Three to five runs should be sufficient.
- In an urban network consisting of some complex junctions with traffic actuated signal control, possibly including public transport priority, a lot of 'random' events influence the signal control (e.g. two trams approaching at the same time). In this case, more runs are needed to get a significant result, especially if one or more junctions operate close to capacity.
Formally, you have to estimate the variance coefficient of the measured value, e.g. travel time. You can do this by running the simulation several times with different seeds and computing the variance. Then you define a confidence level, say e.g. 5 %, and a tolerance interval for the result, say 10%. Then you need n simulation runs to be able to say, that 'with probability 95% the real mean value of travel times lies within the interval measured value +/- 10%.' n is given by the formula: n = t² * v² / e², where t is the value from the t-distribution for the given confidence level, v is the variance coefficient (standard deviation / mean) of the measured value, and e is the tolerance (in this example: 10%).
You can determine the mean speed by travel time measurement - dividing the length by the average travel time gives the average speed. However, this only works if only one shortest route is used from origin to destination.
The data will always collect for all vehicle types. If you will need the results for any specific vehicle class you have to select it separately: Evaluation > Configuration > tab 'Result Attributes' > 'Additionally collect data for these classes'.
You can evaluate the LOS for intersections using node evaluation.
The LOS in PTV Vissim is comparable to the LOS defined in the American Highway Capacity Manual (HCM) of 2010.
You will find an example in the training directory: Help > Examples > Open Training Directory > Evaluation > LOS With UD Thresholds.inpx.
This feature is not available anymore.
Workaround: Rerun the simulation runs from the start, using multiple instances of PTV Vissim in parallel.
The random seed influences many aspects of the model. It merely changes the start values of the random value generators used internally in the model. These values influence the arrival times of vehicle in the network, the stochastical variability of their driving behavior and also selection of a certain distribution value wherever distributions are used (e.g. dwell times, speeds, colors etc.). There is no seed that replicates 'real life' better than another. It's more comparable to the daily changes of the traffic patterns at the same location.
There is likely a 32/64-bit mismatch. After compiling the DLL in the bit-version matching that of PTV Vissim, you should no longer receive this error.
1) Register PTV Vissim as COM server (try with administrator credentials):
Help > Register COM Server
2) Check the used class ID to meet the correct release and architecture:
c:\Users\Public\Documents\PTV Vision\PTV Vissim 10\Examples Training\COM\Basic Commands\COM Basic Commands.bas
3) Install the current service pack.
4) Use instead of late binding ('CreateObject') early binding ('Dim Vissim As New VISSIMLIB.Vissim') with a set reference to the VissimXXX.exe (Excel VBA editor: Extras > References)
Example test scripts:
- Make sure Python27 is installed in C:\Python27 or C:\Program Files\Python27\ matching the architecture (32/64 bit) of PTV Vissim.
- Make sure this path is added to the Windows 'Environment Variables'.
- Make sure to install PyWin in the architecture (32/64 bit) matching the architecture of Python.
- Install the PTV Vision Python Setup from:
- Register PTV Vissim as COM server (try with administrator credentials): Help > Register COM Server
- Install the current service pack.
Reference: ch. 2: 'Executing Scripts from within Vissim' in:
c:\Program Files\PTV Vision\PTV Vissim 10\Doc\Eng\Vissim 10 - COM Intro.pdf
Yes, you can apply for free trial versions on our homepage: https://www.ptvgroup.com/en/solutions/products/ptv-vissim/demo-version/.
In this case, we recommend installing a second standalone installation of the release version and then applying the desired service pack update to it.
Follow these steps:
1) Visit the PTV Vissim and PTV Viswalk Service Pack Download Area (http://cgi.ptvgroup.com/cgi-bin/en/traffic/vissim_download.pl).
2) Click on the desired release version.
3) Click Download next to where 'PTV Vissim Setup' is listed in the Product column. (Depending on the release version, you can download files in an EXE or ZIP file format.)
4) With this downloaded file, install PTV Vissim as a second standalone installation.
5) Back on the PTV Vissim and PTV Viswalk Service Pack Download Area page, click Download next to the desired service pack.
6) With this downloaded file, install the service pack, making sure to select the correct installation.
Please check the following points:
- Is the necessary version of the Microsoft® .NET framework installed on all clients? (see Vissim installations manual for .NET Framework version information)
- Do the clients have write access to the Vissim/exe directory on the server?
- In the 'local intranet' settings of each client, is 'Full trust' activated? To find this setting, go to: Control Panel > 'Administrative Tools'
and select the Microsoft® .NET Framework Wizards. Choose:
Adjust .NET security > Change settings for this computer > Next > local intranet
and move the slider to 'full trust'. Confirm with: Next > Finish.
In addition to the typical specifications of a common PC, these are the main requirements for the current PTV Vissim version:
Windows® 8/8.1/10, Windows Server 2012/2016, 64-bit processor
Processor (CPU): Core i7/i9 or equivalent Xeon processors (recommended)
Clock speed: min. 2 GHz (faster computer speed results in faster simulation speed)
Cores: 1 core (min.); 4 cores or more (recommended)
Memory (RAM): 4 GB (min.); 8-16 GB (recommended). For large networks containing many vehicles and/or pedestrians, more RAM may be necessary.
Hard disk space: Up to 2 GB depending on the installation settings
Hardware lock (dongle) protection: 1 USB port
Screen resolution: 1280x800 or 1366x768 pixels (min.); full HD (1920x1080 pixels) or higher resolutions (recommended)
Graphics card: For 3D Graphics OpenGL® support is recommended. PTV Vissim 11 also supports DirectX but not all functions.
- Release versions are independent program versions which can be updated with service packs.
- Service packs include new features and bugfixes. They can only be used to update the corresponding release version, which means that e.g. service pack 11.00-06 requires a base installation of PTV Vissim 11. The updates are cumulative, meaning that the latest service pack includes all earlier ones.
Setups for the current releases can be found at:
All setups and service packs are here:
The language can only be changed by a new installation. Your VisVAP is in the wrong language, because this was selected during the installation of PTV Vissim.
We recommend installing PTV Vissim again using the current setup: https://cgi.ptvgroup.com/php/vision-setups/?lng=en&view=all.
Yes, the function is still available. Open the Links list and choose the relation 'Static vehicle routes'. The synchronization button has to be active. In the list on the left side, you can select a link and in the list on the right side you can see which routes lead via the selected link.
The model uses the psycho-physical car-following model developed by Wiedemann. It uses vehicle-driver-units that incorporate several stochastical variations. Thus there are virtually no two vehicles that have exactly the same driving behavior.
For lane change a related rule-based model is used that was originally designed by Sparmann.
Continuous development of both models ensures up-to-date driving behaviour in PTV Vissim.
You cannot accelerate one simulation run by using multiple computers, but you can use multiple computers for running different simulation runs, e.g. different scenarios or different random seeds. There is no functionality yet in PTV Vissim to distribute the simulation runs on different computers such as the PTV Visum calculation server.
The maximum acceleration/deceleration curves define the physical limits of a vehicle type. The desired acceleration/deceleration curves model the typical driver behavior.
The desired acceleration is the acceleration that the vehicle uses to reach its desired speed at free flow (i.e. not influenced by any other factors).
1) Following distance (FollowDist): Distance to the interaction object in [m] before the time step if the interaction state is not 'Close up'. If the interaction object is a vehicle, then distance is measured from the front of the vehicle to the front of the preceding vehicle; whereas if it is an object, it is measured from the front of the vehicle to the start of the object. If the vehicle interaction state is 'Close up', then it is the distance to the expected waiting position of the preceding vehicle or to the preceding object.
2) Headway (Hdwy): Distance to the preceding active object in [m] before the time step. If the active object is a vehicle, then distance is measured from the front of the vehicle to the front of the preceding vehicle; whereas if it is an object, it is measured from the front of the vehicle to the start of the object. Note: A vehicle or a red signal head is an active object; a green signal head is an inactive object.
3) Safety distance (SafeDist): Desired safety distance in [m] before the time step. It is based on speed if the interaction object is a vehicle (measured from the front of the vehicle to the front of the preceding vehicle); otherwise it is ax (individual standstill distance).
You can use a command line parameter as follows:
vissim.exe [filename.inp] -s10.
This will run the simulation of [filename.inp] 10 times from start to end.
A Poisson distribution is used for the times when a vehicle enters the network. The user can choose whether these arrival times will be determined entirely before simulation start (to allow for the exact amount of vehicles).
Comprehensive default values are supplied for vehicle types and classes as well as for driving and lane change behavior. The parameters of motorized traffic originate from research work done by the University of Karlsruhe.
A simulation always starts with an empty network. Thus warm-up periods need to be included in order to get realistic results. This is done by enhancing the simulation period by the warm-up period and set the start of the simulation (time of day) earlier by the same amount of time. Make sure that all evaluations start after the warm-up period (by changing their start time).
Yes, any type of pedestrian crossing can be modelled, including zebra crossings, permitted flows (where turning vehicles need to yield to pedestrians) and signalized crossings.
See the '..\Examples\Training\SignalControl' directory on your standard PTV Vissim installation for examples on these topics.
Please see the attribute 'additional level' for sections. Using it you can measure the number of pedestrians on a ramp.
Yes, this is possible with the optional pedestrian module PTV Viswalk.
As an alternative (without the pedestrian module), PTV Vissim can keep track of passenger flows for each transit line and stop (without visualizing them) in order to compute the dwell times of the train/bus at a stop for realistic public transport operation.
Fixed time signal control is included in the standard license. The add-on VISSIG provides additional functionality in the signal program editor beyond the PTV Vissim standard version. Models of several standard controllers for traffic actuated control are available as separate, independent products. Also available is VisVAP, a graphical flow chart tool to develop and edit an own vehicle actuated signal control logic including any type of special features (e.g. PT priority, railroad preemption, variable message signs on motorways etc.).
There are basically two options:
1. For a static offset you may 'shift' all timings of a signal control using the offset attribute in the 'Signal Controller' window.
2. For a variable offset in combination with vehicle actuated controllers you may link two or more controllers using 'Signal Control Communication'. You can link signal controllers which support communication with other control devices.
For additional information please check the PTV Vissim manual 'Linking SC'.
It depends on the issue. If you have problems to start PTV Vissim, then we need different analysis files. If you have an inquiry relating to your model or your results in the software, then we need the network (*.inpx) file and all associated files, e.g. signal controller files, COM script files, files related to scenario management, etc.
These are the analysis files we may need:
Note: Applies to PTV Vissim 11.00-06 and earlier versions. Instructions are provided for PTV Vissim 11 but also apply for earlier versions.
1) Start command prompt (Start > Run, enter cmd > Enter).
2) Move to the Exe directory of the PTV Vissim 11 installation (e.g. cd C:\Program Files\PTV Vision\PTV Vissim 11\Exe).
3) Enter the following command: vissim110 -o -flush
4) Reproduce the error and leave PTV Vissim open.
5) Open the directory EXE\ of your PTV Vissim installation.
6) Start VDiagGUI.EXE by double clicking on the file name.
7) Choose the tab 'Hotline Package'.
8) Ensure that all diagnostics files are selected.
9) Press the button 'Create'.
Note: Applies to PTV Vissim 11.00-07 and later versions. Instructions are provided for PTV Vissim 11 but also apply for later versions.
1) Start command prompt (Start > Run, enter cmd > Enter).
2) Move to the Exe directory of the PTV Vissim 11 installation (e.g. cd C:\Program Files\PTV Vision\PTV Vissim 11\Exe).
3) Enter the following command: vissim110 -o -flush
4) Reproduce the error and leave PTV Vissim open.
5) Open the directory EXE\ of your PTV Vissim installation.
6) Start Diagnostics.exe by double clicking on the file.
7) Choose the tab 'Support Package'.
8) Ensure that all diagnostics files are selected.
9) Press the button 'Create Support Package'.
1) Reproduce this error and leave the error dialogue box open.
2) Press CTRL + ALT + DEL to open the Task Manager.
3) On the Processes tab, right click on the PTV Vissim process and click 'Create dump file'.
4) Task Manager will create a dump file in e.g. C:\Users\Documents\AppData\Local\Temp\procname.DMP.
Start > Programs > CodeMeter > CmDust
This tool creates a file called CmDust-Result.log (the containing folder is opened automatically). If you are using a network license, we need the file from client and server.
Taskbar > System tray > CodeMeter Control Center > License > License Update > Next > Option 'Create license request' > Next > Option 'Extend existing license' > Next > Commit
Please refer to the following documents for any further instructions:
- Chap. 7.1 (Direct Support > 4) Creating a CmDust report
- Chap. 6.1 Creating a context file
The manual and setup file (*.exe) for EnViVer can be downloaded on the following page: https://cgi.ptvgroup.com/php/vision-setups/.
Yes, generally, models built in earlier releases of PTV Vissim can be read in later releases.
Network files created in VISSIM 5.40 or earlier have the extension *.inp, whereas those created in PTV Vissim 6 or later have the extension *.inpx.
*.inp files created in VISSIM 5.30 or earlier must first be saved in VISSIM 5.40-13 before they can be opened in PTV Vissim 6 or later versions.
We do not guarantee that the same results can be reproduced between different releases or even between different service packs.
All the window size and placement settings are stored in the registry. To restore Vissim to the default settings, goto Edit > User Preference and click the button 'Reset dialogue positions'.
Check the following:
- Delete all speed distributions that are not used in the simulation (especially those with higher speeds).
- Check priority rule parameters. Avoid long gap times or headways in combination with multiple look-back paths.
- Multiple look-back paths can also be avoided by reducing the driving behavior parameter 'Look back distance' for all links/connectors where applicable (e.g. at parking lots where each space is modeled on an individual link - such as for diagonal or perpendicular parking).
- At roundabouts, reduce the amount of 'small' connectors (that are used for routing purposes).
Fixed time signal controls are not stored in the INPX file directly but in a separate SIG file for each signal controller (apart from the file extension this is similar to all other types of signal controllers). Hence all SIG files referenced by an INPX file need to exist at the correct location.
Most likely one of the following reasons causes the problem:
the online help is not stored on a local drive
the # character is used in the path of the Vissim installation
In both cases the online help will not function properly.
Problem (1) is caused by a Microsoft® security patch that blocks executing help files on remote drives. To overcome this problem the easiest way is to install Vissim locally or on a virtual machine. If this is not possible or not desired, system administrator find another solution in the Microsoft® knowledge base.
To overcome problem (2), Vissim needs to be installed in a path without using any # characters.
In general it is possible to open files in lower versions of PTV Vissim which were built in higher releases of PTV Vissim. But we do not support downward compatibility and we give no guarantee that files which were created in higher releases of PTV Vissim are also readable in lower releases.
If you open the file in lower releases it is possible that there are some warning messages. You can read this messages in detail and try to change your file in the releases in which you built the model and afterwards try to open it in the lower release again but we give no support for it.
Generally unknown parts (developed for higher releases) will be ignored.
1) Choose Edit > User Preferences.
2) Choose the entry GUI > General.
3) Click the button 'Reset dialog positions'.
Yes, the multi-thread capability of PTV Vissim takes advantage of multi-core-/multi-processor computers if a large amount of vehicles is simulated. A multi-core-/multi-processor PC is also advisable if another application should run besides a PTV Vissim simulation run.
You can reach PTV Support via this web form:
This web form is pre-filled with important information such as your software version, operating system, and licensing details when accessing it within PTV Vissim via the menu Help > (Technical) Support.
Please describe your request as accurately as possible, i.e. which steps lead to a crash. Any solution or workaround will be provided as soon as possible.
Maintenance customers are also supported on modelling issues and software handling.
Feel free to make suggestions for improvement and product development.
This information you can find in the release notes file that is contained in every Vissim installation and service pack in the \Doc\Eng folder. It can also be viewed on our setup website: http://cgi.ptvgroup.com/php/vision-setups/?lng=en.
Along with each service pack, a setup of the updated PTV Vissim Viewer version is also published in the service pack download area (http://cgi.ptvgroup.com/cgi-bin/en/traffic/vissim_download.pl). This site also contains instructions on how to use the updated Viewer version.
If you have a network that was last saved in PTV Vissim 11 and want to open it in ealier versions, first open it and save it in PTV Vissim 10.00-11. Then it can be opened in PTV Vissim 10 or earlier versions.
Please check if you have sufficient free space on your hard disk.
Yes, there are built-in hotkeys in PTV Vissim, and the following lists the most commonly used hotkeys. You can also create custom key combinations for menu commands. For more information on this as well as a full list of all available hotkeys, refer to the following help page: https://cgi.ptvgroup.com/vision-help/VISSIM_11_ENG/#2_Programmbedienung/Tastenkombinationen_Standard_verw.htm.
- Ctrl+A: In 2D mode: Toggle wireframe
- Ctrl+B: Show or hide backgrounds
- Ctrl+D: Toggle 3D mode
- Ctrl+E: During simulation run: Toggle color of vehicle status
- Ctrl+M: Measure distance
- Ctrl+N: Activate or deactivate Simple Network Display
- Ctrl+Q: Activate or deactivate Quick Mode
- Ctrl+R: Recalculate Spline
- Ctrl+U: Switching the simulation time format for the status bar
- Space bar: During a simulation in Simulation single step, execute the next step.
- Plus key: If a continuous simulation has been started, increase the speed of the simulation.
- Minus key: If a continuous simulation has been started, reduce the speed of the simulation.