New features and bugfixes in VISSIM (2009-11-13) =================================== (+ = new features, - = bugs that have been fixed. Details about the fixes are in brackets.) Version 5.10-11 [21194] (2009-11-13) ------------------------------------ + Simulation speed-up of typically 10% to 20% through internal optimizations. - Licenses provided by Siemens: The service pack 5.10-10 damages installations with a license provided by Siemens - VISSIM cannot start anymore after the update. These installations can only be fixed by a deinstall and new install of a setup of a version before 5.10-10. Version 5.10-10 (2009-10-29) ---------------------------- + 3D Mode: LOD calculation now considers the FOV angle to determine the perceived distance (as a result of the focal length) instead of the actual distance. + COM Interface: New method Link.RecalculateSpline() to recalculate the z coordinates of the spline points of a link respectively the whole spline points (x, y and z coordinates) of a connector, keeping the number of points. + COM Interface: Method RecalculateSplineHeight() which doesn't change the x and y coordinates of spline points of connectors (but only z). + Pedestrian Module: If feet is selected as unit for small distances the density (e.g. on measurement areas) is given in ped/ft². - VISSIM saves the *.inp file using comma (instead of point) as decimal separator one some computers and thus the file cannot be loaded again. - VISSIM appears to hang while unloading *.inp files that contain 3D models that failed to load. - VISSIM crashes at the end of a simulation run if an external driver model DLL has been used. - Multithreading (using more than one processor core) in a simulation run may cause an exception message. - Conflict Areas on links with gradients can cause an exception if a prioritized vehicle's desired speed is higher than the maximum possible speed on that link, i.e. if its maximum acceleration with the current speed (which is lower than the desired speed) is already negative. - Conflict Areas: A vehicle dwelling in a bus stop or parking space inside a merging or branching conflict area with a multi-lane link can cause VISSIM to hang. - Conflict Areas: VISSIM can crash during a simulation run if a driver using the Wiedemann 74 car following behavior and approaching a conflict area has an extremely low accelerator capability (internal value, randomly determined, much less than 1% probablilty). - After "Rotate Network" with an open background (and confirmation that backgrounds are not rotated) there is a message upon opening an *.inp file that the background has been changed (which is not true). - Network editor: If a data collection point is deleted or renumbered a discharge evaluation (added manually to the *.inp file) referencing that data collection point is not adapted, so the *.inp file written can not be read in anymore (message "unknown cross section measurement number"). - Detector dialog: Changing the type of one of several detectors with the same number and same SC doesn't work (the change is not saved upon OK). [Now, a message is displayed that the type of all these detectors is changed, similar for the smoothing factors and the detector name.] - Test Mode: Occupancy time, vehicle front end times and rear end times on detectors are not computed correctly if the simulation frequency differs from the signalization frequency. - 3D Mode: Some *.v3d files don't get drawn completely or not at all, especially when used as static objects (e.g. vehicle models from the new vehicle fleet). - Reading a snapshot written for a network containing PT stops fails with the message "guard SCS is missing". - ANM Import: Lane closures are ignored for the creation of static routes during the import of routes from an *.anmRoutes file. This can cause vehicles to wait forever on an adjacent lane because they may not enter the lane that the next connector of their route starts from. - ANM Import: The following condition must be met to identify a node as weaving section: On merging sections the outbound link must have a pocket, on diverging sections the inbound link must have a pocket. [This restriction has been removed now. A weaving section is identified if: 1. All the links have to be of type Freeway or RightSideRule. 2. The node has only one inbound link and two outbound links or vice versa. Reduced speed areas are not created for weaving sections. The lane change distance is set to 1000 m for weaving sections.] - COM Interface: VISSIM throws an access violation if the attribute LINK is called for on street parking lots. - COM Interface: It is not possible to set the (max) deceleration value for a reduced speed area vehicle class and the default value is 0 which is invalid for subsequent simulation runs. [Default value is 2.0 m/s² now.] - COM Interface: Routes.Count returns 1 if the route decision has no routes. - Dynamic Assignment: Reading a matrix file fails with the error message: "The matrix file could not be opened." if the file contains comments that are longer than 255 characters. - Pedestrian Module: When a pedestrian finishes his route at an area where another routing decision (and no input) exists he doesn't take one of the routes but leaves the simulation. (This happens only sometimes.) - Pedestrian Module: Travel time measurements behave unexpectedly if a pedestrian passes the start and/or destination area multiple times. - Pedestrian Module: VISSIM crashes in the network editor (with no simulation running) in 3D upon switching to LOS display (pedestrian areas included). - Pedestrian Module: Clicking Cancel in the "Delete Pedestrian Class" dialog opened after deletion of a pedestrian class which is referenced by a area behavior type causes an exception. Selecting a different class doesn't work either: the area behavior type is always deleted. - Pedestrian Module: Message "Unknown error in moving pedestrians" when a pedestrian walks onto a ramp. Version 5.10-09 (2009-07-29) ---------------------------- + 3D Models / Textures: Other image formats besides BMP (e.g. JPG, GIF, PNG and TIF) are supported now. + Adaptive ANM Import: Use existing short links (e.g. stubs created by previous adaptive imports) completely when connecting edges from changed nodes to preserved nodes instead of splitting these links again. This prevents messages like "split not possible". + COM Interface: Read/write access to vehicle class references of a detector (zero for the virtual class "all vehicle types"). + Dynamic Assignment: Buttons "Continue" (default) and "Abort" added to the message box "The abstract graph (edge structure) in file <...> isn't identical with the current one. Continue the simulation run anyway?" (only if simulation is running, not if only paths/edge dialog is opened!). If "Abort" is clicked the whole simulation run is aborted. + Pedestrian Module: Improved handling of pedestrians that are pushed onto or from ramps. - Lane changing: Vehicle A doesn't change to the lane of the upstream standing vehicle B if vehicle B is less than twice the length of vehicle A back and if vehicle B is still on a link that doesn't connect to the lane of vehicle A (so B cannot see A yet) and if vehicle B has not yet traveled 50 m in the network. - Conflict Areas: Stopped yielding vehicles inside a conflict area can cause VISSIM to crash. - Conflict Areas: If the additional stop line distance of a conflict area extends upstream beyond the start of a (different) connector, a yielding vehicle that will use that connector and thus not reach the conflict area at all is still considered as obstacle inside that conflict area by prioritized vehicles as soon as it has passed the stop line position. This can cause a lock-up situation if the prioritized vehicle is already inside a different conflict area that the yielding vehicle cannot enter. - If a car stops in front of a stop sign referencing a signal group just before that signal group switches from red to green, VISSIM displays an exception message (assertion failed). - Database connection strings containing quotes are not saved correctly in the *.inp file, preventing it from being read in again. - Node evaluation: The initializiation of a simulation run takes very long (with VISSIM not responding to mouse clicks) if there are nodes with many turn edges (inside the node). - Read snapshot can fail if the network contains a vehicle input with exact volumes. - Read snapshot can fail if the network contains parking lots for on-street parking (real parking spaces). - Read Additionally / Select position with left mouse mouse: Displays the old network in 3D (while in 2D multiselect mode) if there are static 3D objects in the file that is read additionally. - Pavement Markers: Upon creating a zebra crossing with distance unit "ft" the entered length is interpreted as "m". - Pavement Marker 'Zebra Crossing' is not displayed in 3D. - 3D lane markings (direction arrows, diamond marker) are too small and not always centered in the lane. - 2D visualization: Pedestrians are not drawn/deleted correctly after clicks on a scroll thumb or zooming with the mouse wheel. - Animation replay doesn't work properly after resizing the main window. - Animation replay: Shirts of "old" VISSIM pedestrians (vehicle type with one color) always appear in white when replaying in 3D from an *.ani file. - Printing is disabled during a simulation run. - Printing can cause a blue screen system crash on some Windows Vista systems. - Network editor: A double click on a routing decision does not open the route dialog anymore. - The dialog "Delete desired speed distribution" (opened if a deleted distribution is referenced somewhere, in order to replace that reference) shows wrong min/max values. - Network Performance Evaluation Configuration: It is possible to select emission attributes even if the emissions module is not included in the licence. - Multi-Run: File numbering of evaluation files and error files does not always work correctly. Sometimes you get a zero before an underscore. - Multi-Run with active option "Archive files" creates wrong archive filenames if the path/cost file names end with a digit. - The toolbar names (can be seen after right click on the menu bar) are not translated properly after repeated changes of the selected language. - Analyzer Reports / Network Performance: The values in the column 'Number of Vehicles' are too low (excluding the vehicles which have already arrived). - Analyzer Reports Dialog: Movement Group Delay: "Section" is displayed instead of "Nodes" (but node numbers). - ANM Import: If a link is very short, it can happen that the start of the link has the same coordinates as the end of the link. In this case an exception is displayed when the VISSIM links are created. - ANM Import does not handle a triangle island correctly if an additional pocket on the outbound link is found. - Adaptive ANM Import fails with the error message "Split not possible: not enough memory!" if there are VISSIM links to be split (to connect the old network with the newly created parts) which are too short. - Adaptive ANM Import of PT lines: - VISSIM PT lines are not deleted if the ANM PT line is deleted. - The entry links of VISSIM PT lines are not always adapted correctly. If the entry links are not adapted correctly, the *.inp file written after the ANM import can not be loaded again (aborts with "Semantic Error: Unknown link number"). - User defined public transport stops are not recovered after the node or links have changed. - Some ANM created public transport stops are missing after adaptive import. - COM Interface: Adding time intervals doesn't work correctly. Immediately adjacent intervals (TIMEFROM = TIMEUNTIL of the last interval) are rejected, and adding a new interval with a gap in between doesn't work either. - COM Interface: Access to attributes of transit lines was restricted to 16 bit in parameter 1 although 32 Bit are possible internally. - COM Interface: The SignalGroup attribute STATE returns TRUE or FALSE instead of the state of the signal group. - COM Interface: The function Signalhead.Count returns an error (instead of zero) if the signal group has no signal heads. - Dynamic Assignment: Suboptimal error messages for network graph problems when reading the path file (only edge numbers listed, no node numbers, or sometimes node number zero). - Dynamic Assignment: Read snapshot can fail if the network contains parking lots for dynamic assignment which contain waiting vehicles. - If Dynamic Assignment is not included in the license route closures are enabled in the routing dialog and when creating a new routing decision. Also, *.inp files with network elements available only for dynamic assignment can be read in which can cause problems in the network editor. - Pedestrian Module: Link dialog: A negative z offset causes first a correct message but then an exception message (not correct) if "use as pedestrian area" is checked. If the height is changed before checking this option, VISSIM shows error messages referring to the old height value. Also, Cancel does not work if a negative value has been entered. The default level for the link is always zero. - Pedestrian Module: Animation: Colors of pedestrians are sometimes wrong. - Pedestrian Module: Simulation stops with an exception message upon switch to aggregated display (Ctrl-Q) if there is a pedestrian area but no pedestrian input. - Pedestrian Module: Ramps with a ceiling opening of length zero can cause VISSIM to crash. [Now, a minimum length of 0.35 m is enforced.] - Pedestrian Module: The ceiling opening of a ramp is not updated when the level 2 of the ramp is changed. - Pedestrian Module: Exception message after deletion of a part of a network with pedestrian areas and pedestrian routes which had been selected with the multiselect rubber band. - Pedestrian Module: Walking Behavior Parameter Set dialog: Creating a new parameter set with "New" in the local menu causes prior changes in the selected parameter set to be lost. - Pedestrian Module: Walking Behavior Parameter Set dialog: Clicking "Del" in the local menu causes an exception message. - Pedestrian Module: Pedestrian area dialog: Crash after changing the thickness with two selected areas. - Pedestrian Module: If there is no walkable ground between two points of a route no error message is shown at the start of the simulation. - Pedestrian Module: Dialogs Walking Behaviour, Area Behaviour Types, Pedestrian Classes: edit name, delete, select next => exception message. - Pedestrian Module: Simulation runs are not reproducible. - Pedestrian Module: The "Visualization" flag of links used as pedestrian areas is ignored for the visualization of pedestrians. - Pedestrian Module: If more than one conflict area exists on one pedestrian link (with pedestrians yielding to vehicles) with less than 1 m distance, the calculation of the pedestrian behavior is not completely correct, causing them to enter the first conflict area even if there is already a vehicle visible upstream which has priority at a conflict area further downstream. - Pedestrian Module: If more than one conflict area exists on one pedestrian link the behavior of pedestrians is always influenced by the state of downstream conflict areas even if they are more than 1 m apart. - If a network contains more than 100 RBC controllers the simulation crashes with an exception error. - Synchro Export aborts with the error message "No nodes generated". - Synchro Export aborts with the error message "Unknown exception during simulation!". (This bug was introduced in version 5.10-07.) - TRENDS signal control: The signal control dialog doesn't accept a filename with explicit path for the controller program. Version 5.10-08 (2009-05-18) ---------------------------- + Adaptive ANM Import Dialog: If an *.inp filename is entered through the file selection dialog, the panm/panmRoutes filenames are changed accordingly, too. + The error message "Unexpected begin/end of node..." includes the number of the relevant adjacent node, too, and the message is also written into the log window, and it is possible to zoom to the node (from the log window). + Wording of several message phrases improved. + COM Interface: Driving behavior parameters for the car-following model Wiedemann 74 are accessible. + Pedestrian Module: + Multithreading: Cores are always used as selected in Simulation Parameters / Number of cores, so there don't need to be separate levels to allow multithreading. + Pedestrian record (*.pp): Column names have changed and there is a legend per column written into the output file. + Area evaluation (compiled data) (*.mesp): File extension changed from *.mezp to *.mesp. File format has changed, data per area evaluation is written row-wise now (instead of in one row). Column names have changed and there is a legend per column written into the output file. + Area evaluation (raw data) (*.merp) Column names have changed and there is a legend per column written into the output file. - VISSIM can crash during a simulation run (possibly with a diagonal red cross) if a background is loaded and the option "Total redraw every time step" is turned on. Too many GDI objects are allocated but not freed every time that a background is drawn. Over the time of a simulation run this can exhaust the available ressources of Windows. - Multirun: Non-critical warnings are displayed at the begin of each simulation run (or even during a run). [These warnings are now only shown during the initialization of the first simulation run.] - A vehicle deciding to change lanes is prepared to run a red light (signal head) or a priority rule closely downstream on the new lane. - Cooperative braking: A standing vehicle that had intended to allow a lane changing vehicle in waits to do so even if it has passed that vehicle almost completely. [Now, it must be at least "behind" by the width (!) of the leading vehicle on the adjacent lane, so that this vehicle might be able to start a lane change.] - If the driving behavior parameters minimum look ahead distance and minimum look back distance are 0.0 all vehicles at the same link coordinate are found. This can cause the simulation to run very slowly if there are many vehicles "stacked" at the same link coordinate (e.g. having been set into the network through COM without checking if there is room). - If the driving behavior parameter "temporary lack of attention" is active (>0) vehicles can leave their route: The emergency stop position for a necessary lane change is ignored during this period as well. - A simulation run can stop with an exception message if a reduced speed area doesn't change the speed of a vehicle. - Negative maximum acceleration because of a high gradient can cause the simulation run to stop with an exception message. - Fatal error at simulation start with a network including partial routes and PT lines if: - the partial routing decision and PT stop are on the same link X - there is a connector to link X between the decision and PT stop - the PT line comes from this connector - Reduced Speed Areas: If a vehicle has once seen a reduced speed area as (n'th) leading vehicle, it will always remember to change its desired speed after travelling that distance (and for the length of the reduced speed area) even if it has left the original link/lane/route in the meantime (e.g. due to a static, partial or managed lane routing decision) and thus doesn't actually pass the reduced speed area. - Conflict Areas: A simulation run can stop with an exception message if a prioritized vehicle must wait upstream of several conflict areas because there are still conflicting vehicles (or pedestrians) inside more than one of them. - Conflict Areas / Network Editor: Shortening a connector so that its end point is located inside an existing conflict area of this connector causes an exception message. - Conflict Areas / Network Editor: If a click on a position where multiple conflict areas overlap highlights a non-existing conflict area (yellow) first, and below there is an existing conflict area it is impossible to double click the existing one because on double click always the "topmost" conflict opens. [Solution: Once a conflict area is highlighted, double clicking does not change the selection.] - Conflict Areas: A vehicle doesn't consider a downstream blocked conflict area at an upstream area already, i.e. it enters the upstream area even if there is not enough room between the two areas. This makes it enter the downstream area regardless of a conflict (because it must leave the upstream area). - Conflict Areas: A yielding vehicle in a merging area ("red") ignores a downstream conflict area if there is not enough room in between for the vehicle, i.e. it enters the downstream area regardless of a conflict because it must leave the upstream area. [From now on, vehicles in merging areas don't try to leave them anymore at all cost - this applies only to crossing conflicts if the vehicle must yield ("red").] - Conflict Areas: The safety distance factor is applied to the estimated static part of the safety distance (standstill distance, 2.0 m), too. If a high factor is used, this can cause vehicles with right of way standing upstream of a merging area to block this area for yielding vehicles completely which in turn can cause deadlocks at uncontrolled intersections (right before left). [Now, the factor is limited to 1.0 when applied to the static part of the safety distance, i.e. this part (with a new default value of 0.5 m) can still be reduced if the factor is smaller than 1.0. The effect of the factor on the speed-dependent part of the safety distance (3.5 times the square root of the speed in m/s) has not been changed. This means that the change is quite small for moving vehicles but can be significant for standing vehicles with right of way.] - On-street parking: Blocking vehicles are found even beyond an unblocked lane without parking spaces which prevents full use of parking spaces on both sides of a drive-through lane. - On-street parking: A simulation run can crash with an exception message if vehicles without parking lot route pass parking spaces. - Signal Changes Evaluation: If this is activated, VISSIM can crash during a simulation run if an external signal controller (e.g. VAP) reports a cycle time of zero to VISSIM. - VISSIM database output does not work correctly with Microsoft SQL Server 2005 and 2008. These can use the SQLNCLI provider instead of the former SQLOLEDB. VISSIM can not recognize that this provider tries to connect to a Microsoft database. This produces following SQL error at runtime with the SQLSERVER 2008: "Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column." - Connectors: When changing the lane assignment (multi-lane start/end link) the height (z-coordinate) is lost. - Network Editor: VISSIM hangs when moving a connector's start or end to a different link if the connector has 3 or more lanes and the new from/to link has at least 2 lanes less than the original from/to link (so the number of lanes of the connector must be reduced by more than one). - Route selection: If a yellow band is visible (route selected), a right click outside the network does not open the route dialog any more. - PT line selection: If a yellow band is visible (line selected), a right click outside the network does not open the list of all PT lines any more. - Partial Routes: When displaying the partial routes as yellow band, the green destination section of only one route is shown highlighted (light green); the destination sections of the other partial routes are shown in dark green. - Link Dialog: Changes of z-coordinates of links can result in changes of x, y coordinates of connectors if the input file is saved. - Display Types Dialog: Attribute changes of the current display type are not saved if New or Copy is selected from the context menu in the list of types. - Vehicle (and Pedestrian) Input Dialog: The message "You defined timeintervals without volumes and compositions. These will be removed when closing the dialog." occured (wrongly!) if continued inputs were defined. - Animation (*.ani) Replay in 2D: Pedestrians (old vehicle type) leave a trail on the link. - Exception messages are not always translated correctly (but shown in German). - Reading a snapshot fails nondeterministically with the message "Guard VEH_END not found". - Analyzer: Travel times distances no longer match with travel times numbers because travel time sections are now sorted by number and distances by name. Distances will also only be reported by name. - Synchro Import: If the Synchro file contains shared controllers VISSIM hangs. [Now, it displays an error message and cancels the import.] - ANM Import: Aborts with the error message "Import failed because of following error occurred while parsing the *.anm file : index out of range" if no to-time is defined in the *.anm file. - ANM Import: Warning "Multi-leg node has zone connectors attached..." for all nodes where extra VISSIM links are created, even for zone connectors to end nodes with only one adjacent node. - ANM Import: Wrong numbers in the warning message " routes (of ) have volume = 0 in all time intervals" (x can even be larger than y). - ANM Import: The emergency stop position for connectors created from an *.anm file exported from Sitraffic Office is always 32767 - ANM Import: If there are two links that are connected with lane turns in the following way (from Lane -> to lane): (1->3), (3,1), (4,2), the lane turn validation reports this combination still as an error (because in an earlier version lane turns with such holes were not allowed) - Adaptive ANM Import: Crashes if the user has removed all public transport stops of an ANM stop in VISSIM. - Adaptive ANM Import: If a new PT stop in the *.anm file (e.g. entered in VISUM) is situated on a link that has not been changed the stop is not created correctly in VISSIM. - Adaptive ANM Import: Aborts if a new node has been inserted manually into the VISSIM network after the initial import and if the changed *.anm file imported adaptively contains a node with the same number. - COM Interface: Paths defined through COM are not written into the snapshot file, so reading the snapshot fails if it includes a vehicle that uses such a path. - COM Interface: The DWELLTIME attribute of COM vehicles and COM transit lines is an integer, so decimals are los. [Now, it is a double value.] - COM Interface: The simulation time after a call of LoadSnapShot() through COM is one time step higher than the simulation time when the snapshot has been saved. - COM Interface: LoadSnapshot does not work if the snapshot file contains a VAP signal controller. - COM Interface: Access to attributes of PT lines was restricted to 16 bit in parameter 1 (i.e. numbers above 32767 didn't work correctly) although 32 bit are possible internally. - COM Interface: Setting/getting the driving behavior parameters CC6 and CC9 of the car-following model Wiedemann 99 doesn't work correctly. - COM Manual: The COM manual wrongly states (in the example) that the command for adding a route is decision.Addroute(2, 200.0) but the command actually is decision.routes.AddRoute(2,200.0). - Dynamic Assignment: Alternative path search: The penalization of the shortest path is working on the same edges throughout the the penalization iteration because the best path is searched only once before the iteration. Third best alternatives are not found because of this. - Dynamic Assignment: VISSIM crashes during a simulation run with dynamic assignment and active path evaluation with database output and one or more of the following attributes selected for output: Travel time path (determined), Travel time path (estimated), Travel time path (smoothed). - Dynamic Assignment: Path Evaluation Configuration Dialog: Changing the configuration file name does not work. The label of the checkbox "[ ] Database" is set to the selected filename instead. - Dynamic Assignment: Exception message at the start of a simulation run if the total time period from all matrice files starts before the simulation start time and exceeds the simulation duration (+ start time). (Only in English language.) - Dynamic Assignment with segment nodes (e.g. imported from ANM): Error messages "The abstract graph (edge structure) in file <...> isn't identical with the current one. Error messages are written to the ERR file." on the screen and "Old abstract graph in <...>.bew: The edge x (node y) cannot be mapped to any edge in the current network graph." in the *.err file at the start of a simulation run during the reading of a path file (*.weg) and a cost file (*.bew) if there is a connector that is part of a turning relation (internal edge) inside a segment node starting almost at the end of a link. When viewing the internal edges of such a node in the Edge Selection dialog, these "end" segments of incoming links (where the connectors start from) are displayed wrongly as complete edges. This happens only after the *.inp file has been read but not immediately after an ANM Import and not after converting a polygon node into a segment node (but it happens after writing the *.inp file and reading it back in). - Pedestrian Module: Areas on different levels can be drawn in wrong order in 2D (higher level number on top instead of higher level height on top). - Pedestrian Module: Obstacles are not drawn properly sometimes. - Pedestrian Module: Walking behavior dialog: Ctrl-C to copy causes an execption message, even if not the walking behavior is active but the field for the parameter file. - Pedestrian Module: Walking behavior parameter set dialog: Paths of XML files that are stored in the data directory (or a subdirectory thereof) are stored absolutely (instead of relatively). [Uses now the keyword "#data#" instead as for 3D model file references.] - Pedestrian Module: Loading a pedestrian network with many ramps can take a very long time. - Pedestrian Module: Elongating a ramp by a small amount can cause the error message "Ramp polygon is not valid (length is too small)." - Pedestrian Module: Changing network objects does not always cause the warning message "Network has been changed" at the start of a simulation run and when VISSIM is closed: - input volume type change from stochastic to exact or vice versa - ped areas after activating "queuing" - ped routes after adding an intermediate point - Pedestrian Module: Activating the pedestrian travel times evaluation also switches the status bar display from simulation seconds to time of day and vice versa. - Pedestrian Module: In the status line (with the LOS evaluation) you always get LOS (grid based) after selecting each LOS scheme once. - Pedestrian Module: At conflict areas, yielding pedestrians react to a second upstream vehicle although the first vehicle is already standing still to give them way. (This can happen for very slow yielding vehicles, too.) - Pedestrian Module: Values for "solid ramp foot" in the ramp dialog do not always work (just try changing them...). - Pedestrian Module: In the Behavior Parameter Set column in the Area Behavior Type dialog there is a misplaced character "c" between [number][colon][space] and [name of behavior parameter set]. - Pedestrian Module: Translate network in z-direction: Construction elements are not moved correctly. The z-offset of the movement is applied to "Z-offset top" of the construction element. Thus - negative values can result (which are not allowed in the dialog) - VISSIM crashes after saving and reopening the *.inp file due to the negative z-offset (if a negative z-movement was done beforehand). [Solution: Change only the level heights (and not the z-offset of individual construction elements) according to the z-offset of the movements.] - Pedestrian Module: Area Evaluations: If 2 or more areas of the same area evaluation overlap, a pedestrian leaving the first of them causes wrong behavior. - Pedestrian Module: Routing Decision Dialog: If you delete the number of the destination area and then delete the decision itself (i.e. without a number) VISSIM crashes. - Pedestrian Module: A memory leak in the PedestrianModel.DLL can cause VISSIM to crash during a simulation run after all available RAM has been allocated. Multiple runs (without closing VISSIM) suffer from an additional memory leak. - Pedestrian Module: Entering a letter as "number" for an area causes an exception. [Numbers of Areas/Ramps/Obstacles cannot be edited anymore now.] - Pedestrian Module: The number of a pedestrian is reused after he leaves the network if that number is larger than all numbers of pedestrians which are still in the network. - Pedestrians Module: Wrong message "input time interval has no volume" after adding of the first pedestrian input. - Pedestrian Module: Evaluations are not reproducible. - Pedestrian Module / COM Interface: Setting route ratios of a pedestrian route doesn't work via COM. Version 5.10-07 (2009-03-04) ---------------------------- + Spanish version available (with English documentation only). + The recent files list in the File menu (saved in the Windows Registry) is updated immediately each time that an *.inp file is opened or saved under a new name and before the File menu is opened. This means that all VISSIM instances of the same main version (5.10) that are running at the same time share a common recent files list. + Improved parking behaviour for multi-lane drop-off: Vehicles don't select a parking space that is blocked by a standing vehicle on it or to the left of it (with left-hand traffic to the right of it). If the parking space selected by a vehicle becomes blocked in this way, the vehicle selects a different space provided there is still a non-blocked one available downstream on a route of this parking lot routing decision. + Signal Control Dialog: The WTT file is set to asc3.wtt by default when a new signal controller of type Econolite ASC/3 is created. + Analyzer: Movement averaged, vehicle separated Delay Report. The user can select groups of movements and groups of vehicle types and the report contains delay values for each combination thereof. + ANM Import: The ANM format does now allow branching from a lane to several lanes on the same outgoing link of a node. (This feature requires that the key of the lane turn includes the the outgoing lane, too.) + COM Interface: New read/write attribute VISUALIZATION for a link which defines if vehicles are visible on this link during the simulation. + COM Interface: New read/write attribute DWELLTIME (in seconds) for a vehicle to access the remaining dwell time of a vehicle in a public transit stop or at a stop sign with a dwell time distribution. + COM Interface: New read-only attributes POSITION (link coordinate in the current unit for short distances) and DETECTORLENGTH (in the same unit) for a detector. + COM Interface: New read-only attributes ROUTE and ROUTINGDECISION for a vehicle, returning the numbers of the current route and the decision (static/partial/parking) that the route belongs to, and zero if the vehicle is not currently on such a route. + Pedestrian Module: Queueing can be defined as a waiting type attribute for a rectangular pedestrian area with a pedestrian route point. This causes the pedestrians to queue for the duration of their dwell time along the direction vector that is displayed in center line mode and defined during the creation of the area. + Pedestrian Module: Threshold value for consistency checker warning about high speeds reduced from 12 to 11 km/h in the pre-sim checker. + V3DM 1.42-02: See V3DM\Doc\Changes.txt. - A vehicle can decide to change to a lane and ignore (pass) a red signal head or a blocked priority rule there if it is too fast to stop upstream of it. [This fix can change simulation results in networks with signal heads or priority rules on multi-lane links!] - The toolbar crashes sometimes (only a diagonal red cross is displayed instead of the menu or buttons) after a simulation run or after an ANM import. - Nodes: Convert segment node to polygon node: The calculated polygon is much bigger than necessary. [Now, it's really the surrounding rectangle.] - Read Additionally: The insert position control is disabled per default, so it is not possible to choose a value there. (This bug was introduced in version 5.10-05.) - Vehicle Input Dialog: Continued inputs cause the inappropriate message "Sie haben Zeitintervalle ohne Belastungen und Zusammensetzungen definiert. Mit Schließen des Dialogs werden diese Zeitintervalle gelöscht." (This bug was introduced in version 5.10-06.) - Signal Control Dialog: Controllers of type Econolite ASC/3 cannot be edited anymore after a simulation run (error message or crash). (This bug was introduced in version 5.10-06.) - Delay evaluation: The first time step of a vehicle arrived in a PT stop or in a parking space is included in the delay. - Link Evaluation with database output aborts with the error message "Error in database output: database is not open". - Analyzer: The reported LOS in the Delay report does not correspond to the Node Summary in special cases. - Analyzer: The Network Performance report no longer allows the selection of any parameters (location, random seed, time, vehicle types, etc.) and no summary is displayed since these are not selectable. Network LOS is not reported. - Analyzer report stops with error message "Delay : The current database is Read-Only. Please check your permissions" - ANM Import (initial) aborts with error "Unexpected end of node " if there are very short edges between nodes. - ANM Import crashes if there is a link polygon that has a loop at the begin or the end. [Now, an error message is displayed listing the respective link and the user must fix that polygon before starting the ANM import again.] - ANM Import: Lane turns from the same link cross each other in left hand traffic if the lane turns are not specified in the *.anm file. - ANM Import: The error message "Unexpected end/begin of node XXX" prevents a simulation run or an adaptive ANM import in a network created by an ANM import. - Adaptive ANM Import: Can be started although the node/edge structure is invalid already before the import. - Adaptive ANM Import: Error message "two adjacent intermediate points are identical" when an input file is opened which was created by the ANM import. - Adaptive ANM Import: Insufficient error handling after failed import can cause an incomplete/invalid VISSIM network. [Now, the network is deleted completely after a failed adaptive import.] - Adaptive ANM Import: Crashes if the attribute ALLRED is defined for a signal group (as in the ANM Export from VISUM 11). - COM Interface: Vehicle loses routing information (and other attributes) after being moved by MoveToLinkCoordinate(). - COM Interface: Setting routing decision properties (vehicle classes, name, time intervals) does not work correctly if the decision is on a link with more than 1 lane. - COM Interface: The value of the attribute LENGTH/VEHICLELENGTH is always returned in meters, regardless of the unit selected currently. The value of the attribute VELOCITY/SPEED/VEHICLESPEED is returned in m/s if km/h is selected as unit for speed and in m/s divided by 1.60934 if mph is selected. - Dynamic Assignment: The message "Parking lots with relative flows but without paths:" in the *.err file lists a wrong number several times. - Pedestrian Module: Dialog "Walking Behavior Parameter Set": Drop Down list of desired speed distributions looks as if disabled. - Pedestrian Module: An *.inp file can't be opened if the pedestrian type with the largest number in a pedestrian composition has a relative ratio of 0. - Pedestrian Module: A simulation run doesn't start if the first line in the routes grid contains only zeros. Version 5.10-06 (2009-01-23) ---------------------------- + View / Load Settings (read *.ini file): Previously loaded background images are removed if the new *.ini file includes (a) background image(s). + Managed Lanes Evaluation Configuration. + Vehicle (and Pedestrian) Input Dialog: Warning message if the user defines a time interval but does not enter data (volume/composition) for that interval. (Previously, that time interval was quietly deleted upon OK.) + External signal controllers accept file names with path for the Program File (SignalController.dll), Dialog DLL file (SignalGUI.dll) and all the *.wtt files. Paths including the data directory (where the *.inp file resides) or the program directory (where vissim.exe resides) are saved as abstract reference so that they still work after copying the data directory to a different location (or computer). + ANM Import: Accepts multiple connectors between two links (as exported from VISUM 11). + Pedestrian Module: Multi-threading: Each level can be calculated by a separate instance of the pedestrian DLL. (The number of levels and the user-selected number of cores in the Simulation Parameters dialog determine the number of parallel threads, whichever is smaller.) + Pedestrian Module: Read Additionally. + Pedestrian Module: Rectangles and Polygons can be rotated. + Pedestrian Module: The pedestrian DLL parameter file from the area behavior type (containing walking behavior parameter sets) is used for pedestrians walking on the respective area. + Pedestrian Module: Zoom function for pedestrian routes, travel times and inputs in the dialogs' grid context menus. + Pedestrian Module: Additional data in the measurement area evaluation: min/max/avg density while on area, min/max/avg speed while on area, min/max/avg desired speed while on area, avg orientation while on area, min/max/avg z while on area, standard deviation of speed(s) while on area. + Pedestrian Module: COM Interface: PedRouteDecision -> PedRoutingDecision. (For consistency with the naming of vehicle routing decisions.) - Conflict Areas: Yielding vehicles block a crossing conflict area more often than absolutely necessary (which would be because of unexpected hard braking of the leading vehicle). [Now, an additional condition must be met to allow a yielding vehicle to enter a crossing conflict area: There must be enough empty room downstream of the conflict area for the whole length of that vehicle if the leading vehicle is slower than 5 m/s and slower than 75% of its desired speed. This fix changes simulation results in networks with crossing conflict areas!] - Delay / travel time /node evaluation: If many vehicle types, many time intervals and many travel time measurements (nodes) are defined, VISSIM uses excessive RAM for collecting travel times which can cause it to crash at the start of a simulation run. [The RAM usage is reduced now.] - Database output of time/date: Month and day are swapped (e.g. January 8th is shown as August 1st). - Fixed time signal control: Cycle times above 4800 can cause wrong signal times if no second green time is defined. - VISSIM writes "PROGRAM 0" into the *.inp file for external signal controllers of type Econolite, RBC, NEMA. - Signal Control Dialog: After OK sometimes all 3D signal head bulbs are turned off and the signal head dialog crashes on load. - Signal Control Dialog / No Lane Change Dialog: After deselecting the last selected item from a multiselect list box for vehicle classes the first item is selected automatically. - Visualization: Even if visualization is switched off, signal heads are displayed at the start of a simulation run. - 3D visualization: The red/amber signal line has z-fighting with links (more than green or amber only). - Animation (*.ani) replay: Some vehicles are flickering (not being shown in several time steps). - Managed Lanes data is not included in a simulation snapshot (so the information about the previous traffic is not correct when starting a simulation run from a snapshot). - Managed Lanes Evaluation: writes no data output at all if the update interval is larger than the simulation period. - GAIA Export and MISKAM Export: Vehicle and signal head positions (x/y coordinates) written into the export file are different from the coordinates shown in the status line. - VISUM Export: When exporting 'Nodes/edges' from VISSIM to VISUM the coordinates of the zone centroids are incorrect. - ANM Import: Auto Routing Selection Dialog: all volumes are 0 if the path file (*.weg) was created by the ANM import of a network exported from VISUM. - Adaptive ANM Import: VISSIM crashes if the input file already contained bus/tram stops imported from ANM and the new ANM data contains the same stops (regardless if changed or not) and VISSIM links of that location need to be re-created (due to changed node geometry). - Adaptive ANM Import: crashes when importing a changed node that has a neighbor with a triangle island. - Dynamic Assignment: Using VISSIM' virtual memory can cause excessive use of RAM and eventually an "out of memory" error message, depending on the computer system's configuration. - Dynamic Assignment: Crashes in all languages but German if the path file contains invalid edges. (Edges in the path/cost file can become invalid if the network is changed after writing the path/cost files and then trying to use the same path/cost file again.) - Dynamic Assignment: Travel time smoothing: MSA is always used if the MSA start iteration has not been changed from the initial value of 0 even if exponential smoothing was selected again after that. (This bug was introduced in version 5.10-02.) - Dynamic Assignment: VISSIM can hang (not responding) at the end of a simulation run if the simulation period is not a multiple of the evaluation interval and if a vehicle reached the end of its path during the last (incomplete) evaluation interval (e.g. simulation period 3900, evaluation interval 600, and vehicle reaches end of path after 3600). - Pedestrian module: VISSIM crashes after changing the number of a pedestrian area and two clicks on Apply. - Pedestrian module: VISSIM crashes after changing the number of a routing decision. - Pedestrian module: Routing Dialog: Sorting in the list of routing areas is not synchronized with the data shown on the right. - Pedestrian module: The undo functionality for measurement areas doesn't work. - Pedestrian module: After moving a pedestrian route's destination point from one area to another one this route point can't be selected if the decision is selected. The attempt may also cause a crash in VISSIM. - Pedestrian module: Measurement areas cannot be resized, moved and deleted like 'normal' areas. - Pedestrian module: If an area is moved, routing decisions and destination points on it are relocated unexpectedly. - Pedestrian module: Pedestrians sometimes get a too high walking speed when leaving a ramp. - Pedestrian module: In the Pedestrian classes, Walking behavior, Area behavior dialogs the selection change doesn't work properly. - Pedestrian Module: After creating a new pedestrian input in the dialog the input of the previous interval is deleted. - Pedestrian Module: Pedestrians don't proceed from short/steep ramps - instead, they walk up and down the ramp forever. - Pedestrian Module: In measurement area evaluations (*.mezp) some header items are missing. - Pedestrian Module: A click on a selected ramp can cause an exception message if the ramp dialog is open and a new level has been created and assigned in between. - Pedestrian Module: Sometimes pedestrians find no route after they move from a ramp to a level (message "no route exists" some time steps later). - Pedestrian Module: Dialog/Editor synchronization doesn't work properly for multiple selection in Area/Obstacle/Ramp mode. - Pedestrian Module: Reading an *.inp file without pedestrian data but with the pedestrian module included in the VISSIM license creates the default desired speed distributions for pedestrians again if they already exist. *.inp files which are saved by users without and with the pedestrian module in the VISSIM license alternatingly can't be opened anymore without the pedestrian license after having been saved with the pedestrian license. (This bug was introduced in version 5.10-02.) - Pedestrian Module: VISSIM crashes with an unhandled exception when a new walking behavior is created. - Pedestrian Module: The consistency check at the start of a simulation run doesn't always detect that inputs have missing routes in some time intervals. - Pedestrian Module: Rotate network: Some pedestrian objects are not rotated correctly and the simulation doesn't work afterwards. - Pedestrian Module: If "LOS display" is activated and then visualization switched to 3D the pedestrians are not displayed as individuals and the 2D LOS display flashes over the static 3D background each time step. - Pedestrian Module: Movement on stairs and ramps (which is slower in x-y direction than horizontal movement) is considered as delay in the travel time evaluation. - Pedestrian Module: If a pedestrian cannot be created on an input area because of temporary overcrowding this pedestrian is not created in a later timestep. [Now he is created as soon as possible.] - Pedestrian Module: Aggregated area evaluation data of an incomplete interval at the end of the simulation run is not written into the evaluation file. - External Driver Model DLL interface: Simple lane change doesn't work correctly with DRIVER_DATA_WANTS_SUGGESTION: It's necessary to set DRIVER_DATA_ACTIVE_LANE_CHANGE back to zero in the time step after it has been set to 1 or -1 in order to make the vehicle actually start a lane change (in that second time step!). - External Driver Model DLL interface: Trailing vehicles on adjacent lanes are swapped: All data including the vehicle numbers (DRIVER_DATA_NVEH_ID) for index2 = -1 and index2 = -2 is swapped (index2 = -2 provides the data of the first trailing vehicle, index2 = -1 the data of the second one (farther upstream)) on all adjacent lanes (index1 from {-2, -1, 1, 2}). - External Driver Model DLL interface: Vehicles using Wiedemann 99 suggest a low acceleration (about 0.3 m/s²) even if their desired speed is much higher than their current speed and there are no obstacles. This happens only if an external driver model DLL is used (because the vehicles have the interaction state "PELOPS" and don't ever reach "FREE" which is necessary for higher acceleration with W99). [Now, the interaction state is recorded as the suggested one if the driver model DLL requests suggestions and doesn't change the suggested acceleration.] Version 5.10-05 (2008-11-19) ---------------------------- + The directory of the VISSIM installation can be seen in the Support window for the VISSIM installation as additional comment in the Add/Remove programs dialog of the Windows Control Panel. This makes it easy to identify the correct VISSIM installation (out of several) to remove. + Routes Dialog: Managed Lanes decisions: Link filter (show routes over link). + Display of Network Elements Dialog: + Pedestrian network elements are included (if the license includes the Pedestrian module). + Labels for links and connectors can be set to cost, display type or behavior type, too. + Labels for vehicle inputs show the link number instead of the obsolete vehicle input number. + Additive Reading: Managed Lanes Facilities are included now. + Both 1-color and 4-color adult pedestrian 3D models are now included in the provided library of 3D models. For vehicle types with category Pedestrian ("old" pedestrians) the 1-color models should be used, for "real" pedestrian types (pedestrian module) the 4-color models which have got new names now such as "Woman20Fram4Col-Biz01.v3d". + Pedestrian Module: 3D models of pedestrians use the appropriate 3D frame (standing still) if their speed is zero. + Pedestrian Module: Default desired speed distributions for pedestrians use numbers starting from 1001 (so they don't mix with the default desired speed distributions for vehicles in the dialog). - The warning messages - "Simulation time T: Vehicle N (on route X of routing decision Y) after Z seconds of waiting for lane change removed from link L at position P", - "Simulation time T: Vehicle N (PT line X) after Z seconds of waiting for lane change removed from link L at position P", - "Simulation time T: Vehicle N with destination zone X arrives at parking lot Y which is not assigned to this zone. The vehicle stops for one time step and continues its trip after that." and - "Simulation time T: Vehicle N with destination parking lot X arrives at parking lot Y from the same zone. The vehicle stops for one time step and continues its trip after that." [actually saying "destination zone X" which was incorrect] are not written to the *.err file anymore (even if the respective problem happens). - Conflict Areas: VISSIM can crash during a simulation run if a slow vehicle A sees a green conflict area downstream with a vehicle B on the conflicting link not yielding and not passing soon enough, thus forcing vehicle A to start to brake not immediately but some time steps in the future. - Conflict Areas: Upstream vehicles are ignored if the conflict area extends over the whole length of a link/connector. [Now, even connectors leading "into" a conflict area on the first 0.5 m of a link are not ignored anymore when looking for upstream vehicles.] - Conflict Areas: A yielding vehicle that is in the "anticipate routes" percentage ignores a prioritized vehicle that has already passed the crossing conflict area with its front end but is still inside with its rear end. - Stop signs with dwell time distributions can produce different dwell times after other network elements (e.g. data collection points) have been added. - Partial routing decisions ignore public transport lines. - Cooperative braking: Vehicles do sometimes brake cooperatively even if the vehicle on the adjacent lane that they try to make room for will not start a lane change anyway because its next vehicle downstream wants to change to the same lane, too. - Node evaluation (compiled): Edge (fromLink) can be reported incorrectly if the node can be reached from a travel time start section along different edges entering the node. - Managed Lanes Facilities: Deleting a vehicle class used by a facility and/or changing the number of a vehicle class used by a facility caused invalid data (dialog did not work, error loading input file). - Conflict Area Dialog: Items with more than 4 characters in the vehicle-class dependent drop-down controls cause VISSIM to crash, upon OK or when opening the control again. - Routes Dialog: Routes "Select All" ignores the link filter (even if the link filter is set, all routes are drawn selected, not only the ones in link filter). - Additive Reading: VISSIM reports an error if you try to read additionally an input file that contains a PuT stop with a duplicated number and detectors that reference these stops. - Background: *.ecw files cannot be loaded. (This bug happens only in full setups (not updates) of version 5.10-03/-04.) - Analyzer: Clicking the Print PDF button in Analyzer after the reports have been run results in an error message. No PDF creation is done whether PDF creator is installed or not. - Synchro Export dialog: doesn't accept backslash characters in the path. - Multi-Threading: Dwell times at stop signs with dwell time distributions can be not reproducible if more than one core is used for the simulation. - The command line parameter -threads doesn't work correctly with the "new" multithreading since VISSIM 5.10-00. [Now, it is used only if an *.inp file is specified in the command line, too. The number of threads is overwritten as soon as a new *.inp file is opened.] - COM Interface: The Simulation attribute THREADS doesn't work correctly with the "new" multithreading since VISSIM 5.10-00. - COM Interface: The attribute "PEDCOMPOSITION" at pedestrian inputs is missing. - Dynamic Assignment: Volumes and travel times for time intervals are not read correctly from the path (*.weg) file. As a consequence: - All or some path volumes are not displayed correctly in the Auto Routing Selection Dialog (often 0.0). - The option Create Static Routing doesn't work properly (i.e. vehicle inputs will not correspond to the real volumes from the path file). - Convergence evaluation results are wrong. - Dynamic Assignment: If the matrix time periods exceed the simulation period there can be slightly exaggerated (and possibly completely unnecessary) warnings "n vehicles could not leave parking lot x" in the *.err file (because vehicles with a determined start time inside one second after the simulation period are counted, too). - Pedestrian module: Different behavior between different simulation runs even in simple scenarios with pedestrians. - Pedestrian module: The density check at pedestrian inputs doesn't work correctly. Sometimes pedestrians are inserted when they should not and sometimes a message is displayed that too many pedestrians were on the area and thus further pedestrians weren't inserted when there aren't many. - Pedestrian module: The resolution for the pedestrian protocol is written as 0 to the input file by default, and such an input file cannot be read (message "Syntax Error"...). [Now, this value is changed to the correct default value of 1.] - Pedestrian module: Pedestrian link with conflict area: Deletion causes an exception message. - Pedestrian module: Error message "Unknown error while creating pedestrian in AnimatePedestrian" during an animation run without pedestrians in the network, followed by an exception message. - Pedestrian module: Pedestrian Input dialog: The (internal) numbers of the pedestrian inputs (possibly used by COM scripts) are changed after the input dialog is closed. - Pedestrian module: Walking Behavior Parameter Sets dialog: The time intervals are not displayed before you click "-" and then "+". - Pedestrian module: Ramps and input areas may not overlap. The consistency check reports an overlap even if it is only the overlap area of the ramp that overlaps (which is necessary). Version 5.10-04 (2008-10-17) ---------------------------- + External signal controllers: VISSIM does not allow to edit data of an external signal controller if the input file has not been saved yet. [This is to make sure that the current directory is the right one.] + Managed Lane Toll Pricing Model: A user-defined DLL can be used for the price calculation instead of a COM script. The C++ header file for this DLL is provided in the subdirectory API\TollPricing_DLL\. + Pedestrian module: The bidirectional width control of a new rectangle is activated with the Ctrl key (instead of Shift which is used for 45 degree angles, too). + Pedestrian module: Improved pedestrian area / ramp / obstacle dialog: A grid of all objects of this type allows to multi-select, delete and zoom (in the local menu). - VISSIM can crash with an exception message during a simulation run in rare cases involving special situations during lane changes. - VISSIM crashes after creating an empirical dwell time distribution. - Driving Behavior Parameter Sets Dialog - Lateral tab: Error when adding a "Vehicle class to be overtaken" if a vehicle class with the same option (on left/on right) already exists. - Partial routes: Once a set of partial routes has been created, the destination sections of the routes can be moved to different positions. This persists even after saving and reloading the *.inp file. - Routes Dialog - Parking Routes - Routing: The column "Parking Lot No." is sorted alphabetically (instead of numerically). - Node evaluation delays can be different from delay evaluation delays even if the travel time sections are placed exactly where the internal sections for the node evaluation are created. [This is not a bug but can happen by design if a vehicle passes the same start section at the exit of a node twice (because of a loop in its route). In this case the delay measurement continues to collect delay while the node evaluation delay starts again at zero as the previous total has already been assigned as one data item to the respective movement. Now a warning message is written to the *.err file whenever a vehicle passes the same travel time start section a second time.] - Signal controller type Siemens VA: New controller EXEs (created with Control 4.6) don't work with green arrow and flashing signal groups: VISSIM crashes during a simulation run as soon as the controller sets such a signal group to a special signal state (flashing or amber-green). - ANM Import: The desired speed decisions are created with the flag "Label" set to false, so no labels are displayed. - ANM Import: Zoom doesn't work in the message window after an ANM Import if the zoom button is active in the VISSIM main window. - Adaptive ANM Import: If the network contains used-defined routing decisions, the import can fail/abort (on adjusting these user defined routing decisions / routes). - Adaptive ANM Import: Fails if a node was imported initially without a specific lane turn configuration but the user creates a lane turn configuration after this and tries to import it adaptively and vice versa. - Adaptive ANM Import: Retained "old" node polygons (manually created after a previous ANM import) do not always include all "new" segments after a subsequent adaptive import. - Dynamic Assignment dialog: Error message "Ungültiges Zahlenformat" is not translated into English. - Pedestrian module: Pedestrian Compositions dialog: can crash after deletion of a selected type/speed/ratio line (except the last one). - Pedestrian module: Dialog "Walking Behavior Parameter Set": - The drop down list of desired speed distributions looks gray as if disabled even though it is possible to select a value. - A left click on the right edge of the splitter between list and details changes the size of the splitter instead of its position. - The left edge of the middle grid is not visible. - A right click in the middle grid opens a context menu that doesn't apply. - Pedestrian module: The offset value of a link which is used as pedestrian area of a level with a height greater than 0 changes after modifying the length of the link. - Pedestrian module: If you scroll with arrow keys while drawing the width of a rectangle, the rubber band is drawn in the wrong position - Pedestrian module: VISSIM crashes after changing the level of an existing pedestrian link and then deleting that link. - Pedestrian module: Adding new vertices to existing pedestrian area polygons is not possible in some cases. - Pedestrian module: The pedestrian routes dialog crashes after changing of a pedestrian class and subsequent creation of a new decision. - Pedestrian module: The warning message about the network size exceeding the limit in the VISSIM license shows the size of one level only, not the size of the whole network. - Pedestrian module: Link behavior type dialog: The context menu "Multiselect in network" is enabled in pedestrian mode. - Pedestrian module: Pedestrian record: Filter and configuration files are not written to the *.inp file and not read in. - Pedestrian module: The OK button of the pedestrian filter dialog is disabled if the section 'Evaluations' is empty in the *.inp file. - Pedestrian module: Deleting several areas at once (in multi-select mode) can cause VISSIM to crash or fail silently if there are routing points on some of the areas. - Pedestrian module: The behavior type of pedestrian links is removed (empty) when the link dialog is reopened. - Pedestrian module: Pedestrians on conflict areas are ignored if the link is (almost) parallel to the x axis (horizontal in 2D view). - Pedestrian module: The detector dialog crashes after changing the pedestrian classes, OK and reopening the dialog. - External Driver Model: VISSIM doesn't consider signal heads and priority rules on adjacent lanes for the suggested acceleration. This causes the "default" DriverModel.dll which simply returns the suggested behavior back to VISSIM to behave differently from the normal internal vehicle behavior. Lane changing vehicles can see red signals too late, possibly causing them to ignore them. - Some bugs in V3DM 1.42. [New version: V3DM 1.42-01, see V3DM\Doc\changes.txt] Version 5.10-03 (2008-09-23) ---------------------------- + Background 3D display mode "Tiles": If no navigation (zoom) is done while the image loads, then the view snaps back to wherever it was prior to texturization. However, if the user decides to navigate (either by keyboard, mouse, or tool) then no snap-back will occur. Furthermore, the main menu is disabled during texture load. + COM Interface: Toll price calculation models can be user-defined through a COM script which is called at the startof each update interval of a hot lane facility. For details please see the updated COM manual under Triggered Scripting. + Pedestrian module: A walking behavior parameter set can have a pedestrian model parameter file assigned for each user-defined time interval. - File selection box crashes on some Windows Vista computers (Exception message or VISSIM closes, e.g. as soon as something is typed into the filename box). - Priority rules: If two vehicles see each a red priority section as relevant leading "vehicle" in the distance and if each priority section is blocked because the other vehicle is already inside the minimum headway, one of the vehicles decides to ignore this priority section. This happens even if the two vehicles would leave the respective headway before reaching the red sections and thus not collide - the geometry of the links is not considered. [Now, the deadlock resolution only considers vehicles that are at most 10.0 meters away from the relevant red priority rule section.] - Network editor: Splitting a link can cause a PT stop on it to cease to work correctly. Moving and editing a PT stop can cause a subsequent adaptive ANM import to fail. - Node Evaluation (compiled data) / queue lengths: The internal queue counters for node evaluation stop counting as soon as they reach an upstream internal queue counter for node evaluation - even if that one is in the same node, causing the determined queue lengths to be far too low. This can happen if not all movements have signal heads or priority rules, so for at least one of them the queue counter is created at the node border. This one is seen by queue counters positioned at signal heads or priority rule sections inside the node. - Selection of an Access database for VISSIM and/or Analyzer database changes the working directory to the directory of the database file. - *.avi file recording: If you start recording an *.avi of a simulation and then minimize the VISSIM window (like if you are going to work on other things while it runs in the background) the final video will not refresh during the simulation time in which it was minimized. - The names of mass or desired speed distributions are not written to the *.inp file and cannot be read in. - After creating a new desired speed or mass distribution VISSIM crashes upon click on OK in the dialog. - The error message file *.err is written in ASCII encoding which can prevent text in Russian, Chinese or Japanes to be displayed properly. [Now, the *.err file is written in Unicode (UTF-8) encoding.] - Adaptive ANM Import / Routing for DTA: An invalid path file is created if the user has changed a node polygon manually so that there exists an edge outside the node polygon but leading back to same node. [Such edges are now ignored on adaptive import for DTA.] - Adaptive ANM Import: If a new signal controller (in the *.anm file) has already been added manually to the network by the user, the signal groups from the ANM data are added to the SC, possibly causing duplicate numbers. [Now, the whole controller is deleted and created newly from the ANM data.] - Adaptive ANM Import: Some user-defined network elements on edges between nodes are deleted unnecessarily. - Adaptive ANM Import: Aborts with the error message "...No valid temporary node number found!" - Adaptive ANM Import: Can abort if there are manually created nodes in the VISSIM network with 10 digit node numbers (which might be used for automatically created nodes for zone connectors, too). [Now, warning messages are displayed when such node numbers are to be used in ANM Import / VISUM Export.] - Adaptive ANM Import: Fails because split link is not possible with a transit stop or other network element with a length > 0 is located on the link. - Dynamic Assignment: Only one destination parking lot per destination zone is used by each origin parking lot. - Pedestrian module: VISSIM crashes when a recorded *.ani file is played which contains pedestrians. - Pedestrian module: It's impossible to select or move a route point if the location is on a level with a height of more than zero. - Pedestrian module: Pedestrian Compositions dialog: New lines added to the list of types and changes in cells are lost after closing the dialog with OK. - Pedestrian module: The default pedestrian weight distribution is not generated (and assigned) when loading an existing *.inp file in which no pedestrians are defined. Instead, another (randomly selected) distribution is assigned to the default pedestrian types. - Pedestrian module: The resolution of the pedestrian record is interpreted as simulation seconds (instead of time steps). - Pedestrian module: Exception when clicking on a ramp after having created a new level with the ramps dialog open. - Pedestrian Module: Travel time evaluation files are created but no data is written (0 pedestrians in all intervals). - Pedestrian Module: If the first level has a height greater than 0 m VISSIM crashes after the creation of a pedestrian link without setting the height at least to the level height. - Pedestrian Module: Checking at inputs for routes for each pedestrian type doesn't work properly in some cases. Version 5.10-02 (2008-08-29) ---------------------------- + Multi-Run / SC/Detector Record: The current random seed / run index is appended to the evaluation file name prefix (just before .ldp). + Desired speed and mass distributions have the new attribute 'name'. + COM Interface: New functions WriteChannel and ReadChannel in the SignalController interface, allowing to write a value directly to a SC communication channel of a controller (overwriting the value passed from an other controller if this channel has been selected as input channel in the SC communication dialog) respectively to read a value from a communication channel (which must have been set by the controller dll or exe). + Pedestrian module: Level of service (LOS) display in 2D mode during a simulation run if "Aggregated values" is selected under View / Options / Traffic. Switching between several LOS definitions is possible through the shortcut key "L" - the name of the current definition is displayed in the status bar. (A future version will have a dialog which shows the color-coding and allows to create user-defined LOS definitions.) + Pedestrian module: Checkbox "No Visualization" for pedestrian areas and ramps, causing pedestrians on this area not to be displayed in 2D and 3D when selected. + Pedestrian module: Copy functionality in the dialogs for pedestrian classes, pedestrian types and pedestrian compositions. + Pedestrian module: Zoom Feature for pedestrian routes, travel time measurements and inputs in the dialog's grid's context menu. + Pedestrian module: New mass and desired speed distributions for different types of pedestrians. - Multi-Threading (use of more than one processor core) can cause wrong lane selection despite of downstream connectors and thus vehicles leaving the network (reported in the *.err file). - Network Editor / Multiselect Mode: If connectors have different lane change distances they are all set to zero when the dialog is closed with Ok. - Priority rules: may disregard upstream vehicles just inside the look-back distance that have just passed a red priority rule section: If a vehicle passes a red priority rule section but doesn't pass another downstream network object (see list below) in the same time step and if that priority rule section is just outside the maximum lookback distance of a downstream green priority rule section, the downstream priority rule ignores the vehicle in this time step (but not in the next one). Network objects passed that prevent this problem are: green priority rule section, signal head, stop sign, data collection point, travel time section, detector, reduced speed area, start or end of connector. [This fix can cause VISSIM 5.10-02 to have different simulation results from previous versions!] - Background graphics: Some DWG backgrounds get distorted and misaligned with the network in 2D mode when zoomed or panned. - Detectors are drawn not wide enough (possibly even invisible) if the lane width is smaller than 2 m. - The SC/Det. Record window flickers during a continuous simulation run on several graphics cards (e.g. Nvidia GeForce FX 5600XT, GeForce 6600, GeForce 7600GT, Quadro FX 1700, Quadro FX 370). - Animation Recording: If only a part of the network is visible (i.e. it is zoomed in) during the recording of an animation file (*.ani), the *.ani file contains alternative link display information only for the visible part of the network. - Animation run: Both blinkers are on while a vehicles brakes. - Animation Parameters dialog: From times below 1.0 are not accepted but it's possible to create .ani files that have zero as start time as default value without entering the dialog. - Animation Parameters dialog: A new overlapping interval is accepted if the new interval starts before an old interval and ends after the old interval. - Signal Control dialog: After changing the name or number of a SC and selecting a different controller from the list the scroll bar jumps to top of the list. - The license dialog doesn't have a Close button anymore. - The detector dialog doesn't suggest the values from the last edited detector anymore for a new detector. - An *.inp file saved with 1) Analyzer evaluation switched on and 2) empty analyzer database connection string can not be opened ("bug on writing analyzer evaluation data"). - Test Mode: If the simulation resolution is higher than one time step per second PT telegrams that are not entered in the very last time step of a second are not passed to the signal controller(s). - Error in file selection dialog under Scripts - Run script file... when trying to select a Python script file with extensions *.pys or *.py. - Export - VISUM - Nodes/Edges: Overlapping VISUM node numbers are generated if VISSIM node numbers > 999999999 exist (more than 9 digits). - Export - 3DS Max: The gradient of a vehicle (used only for 3D and ANI) can be undefined if the vehicle's front and back edges are not on the same link. This can cause a corrupt ani.txt file which cannot be imported into 3DS Max. - Import - Synchro: Doesn't work with VISSIM level 1 licenses (because of the limitation to 2 link types). [Now, only two link types are created for level 1 licenses: VISUM link type 0, VISUM Junction Editor.] - ANM Import: can crash with an access violation if two adjacent nodes have only a short distance. - Dynamic Assignment: Damaged error message "Zone No. 0 which is defined in (a) matrice file(s) is not assigned to any parking lot." - Dynamic Assignment: Using 0 as the number of previous iterations for the MSA method causes corrupt *.bew files (with negative cost values) that cause the shortest path search to crash during the next simulation run. - Pedestrian module: Error message "Unknown error while creating pedestrian in AnimatePedestrian" during an animation run without pedestrians in the network, followed by an exception message. - Pedestrian module: The start of a test run takes a very long time in a large network with pedestrian elements (because objects for the simulation are initialized unnecessarily). - Pedestrian module: Pedstrian inputs add pedestrians to input areas even if the density is above realistic values. [Now, no pedestrians are added while the density is at least 4 pedestrians per square meter. The waiting pedestrians are added as soon as the density drops below this threshold.] - Pedestrian module: Area evaluation has wrong aggregated values especially with low numbers of observed pedestrians. - Pedestrian module: The default value of maximum speed for detectors is too small (1 m/s). [Has been changed to 10.0 m/s.] - Pedestrian module: VISSIM can crash after deleting a pedestrian route from the routes dialog. - Pedestrian module: VISSIM crashes during an animation run with a pedestrian on a ramp. - Pedestrian module: When an old *.inp file (without pedestrians) is loaded, the automatically created default level has No. 1 and not 0. After selection of "Base Data - Level Properties" an exception occurs. - Pedestrian module: Level 0 is not editable. - Pedestrian module: Obstacles may not overlap with pedestrian areas that have a pedestrian input. - Pedestrian module / Network Editor: Exception message if the selected geometry mode in toolbar (Polygon, Rectangle) doesn't match an edited area's type. - Pedestrian module / Network Editor: In editor mode "measurement areas" the pedestrian areas are drawn as selectable (like in pedestrian area mode). - Pedestrian module: Rotate network doesn't work for pedestrian areas and measurement areas. - Pedestrian module: Creating a pedestrian link on a level with a height > 0 creates a pedestrian area with the level's height and a pedestrian link with double that height. - Pedestrian module: Changing a level's height doesn't change the height of the pedestrian links on that level. - Pedestrian module: The default interval of pedestrian inputs always ends at 99999 and not with the simulation end time. - Pedestrian module: If a ramp's base/top intersects in x/y with an input on another level a warning/error is posted unnecessarily. Version 5.10-01 (2008-07-29) ---------------------------- + Network editor: If the attempt to change a route by dragging an intermediate point is unsuccessful (because not route using the new position can be found) a warning message is displayed. + Status line information about pedestrian visualization (switched through Ctrl-Q). + Pedestrian travel time measurements results are displayed in the travel times window. - 2D visualization: Both blinkers are on while a vehicles brakes. - The pavement markers 'zebra crossing' are drawn incorrectly when not in pavement marker mode. - Network editor: Detectors and pavement markers are invisible while being moved away from their original position. - ANM Import: PT lines with invalid link sequences/routes cause the simulation to crash. - Pedestrian module: Pedestrians do not head for the closest point on the border of a destination polygon but they head for the average of the corner coordinates of the destination polygon. Version 5.10-00 (2008-07-18) ---------------------------- + Faster simulation by a new implementation of multi-threading for time-consuming algorithms which makes better use of multiple processors and processor cores. The number of processor cores to be used can be set in the Simulation Parameters dialog. + Faster simulation in networks with (many) priority rules with many upstream look-back alternatives, e.g. through single parking spaces on separate links/connectors. + New pedestrian model (add-on module): Area-based social force model, including network editor for multiple floors. + Managed Lane Routing Decisions for managed lanes, with user-defineable toll pricing model and decision model, depending on vehicle occupancy (SOV, HOV2, HOV3+), simulation time and current traffic situation (travel time savings, average speed). + Complete unicode support for filenames (for Russian, Chinese, Japanese). + Menu item "Log Window" (in "Help" menu) opens a window with error and warning messages. + Filter for link behavior type or display type: Right-click on the selected type in the type dialog, "Multi-Select in Network" in local menu, OK in dialog, keeps the links with that type selected in multi-select mode. + Vehicle Input dialog: Additional item "scale volumes" in the context menu of the grid. If selected, a dialog asks for a factor, and the volumes in all selected cells are multiplied by this factor. + Additional parameters for conflict areas: + Gaps and Safety Distance Factor vehicle-class dependent + Additional Stop Line Distance (for yielding vehicles) + Observe Adjacent Lanes (yield to lane-changing vehicles) + Anticipate Routes (don't yield to vehicles that take a turn upstream of the conflict area) (ratio 0..1, default 0) + Avoid Blocking of the conflict area (ratio 0..1, default 1): If a prioritized vehicle is in the selected percentage, it checks the room downstream of the crossing conflict area. If this is less than the vehicle's length plus 0.5 m and if the blocking vehicle is slower than 5 m/s and slower than 75% of its desired speed (or if the obstacle is a red signal head), the prioritized vehicle will not enter the conflict area. (The condition for minimum exit speed 2 m/s has been removed.) + Link parameter "No Lane Change": Vehicle-class dependent prohibition of lane change (per direction). + Driving parameters minimum and maximum look-back distance in parameter set dialog. + Default Driving Behavior Parameter Set "Urban": number of observed vehicles changed from 2 to 4 + Network Elements Display: New option "Lane change distance / emergency stop position" as label for connectors. + Units for length, speed and acceleration are translated into the selected language when displayed in dialogs or evaluation files. + Evaluations: The VISSIM version, service pack and build number are written to a new line in the file header. + Evaluation of signal changes: The columns of the output file are separated by semicolons. + Evaluations / Database output / SQL Server / Multirun: fails because of timeout if a huge amount of data has to be written. + The VISSIM build number is written to line 4 of the *,inp file (after the version and service pack number), too. + Special versions show "Demo" / "Uni" in title bar and file version properties. + New external signal controller emil_controller.dll for fixed time control with graphical signal time table editor (emil_gui.dll). (This will eventually replace the internal SC type fixed time, and an extended version will be available which contains automatic creation of signal times.) + New controller type RBC (Ring Barrier Controller) with graphical interface. The new controller has the ability to simulate up to 16 vehicle phases, 16 overlaps, 4 rings, and 16 barriers and includes many new features. Please see the RBC manual for further details. + New signal controller type LISA+ OMTC. + Signal program number can be set for controller type "External". + Signal Times Table window: The width of a (signal controller) time step in the signal times table is now the (usual) 4 pixels only if the controller runs at 1 time step per simulation second. If the controller runs at 2 time steps per simulation second one time step is 2 pixels wide, and if the controller runs at 3 or more time steps per simulation second one time step is only 1 pixel wide. The cycle second is displayed only for each full 10 seconds even if the controller runs at several time steps per simulation second. Tick marks are displayed for each full 5 seconds. In addition, if the controller DLL (or EXE) sends the same cycle second more than once in a row, it is displayed only the first time as label on the time axis. The signal times table can now remember up to 5000 controller time steps (instead of only 500 so far) + Background files: Warning message if the file to be loaded is bigger than the free physical memory with option to load it anyway after user confirmation. + Background files: Improved drawing of vector formats (from CAD programs). + View / Options / Colors / 3D Background Resolution: New option "Tiles" with user selectable tile size (in pixels). This option splits the background file into square tiles which are loaded and displayed separately. + Analyzer dialog: Ability to both edit and delete time periods: Right click opens a new blank dialog (create new); double left click on an existing time period opens that time period for editing. New edit dialog has delete button. Delete is also possible by highlighting a time period and selecting the delete key. + Analyzer Evaluation/Reports: allow any SQL:1999 conform database type (instead of only Microsoft Access). + Analyzer Report: 85th percentile speed added to travel time report. + Analyzer Report: Average queue length column added to the queue lengths table. + New pavement marker type "Zebra Crossing". (To be placed on the crossing pedestrian link because the stripes are placed parallel to the link.) + ANM Import: Emergency stop distance of connectors for turning movements in ANM nodes has been changed to pocket length minus 10 meters. + ANM Import: Driving Behavior Parameter Set "Urban": The waiting time before diffusion has been changed to 120 seconds. + ANM Import: In signalized nodes the front gap for a conflict area of a movement left-turn movement yielding to a crosswalk is set to 2.0 seconds. (This allows vehicles from the opposing right-turn (with 0.5 seconds front gap) to start moving before the left-turning vehicles in most cases.) + COM Interface: Access to vehicle inputs through the link number: Function GetVehicleInputsOnLink(), read-only attributes LINK and TRAFFICCOMPOSITION. + COM Interface: Functions AddVehicleInput(), RemoveVehicleInput(), attribute TRAFFICCOMPOSTION writeable. + Dynamic Assignment: Option to save zipped path and cost files created during a multi-run series. + Dynamic Assignment: Expected, measured and smoothed path travel times can be listed in the path evaluation (in addition to the expected, measured and smoothed totals of edge travel times). (Smoothed path travel times are written to the path file as well but not yet used for dynamic assignment. This option will be added eventaully.) + Emission model: Vehicle weight and power are derived from the distributions in the vehicle type (not from the emission layer file). Model year and mileage distributions (which were not used at all) have been removed completely. - Everything listed in 5.00-09 (except where 5.10-02 is mentioned) plus: - Multi-Run: The message "Error opening file *.fzi" (if the configuration file for the vehicle information window is missing) must be clicked away before each run. - Traffic composition dialog; Cancel button doesn't work properly (deleted vehicle types are removed even if the dialog is closed with Cancel). - Signal Control dialog: After reading an *.inp file with a signal group of type "Perm. Green" or "Perm. Red", changing this type to "Cycle" results in zeros being written to "Red End 2" and "Green End 2". Because this is not allowed an error message appears and the zeros need to be deleted manually ("Red End 2" and "Green End 2" must remain empty as long as they are not used.) - 3D Signs: Background and border color is not saved in the *.inp file. - Analyzer: Nodes with the flag "use for evaluation" not set are included anyway. - COM Interface: Registering VISSIM manually as COM server doesn't work on Windows Vista with the simple call "vissim-regserver" from the command line. [The VBS script RegVISSIMAsCOMSvr.vbs has been added to the Exe\ directory. This script can be run to register VISSIM as COM server on Vista.] - COM Interface: Wrong error message is passed to the COM client if no 3D model file exists while reading an INP file and later an error occurs afterwards while running a simulation. For example if a wrong parameter is passed to a method during a simulation run the message "3D model file xxx not found" is passed to the COM client. Version 5.00-09 (2008-07-25) ---------------------------- + Background files: Warning message if the file to be loaded is bigger than the free physical memory with option to load it anyway after user confirmation. + ANM Import: + The emergency stop distance of connectors for turning movements in ANM nodes has been increased to pocket length minus 10 meters. + Driving Behavior Parameter Set "Urban": The waiting time before diffusion has been changed to 120 seconds. - VISSIM hangs (and possibly even crashes after all RAM has been used up) at the start of a simulation run with nodes or Analyzer evaluation enabled if there is a very short connector pointing backwards on the same link (possibly with identical from and to link coordinates). [Now a warning message is displayed announcing a possibly extremely slow simulation.] - Conflict Areas: Error message "Some conflict areas from the input file could not be created" when loading an *.inp file if the conflict areas start exactly at the beginning of one of the links. - Standing vehicles cannot change to a lane with a nearby conflict area: If a vehicle that cannot move (more than a few meters) on its own lane (e.g. because of a dwelling bus in front of it) sees a conflict area on the adjacent lane it assumes that it will never pass that conflict area because its expected trajectory is standstill. Thus, the vehicle calculates the additional room on the adjacent lane only up to that conflict area which might not be enough (less than 1.5 times the vehicle's length) to warrant a lane change. - Partial routes: Once a set of partial routes is established, the destination cross sections of the routes can be moved to different positions. Even after saving and reloading the *.inp file it remains like this. - Parking Routes: PT vehicles (!) aiming at a downstream parking space don't overtake PT vehicles standing in the next upstream parking space if there is less than 2 m reserve room (in addition to the length of the second PT vehicle) downstream of the standing vehicle. - PT Lines: Buses aiming at a downstream bus stop alternate in and out of that lane between vehicles standing in upstream parking spaces (and they don't overtake conflict areas). - Block signals (editable only in the *.inp file) can in rare occasions display green when they shouldn't. - Link segments of a segment node are not adjusted if a link or connector is edited using the link spline feature (ALT + left mouse drag from segment to segment). This can cause subsequent problems due to a corrupt node/edge structure. - Node evaluation raw data ASCII output: all values are written into the file without any decimals. - Display Type dialog: The selection is lost after modifying the number of a type or copying a type. After this, VISSIM crashes if the active type is deleted. - Display Type dialog: If a texture is deleted from a display type the *.inp file written subsequently cannot be read in because of a reference to texture number 0. - Link Behavior Type dialog: Exception message after the selection in the "Vehicle Class / Driving Behavior" grid is lost (e.g. after opening the vehicle class combo-box and hitting Esc) and a subsequent click on "Delete" in the context menu. - The edge selection dialog can be opened even if there is no node for dynamic assignment. [Now the message "No DTA nodes exist!" is displayed instead.] - 3D Signs dialog: The units for the sign dimensions are always displayed in metric even if selected differently in View/Options. - Test mode: The simulation time is increased by 1.0 each time step even if a simulation resolution of several time steps per simulation seconds is used. This causes external controllers with a controller frequency above 1 not to work correctly. - Analyzer: Error message "There has been an error generating this report, please s. AnalyzerErrorLog.txt for details" during the creation of a report if there are many omitted nodes. - ANM Import: Lane closures are not preserved for links and connectors and thus not considered for static routes nor for dynamic assignment. [Now, additionally, if the from lane and to lane of a lane turn are closed for a vehicle class the corresponding VISSIM connector is now closed for it as well, even if the ANM lane turn is not closed for that vehicle class.] - ANM Import: The route finding routine doesn't always use the shortest edge inside a node. - ANM Import: Aborts with the error message "Link data cannot be generated. Existing corresponding VISSIM link doesn't allow split operation" if a parking lot exists at the split position. - Initial ANM Import: Exception message with the message "Internal error: CalculateNodeSegments: previousConnector->V_Nach != maxLink?" in the *.err file. - Adaptive ANM Import: Fails with runtime error "Unexpected end of node x" if the node/edge structure is invalid (e.g. because of editing of connectors in a segment node). - Adaptive ANM Import: Aborts if ANM FromTimes not changed (*.panm file and *.anm file) but the user manually changed the start time in VISSIM. - Adaptive ANM Import: Fails because split link is not possible with a reduced speed area located on the link. - COM Interface: The attribute "IDVEHICLES" of the IDataCollection interface returns the last collected results if no vehicle data was collected during the previous interval. - COM Interface: The method GetArrived() of the IVehicles interface returns erroneously an empty collection of vehicles. Vehicles routed with paths from the dynamic assignment path set using attributes like DESTPARKLOT or DESTZONE of the IVehicle interface disappear from the network when reaching their destination parking lot although they were added to the network using the COM interface with methods like AddVehicleInParkingLot(). - Dynamic Assignment: Error message(s) "parking lot x is full" at the start of a simulation run if a trip chain file contains an unknown zone number. - Dynamic Assignment: Memory leak during the reading of parking lots from an *.inp file (only relevant for networks with many parking lots). - Dynamic Assignment: Shortcut Ctrl-Z doesn't work correctly. These bugs were not fixed in 5.10-00 but in 5.10-02: - Signal control dialog: If an external SC has no controller program dll (or exe) defined (i.e. empty field in the signal control dialog), an exception message is displayed at the start of a simulation run. - ANM Import: Lane closures are not calculated correctly in some cases for left-side traffic. - ANM Import: Aborts with an exception message if a node includes a one way exit link that is connected with its inbound neighbor through a triangle island. - Adaptive ANM Import: If a node's geometry has to be re-created user-defined parking lots and reduced speed areas and other network objects on the node or close to it can be deleted. - Adaptive ANM Import: After the routes import many route decisions are located "under" a connector so they don't affect the vehicles. - Synchro Export: "Full simulation" and "Demand volumes" modes result in all volumes zero in the generated file. Version 5.00-08 (2008-05-07) ---------------------------- + Public transport lines without start times are accepted (for ANM Import). + Analyzer: Warning message at the start of a simulation run if Analyzer Evaluation is active but no nodes are selected for evaluation. + Adaptive ANM Import: If the new ANM FromTime is different from the old one, then the VISSIM simulation start time is set to FromTime and the PT lines departure times are adjusted according to the change of the start time.. + COM Interface: Link attribute "TYPE" replaced by "DISPLAYTYPE" and "BEHAVIORTYPE". + COM Interface: New read-only attribute "ISRUNNING" in the ISimulation interface: true during a simulation run, otherwise false. + COM Interface: New read-only attributes "LINK" and "TRAFFICCOMPOSITION" in the IVehicleInput interface to allow to find the appropriate vehicle input by iterating over the collection of all of them. (This makes the vehicle input number obsolete.) - Exception message "interakt.cpp, line 3321" during a simulation run: This can happen if a standing (or very slow) vehicle cannot accelerate because its maximum and/or desired acceleration (decreased by 0.1 m/s² per % gradient) is zero (or less) for its current speed. Usually, this is caused by too small lower bound values of a user-defined maximum or desired acceleration function, typically for HGV (where the chance of using the lower bound is higher). - Stop signs don't work for vehicle following model "No Interaction". (This bug was introduced in version 5.00-07.) - Network Editor: Static routes and PT lines can be created across an impossible link sequence if a connector from a link to the same link overlaps with the next connector of the route from the same link so that the first connector ends downstream of the start of the second connector. When VISSIM tries to complete this broken route at the start of a simulation run (or when selected in the routes / PT lines dialog) it enters an infinite loop so it uses up all available memory and then crashes. - Network Editor / Data Collection Points mode: A right click outside any net object in opens an empty dialog. - Network Editor: If a polygon node containing no links and connectors is converted to a segment node it becomes invisible and cannot be converted back. [Now, a warning is displayed instead of the first conversion.] - On-street parking: A vehicle trying to enter a parking space blocks the exit of the vehicle trying to leave it (or a upstream one, having moved downstream inside the parking lot). - Parking lot routes: The route search back from a parking space to the original route of a vehicle has a memory leak. If the original route has many links and if there are many vehicles using parking spaces the RAM can be used up quickly and the lost memory doesn't become available again after the simulation run, so the RAM can be insufficient after some runs (without closing VISSIM in between). This causes first a massive breakdown in simulation speed and finally an "out of memory" crash. - Parking lot routes: VISSIM crashes during a simulation run if a vehicle on a broken route passes a parking lot routing decision. - If some changes were made in the network before a multi-run simulation and thus VISSIM needs to ask for saving it before the run then the *.inp file is saved in the specified multi-run output directory with the random seed appended to the filename. - If only data in the multi-run dialog has been changed the message "Data has been changed. Save changes?" is not diplayed before simulation start nor when VISSIM is closed. - Analyzer: Error message "Analyzer Data Evaluation not possible: error creating data base *.mdb!" at the start of a simulation run if the same database is used for Analyzer data and for another active evaluation (e.g. travel time raw data). [Now, the database names must be different when defined.] - Generation of Analyzer report does not work if the Analyzer database was created with MultiRun and the selected language is not English. - Generation of Analyzer report does not work with user-defined time intervals if French is selected as language. - Exception message when the PT line selection dialog is closed after a click in the (empty) third column. - Vehicle Inputs dialog: Error messages can refer to a hidden cell (e.g. an empty composition cell if only volumes are displayed). [Now, the respective row is made visible automatically.] - Parking lot dialog: Change location ("At") works only for on-street parking lots, changes for other types have no effect on OK. - 3DS Max Export: The vehicle position in the ani.text file is set to the center of the vehicle but the 3DS Max script uses the value for the front edge. - ANM Import / Routing: If no routes are in the file the error message "During reading of ANM file, parsing failed..." is displayed. - COM Interface: A vehicle input can cease to work correctly after changing its volume with the attribute VOLUME or its time interval with TIMEFROM and/or TIMEUNTIL: - If the vehicle input is stochastic, changing VOLUME during a simulation run but after the end of the vehicle input interval has no effect, even if TIMEUNTIL of that time interval is changed subsequently. - If the vehicle input is exact, VISSIM can crash if VOLUME is changed during a simulation run. - COM Interface: The attributes 3DMODELSTATE of IVehicle and STATE of IStaticObject are always -1. - COM Interface: VISSIM does not return 1 and 0 for the detector attributes IMPULSE, PRESENCE, DETECTION, but -1 and 0. (This bug was introduced in version 5.00-05.) - VAP 2.16-03: Better error messages including the current SC number. - Dynamic Assignment / ANM Import: Warning "Parking lot has a relative volume but no paths" at the start of a simulation run after ANM Import for dynamic assignment if there are fractional volumes (exported from VISUM) in the ANM routing data which are rounded down to zero. [Now, the flag "Search paths for O-D pairs with zero volume" is activated by default during the ANM Import, so paths exported from VISUM for these relations are not discarded.] - Dynamic Assignment / ANM Import: Parking lots are not created correctly during the ANM Import if there is not enough room between two VISSIM nodes to place a standard 3,5 meter parking lot on the edge between the nodes. This causes the error message "Parking lot is not on an edge" at the start of a simulation run. - Dynamic Assignment: Exception message at the start of a simulation run during the check of the edge structure read from the path and cost file if the network contains nodes which are used only for evaluation and have smaller numbers than nodes used for dynamic assignment. - Dynamic Assignment: Trip chain files don't work together with PT lines, vehicle inputs and matrices if (small) vehicle numbers listed in a trip chain file are duplicated by other inputs. - Emission Model: The weight of a vehicle given in the emission layer file is wrongly multiplied by 1000. This causes wrong driving behavior (low acceleration) if the vehicle type has the category HGV. [The driving behavior of vehicles with category HGV and an assigned emission layer still differs between a simulation run with emissions in the VISSIM license and another run without emissions in the VISSIM license! The weight and power of a vehicle is defined by the emission layer file (*.sch) if emissions are activated (so the mass and power distributions from the vehicle type are ignored).] - VISSIM API: The x/y world coordinates for vehicle front and rear ends passed to the DriverModel.DLL are off. (They are based on the auto-translated network centered on (0.0, 0.0).) Version 5.00-07 (2008-04-04) ---------------------------- + Intergreen times (amber, red/amber) for a SC of type "External" can now be controlled by VISSIM (as specified by the SC GUI DLL) if the external controller DLL requests this. + ANM Import / Reduced Speed Areas: The default deceleration for HGV and BUS has been reduced from 2.0 to 1.3 m/s². + COM Interface: New read-only attributes "LINK" and "TRAFFICCOMPOSITION" in the IVehicleInput interface to allow to find a specific vehicle input by iterating over the collection of all of them. - VISSIM cannot open files that contain a blank character between the filename prefix and the extension. (This bug was introduced in version 5.00-05.) - VISSIM does not open an *.inp file that contains strings of more than 200 characters, e.g. a database link on a network drive. It can crash after opening such a file, too. - Several special characters (e.g. Umlaut characters: ÄÖÜäöü) are not accepted in dialogs in edit fields for filenames, even if the *.inp file name contains the same character(s) (message "Filename expected!"). - Read Additionally: If there are link behavior types or display types used by connectors in the network to be read additionally which don't exist in the original network VISSIM can crash with an exception message (up to VISSIM 5.00-01) or stop the reading with the message "Unknown link type". - Read Additionally: "New numbers" is selected (and disabled) for conflict areas (which doesn't make sense as conflict areas don't have numbers). - Read additionally: "Keep original world coordinates" doesn't work correctly: The additional network is not at the right position. (This bug was introduced in version 5.00-05.) - Vehicles using the car following behavior "no interaction" (e.g. the default pedestrians) stop forever upstream of reduced speed areas. [Now, they ignore reduced speed areas.] - Vehicle inputs with stochastic volumes generate different input times in multi-run and single run mode if data collection for aggregated data (*.mes) is activated. - External signal controller EXE: VISSIM does not find the signal control executable (program file of an external signal controller) if it is located in the Exe\ directory (but only if it is located in the data directory). (This bug was introduced in version 5.00-05.) - Node evaluation: Emission parameters cannot be written to a database (message "Error creating table NODEEVALUATION!" at the start of a simulation run). - The 3D model files Woman20Frames-Biz1.v3d and Woman20Frames3.v3d are corrupt (position of front axle and rear axle = 0.0) causing vehicles using them to be invisible in 2D and 3D mode. - Animation: Playing an *.ani file recorded with VISSIM 5.00-06 causes a run-time error. (These files are corrupt. They cannot be replayed with 5.00-07 either.) [New *.ani files recorded with 5.00-07 are okay.] - Network Editor: Conflict areas might not be created if one link is nearly orthogonal to the x-axis (vertical on the screen). - Network Editor: Moving a routing decision downstream along its route(s) can cause the warning message "Broken routes" after saving and reopening the *.inp file even if the routes could start without problems from the new position. - Network Editor / PT Line Mode: Clicking Del or Edit/Delete when a link with a PT line start section is selected causes an Exception message. - Network Editor / Nodes Mode: A double click on a selected node does not open the node dialog if nodes already overlap (displays a warning message only). - Network Editor / New Connector: VISSIM crashes if the "Insert Connector" dialog is closed with the close button (X) instead of the Cancel button. - Network Editor / Split Link: If the dialog "Select split position" is closed with the close button (X, right upper corner) all menu items stay disabled. - Network Editor: Closing of dialogs with the close button (X, upper right corner) does not work correctly (as Cancel) for: PT Lines, New Starting Time, New Dwell Time Distribution, New Dwell Time Normal Distribution, Conflict Areas. - Test mode: The shortcut keys + - * / 1 for simulation speed don't work. - Dialog "Link Behavior Type": Typing a name after creating a new behavior type (without assigning any vehicle class) and then assigning a vehicle class causes VISSIM to crash. - The initial language after the installation from a different user account is always English. - ANM Import: Reduced speed areas are generated for weaving sections. - Adaptive ANM Import: fails if nodes with active flag "Node evaluation" exist in the current network. - COM Interface; vissim.Evaluation.AttValue("SCDETRECORD") = True does not work. - COM Interface: VISSIM displays some warnings and messages in message boxes even if it has been started via COM. - COM Interface: When the dwell time distribution of a stop sign is set (with the attribute TIMEDIST) VISSIM doesn't check the existence of this distribution number, causing a subsequent exception message. - Dynamic Assignment: Exception message during a simulation run if there exists a non closed path for a specific relation (from plot - to plot - vehgroup) in one evaluation interval but all paths found for the same relation in the next DTA evaluation interval include route closures. - Dynamic Assignment: Two iterations starting from the same path and cost files and using alternative path search can have different results. [After this fix, the iterations are reproducible but possibly different from earlier versions.] Version 5.00-06 (2008-02-21) ---------------------------- + ANM Import / Static Routes: Each routing decision is assigned a name containing the ANM origin zone number. + ANM Import / Dynamic Assignment: If an *.anmRoutes file is imported with the option "for dynamic assignment" and if there is no matrix data in the file a warning message is displayed. - VISSIM can crash during the startup after displaying the splash screen if the driver of the default printer doesn't work correctly. - Conflict Areas: Merging areas with different length on the two conflicting links can cause a deadlock if one vehicle has just entered the conflict area while the other one is standing just outside. - VISSIM can crash with an exception message (Unknown exception in interakt.cpp, Line 7473) during a simulation run in a network with conflict areas. (This bug was introduced in version 5.00-05.) - VISSIM can crash with an exception message (Unknown exception in interakt.cpp, Line 7460) during a simulation run in a network with a conflict area close to a reduced speed area on a multi-lane link. (This happens when a vehicle approaches this combination of network elements during a lane change.) (This bug was introduced in version 5.00-05.) - Driving behavior: Vehicles can miss their route after having parked on a parking space. If the original route of a vehicle has a necessary lane change soon after the first connector that the vehicle reaches after returning from the parking space to the original route, the vehicle doesn't anticipate this on the previous link, so it might be too fast to stop before the emergency stop position, thus missing the next connector of its route and leaving the network at the end of the link. - Changed driving behavior parameters for 'Reduced safety distance close to a stop line' (under Driving Behaviour Parameter Sets -> Signal Control) are not written to the *.inp file if none of the values is bigger than its default. - Delay evaluation: If a vehicle using the Wiedemann 99 car following model is assigned a lower desired speed by a desired speed decision while it is on a travel time segment, the delay calculation adds a few seconds delay to the real value incorrectly because it expects lower deceleration values. [There's no problem with the Wiedemann 74 car following model, nor with desired speed decisions that increase the desired speed.] - Node evaluation: If an *.inp file is saved after a simulation run with activated node evaluation the internal travel time measurements and delay measurements are written to the *.inp file, too, and thus subsequently included in the normal travel time and delay evaluations. (This bug was introduced in version 5.00-05.) - Leaving a signal times table open when opening a different VISSIM file which doesn't contain this signal controller number causes a fatal error. - 3D Model selection dialog: VISSIM looks for the non-existing SelectVehic_C.dll if the language is Chinese and shows an error message. [For VISSIM 5.00, the English version is used. A Chinese dialog will be available in VISSIM 5.10.] - COM Interface: Writing a time interval with AttVal ("TIMEFROM ") doesn't change anything. - COM Interface: Writing a desired speed distribution number with AttVal1 ("DESIREDSPEED, ) doesn't work. It returns the error "The passed value is not valid." - ANM Import: In links with many closely spaced intermediate points sometimes a considerable number of points is missing. - ANM Import: Conflict areas on crosswalks are not created if the crosswalk doesn't extend for at least 5 m downstream of the conflict. - ANM Import / Static Routes from an ANM file with parallel links exported from VISUM fails with the error message "VISSIM route not created, ANM link sequence could not be deduced." (This bug was introduced in version 5.00-05.) - ANM Import: If an ANM or ANMRoutes file is located directly in the root folder of a local drive, the VISSIM import cannot find it and posts an error. - ANM Import / Static Routes: The vehicle type percentages in traffic compositions for vehicle inputs are not updated during the import of an ANM file with more than one vehicle type (only volumes are changed). - ANM Import aborts with the message "GetBisector. Second (first) segment is trivial" if there are two or more pockets on a link that are both longer than the link polygon. - Dynamic Assignment: VISSIM generates corrupt path and cost files (with a bigger specified number of edges than the number of listed edges) if both the path and cost files are written and the node evaluation is activated and there is at least one node which is not used for dynamic assignment but for the node evaluation. This causes the error message "The node number could not be read" when such a path or cost file is read in later. (This bug was introduced in version 5.00-02.) - Dynamic Assignment: The node evaluation has wrong results for nodes that are used for dynamic assignment, too (volume and delay mostly zero) and possibly wrong results for nodes that are not used for dynamic assignment (travel time start section can be placed upstream of an upstream node, so delay can include delay from an upstream node). (This bug was introduced in version 5.00-02.) - Dynamic Assignment: Exception message ("Assertion failed in file bewdatei.cpp, line 512" in the *.err file) during a simulation run after the paths dialog had been opened. - Dynamic Assignment / Create Static Routing: If the simulation period has been changed after the path file has been written so that the number of saved path volumes (one per evaluation interval) doesn't fit anmore VISSIM issues one error message per path. [Now, there's only one warning.] Version 5.00-05 (2008-01-23) ---------------------------- + Several improvements for conflict area behavior: + Vehicles on the minor road can always enter a merging (!) area if there is no traffic on the major road - even if they cannot leave the merging area. + Vehicles have a better expected trajectory calculation when approaching a standing obstacle. + Vehicles don't enter a (long) crossing area that they cannot pass even if they can initially move with the same acceleration as in free driving. + Routes Dialog: Shortcut for selection of all routes: New context menu item "Select All", in both the decisions and routes grid which selects all rows and columns in the respective grid. (Ctrl-A could not be used because this toggles the link display in the network window.) + Routes dialog: Tabs Static, Partial, Closures: After selecting a decision the first route of that decision is automatically selected (and thus displayed in the network window). + ANM Import: extended for files exported by SITRAFFIC Office. + ANM Import - Routes: VISSIM route numbers of static route decisions are set to the unique IDs of ANM routes. (This allows to find them in the *.anmroutes file and to determine the associated O-D relation.) + ANM Import: Matrix (*.fma) file names include the name of the *.inp file to avoid overwriting matrix files from a previous import. - VISSIM can crash during a simulation run if a vehicle that can overtake other vehicles on the same lane has a desired deceleration of zero (i.e. if the upper bound of the desired deceleration function of its vehicle type is zero). - Conflict Areas: A vehicle with right of way standing upstream of a conflict area doesn't enter it even if there is enough room downstream. This can happen if the driving behavior parameter set for this vehicle on its link uses the car following model Wiedemann 99 which limits the acceleration in the very first time step of free driving to cc7 (the oscillation acceleration). The vehicle wrongly expects to use this acceleration throughout the conflict area, so if the conflict area is not long enough the vehicle expects not to reach the minimum speed of 2 m/s when leaving the conflict area, so it doesn't enter. - Conflict Areas: A vehicle with right of way standing upstream of a conflict area does enter it even if there is not enough room downstream. If the leading vehicle (the next vehicle downstream) is not standing, too, the vehicle wrongly expects to be able to accelerate to its desired speed and then to continue driving on with its desired speed, and thus the vehicle decides to enter the conflict area. If the leading vehicle is not so far away this won't actually happen but the vehicle might not even be able to leave the conflict area. [After the fix, the vehicle expects to stop upstream of the leading vehicle's current position if the leading vehicle's speed is smaller than 2 m/s.] - Conflict Areas on pedestrian crosswalks can not be created if there is less than 0.5 m link length downstream of the conflict area. [Now, this restriction is lifted for links with vehicle inputs with pedestrians.] - Read Additionally / "Select position with left mouse button": - After additional reading of a network (with a different center position from the original network) the zoom area is changed but the displayed position of the original network is not updated - clicking on a scroll thumb shows the real positions. After moving the additional network, the original network is displayed at its actual position which gives the impression that it has jumped away. - The first displayed position of the additional network is not in the center of the network window if the VISSIM window is not aligned with the top/left corner of the screen. - The mouse pointer position after reading the additional network is not exactly in the center of the network window. - 3D mode: VISSIM displays only the light blue background ("sky") when you switch to 3D mode on a computer that has hardware acceleration disabled for the graphics card (or possibly a very old graphics card). [This bug was introduced in version 5.00-03.] - Vehicle model distribution dialog: Error message "SelectVehic_E.dll not found!" upon click on the "..." button for the 3D model if the runtime libraries for VisualStudio 7.1 are not installed on the computer. - Vehicle input dialog: If only "View volumes" is selected for display when a new time interval is inserted, the volumes table on left side is broken. - Signal control dialog: If there is no signal control defined and you select copy in context menue, VISSIM crashes. - Signal control dialog: If the signal controller's number is changed to an existing number VISSIM displays a "Retry" message instead of the correct message "Number already used.". - Nodes Dialog: After changing flags for DTA / Evaluation in the dialog there is no warning about overlapping nodes caused by this change. - AVI file recording: The recorded file has only one frame if a VISSIM network has been loaded before but after a previous AVI file had been recorded. - Starting the simulation after a snapshot has been loaded can cause a fatal error if a vehicle uses the very first 3D model of its model distribution. - Batch mode: If VISSIM is started with command line parameter -s and a message dialog is shown because of an error in the file (e.g. a missing 3D model) the simulation starts although the modal dialog is still open and the network has not been read in completely. - Travel time evaluation: A comma is missing in the header between the location of the travel time measurement and its length. - Evaluations cannot be written to a database if there are special characters (e.g. Chinese) in column names (e.g. parameters). - The vehicle record cannot be written to a database if column names (for parameters) differ only by capital letters / no capital letters, e.g. if French is selected as language and if desired lane and desired speed are both included in the configuration. - Database output in French: Error creating the internal table "EvalInfo" (error message only in the VISSIM error file *.err). - The 3D model file Woman20Frames-Biz1.v3d doesn't use the color selected in VISSIM. - COM Interface: Changing the type of a vehicle with the attribute "TYPE" of the Vehicle interface doesn't actualize the vehicle's length (it should use the length distribution of the new type). - COM Interface: AddVehicleInZone() causes an assertion message if it is called when no simulation run is active. No parking lot can be found. - ANM Import (for dynamic assignment): VISSIM crashes on creating matrices if the ANM matrix data does not have origin volumes for one or more zones. - Adaptive ANM Import (for dynamic assignment): Wrong matrix values are set if a zone had differences and was adjusted. - VISUM Export - Nodes/Edges: VISSIM data created by ANM import and then exported to VISUM cannot be read in by VISUM because there are node numbers with more than 9 digits.. - Dynamic Assignment: Fatal error at the start of a simulation run when a corrupt path file (listing fewer edges than the specified number) is used. - Dynamic Assignment: Fatal error at the start of a simulation run if the node evaluation is active. Version 5.00-04 (2007-12-10) ---------------------------- - If the external driver model DLL interface is not included in the VISSIM license, all vehicles ignore all other vehicles and most network elements (e.g. signal heads, priority rules, conflict areas) and don't do any lane changes so they just keep on driving with their initial speed until they leave the network at the end of a link without having passed a suitable connector (the next one of their route respectively with criterion "All"). [This bug was introduced in version 5.00-03.] - German phrases including Umlaut characters (ä,ö,ü,ß) in listboxes and dynamic text fields (e.g. a legend depending on a selection in a listbox) in dialogs are not translated into languages that have a different Windows code page from German (e.g. Russian, Chinese, Japanese). [These configuration dialogs are fixed: Data collection, Link evaluation, Vehicle information window, Path evaluation.] - Analyzer Reports dialog doesn't work correctly in French. - Adaptive ANM Import: Changes in a VISSIM node can cause the incorrect error message "No edges found from node , through node , to node ." Version 5.00-03 (2007-12-06) ---------------------------- + Multiselect Connectors dialog: option to recalculate the spline points, either keeping the old number of points or using a new number (for all selected connectors). + Network Editor: Editing of segment nodes (exported from VISUM) is possible: + A polygon node can be converted to a segment node through a right click inside the polygon of the selected node (and OK in the confirmation box). (A segment node can still be converted to a polygon node through a right click inside the surrounding rectangle of the selected node.) + If a segment node is selected, a link can be selected with Ctrl + left click. ("Next" button and TAB key select another link at the same location.) If there are link segments of the selected node on this link, their start/end sections are now displayed in red/green and can be selected through left click. + A link segment can be excluded from the selected node by dragging its start or end section outside of the link. If there is only one link segment (e.g. the whole link) this can be excluded through a right click on the selected link, too. + VISSIM tries to avoid inconsistent nodes, so it's not possible to exclude a link segment if a connector belonging to the same node starts or ends inside this link segment. In this case the connector needs to be excluded first. + A link segment can be included in the selected node by dragging with the pressed right mouse button from the start to the end of the new segment on the selected link. A whole selected link/connector can be included as one segment through a single right click on the selected link if no segment section is selected and if not the whole link is already included as one segment . + A whole connector can be included as segment only if its start and end position are located in link segments of the same node, so these need to be included first. + The selected start/end section of a link segment can be moved inside that link through dragging with pressed left mouse button. The selected start section can be moved to link coordinate 0.0 (start of the link) through a right click on the selected link. The selected end section can be moved to the end of the link (maximum possible link coordinate) through a right click on the selected link. + Vehicle Inputs dialog: Default time interval is from 0 to the simulation period (instead of 0-99999). + Completion of broken routes is much faster now. + Read *.inp file: Better warning message if overlapping nodes are found, referring the user to the *.err file. + ANM Import: Conflict areas are created on connectors from/to VISSIM links that represent zone connectors in ANM / VISUM so that the vehicles entering/leaving the network from these links don't interfere with the "normal" traffic. + ANM Import: Better warning messages about broken routes / PT lines. + ANM Import - Routes: More detailed error messages for errors with zone connectors. + ANM Import - Routes: Warning message "VISSIM route not created, route contains no links (via ANM FromZone - Node - ToZone)." does include zone/node numbers. + Dynamic Assignment: Edge selection dialog: If a node has been selected in the network editor before the dialog is opened it is now automatically selected in the dialog, too. - Network editor: VISSIM crashes after closing the signal head selection dialog if the dialog is opened with right click in an empty region while a link is already selected. - Network editor: Exception message on creating a parking lot of the type real parking spaces if the location "On new right lane" is selected and there is a route decision on the link. - Network editor: Conflict areas might be not updated after moving a link or end points of a connector. - Network editor: After changing a connector's from/to link/position only static routes and PT lines using the connector are checked/adapted, but partial routes, parking lot routes and route closures are ignored. - Network editor: If a broken route/PT line can not be completed after changes in the network the partially fixed link sequence is inserted into the route/line and the original link sequence is deleted. The displayed error message refers to the partially fixed link sequence [Now, the route/line keeps its original link sequence (with all errors), and the error message refers to the original link sequence.] - Network editor: If one or more broken routes are found and repaired, and then another route can not be repaired no error message is displayed. - Network editor: Copying nodes does not work anymore. (This bug was introduced in version 5.00-02.) - Signal Times Table window: VISSIM hangs after 500 simulation seconds with an open signal times table window if the external controller DLL's cycle second is never a multiple of 5 or 10. - Vehicle Input dialog: takes a very long time to close if there are many cells. - Multiselect Connectors dialog: Click on OK causes VISSIM to hang. - Node dialog: Edit field for number is too small (ANM imported numbers are cut). - VISSIM crashes when the simulation is started if the *.inp file contains a link with an invalid behavior type (only possible through manual editing). - ANM Import - Routes: can crash if broken routes (due to changes in the VISSIM network) need to be completed. - ANM Import - Routes: Error message "VISSIM route not created, corresponding VISSIM node to ANM source connector (Zone x -> Node y) not found." if a node in the ANM file is connected to exactly one origin zone and exactly one different destination zone. - ANM Import: Creates wrong matrix filenames and wrong times in matrix files (seconds instead of minutes). - ANM Import: Creates a vehicle input on a crosswalk only if it is signalized. - ANM Import: If import routing is checked but a routes file entry is missing, a message appears that this entry is missing, but user doesn't know which entry is missing as the focus isn't set to the respective edit field. - ANM Import: VISSIM connectors that connect VISSIM links that represent zone connectors with the network often have sharp angles. (Vehicles on these connectors are invisible but movements of vehicles entering these VISSIM connectors (or leaving them) which often perform circular movements in order to adjust to the sharp angles are visible because they are performed on VISSIM links representing ANM links.) - ANM Import: Error message during the initial (!) import: "Current network contains data for static routing from previous import. Really import new routing for dynamic assignment? Note: Vehicle inputs, static routing decisions and routes created on previous import will be deleted in this case." - Adaptive ANM Import: crashes if the *.panm file or the *.panmRoutes file does not exist. - Adaptive ANM import: Sometimes VISSIM connectors that are part of adjacent nodes that were regenerated are removed incorrectly. This happens if the edge consists of a VISSIM link and a VISSIM connector in that order. - Adaptive ANM Import: creates corrupt link sequences for changed PUT lines starting from the same link. - Adaptive ANM Routes Import: Matching ANM connectors to VISSIM nodes can fail, causing a VISSIM route not to be created. - SSAM trajectory file export: - All world coordinates written to the file are internal coordinates after auto-translation, i.e. with the network centered to (0.0, 0.0), so they don't match the coordinates displayed in the status line of the VISSIM window. - The max/min world coordinates written to the file use the current zoom area instead of the full network size. - Dynamic Assignment: Edge Selection dialog crashes: 1. start Edge Selection dialog (internal node structure is built), close dialog 2. click a node to start node dialog, change flag Dyn.Assignment 3. start Edge Selection dialog => Exception error message - Dynamic Assignment: VISSIM crashes during a simulation run with a trip chain file if a vehicle with a subsequent trip arrives in a parking lot after a vehicle without subsequent trip has arrived there. 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.