New features and bugfixes in VISSIM (2007-12-19) =================================== (+ = new features, - = bugs that have been fixed. Details about the fixes are in brackets.) Version 5.00-02 (2007-11-09) ---------------------------- + Conflict Areas: Can be created now at places where no traffic can arrive from upstream (e.g. because no vehicle inputs have been defined yet). + Routing Dialog: The handling of broken routes can be started through the new context menu item "Check" in the routes table. This new menu item is available for routes of type Static, Partial, Parking and Closure. The new item "Check" can be selected if there is at least one route selected (marked with blue) in the routes table. A route is considered to be selected if at least one cell is selected (same as for "Zoom"). The checking is applied to selected routes only. + Network editor: Improved handling of "Segment" nodes (exported from VISUM, into an ANM or INP file): + Selection of a different node at the same position (overlapping containing rectangle) through the "next" button (circular arrow icon) in the selection toolbar or through the TAB key. + The link segments of the selected node are displayed in red. + Connector segments are displayed slightly less wide. + ANM Import: The file names for the *.panm and *.panmroutes files (where the original ANM data is saved) can be specified by the user. + ANM Import: Improved handling of routing import: + Routing import can be canceled by the user. + New option "[x] Complete routes after Import" (This option is active only if ANM data has been imported previously.) If checked: All Vissim routes are checked. Incomplete/broken routes are repaired if possible. All found errors (and the repaired routes) are listed in "Documents and Settings\\Local Settings\Temp\VISSIM\vissim_msgs.txt" If not checked: All Vissim routes are checked. Routes are not repaired, just checked. All found errors are listed in vissim_msgs.txt (same directory as above). + Adaptive Import Routing: If routes file doesn't differ from previous import, a warning message is displayed: "ANM Routing not imported, routes files do not differ". + Forced re-import of the same routes file: In order to re-import the same routes file again you can use the dialog ANM Import (not adaptive). You can now enter only a routes file here, no network/data file. This forces the re-import of routes, without comparing the routes files first. + ANM Import: VISSIM links and connectors representing zone connectors in the ANM (VISUM) network are created with "no vizualization" checked by default, causing the vehicles driving on them to be invisible. + ANM Import: (Right) turn on red movements are created in VISSIM (with stop sign, signal head and conflict areas). + ANM Import: Can read laneturn data from ANM file and create multi-lane links from it. + About Dialog: Hyperlink to the VISSIM FAQ web page. + Dynamic Assignment: New checkbox "Dyn. Assignment" in the node dialog (checked by default). If this checkbox is unchecked, the node is not used for the dynamic assignment network graph - it can be used for node evaluation, however, if the checbox "Node evaluation" is checked. (Attention: The "Edge Selection" dialog displays only the nodes with "Dyn. Assignment" checked.) - Multirun: All error messages are written to the same file name, so only the messages from the last run are saved. (This bug was introduced in version 5.00-00.) - Parking routes: If a parking lot is moved in the network editor so that a parking route referring it gets broken (because the parking lot cannot be reached from the routing decision) VISSIM crashes during the simulation run with an exception message ("fahren.cpp, line 2493" in the _exception.err file) if a vehicle selects a parking space from this parking lot as destination when passing the routing decision section. - A large Mr.Sid background image is displayed as a white rectangle if the height is larger than the width. - Read network additionally: VISSIM crashes if the new file contains a connector that has a display type that is not defined in the existing network. - The Ctrl-Shift-F10 warning window does not change the language when the user selects a different language in View/Options. - Display types: If a display type without a name is created and the *.inp file is written it cannot be opened again (parser error message). - Network editor: A double click on a data collection point and a subsequent click on OK in the dialog causes the data collection point to be removed from all data collections. - Network editor: A conflict area can disappear if its whole link is moved (even if the overlap still exists). - Network editor: If the start or end of a connector is moved VISSIM can display the "Complete route as shown?" dialog for routes that don't include this connector and with the buttons "Yes All" and "No All" disabled. [Now, only broken routes that include that connector are shown, and the two buttons are enabled, and there is an additional "Cancel" button to stop the check for broken routes.] - Network editor: "Segment" nodes (exported from VISUM, into an ANM or INP file) get corrupted by editing of links/connectors that belong to these nodes. This prevents the creation of a correct network graph for dynamic assignment or node evaluation. [Now, VISSIM tries to adapt the link segments assigned to the node.] - ANM Import: Wrong messages about broken routes in ANM routes import (the node numbers are mixed up). - ANM Import: Signal groups are sometimes duplicated in the created *.inp file which makes it impossible to open that file. - ANM Import: Wrong error message in routes import if a route contains only one node. - Adaptive ANM Import stops with the message "No split information found" if an edge in the node / edge graph is not found. (The edge had to be adjusted because one of the end nodes had to be reconstructed.) [Now there is no error message anymore but a warning that something went wrong and the user should review the generated geometry.] - Adaptive ANM Import: The written *.inp file can contain invalid link numbers for pavement markers at adapted nodes so that it cannot be read in again. Editing these pavement markers can cause an exception message, too. - Adaptive ANM Import: If only routes are imported the network is translated (so that the center of the network has doubled x and y world coordinates). - Adaptive ANM Import: Existing speed distributions are not used. - Adaptive ANM Import: The routes import crashes if the network graph of the existing VISSIM network is not consistent. - Adaptive ANM Import: Creates routing decisions without time period if only routes are imported and if the start time in the ANM routes file doesn't match the start time in VISSIM. [Now, the import is canceled with an error message.] - The adaptive ANM Import fails with the message "Unexpected begin / end of node ..." if 1. a zone or its connectors have changed and 2. the VISSIM node representing the zone at this connector was changed into a polygon based node, as recommended. The reason is that the new node representing the node is generated inside of the polygon of the old node which is not legal. - Adaptive ANM Import: VISSIM can crash if a link with a routing decision or desired speed decision needs to be split because of a changed node in the ANM data. - Adaptive ANM Import: Node geometry ís not created correctly for nodes that need to be created from scratch because of a reduced number of lanes. - Adaptive ANM Import: VISSIM can crash if some nodes for dynamic assignment must be deleted. - Adaptive ANM Import sometimes aborts with the message "Split not possible, not enough memory!", although there still is enough memory. This happens if there are old links in the network that need to be split more than once in order to create stubs where the new network elements can be connected. - Adaptive ANM Import: Node data is not adjusted if only detectors are removed from the lanes. Old detectors remain in the network. If the node is generated newly due to other differences, no new detectors are inserted, though. - Analyzer: When the generation of reports is canceled then restarted, the progress bar fails to reappear. - COM Interface: If a simulation run is started through the COM interface the vehicle behavior can be slightly different from the behavior when the simulation run is started manually: If a vehicle determines during a lane change that it overlaps with its trailing vehicle and if the middle of the trailing vehicle is in the direction of the lane change then the lane changing vehicle doesn't continue its lateral movement (e.g. to the middle of the lane if that is selected in the driving behavior parameter set). This can cause any kind of differences in the subsequent traffic flow. Version 5.00-01 (2007-09-25) ---------------------------- + Evaluations Database dialog: + Button to create a new Access 2007 database + Provider and data source is displayed - Conflict areas can be deleted if a spline or end point of an involved link is moved in the network editor so that the link coordinate of the start/end of an involved connector is changed. - License dialog: Does not show SCATS and Export3DMax at all, shows wrong value for Econolite ASC/3. - Chinese text is shown as ??? for internal data (vehicle type names, error messages, ...). - ANM Import / Public Transport Lines - VISSIM Line Stops: Generated VISSIM lines stop on all VISSIM PT stops on the line route, not only on the active stops from the ANM data. Generated VISSIM line stops use default dwell time distribution instead of a dwell time distribution according to the ANM data. - COM Interface: Using the enumeration methods to iterate over the vehicles from the IVehicles interface causes an exception message (assertion failed at line 185 of file COMVehicleIterator.cpp). - COM Interface: Vehicles inserted into a parking lot with the method AddVehicleInZone() or AddVehicleInParkingLot() and using the attribute DESTZONE or DESTPARKLOT don't use any path from the path file (*.weg). Version 5.00-00 (2007-09-06) ---------------------------- + ANM (Abstract Network Model) Import: New file format (XML) that is exported from VISUM 10.0 and can be exported from other traffic planning software, too. This network model is based on nodes and edges with optional node details (lanes, lane turns, pockets, pedestrian crosswalks, control type, signalization, detectors). The actual geometry of the VISSIM links and connectors is created in VISSIM. Demand and routing can be imported either for dynamic assignment in VISSIM (creating a matrix and a path file with volume data which is used in the first simulation run) or for static routing (creating vehicle inputs and routing decisions with static routes). + ANM Adaptive Import: If a VISSIM network has been imported initially from an ANM file VISSIM saves the original ANM data, even after manual changes in the VISSIM network editor. If a changed ANM file is read through the adaptive import VISSIM uses only the changes in this ANM file (compared with the original ANM data) to change the VISSIM network accordingly. If a node has been changed in the ANM file only this node and the connected edges are created from scratch by the adaptive import, so any manual geometry improvements in this (small) part of the network are lost. All manual changes in the VISSIM network in nodes (and edges) that are not affected by the changes in the ANM file stay intact, however, as do VISSIM network objects that have been added only in the VISSIM network editor. This allows to export changes in a VISUM network into a previously exported VISSIM network which has been refined manually in the meantime without losing much of the work in the VISSIM network editor (code word "SUMSIM"). A different demand scenario (matrix and assignment result) from VISUM can be loaded through adaptive import as well - in this case the VISSIM network stays completely unchanged (unless a necessary parking lot or route needs to be added). + Link types are split into link behavior types and display types. Display types have additional 3D display features: + Curved textures (texture follows the curvature of link) + "Crisp" textures (no mipmapping for road markings etc.) + Shaded side walls (instead of plain color) of links with thickness > 0 + Colored/texturized side walls and bottom similar to link surface (without curved textures) + Parameters for display of railroad tracks + View / Options / Colors: User selectable maximum resolution for background images (raster and vector graphics) in 3D. (The maximum resolution which provides correct display of background images in 3D depends on the graphics hardware in the computer and on the number of images loaded at the same time.) + Analyzer now gives the user the ability to select which reports they would like to see generated. All reports are selected by default, however, the user can deselect the report by right clicking on the report title and selecting "DeSelect Report" from the pop up menu. They can also select reports that are not selected by right clicking and selecting "Select Report" from the pop up menu. + Analyzer: Time intervals for a report can be added through a right click on "Time interval". + Analyzer: Additional hidden column "from link / to link" for the detailed movement description in the Excel sheet. + Analyzer allows the user to pause, cancel, and restart report generation using the pause and cancel buttons that appear after report generation has started. + Relative volumes of routes can have decimals. + 3D Signals: Maximum z-position, height and arm length increased. + Info dialog: When the user clicks the hotline link, additional data (Windows version and service pack, VISSIM version and service pack, dongle and client no.) is automatically entered in the hotline web form. + Splash screen at startup. + COM Interface: Access to connector attributes lane change distance and emergency stop distance. + COM Interface: Access to parking lot attributes zone and relative flow (read only). + COM Interface: Access to analyzer reports: + Allow to switch the Analyzer database on/off from the Evaluation interface, + Allow to open the Analyzer Report dialog. + COM Interface: Access to multirun parameters and start of a multirun process. + COM Interface: Screenshot functionality. + COM Interface: Vehicle attributes DESTPARKLOT and DESTZONE are writeable (for a vehicle in a parking lot, instead of assigning a complete path). The route selection (and the destination parking lot selection if DESTZONE is set) is done according to the dynamic assignment model. + COM Interface: New method AddVehicleInZone which places a vehicle in a random parking lot of a given zone. The origin parking lot is selected according to the relative volumes of the parking lots as in dynamic assignment. + V3DM 1.40: Import of Sketch Up (*.skp) and DWF models. + Dynamic Assignment: Path volumes (if the *.weg file is written by the ANM Import) can have decimals (as in a VISUM assignment result). + Dynamic Assignment: Overlapping nodes are detected correctly even if an imported node (defined through link segments) overlaps with a node that has been created manually (defined through a polygon). + VISSIM 5.00 is used as node previewer for VISUM 10.0 (using ANM). - Conflict Areas: A vehicle on the minor road that determines that it can't brake anymore to a stand before the conflict area doesn't brake at all even if it will be in the conflict area only a little bit too early. [After the bugfix, vehicles that determine that they will have a rear conflict (because they leave a crossing conflict area too late or are too late completely inside a merging conflict area) still don't brake and hope that the conflicting vehicle will see them and can brake to avoid the collision, but vehicle that determine that they will have only a front conflict (too early inside the conflict area) do brake now and hope that the conflicting vehicle leaves earlier respectively moves faster.] - Conflict Areas: If a reduced speed area inside or upstream of a conflict area assigns a higher desired speed to a vehicle than the vehicle's previous desired speed VISSIM can crash when such a vehicle approaches that reduced speed area. - Conflict Areas: If a merging conflict area without priority (red/red) that was blocked because of a downstream queue becomes free and there are standing vehicles on both entering links they won't move because the required safety distance after entering ist not met. (This is not actually a bug as behavior with red/red was not specified before.) [Now, the behavior is approximating alternating entry from both links.] - Conflict Areas: If a connector ends on its destination link inside a crossing conflict area that refers to its start link vehicles that plan to use this connector wait for themselves: They brake to a stop before they move on. - Reading of a snapshot file with a vehicle on a parking lot route fails with the following error message: "Internal error while reading snapshot. Guard SNP_END is missing." The error file *.err contains the following entry: "Snapshot data is inconsistent with the network! Return value of readSnapshot() = 31." - Saving a snapshot can cause an exception message if a previous simulation run has been stopped at a moment when a vehicle from a vehicle input could not enter the network because of insufficient room. - The PT stop alighting probability (in percent) is saved as a rounded value without decimals in the *.inp file. [Now, two decimals are saved.] - VISSIM issues an exception message with "Assertion failed in fahren.cpp, line 4285" in the *_exception.err file. - Distribution of green times evaluation can crash if the evaluation file name (including multirun run index) including path is longer than 80 characters. - The queue counter evaluation file contains an additional row (time = (end of evaluation period + interval) or end of simulation, which ever is smaller) if the end of the evaluation period is smaller than the simulation duration. - Lane Change Evaluation: The time period entered in the Filter dialog is ignored. - VISSIM displays the German error message "Unbekannter Fehler beim Netzaufbau!" if more than 99 discharge rate evaluations are defined in the *.inp file. The number of read discharge evaluations is not reset before a new *.inp file is loaded, so opening the same file (with fewer evaluations) several times causes the same error message. - Multi-run can crash if writing to the Analyzer database is activated. - Multi-run can crash if node evaluation writing to the database is activated. - A multi-run simulation run with a certain random seed can have different results from a single run with the same random seed, e.g. public transport dwell times are different when drawn from a distribution. - Analyzer Reports / QueueLenghts: No data is shown in Excel sheet for queue lenghts if the Analyzer database has been created with the VISSIM language set to anything but English. - If the SC dialog is opened and closed with OK for a VAP SC during a simulation run (e.g. for switching the debug mode on or off) the current signal state run time values of all signal groups (reported by the VAP function t_green/t_red and the green time evaluation) are reset to zero. This can cause VAP signal controllers to behave differently from a simulation run during which the SC dialog is not opened. - Link dialog: The key doesn't work after edting a field (for example the number of lanes). - Vehicle input dialog: can crash upon click on OK. - Vehicle input dialog: Paste into an empty name field is not possible (the paste menu item is disabled). - Vehicle input dialog: Negative values are allowed for vehicle inputs. - Color distribution dialog: Editing does not work correctly if the share value of one of the first colors is changed to 0. - Emission Calculation dialog (Vehicle Type / Special): The default value (1.0%) for the load percentage makes no sense. [Now, it's 100%.] - Raster background images (BMP, JPG, GIF) are displayed in 3D as a white rectangle on computers with a simple (not high-end) graphics card. - 3D Signs: In the 3D signal default values, if you change the scale, all the existing signs change their scale. Changing the scale value in the *.inp file for an individual sign does not have any effect. - VISSIM beeps each time that a key is pressed (for a keyboard shortcut) during a simulation run if a vehicle information window has focus. (This bug was introduced in version 4.30-01.) - COM Interface: The NodeEvalution interface can not be instanciated. No method is available. - COM Interface: Vehicle.AttValue("LinkCoord") ignores the current unit for distance, passes the coordinate always in meters and interprets a new value as meters. - COM Interface: If a vehicle is added with AddVehicleInParkingLot() during a simulation run but is not assigned a path (attribute PATH) immediately an exception message is issued (assertion failed in line 1206 of PARKP.CPP). - Dynamic Assignment: Split Link: Node segment lists are not adjusted. - Dynamic Assignment: Alternative path search adds link cost (and surcharge) to the expected travel times once per iteration, so the expected travel times increase in each iteration. - Dynamic Assignment: An unknown exception message occurs when using link costs of 1,000,000,000. [Now, link cost values are limited to 1,000,000.] - Dynamic Assignment: The random number sequence used for random round of decimal values of matrix volumes (e.g. because of a scaling factor in the matrix file) depends not only on the current random seed but also on the random seed of the first simulation run after the network has been loaded. Setting the random seed to a certain value produces the same results as in a previous run with the same random seed only if there was no previous simulation run in both cases or if the very first simulation run after the network had been loaded used the same random seed in both cases. Example: A) load network, multi-run start seed 2, seed increment 10, number of runs 3 (=> random seeds 2, 12, 22) produces the same result in the third run (random seed 22) as B) load network, multi-run start seed 2, seed increment 20, number of runs 2 (=> random seeds 2, 22) in the second run (random seed 22) but C) load network, multi-run start seed 12, seed increment 10, number of runs 2 (=> random seeds 12, 22) produces a different result in the second run (random seed 22) because the first run used the random seed 12, not 2. - VISSIM issues an exception message ("Attempt to divide by by zero" in the *.err file) when building the network graph (nodes/edges), e.g. when the edge selection dialog or the path dialog ("Auto routing selection") is opened if there are no links in the network but at least one node. - VISUM Export (Nodes/Edges): The coordinates of the zone centroids are not correct. Version 4.30-03 (2007-06-21) ---------------------------- + Vehicle input and routing dialogs are modeless so it's possible to navigate and zoom in the network while they are open. + Network editor: A route (static, partial or closure) can be selected through a click on the destination section (with previously selected destination link) without previous selection of the routing decision. + Node evaluation compiled data output: The output file name includes the current run index if VISSIM has been started with the command line parameter -s or if the simulation run has been started through COM and the RunIndex has been set to a value >0. + COM Interface: Parking lot world coordinates X and Y are accessible. + Dynamic Assignment: New (much faster) implementation of "Create Static Routing". No vehicles are placed in parking lots anymore but the path volumes from the last iteration written to the path file are used. The vehicle input volumes and the relative volumes of the static routes are taken directly from the path volumes in the path file, the traffic compositions are derived from the matrix files. - Read additionally: "Keep original world coordinates" doesn't work right: The read network is not at the right position. - Reading additionally an INP file with data collection points creates duplicate data collection numbers. When you try to change a duplicated data collection number VISSIM crashes. - Conflict Areas: Vehicles can sometimes ignore a conflict area further downstream of a slow vehicle or a reduced speed area. This can cause them to enter an upstream conflict area even if they should not because they cannot leave it without a downstream conflict. [Vehicles still don't look for conflict areas beyond the number of observed vehicles set in the driving behavior parameters. This means that with the default value of 2 a vehicle ignores all conflict areas downstream of a reduced speed area and a real vehicle, for example. Thus it is recommended in large intersections where movements pass several conflict areas to set a higher minimum lookahead distance to make sure that the vehicles consider all conflict areas before entering the intersection.] - Conflict Areas: Vehicles on a multi-lane minor road (e.g. a dual left turn) that have already passed the start of a conflict area on an adjacent lane behave as if they were already inside a conflict area on their own lane, i.e. they continue to drive in order to leave that conflict area even if subsequent conflict areas are not free. - Conflict areas are always drawn with yellow color in other editor modes even if a different color is selected in the network element configuration display dialog. - Analyzer Evaluation / Analyzer Database / Analyzer Reports: Incomplete data in table QUEUE_DATA: only queue lengths > 0 are written. This results in completely wrong data in Analyzer Reports / Queues. - Analyzer: Travel time min/max values are wrong. - Analyzer: Movements are not correct with left-hand traffic. - Analyzer: Volumes and delay differ from the node evaluation with identical parameters. (The analyzer uses aggregation by time of passing the travel time start section while the node evaluation uses aggregation by time of passing the destination section.) [Now, the analyzer does the latter, too.] - Analyzer Database Table SIMULATION: Column RunIndex is not correct (always 0) if the simulation has been started via COM even if RunIndex had been set explicitly in the COM script. - Analyzer dialog: Allows selection of multiple time periods (but only one is used). - View / Options / 3D Signal Property Defaults dialog, 3D Signal Post dialog, 3D Signal Arm dialog: Several spinners where negative values should be possible don't work anymore and values that are entered manually are ignored. The shown values are much too big, too. - Presentation / 3D Video / Anti-Aliasing: When this option is activated in 3D mode, then switched to 2D mode and returned to 3D mode, the check-mark in front of "Anti-Aliasing" is gone even though the option still seems to be active (i.e., if you click on Anti-Aliasing again then no checkmark appears, only if you click it a second time). Dito for "Stereo (2 AVIs)". - Backwards animation (*.ani) replay shows all vehicles at wrong positions. - Link evaluation: The attribute Segment start Y has wrong values. (Segment end X/Y and Segment start X are okay.) - PT vehicles on PT Lines ignore their route if they enter the network at a simulation time greater than 99999. - Driving behavior parameters set dialog: if there is more than one line in the Min. Lateral distance table the values of the first line are saved for all other lines, too. - Signal control dialog: VISSIM crashes after editing a SC number and selecting Copy from the context menu without selecting another SC before. - Node evaluation: Emission parameters are not written (and are removed from the configuration if the configuration dialog is opened again) if the VISSIM license doesn't include the module "Emissions". - Node evaluation - compiled data - database output: no data is written to the database for this evaluation. [This bug was introduced in version 4.30-02.] - Network Editor: If a connector from a link to itself is moved completely to another link it remains in all routes that used it in its old position in the link sequence. This can cause surprising confirmation requests for completion of routes. [After the fix, the connector is deleted from all routes when its start or end is moved to a different link.] - VISSIM crashes after a double click on a vehicle to open the vehicle information window if the FZI file isn't available anymore because it was removed manually from the project directory after the network was loaded. - Parking lot dialog: Wrong world coordinates are displayed. - Vehicle Input dialog: takes a very long time to close if there are many cells (vehicle input links times time intervals). - Chinese text is shown as ??? for internal data (vehicle type names, error messages, ...). - COM Interface: It's not possible to start more than one instance of VISSIM through the COM interface. Only one VISSIM is started and used by each VISSIM object created by CreateObject. - COM Interface: Vehicles.GetArrived() doesn't work anymore. It returns always an empty collection of vehicles even if vehicles have arrived during the last simulation time step. - Export 3DS MAX: The exported network doesn't match the exported ani.txt file (world coordinates are wrong). - Dynamic Assignment dialog / Create Static Routing: If not enough memory (RAM) is available, VISSIM displays an exception message (volume <= MAXLONGCARD). - Dynamic Assignment: Edge selection dialog: If the selected edge has a different closure state from the first edge in the listbox VISSIM displays an error message when a different time interval is selected (and so the first edge is selected). - Dynamic Assignment: Edge selection dialog: A click on "Close all edges" or "Open all edges" doesn't change the state of the checkbox "Edge closed" even if the first edge (which is selected) has now a different state. Version 4.30-02 (2007-05-22) ---------------------------- + Background image file format Enhanced Compression Wavelet (*.ecw) added (fixed resolution only). + COM Interface / Dynamic Assignment: The Kirchhoff exponent and the extended parameters for "Search New Paths" are accessible through the interface DynamicAssignment. - Crash during a simulation run if a vehicle on a partial route passes a parking lot decision if the last link of its route is the last link of its original route (after the partial route), too. - Conflict areas are ignored by vehicles with car following model "no interaction" (usually pedestrians). - Crossing conflict areas: Vehicles on the main road brake unnecessarily when a vehicle on the minor road is inside the crossing conflict area even if they can expect to pass safely behind this vehicle without braking. - Merging conflict areas are kept free by vehicles from the main road. - Vehicles that have a small desired deceleration value (e.g. buses) sometimes cannot pass a conflict area if they are already standing in front of it and planning to move only up to a fixed obstacle downstream (e.g. a signal head ot the end of a bus stop). - Conflict area dialog: Wrong visibility distance value is displayed if "feet" is selected as unit for small distances (meter value multiplied by 0.3048 instead of divided by 0.3048). - Multiselect link dialog: Crashes upon Cancel or OK on Vista and sometimes XP without installed VisualStudio. - Multiselect link / lane closure dialog can crash if the selected links don't have the same lane closures for all vehicle classes. - Network editor: If the compass is in edit mode VISSIM can crash if a network element (e.g. pavement marker, desired speed decision, stop sign, detector) is selected or a new one is created. - Network editor: VISSIM can crash if a link is split that contains a reduced speed area. - Analyzer: Wrong directions are listed for turn volumes. (The direction of the turn is calculated from the second last link segment.) - Analyzer: Generating Analyzer Reports fails on Windows 2000 (possibly only with with Office 2000) with the error message: "Volumes: Bad variable type. (DISP_E_BADVARTYPE)". - Data collection / measurement dialog: Internal data collection points (for travel time measurements and detectors) are shown, some as number zero. This causes an exception after a click on an "Auto" button. - Multirun doesn't write the error notes to different files. All runs use the same file and delete the data of the run before. - Multirun / External signal control: A dialog appears in multirun mode after each simulation if an external signal controller produced an error file. This prevents unsupervised runs. - Signal Control dialog / SigTimTbl/LDP Configuration: Rows/columns with internal values (e.g. signal group state, detector state) are displayed multiple times (and saved so to the configuration file after changes) if there are multiple *.wtt files assigned. - Vehicle model distribution dialog: Error message "SelectVehic_E.dll not found!" upon click on the "..." button for the 3D model. - 3D Video Recording: Anti-Aliasing doesn't work anymore. - SynchroExport: aborts at the start of a simulation run. - 3DS MAX Export: Exported network can't be imported into 3DS MAX if a link's name contains a space or comma. - Dynamic Assignment: Exception message in Edge Selection dialog if closed edges are defined. - Dynamic Assignment: Exception message in Auto Routing Selection dialog if the cost file is not found. - Dynamic Assignment: VISSIM doesn't always write the *.weg file after the first iteration even if there is no prior existing *.weg file. This happens if you 1) open an *.inp file with an existing *.weg file, 2) remove the *.weg file from the working directory, 3) start the simulation without opening the dynamic assignment dialog previously. - Dynamic Assignment: Exception message ("Assertion failed on line 1561 in WEGE.CPP" in the *.err file) when reading the WEG file if all paths of a parking lot relation are closed for a vehicle type due to a connector closure. (This bug was introduced in version 4.30-01.) - Dynamic Assignment: Using "Alternative Path Search" or "Penalization of the shortest path" together with the option "Limit number of paths per parking lot relation" doesn't work properly. If a new path is found the penalized edge costs are used instead of the real costs to determine which path is deleted. - Dynamic Assignment / "Alternative Path Search": The "Stochastic edge penalization" and the "Penalization of the shortest path" ignore link cost values from the second pass on (use only travel times). - Dynamic Assignment: Searching new paths when using the option "Limit number of paths to N per parking lot relation" doesn't work in some cases. For example, if the option is activated with N = 1 and a (better) second path is found for a parking lot relation the old path should be removed. If this path cannot be removed because some vehicles are still using it this path is still counted as an already existing path and so the new path is not used although it is a better alternative. - Dynamic Assignment: Non-integer demand values from the OD-Matrix are truncated when the matrix file is read (instead of leaving them to be random rounded during the scaling of the matrix values). - Dynamic Assignment / Route Guidance: Doesn't work for most vehicles if connector closures are defined for certain vehicle classes or if the cost coefficients are different for at least one vehicle class. (Shortest paths are searched for one vehicle type set only.) Version 4.30-01 (2007-04-20) ---------------------------- + Keyboard shortcuts (e.g. Space/Enter for simulation single step / continuous) work if a vehicle information window has focus as well. + Synchro Import: + Updated calculation of storage for turning bays that are greater than half the distance between links. + Updated Offset Reference Value for Signal Timing based on Synchro sign value. + Dynamic Assignment: The relative volumes of parking lots can be adjusted to the total of the volumes from the current path file (*.weg) with the keyboard shortcut Ctrl-Shift-C. This can be useful for a different demand scenario (only new matrix file and path file) for a VISSIM network that had been exported from VISUM and then manually updated. + External Driver Model DLL Interface: VISSIM sends DRIVER_DATA_VEH_REAR_X_COORDINATE and DRIVER_DATA_VEH_REAR_Y_COORDINATE data to the DLL even if DriverModelGetValue (DRIVER_DATA_SETS_XY_COORDINATES, ...) returned 0. This means that vehicle rear world coordinates are available in an external driver model for vehicles on VISSIM links. - Animation recording: Vehicles from an animation file (*.ani) created in VISSIM 4.30-00 are not positioned correctly. The animation areas are off, too. [This bugfix doesn't fix *.ani files from VISSIM 4.30-00.] - If a simulation run is started once before and once after a multirun series with random seed increment the results are different (the random seed after a multirun series remains the one used in the last run). - Conflict areas: Vehicles don't pass a conflict area (even on the main road) if their (desired) speed is smaller than 2 m/s (e.g. pedestrians). - Conflict areas: A vehicle can sometimes pass a conflict area even if there is not enough room for its whole length before the next conflict area that it cannot pass (yet), so it stays partially inside the first conflict area. Vehicles on the conflicting link don't see these "stuck" vehicles and drive right through them. - Conflict areas: If a new merging conflict area is created on a newly created connector and its destination link the conflict area doesn't work before the network is saved and reloaded or the connector is edited again. - Conflict area dialog: VISSIM crashes upon selection of "show all possible conflict areas in" a node that includes real parking spaces. - Node labels are drawn at the wrong place, and zooming to a node from the node selection list doesn't work. - Dialog "Display Network Elements": Clicking on "Zone Number" for the parking lots enables the "Occupany" display and vice versa. Some label selections don't work (are set to "None" after click on OK). - Dialog "Vehicle Inputs": Fractional digits of volumes are not displayed and thus lost upon click on OK. They can't be entered either. - VISSIM can crash with an exception message during a simulation run with activated 3D visualization. - 3D visualization: Textures on 3D vehicle models are not transparent, so vehicle colors are not shown. - 3D visualization: The compass doesn't rotate in first person viewing mode. - Animation playback: 3D signals flash wildly with all bulbs on. - Link evaluation: Wrong error message ("no parameter defined") if no links are selected for evaluation. - Link evaluation / VISUM Export (*.net format): Some column headers include square brackets. - Error while reading a snapshot file of a network without detectors. - Evaluation database: Writing evaluation data to other databases than Microsoft SQL Server or Microsoft Access fails. [Now, all SQL:1999 conform databases should work.] - COM Interface: the attribute VOLUME of DynamicAssignment doesn't work. - COM Interface: Using AddPathAsNodeSequence() during a simulation run can cause VISSIM to crash. If AddPathAsNodeSequence() is called with a sequence of node numbers starting with an impossible node pair VISSIM crashes. - Dynamic Assignment: The volumes in path files (*.weg) exported from VISUM are not used correctly: The path volume of the first interval is used for all intervals. - Dynamic Assignment: The option "limit number of paths to x per parking lot relation" doesn't actually eliminate the worst paths when a path file (*.weg) is read. VISSIM ignores the cost values in the *.bew file (respectively the distances if there is no *.bew file yet). - Dynamic Assignment: Auto Routing Selection Dialog: If there is no *.bew file yet all path costs are displayed as 0.1 times the number of edges if the option "limit number of paths to x per parking lot relation" is enabled, otherwise all zero. [After the fix the distance is displayed as cost value in parentheses because this will be used for shortest path search in the first simulation run.] - Dynamic Assignment: If all paths of a parking lot relation in a *.weg file (exported from VISUM) have volume 0 none of them is used and the error message "No path found to parking lot X for vehicle N in parking lot Y" is written to the *.err file for each vehicle parked. - Dynamic Assignment: Route closures can cause VISSIM to crash if there is a path that includes a route closure up to its very end (i.e. path and route end on the same link). - Dynamic Assignment: VISSIM crashes during a simulation run if partial routes are defined that are not part of any static route in a network with dynamic routing decisions. - Dynamic Assignment: Messages of the type "No path from parking lot X to parking lot Y can be used because of the following edge closures:..." are written for zone relations without demand. - Dynamic Assignment: The message "No edge turn in the node 0 from node 0 to node 0 could be found" is written to the *.err file if a turning relation from a *.weg or *.bew file cannot be found in the current network. - Dynamic Assignment / Creation of static routing: The message "creation of vehicle inputs cancelled because of duplicate numbers" is shown when there are parking lots with an ID greater than 49249. - Dynamic Assignment: Wrong, truncated and untranslated error message "e Kantenstruktur der Datei <*.weg> stimmt nicht mit der aktuellen überein. Fehlermeldungen werden in der ERR-Datei aufgelistet" instead of a more detailed message mentioning the edge number. - Parallel version: Big link numbers (9 or 10 digit) cause the simulation to stop with an error message. Version 4.30-00 (2007-03-25) ---------------------------- + Support of WiBu CodeMeter license protection. + Conflict Areas: New network element for handling of conflicts between links (and connectors). A conflict area can be created at any position where two links/connectors overlap (unless the overlap is shorter than 0.5 m or there is no possibility of vehicles traveling on at least one of the links). It can be used for crossing conflicts (one link crosses the other), merging conflicts (two connectors lead to the same link or one connector leads to a link that has other traffic coming from upstream) and branching conflicts (two connectors come from the same link or one connector comes from a link that continues further downstream). A single left click on such a position displays the two link segments in yellow, with the links outlined in yellow. Subsequent right-clicks define/switch the priority, displayed by different colors: main road (right of way) = green, minor road (yield) = red. (Both red may be used for branching conflicts, so vehicles need to "see" each other but the priority is defined through their order on the previous link.) Both yellow is passive again. A double click on the conflict area opens the conflict area dialog. Each conflict area has several parameters that affect vehicle behavior: "Visibility" is the maximum distance from where approaching vehicles on the respective link can view apporaching vehicles on the other link in order to detect possible conflicts. Outside of this distance, vehicles on the minor road will always brake for a stop close to the conflict area. (Very small values can cause vehicles to stand forever in front of the conflict area because they never reach such a small distance.) "Front Gap" is the minimum gap in seconds between the rear end of a vehicle on the main road and the front end of a vehicle on the minor road. "Rear Gap" is the minimum gap in seconds between the rear end of a vehicle on the minor road and the front end of a vehicle on the main road. "Safety distance factor" is a value that is multiplied with the normal desired safety distance of a vehicle on the main road to determine the minimum headway that a vehicle from the minor road must provide at the moment when it is completely inside a merging conflict area. A double click on a link number in the conflict area dialog makes this link the major road for this conflict area (row), displayed on green background, and the other link the minor road (red). The conflict area can be switched to all-red (e.g. for a branching area) through a right click on the green link and setting it to "Yield", too. Selecting "Passive" in the local menu after a right-click disables this conflict area completely (white, respectively yellow while selected). If the checkbox "Show all possible conflict areas in node:" is checked a node number can be selected and only all conflict areas and possible conflict areas inside this node are displayed in the table. The driving behavior of vehicles approaching a conflict area provides the maximum possible flow-rate for the minor road without interfering with the traffic on the main road. (In the case of merging areas, vehicles entering from the minor road may interfere with the traffic on the main road, the more the smaller the user defined saftey distance factor.) A vehicle on the minor road approaching a conflict area (where it must yield) determines if there will be a sufficient gap in the major road movement when it arrives at the conflict area (with its current travel plan, i.e. if it ignored the conflict area). If there is not such a gap, the vehicle decelerates as if it had to stop in front of the conflict are. (In the next time step the vehicle calculates again, so it can possibly stop the braking and continue even with a certain acceleration, "aiming" at a later gap.) A vehicle on the major road tries not to "crash" into vehicles on the minor road. If it determines that a vehicle on the minor road will still be inside the conflict area when it arrives there, it brakes to stop in front of the conflict area. (As this deceleration causes it to arrive later, it can possibly continue its journey without further braking in a later time step so that it passes just behind the vehicle on the minor road.) All vehicles (on minor and major roads) try not to enter a conflict area if there is not sufficient space downstream of the conflict area to leave the conflict area completely. + VISSIM Analyzer: See manual for details + New signal controller type SCATS. Needs the files scats.dll and scats_gui.dll and the programs WinTraff and ScatSim (and possibly SimHub) from RTA NSW. + 3DS MAX Export: Network export, extended ANI.TXT file and a script for 3DS MAX to allow creation high-end animations. + Link texture can be defined per link/connector (and in the multiselect link dialog). + Navigation in 2D and 3D: Panning with pressed middle mouse button. + 3D mode: Changed background texture properties for crisper look-and-feel up close, and smoother in the distance. + 3D visualization / *.avi recording: Field of view data is stored in keyframes. + Option "total redraw every time step" improved: If this is selected in 2D the link type colors are visible and the vehicles don't draw lines through a background image. (It isn't possible to change this option during a simulation run.) + New pavement marker type "Roundabout US", including optional center island (dot). + Pavement markers are displayed in 3D, too. + New layout for network elements display dialog. + Node evaluation raw data: optionally written to *.knr file or database table. One line per vehicle that reaches a node exit: Column / Type / Description: VehNo / long / Vehicle number VehType / long / Vehicle type number TStart / double / Simulation time when the vehicle crossed the start of the travel time section TEnd / double / Simulation time when the vehicle crossed the end of travel time section (i.e. the node exit) StartLink / long / Number of the link at the start of travel time section StartLane / long / Number of the lane at the start of travel time section StartPos / double / Link coordinate/Position of the travel time section on StartLink (meter/feet according to current unit selection) NodeNo / long / Node number Movement / Text / Bearing from-to (compass settings) FromLink / long / Number of the link entering the node (Note: link where the shortest path from the start of the travel time section enters the node, this is not necessarily the link where the vehicle entered the node!) ToLink / long / Number of the link leaving node. (The vehicle really did leave the node on this link.) ToLane / long / Number of the lane leaving node. (The vehicle really did leave the node on this lane.) ToPos / double / Link coordinate/Position of the node exit on ToLink, i.e. where the link leaves the node (meter/feet according to current unit selection) Delay / double / Delay in seconds (since travel time start section was passed) TStopd / double / Stopped Delay in seconds (ditto) Stops / long / Number of stops (ditto) #Pers / long / Number of passengers + Evaluations / Database: Table "EvalInfo" lists all evaluations written into the database, with the type of the evaluation, table name, date/time when the simulation run was started and the name of the network file (*.inp). + Multirun parameters are stored in the *.inp file. If the selected evaluation directory is a subdirectory of the current data directory (or the data directory itself) it is stored as relative path, so copying the *.inp file to a different directory will cause subsequent multirun evaluations to be written into a subdirectory of this new directory. + COM Interface: Option to run COM scripts from within VISSIM through the menu item "Scripts". + COM Interface: Vehicle properties: Leading and trailing vehicle (Attributes PRECEDING and TRAILING) + COM Interface: Signal group: Read current state. + COM Interface: Attribute "Controller Frequency" for ISimulation interface. + COM Interface: Link properties: Flag "connector" (true/false); if connector: from_link, to_link, from_lane (rightmost), to_lane, from_x, to_x, closed + COM Interface: Option to change the state of a 3D vehicle model during the simulation. + COM Interface: VISSIM is registered as COM Server during the installation of VISSIM (when administrator privileges are necessary anyway). + COM Interface: Update of the status line is user configurable with the attribute STATUSLINE in the ISimulation interface. (Setting this to false can dramatically increase simulation speed in a loop of RunSingleStep().) + Dynamic Assignment: Option "exclude full parking lots" for the destination parking lot selection for dynamic routing decisions. + Hardlock driver updated to Windows Vista. - 3D mode: If coordinates are very large (e.g. from VISUM export) 3D vehicles "flicker" sideways due to rounding problems. Also, links and lane markings are often not shown properly. - 3D Signals: The property for automatically inserting a street light to mast is not getting overridden when reading from an *.inp file. This causes some *.inp files to not load, and in some cases to crash, when the defaults are to include such a light. - DWG/DXF background images: The size/position has changed from 4.20-03 to 4.20-04. - Vehicles can get ridiculously high speed values if they don't see a leading vehicle and if the last segment of their user defined desired acceleration function is not horizontal but ascending. (The desired acceleration function is extended to the right in the direction of the last segment and if this extension crosses the speed axis (acceleration zero) vehicles with a higher speed than this crossing point will always accelerate if they can drive freely.) - Export VISUM / Links/Connectors: All VISUM turns are closed for all VISUM traffic systems because turns are not exported at all. - The menu Edit/Selection List stays enabled during a simulation run. - New *.bgr file format from VISUM (with 7 numbers) is not interpreted correctly in VISSIM. - Evaluation configuration / database table name: The replacement algorithm for illegal characters in the table name did not work correctly in all cases. - The extension for the lane change filter file is now *.lcf, to prevent confusion with the vehicle record filter file. - Error message "..decision is only xy meter upstream of...": After clicking "No message" further errors/warnings are not written into the error file. - Signal Control Dialog: The edit field "Offset" isn't enabled again for a Fixed time, Siemens VA, TRENDS, VAP, VAS or VS-PLUS controller after it has been disabled for an External or NEMA controller. - Connector dialog: If "Spline" is checked for an existing connector the new spline points have all height zero unless "Recalculate Spline Point Height" is checked, too. [Now, "Spline" is replaced by "Recalculate Spline" for existing connectors, and checking this does automatically check "Recalculate Spline Point Height", too.] - Vehicle Information Window: A cursor is blinking in last (empty) line and causes a vertical scroll bar if there is no room for the empty line. - COM Interface: Error messages about unexpected tokens in the *.inp file (e.g. if this was written by a later VISSIM version) during the LoadNet() method are displayed on the screen instead of COM messages. - COM Interface: If a path (for example to the method SaveAs()) with a network server name (e.g. "\\ska-wn-f00") is passed to VISSIM the method issues the error message "invalid directory". - Dynamic Assignment: The volumes in path files (*.weg) exported from VISUM are not used correctly: They are only used to initialize the "previous" volumes (for convergence evaluation) in VISSIM but not as the base distribution for the path selection in the first iteration. (The edge costs from the imported *.bew file are used for the path selection.) - External Driver Model DLL Interface: - DRIVER_DATA_SIGNAL_DISTANCE, DRIVER_DATA_SIGNAL_STATE, DRIVER_DATA_SIGNAL_STATE_START have always zero as index2 (should be the signal head number). - DRIVER_DATA_SIGNAL_STATE_START is incremented after 0.5 simulation seconds if the simulation resolution is lower than the signal controller frequency (i.e. more simulation time steps per simulation second than controller intervals).