New features and bugfixes in VISSIM (2011-05-02) =================================== (+ = new features, - = bugs that have been fixed. Details about the fixes are in brackets.) Version 5.20-14 [28521] (2011-05-02) ------------------------------------ - 3D Visualization: The performance when drawing static objects has dropped considerably, especially on ATI cards, from VISSIM 5.20-06 to 5.20-08. (#6085) - Conflict areas: A simulation run can crash with an exception message if a vehicle with car following model "no interaction" approaches a conflict area (where it must yield) while another vehicle is inside another downstream merging or branching conflict area on the conflicting link. (#6023) - Vehicle Record / Vehicle Information Window: Following distance and distance to Headway are given as net values (not including the leading vehicle's length) while a vehicle uses the car following model "no interaction". (#6023) - The duration of the current state of a signal group for an external signal controller is always initialized with 1.0 even if the controller runs with a frequency higher than 1. [Now, the run time is correctly initialized with the length of the controller time step.] (#6005) - [Fixed in VAP 2.16-05:] VAP functions that return time durations (e.g. t_red()) can sometimes return decimal values even at integer simulation seconds (e.g. 2.0000004 instead of 2.0) if the simulation resolution is higher than 1 time step per second. This can cause comparisons for equality to fail which have worked in previous VAP versions. (This problem has been introduced in VAP 2.16-04. In earlier versions, these functions had ONLY integer return values.) (#SC-71) - [Fixed in VAP 2.16-06:] All PT telegrams are lost (tele_count = 0) if two or more VAP SCs use the same controller DLL and at least one of them (and not only the SC with the highest number) has a controller frequency > 1. (#SC-78) Version 5.20-13 [27118] (2011-01-23) ------------------------------------ + Vehicle Inputs: The warning message about remaining vehicles (in the error file) includes the time interval of the input. + Pedestrian Module: The consistency check writes warnings and errors into the log window. Upon click on such a message in the log window VISSIM automatically zooms & selects the element. (Note: zoom & select work only if the simulation is not running.) + Pedestrian Module: Warnings about too high density on pedestrian areas (in the error file) include the simulation second and the area number. + C2X Interface: The trailing and leading vehicle of a C2X vehicle can now be retrieved through the C2X interface via Vehicle.TrailingVehicleID and Vehicle.LeadingVehicleID. - Closing VISSIM via menu File - Exit causes the "Save changes?" dialog to appear twice if you choose "No" the first time. - RBC dialog (VISSIM 64-bit versions): Changing the file name does not update the file name in the Signal Control dialog. - Signal Times Table Window: The lower line of a blinking signal is not drawn correctly if a red state follows a blinking state. - Test Mode with more than one time step per simulation second: Siemens VA signal control doesn't get all detector actuations, e.g. continuous detection (pink) set in a time step before the last one of a controller time step. - PT vehicles dwelling in a stop and parked vehicles are drawn with wrong color in 2D (should be drawn white). - Connectors: Recalculate spline resets z-coordinate to 0 both in single and multiselect mode. For any connector with a height (z-coordinate) different from 0, if "Recalculate Spline" is activated in the Connector dialog (or corresponding dialog in Multi-Select mode) and "Recalculate Spline Point Height" is deactivated afterwards, all intermediate points of the connector(s) are reset to height 0. - Vehicle animation is not saved in the *.ani file if the vehicle visualization is off and the pedestrian visualization is on. - Attribute 'PT Lateness' shows negative values in vehicle record evaluation and in vehicle info window. - Static and partial routes: If the total of all relative volumes is smaller than 1 the decision is ignored by some vehicles. - Parking space selection: A vehicle can select a space it has already partially passed, so it cannot change lanes in time anymore. This causes that parking space to stay empty for the rest of the simulation. - Conflict Areas: Additional stop line distance can cause a lock-up if a vehicle which won't pass the conflict area (because its route continues across an upstream connector) is already inside the additional stop line distance. - Conflict Areas: Message "Error creating conflict area" in the log window if the start of one link is inside the conflict area. - Deleting or changing the number of a dwell time distribution which is used by a parking decision produces invalid data (input file cannot be loaded again). - A vehicle cannot leave a parking space because it doesn't start a lane change to the next lane (which is better suited for the vehicle's route) if there are parking vehicles on that lane, too, with a gap downstream which has at least the length of the vehicle. (The vehicle plans to pass the parking vehicles first on its current lane and doesn't consider if its current lane is blocked, too. The turn signal displays the direction of the desired lane for the route in this case, not an actual lane change.) [Now, the vehicle does start the lane change if the current lane is blocked by a parking vehicle upstream of the gap.] - PT: Waiting pedestrians from previous time intervals are added to the boarding passengers for the subsequent time interval, but not subtracted from waiting passenger amount if they are boarding. [Boarding order: waiting passengers from earlier time intervals board first] - Link evaluation & VISUM Export: Exported VISUM attribute names for vehicle class dependent attributes are corrupt/undecipherable (like "????"). VISUM shows undecipherable/corrupt attribute names. - ANM Import: If there are multiple lane turns to a link with an unused lane (without incoming lane turn) and if a triangle island is defined for a link connected to that link, an internal error can occur. - ANM Import: The extensions of the filenames in the import dialog are checked case sensitively, so the warning message "Extension changed!" appears upon OK if the filenames differ only by case from the default extensions. (*.anmRoutes with capital R is default, *.anmroutes causes the warning.) - ANM Import: Import aborts with the error message "VISSIM has encountered a severe problem and should be restarted." upon importing channelized turns with left hand traffic. - ANM Import: Signalization: Minimum red time is imported incorrectly (has the value of the minimum green time). - COM Interface: If vehicle visualization (Graphics.AttValue('VISUALIZATION')) is switched off before the first simulation step, then switching the visualization on during the simulation run has no effect. - Dynamic Assignment: Route guidance can crash if a vehicle gets a subsequent individual path (after it has already got another indivdual path before). - Dynamic Assignment: Warning message "The dynamic routing decision is part of several different links" shows the link number instead of the decision number. - Dynamic Assignment: The simulation aborts during alternative path search if the network contains route closures and if a destination parking lot is located on the same link as a route closure destination section. - Export / VISUM: Created VISUM traffic systems are invalid, the VISUM restriction of only one PrT TSys per PrT Mode is not considered. - Pedestrian Module: Undo/Redo of create and change levels cause crash. - Pedestrian Module: After duplicating an area with CTRL-Move the Undo menu shows 'Unknown Command'. - Pedestrian Module: Undo/Redo of geometry changes of ramps cause a crash. - Pedestrian Module: If different parameter files are used by one pedestrian DLL the global behavior parameters (which are constant for all pedestrians on all areas) are taken from the parameter file assigned to the area with the largest number (of all areas with an area behavior type) and if no area has a parameter file assigned, from the parameter file of the pedestrian type with the largest number. [Now, the global parameters are taken from the parameter file of the pedestrian type with the lowest number, ignoring area behavior types.] - Pedestrian Module: VISSIM crashes at the end of a simulation run if there are levels without pedestrian areas (only in the 64 bit edition). - Pedestrian Module: When a new level is created the height is not set according to the heights of the previous levels. - Pedestrian Module: Crash at simulation start if pedestrian areas have big world coordinates. - Pedestrian Module: Deleting all routes of a partial routing decision doesn't reset the destination area shown in the routing dialog. - Pedestrian Module: Travel time evaluation calculates wrong values of the standard deviation of speed. [Now, the standard deviation of speed is not available anymore but the average absolute difference between current speed and desired speed, "deviation of speed".] - Pedestrian Module: Area evaluation raw data does not have enough decimals for density [now 2] and deviation of speed [now 2]. Travel time evaluation raw data does not have enough decimals for deviation of speed [now 2]. Version 5.20-12 [25026] (2010-08-24) ------------------------------------ + 3D Signal Dialog / Mast Arm Style selection box: Switching between signal arm and light disabled, empty line removed. - Error message "Figure expected" upon click on the "..." (Geometry) button in the 2D/3D Model Distribution dialog. (This message and others, e.g. "Figure too small/large!" can appear upon opening other dialogs as well.) (This bug was introduced in version 5.20-11.) - The lane closure dialog ignores changes for the last selected lane if no other lane is selected before clicking OK. (This bug was introduced in version 5.20-11.) - Wrong warning messages about adaption of period and interval length for queue lengths and delay measurements to the respective values for the node evaluation. - Default controller files for SC Type Econolite ASC/3 are not set automatically in the signal control dialog. - Vehicle routes editor: VISSIM crashes upon selecting an abstract parking lot or a zone connector for a parking lot route decision. - RBC Controller: Reservice Inhibit Same and Reservice Inhibit All were not stored and utilized properly. - RBC Controller: Queue detector information was not stored and utilized properly. - Pedestrian Module: VISSIM can crash if "remaining distance" is selected for the activated pedestrian record. - Pedestrian Module: Pedestrians waiting for PT vehicles are not displayed in the state "standing" in 3D visualization. - Pedestrian Module: Memory leak in the pedestrian behavior model DLL. - Pedestrian Module: Pedestrian Area Dialog: If multiple pedestrian areas are selected, changing a value that is different between the selected areas and then selecting one area results in the list being filled with only 1 area. - Pedestrian Module: Travel Time Measurements state the value for "TravDist: Distance traveled from start to destination area [ft]" in meters rather than feet in the raw data file (*.rsrp). Version 5.20-11 [24799] (2010-07-29) ------------------------------------ + AVI file recording: The selection dialogs for the name of the *.avi file and for the video codec are displayed before the simulation initialization (which can take quite some time, especially with many pedestrian areas). + VISSIG: Daily signal program lists. Each list can contain different signal programs for different times during the day. During the simulation run, a fixed time (VISSIG) controller switches from one signal program to the next one as soon as the switch point of the active program is reached for the first time after the specified start time for the next program which continues the cycle from its own switch point. (This happens at the first start time after midnight, too.) The number of a signal program list must be different from all defined signal program numbers because it is selected in VISSIM in the SC dialog as "signal program number". - Conflict areas don't see vehicles more than 100 m away from the end of the conflict area. This can cause long conflict areas not to work properly. [Now, conflict areas look upstream up to 100 m from the begin (!) of the conflict area.] - The driving behavior parameter "Desired position at free flow" (lateral) doesn't work correctly if "Overtake on same lane" is not checked for any vehicle class (nor for "All"). It is considered only on the link where the vehicle enters the network and after lane changes but not when the vehicle enters a new link with a different value of this parameter. - Node evaluation: If the user-defined delay segment length reaches back beyond a parking lot then no traffic from this parking lot is measured in the node volumes. - The menu item "AVI Recording" is disabled after it has been switched off until the mode is changed to 2D and back to 3D. (This bug was introduced in version 5.20-10.) - ANM Import: does not create conflict areas for nodes of type TwoWayYield (e.g. exported from Sitraffic Office). - ANM Import: Because of a bug in the computation of the allowed lanes for public transport lines, trams sometimes cannot use a PT stop on a multi-lane link. These trams wait on their lane close to the stop until they disappear. - Adaptive ANM Import: aborts with the error message "Internal error CreateVehicleTypes: VISSIM link type already exists?" if a new link behavior type created manually in the VISSIM network has been added in the new *.anm file, too. - COM Interface: The detector attribute "VEHICLEID" doesn't work reliably with multiple detectors with the same number. If there is a vehicle on only one of these detectors, zero (for "no vehicle") can be reported. - Dynamic Assignment / Parking lot dialog / Desired Speed: selecting Default and clicking the Delete button causes a Fatal Error (only for zone connectors and abstract parking lots). [It is not possible to delete the Default, even if desired speeds for specific vehicle classes are assigned. Now, the Delete button is disabled.] - Pedestrian Module: Conflict areas on pedestrian links are not updated correctly after moving the intermediate points of the link. - Pedestrian Module: Partial routes ending on ramps can cause pedestrians to disappear from the simulation. - Pedestrian Module: Multi-threading (use of multiple processor cores) has no effect anymore. (This bug was introduced in version 5.20-06.) - [Fixed in VAP 2.16-04:] Most of the VAP functions referencing signal group timings return always a (rounded) integer value instead of the decimal value which would be expected if the controller frequency is not 1. Version 5.20-10 [24185] (2010-06-16) ------------------------------------ + Data collection point selection dialog: The name of the data collection point is listed. + Detector selection dialog: The name of the detector is listed. + Signal head dialog: The names of the signal head and the signal group are listed. + COM Interface: The link attribute LANECHANGE (used only for connectors) has been renamed to LANECHANGEDISTANCE and is a floating point value. + NEMA: Networks with NEMA controllers can be read in and NEMA controllers can be converted to RBC if the VISSIM license includes RBC even if it doesn't include NEMA or if there is no NEMA installation on the PC. + SCOOT: Checkbox "Write log information" in SC dialog on tab page "SCOOT". + API / External DriverModel.DLL Interface: Additions to the source code files DriverModel.h and DriverModel.cpp which prevent error messages concerning the data type codes DRIVER_DATA_VEH_ACTIVE_LANE_CHANGE, DRIVER_DATA_VEH_REL_TARGET_LANE, DRIVER_DATA_STATUS and DRIVER_DATA_STATUS_DETAILS. - VISSIM can hang when using multiple cores if a vehicle information window is open (especially if it is already open at the start of the simulation run). - Database output fails if a node name contains the character ' (single quote). - Exception message if you delete a desired speed distribution with more than 6 digits in its number. - Node evaluation: If a vehicle passes the start of an automatically created travel time section in the same time step as its destination (e.g. if there is a possible circle along an edge from a the node back to itself), the vehicle is counted as having passed each turning movement that is part of a possible connection from the start section to the end section (without any other nodes in between). This happens even if the start section is downstream of the destination section. If there are multiple parallel edges from a node back to itself and/or multiple turning movements in the node (because of parallel connectors or connectors from a link to itself) the vehicle is counted multiple times. If there are other movements to the same node exit which consist of more than 10 link numbers vehicles on these movements are counted for the critical movement, too! This can cause the volume for a movement to be listed as far too high. [After the bug fix, a vehicle is not counted if it passes the start and end section of a travel time measurement in the same time step. It is undefined if it remembers the start section for a future pass if the sections are not at the exact same link coordinate.] - Pavement markers: link positions in 2D and 3D don't always match. - Vehicle model geometry: Two vehicle doors at the same position are not accepted (if you enter a second one at the same position in the Geometry dialog it is gone after OK and opening the dialog again). [Now it is possible if the doors have different parameters, e.g. boarding / alighting.] - 2D view: The compass is displayed only after a screen refresh: After hitting Ctrl-M nothing happens initially - only after zooming or otherwise refreshing the screen it is displayed. Similar with deactivating the compass display. - 3D Models: Textures of newly loaded models are not displayed (neither in the 3D model selection dialog nor in the network) before saving and reading the *.inp file again. (This bug was introduced in version 5.20-09.) - 3D Signals: Several problems with editing: - The complete mast with arm and signal is never visible in the 3D dialog if the mast is on the left side and the arm extends to the right in the 2D view (which is the default orientation upon creation with right-side traffic (default)). [Rotating the arm by at least 90 degrees makes the mast visible in the 3D dialog. Rotating it back makes it invisible again.] - 2D Network Editor: Rotating the arm of a 3D signal created for left-side traffic causes strange effects (arm separated from the mast). - Display types / Rail properties (3D): If you make a change in this dialog and click OK, then reopening the dialog will show the change in tact. However, as soon as you click OK in the Display types dialog, those changes will be dropped. - Background images in *.dxf and *.dwg format: Problems with zooming if the file contains coordinate transformations. - Fixed time control: Conversion of fixed time to VISSIG creates a bad *.sig file (causing a crash) if permanent red or permanent green was coded using green end and red end in the *.inp file (very old format). - ANM Import: Crashes if there is a detector on a ANM link which is modeled as a single VISSIM link (no turning bays or triangular island) and too short for the detector position upstream of the stop line (as given in the *.anm file). - ANM Import: Node routes are not always created correctly if there are parallel turning movements for different vehicle classes inside a node. - COM Interface: AddVehicleInParkingLot() without setting the attribute "PATH" eats about 2 KB memory per time step as long as the vehicle has no path. - COM Interface: COM server registration of the 64 bit edition of VISSIM fails, so COM clients cannot connect to a 64 bit VISSIM. - COM Interface: The attribute VEHICLE of IDetector can have a nonzero value even if no vehicle has reached the detector in the current time step. - COM Interface: RemoveVehicle() causes a misleading warning message in the *.err file: "Simulation time %d: Vehicle %d (on path %d (inserted via COM) from parking lot 0 to parking lot %d) has left the network at the end of link %d without having reached its destination parking lot." - COM Interface: Setting the Vehicle attributes EMERGENCYSTOP and LANECHANGE always sets the value to 0. - COM Interface / Dynamic Assignment: Vehicle.AttValue ("PARKLOT") returns the origin parking lot for a vehicle that has just arrived in its destination parking lot. - Dynamic Assignment: Network performance evaluation and Analyzer reports: Vehicles from a trip chain file are not included in the number of arrived vehicles. - Pedestrian Module: Queue evaluation for areas with no dwell time distribution counts only pedestrians who have come to a stop before reaching that area or who are adjacent to such a pedestrian. - Pedestrian Module: A PT waiting area with a different level from the level of the platform area causes pedestrians not being able to board. - Pedestrian Module: A PT waiting area which is not big enough to hold all waiting passengers can cause unrealistic behavior when the PT vehicle arrives: Each pedestrian tries to reach his (random) waiting point on the area before moving on to the vehicle. [Now, pedestrians who are not more than 5 m away from their destination waiting area and who have come (almost) to a stop start waiting there and don't try to reach their original waiting point.] - Pedestrian Module: Dwell time is ignored on areas with a partial route decision. - Pedestrian Module: Boarding of passengers doesn't work correctly if two PT vehicles (at different stops) have overlapping dwell times. - Pedestrian Module: Dynamic Partial Routes: Method travel time: Wrong calculation for Logit of Reciprocal. - Pedestrian Module / Measurement Areas: Obstacles which are completely inside a measurement area are handled wrongly in the density calculation, causing artificially low values of density. - Pedestrian Module: Area-based LOS display doesn't work right: A big area is drawn over small areas. (This bug was introduced in version 5.20-09.) - Pedestrian Module: Static partial routes crash when the last routing time interval ends before the end of the simulation run. - Pedestrian Module: If an overlap area at the end of a ramp is divided into separate parts by obstacles the pedestrians sometimes use only the smallest part (instead of the biggest one). - Pedestrian Module / Conflict Areas: Yielding vehicles ignore pedestrians with right of way as long as these are more than 3 m upstream, so the vehicles cannot always brake early enough to keep the user-defined rear gap. [Conflict areas now use a dynamic look-back distance for pedestrians with right of way, assuming 0.5 s passing time for the yielding vehicle and a pedestrian speed of 1.5 m/s and taking the rear gap into account. Attention: large rear gaps cause big look-back distances, and these are not limited to the existing pedestrian areas!] - Default location distributions are created and written to the *.inp file even if the Pedestrian Module is not included in the VISSIM license. (This bug was introduced in version 5.20-05.) Version 5.20-09 [23492] (2010-04-16) ------------------------------------ + Data collection, raw data evaluation: New line with the simulation start time (if defined), before the list of the data collection points, ISO format. + Pedestrian Module: New attribute in pedestrian record and pedestrian info window: Remaining distance to next internal destination. The given value refers to the next user defined route intermediate point or the next internal intermediate point (e.g. for ramps and boarding/deboarding), whichever is closer.) - Read additionally doesn't work properly for 3D model distributions with identical filenames but different geometry data. - 3D Model Selection Dialog: doesn't show directory and file names with special characters from other code pages (e.g. Cyrillic). - ANM Import: aborts with the error message "Can not find anm.xsd in the VISSIM application folder." (but the file is there). (This bug was introduced in version 5.20-07.) - Dynamic Assignment: Very short edges can cause problems: A large travel time for an edge (determined by queue detection in an early iteration) is kept forever and not smoothed exponentially if no subsequent travel time for this edge is bigger than 0.1 seconds. - Pedestrian Module: Pedestrian record: The world coordinates are wrong. Version 5.20-08 [23316] (2010-04-01) ------------------------------------ - 3D Visualization: Articulated vehicles (e.g. trucks with trailers, trams) are broken. (This bug was introduced in version 5.20-07.) - Stereoscopic video recording (Presentation / 3D Video / Stereo (2 AVIs)) doesn't work correctly (the two *.avi files are (almost) identical). Version 5.20-07 [23304] (2010-03-30) ------------------------------------ + New driving behavior parameter "Overtake reduced speed areas" (tab page "Lane Change"). This option is off by default but it can be switched on to allow modeling of lane-dependent speed restrictions which are considered by vehicles for lane changing. (If the option is off, vehicles don't ever change lanes directly upstream of a reduced speed area and they ignore reduced speed areas on the target lane.) + Multiselect links dialog: New checkbox for recalculation of the z-coordinates of connectors (as in the single connector dialog). + Option "[x] Don't show this message anymore" for the warning message "Error opening *.szp". + RBC Controller for the 64 bit edition. + COM Interface: Access to all signal controller data available for the SC/Detector record: New object ISignalController.SCDetRecord with the (only) method ISignalController.SCDetRecord.GetResult ("CategoryName", var_no) with all type(category) names from the LDP configuration (which depends on the *.wtt file(s)) accepted as the first (string) parameter and the object number specified by the second parameter (int). The return type is a VARIANT (string or number depending on the settings in the *.wtt file). If the value has not been passed from the signal controller to VISSIM during its last signalization time step the return value is NULL (use VBS function IsNull() to check this). (So, the current LDP configuration has no effect on these calls but only the data actually sent from the controller (DLL) and listed in the *.wtt file.) + Pedestrian Module: Partial routes: All pedestrians who enter the area with the partial routing decision and who have the destination area of the partial routing decision as intermediate area or destination area in their current route are assigned a new route from the decision area to the partial route's destination area, continuing their original route from there. Multiple partial routes can overlap - the complete current route (extending all the way to the destination of the original route) is checked for the destination area of the partial routing decision. + Static partial routes: Each partial route is assigned a relative volume per (user-defined) time interval. + Dynamic partial routes: Several route choice methods will be available. The first one is "Travel Time": VISSIM determines the average travel time from the decision area to the route destination for all pedestrians using partial routes of this partial routing decision. The number of pedestrian travel times used for calculation of the average can be set by the user. As long as not all routes have been used, each route has the same probability to be used. After this, the probability of a pedestrian choosing a certain route is determined by one of 4 ways: a) Best Route: The user-defined percentage of pedestrians uses the best route. All other pedestrians are distributed randomly among all other routes. b) Kirchhoff: The probability of a route is calculated as the inverse of the travel time to the power of the user-defined exponent a divided by the sum of these powers for all routes: (1/tt)^a / Sum[(1/tt)^a]. c) Logit: The probability of a route is calculated as e to the power of (the negative travel time divided by the user-defined constant tau) divided by the sum of these powers for all routes: e^(-tt/tau) / Sum[e^(-tt/tau)]. d) Logit of the reciprocal: The probability of a route is calculated as e to the power of (the user-defined constant tau divided by the travel time) divided by the sum of these powers for all routes: e^(tau/tt) / Sum[e^(tau/tt)]. + Pedestrian Module: Pedestrian information window with configuration dialog (accessible via Evaluation / Windows / Pedestrian Information). + Pedestrian Module: 3D view from a pedestrian's perspective: + activated by double-click on a pedestrian in 2D, + stays active while the pedestrian's information window is open. + Selection of a different pedestrian's information window switches the 3D perspective to that pedestrian. + Pedestrian Module: Pedestrian Record: New attributes for partial routes. + Pedestrian Module: Parameter file parameters_for_quicker_draft_simulation.xml which can be assigned to a pedestrian type or a walking behavior parameter set in order to have a faster (but less accurate) simulation. - A leading vehicle is ignored if its front end is downstream of the emergency stop position of the following vehicle. This allows the following vehicle to drive "into" that leading vehicle. - Lane change behavior: The safety distance of the following vehicle on the target lane can be ignored in some cases if the lane change is not required by a route. - Driving behavior parameters: Desired lane position of free flow "left" on an input link causes an exception message. - Left-hand traffic: The default driving behavior parameter set for bicycles uses the desired lane position "right" [now "left"]. - Network editor: Splitting a link can cause a routing decision from a different link (but at a similar link coordinate) to be moved from its original link to the link that was split (only if automatic creation of the connector is activated). - Vehicle and pedestrian input and routing dialogs: Time interval bounds with decimal digits can cause problems. - Read additionally: 2D/3D model distributions are always duplicated even if they are identical. Because of this, vehicle types, vehicle classes and vehicle compositions using these are also duplicated. - Vehicle Record: The average waiting time of boarding passengers at a PT stop is always given as zero if there is another time interval for boarding passengers at that line stop after the current one. - ANI.TXT (for 3DS MAX visualization): Pedestrian height and (only for old "pedestrian" vehicles) frame information are not exported correctly. - Visualization of individual vehicles in big networks is very slow. (This bug was introduced in version 5.20-06.) - 2D Visualization: VISSIM can crash during a simulation run if a) the length and width of a vehicle/pedestrian model are equal and both are exactly 0.5 meters and b) the vehicle/pedestrian size on the screen is less than 1 pixel (depends on the zoom level). - 3D visualization of "old" pedestrians (vehicles with category "Pedestrian"): Wrong z-coordinate (too high) for these pedestrians on connectors between links with different z heights. - Analyzer Report Generation: A VISUM network file (with LOS values) is only exported if the input file name in the Analyzer database corresponds to the current VISSIM input filename, including the complete path. [The path is ignored now.] - COM Interface: The method Vehicles.GetArrived() does not always return all arrived vehicles if the simulation resolution is higher than 1. - COM Interface: The method AddPathAsNodeSequence() does not exclude closed edges. - COM Interface: AddVehicleInParkingLot() can cause duplicate vehicle numbers if it is used before the start of the simulation run and if there are more vehicles inserted after the start of the run through this method or through vehicle inputs or matrices or a trip chain file. - Export - VISUM - Nodes/Edges - For assignment: Closed edges are included for the creation of VISUM zone connectors. - External DriverModel.DLL Interface: A simulation run using an external driver model DLL is canceled with error messages concerning the data type codes DRIVER_DATA_STATUS, DRIVER_DATA_STATUS_DETAILS or DRIVER_DATA_PARAMETERFILE. [These had been added to the interface since the release of the official documentation. Now, they are optional again and will be added to the documentation, soon.] - External DriverModel.DLL Interface: Setting the desired speed of a vehicle to zero through this interface causes invalid values in several evaluations. - Pedestrian Module: Pedestrians at PT stops: Doors which are outside of the PT stop length are considered for de-/boarding but don't work correctly. [Now, only doors inside the PT stop length are used. If any are outside, a warning message is issued.] - Pedestrian Module: If more than one route is selected, only one of them is displayed in the network (as yellow ribbon). - Pedestrian Module: Platform edges generated automatically don't work for PT vehicles with vehicle width >= lane/link width. No doors are created, so no passengers can alight or board. - Pedestrian Module: Pedestrians on ramps are not recorded correctly in an *.ani file. This can cause wrong display in 2D and wrong LOS display during animation replay. - Pedestrian Module: The z-coordinate (height) of boarding pedestrians is not correct if the PT vehicle is on a link with height > 0. - Pedestrian Module: Ramps with obstacles close to their start/end can cause strange pedestrian behavior. - Pedestrian Module: Areas that are completely inside a ramp opening cause a crash at the start of a simulation run. - Pedestrian Module: Grid-based LOS: Grid cells that only lie partially on walking ground have wrong LOS values (assuming the whole cell size as available). - Pedestrian Module: It's possible to delete the only existing pedestrian composition by deleting the only pedestrian type it contains. - Pedestrian Module: Pedestrians slow down unnecessarily when they reach the end of a route and there is another route decision which applies to them. - Pedestrian Module: Pedestrians who want to board a train/bus are standing at one single point near the door instead of queuing behind each other. (This bug was introduced in version 5.20-04.) - VISSIG: If the state of signal group in a stage is "don't care" VISSIG can crash if an interstage is extracted from a signal program. - Some bugs in VisVAP 2.16 [New version: VisVAP 2.16-05, see VisVAP\DOC\Changes.txt] Version 5.20-06 [22271] (2010-01-21) ------------------------------------ + Lane change behavior: Lane change distance in the connector dialog can be defined optionally as value "per lane". if this option is selected the entered value is multiplied by the number of lanes a vehicle needs to change to reach the detector. e.g. for a detector starting only from lane 1 with lane change distance 200 m per lane, a vehicle on lane 3 starts to look for a gap to change lanes from 400 m upstream of the start of the connector. + Option to convert one or more NEMA signal controllers to RBC: + A single controller can be converted by changing its type. + All controllers can be converted through Signal Control / Convert NEMA to RBC. + The signal state "flashing red" (can be set by external controllers) is treated as red ("stop!") by vehicles and pedestrians. + Driving Behavior Parameters / Signal Control: New parameter "Behavior at red/amber signal" with the options "Go (same as green)" (default) and "Stop (same as red)". + Display the direction of the next connector of the route (as selected in the connector dialog) by "blinking" (direction indicator) of the vehicle. + Pedestrian Module: Detectors on pedstrian links detect changes between occupied and free between subsequent time steps and pass these to the controllers as "front ends / rear ends". [Formerly, only the presence at the end of the controller time step was passed to the controller.] This enables to play the assigned sound file when a pedestrian arrives on an empty detector, too. + Pedestrian Module: The new parameter side_preference in the parameter file allows to choose if pedestrians with opposing walking directions evade more to the right, to the left or without side preference. By default "no side preferences" is set, which is as it was done before. - Creating a desired speed distribution uses the invalid number 0 (which cannot be edited). VISSIM crashes if this distribution is deleted. If the network is saved after creating such an invalid distribution the input file cannot be loaded (aborts with the error message "Number must be positive"). (This bug was introduced in version 5.20-05.) - Network Editor / Routes mode: Exception message upon pressing Delete if only a link is selected but no decision or route (after another link has been selected before). - Display Options / Vehicles / Individual vehicles / Configuration: A click on the button Default Classes causes an Exception message if a) the selected parameter is Parking Lot Origin or Parking Lot Destination and b) the current network contains parking lots and c) the difference between the smallest and biggest parking lot number is less than 100. In VISSIM 5.20-05, VISSIM crashes too when View / Load Settings is called if the conditions b) and c) are met. - Animation Replay: Crashes with the message "Unknown error while creating pedestrian in AnimatePedestrian" if there are signal heads in the animation area - even if the Pedestrian Module is not part of the license. (This bug was introduced in version 5.20-05.) - Vehicle Routes Dialog: Exception after adding a new time interval value for a partial route or parking route. - Vehicle Routes Dialog: Changing dynamic routing decision attributes (condition, strategy etc.) does not work correctly if the routing decision is located on a link with more than 1 lane. - Dialog "Evaluations (Files)" is too large to fit on displays with low resolution. - Menu "Presentation": After switching from 3D to 2D and back to 3D mode the menu item AVI Recording is not selected even if it was selected before. The AVI Recording is still active, however, so a single click on the menu item switches it off (!) and only the second click activates the selection again. - Flashing signal states are displayed as constantly "off" (black) in the network if the simulation resolution is only 1 time step per second. [Fix: With simulation resolution 1 the flashing frequency is now 0.5 Hz (alternating on/off per time step) instead of 1 Hz (alternating per half a second).] - Fixed Time / VISSIG signal group names containing non-Latin characters (e.g. Chinese) are damaged when saved in the *.inp file. - VS-PLUS signal controller DLLs always show cycle time 0.0 after initialization (which is displayed in the signal times table, for example). (This bug was introduced in version 5.20-05.) - Test Mode/COM Interface: Externally set detections can get lost if the controller frequency is smaller than the simulation resolution and if the detection is set not in the last simulation time step of a signal control time step. - Direct static 3D object import (*.skp, *.dwf, *.3ds: Ctrl-Rightclick): - Transparent materials and textures are not shown correctly. - Scaling and units are not read. The DWF and 3DS models are too large. - Colors and textures in component objects are not shown correctly (only SKP format). - The cobject's color is changed after scaling it down. - Translating an object along the Z axis (Shift+alt) moves the object in wrong direction. - The objects' color is missing in some DWF files. (Notes: It's recommended to use only the Sketchup 7 format. There are some issues regarding transparent objects in the older formats. There is no support for non triangular objects, like curves and edges. Mirrored (flipped) components can be shown with wrong texture. To solve this problem the component needs to be exploded and created again or the textures must be assigned after flipping the component. The graphic card driver should be up to date.) - ANI.TXT Recording: If any evaluation is defined VISSIM crashes while recording ani.txt. It's enough to have some evaluations defined in the input file. It crashes if no evaluation is activated too. - Adaptive ANM Import: Some nodes are not connected with their neighbor nodes after the import because of wrongly computed split positions if there are multiple edges betwenn these nodes. - Adaptive ANM Import: aborts sometimes with a Runtime Error if the network contains travel time measurements on VISSIM links that are re-created due to changes in the *.anm file. - COM Interface: Message box "All selected convergence conditions are true. Cancel batch run?" during a multi-run series started through COM. [Now, the multi-run series is stopped at that point without a message box.] - External DriverModel.DLL Interface: A simulation run using an external driver model DLL is canceled with error messages concerning the data type codes DRIVER_DATA_VEH_REAR_X_COORDINATE, DRIVER_DATA_VEH_REAR_Y_COORDINATE or DRIVER_DATA_VEH_DESTINATION_LINK. [These had been added to the interface since the release of the official documentation. Now, they are optional again and will be added to the documentation, soon.] - Pedestrian Module: Pedestrians at PT stops: Wrong orientation for boarding pedestrians in the boarding queue (only on the left side of the vehicle). - Pedestrian Module: If "alighting possible" is switched off for a door at a PT line stop alighting pedestrians can be assigned to this door anyway, causing the vehicle to dwell forever because it is waiting for these passengers to alight. - Pedestrian Module: Travel time measurements don't detect pedestrians who are already there at the start of the evaluation period or who are created there (on input areas). - Pedestrian Module: The ceiling opening length of ramps does not correctly consider the thickness of areas on the upper level if it is defined by the headroom. - Pedestrian Module: Network editor in area mode: +click on a selected "inside" area (selected with -click and no mouse movement in between) does not only deselect that area (correct) but selects the surrounding area. - Pedestrian Module: Area based walking parameters from a parameter file are ignored on ramps. - Pedestrian Module / Animation Replay: Backwards replay can stop suddenly and display a negative simulation time. - Pedestrian Module / Demo Version: Files with pedestrian measurement areas cannot be opened. - Some bugs in V3DM 1.42. [New version: V3DM 1.42-03, see V3DM\Doc\changes.txt] Version 5.20-05 [21802] (2009-12-14) ------------------------------------ + File Menu: New item "Open Working Directory" that opens the Windows Explorer in the current working directory (where the *.inp file resides). + Network editor, mode "Nodes": Different colors for dynamic assignment nodes and evaluation nodes: BLACK = both DTA + eval, RED = only DTA, GREEN = only eval, WHITE = neither, YELLOW = selected segment nodes (used to be red). + 3D model selection dialog: Blinking cursor in the "group" section to show the current insert position for "Add to group". + COM Interface: Read access to the signal group attributes GREENEND, REDEND, GREENEND2, REDEND2 (only for fixed time) and the signal controller attribute CYCLESECOND. + COM Interface / Pedestrian Module: Read access to type of pedestrian. + Dynamic Assignment: Archiving of cost and path files saves the existing initial files, too. These additional initial archive files (with number zero) are created for the path and cost files if a) option Archive File is on and b) path and/or cost files exist (when starting the simulation) and c) there are no already existing archive files in the directory. This is done for both a normal continuous simulation and for the first run of a multirun series. (If there are archive files already in the directory then these initial archive files are not created because it is assumed that the last archive files correspond to the current start path/cost files. This is not checked, however!) + Pedestrian Module: View / Options / Pedestrians: Configuration for display of aggregated values (LOS): + Update interval + LOS either area-based (LOS per area) or grid-based (with user-defined cell size) + Selection from 12 predefined LOS schemes (with user-defineable colors) or user-defined definition of a LOS scheme (including class boundaries), depending on the average density or speed. + Option "cumulative": calculating the average over the whole time since the start of the user-defined aggregation period. (This causes fewer color changes the more simulation time has already passed.) + Pedestrian Module: (Optional) selection of a LOS scheme for a display type, to override the global settings. + Pedestrian Module: (Optional) selection of a LOS scheme for a pedestrian area or ramp, to override the display type setting. + Pedestrian Module: Pedestrian queue evaluation (*.pqe) for areas without orderly queuing (i.e. not single file but only stopped at a bottleneck): If a queuing area which is selected for queue evaluation has no dwell time distribution selected, the pedestrians who have this area as next routing destination (or have alread arrived on that area) and who are slower than 0.4 m/s and who are either closer than 2 m to the area edge that the queue arrow points to or closer than 2 m to another pedestrian who belongs to that queue are considered to be part of that queue for the queue evaluation until they leave this area. + Pedestrian Module: The allocation of alighting passengers to the doors of a PT vehicle can be defined through a location distribution (Base Data / Distributions / Location) which shows how the total number of alighting passengers is spread over the whole length of the vehicle. Each door of a vehicle dwelling inside the PT stop (which is used for alighting) calculates "its" part of the total vehicle length (half-way to the adjacent door(s) respectively full distance to the front/rear of the vehicle) and the increase in y direction over this part on the x axis of the location distribution is assigned as percentage of alighting passengers to the respective door. The alighting location distribution can be selected per PT line stop (double click on a red PT stop in a selected PT line). Default is "no distribution" which assigns the same percentage to each door (regardless of the position). There are five predefined distributions (in new networks): Uniform (linear over the whole length of the vehicle), Center (more passengers alight near to the middle of the vehicle), Front (more passengers near the front), Rear (more passengers near the rear) and "Front and Rear" (fewer passengers near the middle of the vehicle). + Pedestrian Module: Dialog Display Options, tab page Colors: If "Use display type colors" is NOT activated: + "Links/Areas" color is used for ped areas and ramps (NOT obstacles) + "Land" color is used for obstacles. - A simulation run of a new unsaved network ("Untitled") without any evaluation file selected cannot be started and the error message "Names of output files undefined! Define them by File/Save!" is displayed. (This bug was introduced in version 5.20-04.) - The crosswalk computation for external controllers uses the dynamic assignment network graph (only from nodes with active "Dy. Assignment" flag) instead of the evaluation network graph (from nodes with active "Node valuation" flag). This can cause VISSIM to freeze at the start of a simulation run if there are very few dynamic assignmen nodes in the network so that there are a lot of edges between them (and/or turning movements inside them if they are big). - If a node is created around an intersection with signal heads of a fixed time controller the fixed time signal editor (VISSIG) sometimes cannot be started before the network has been saved and read in again. - Network Editor: PT line stops (on a selected PT line) cannot be selected at all with a double click if the destination cross section of the PT line is located closer than 4 pixels to the start of the destination link (in the current zoom resolution, so zooming in can help). - Dialog "Conflict Areas": Cancel doesn't work (behaves as OK). - Link Behavior Type Dialog: List scroll with arrow keys does not work (after one line change another control has the focus). - 2D/3D Model Distribution dialog: Changed geometry values (e.g. length) are used in a subsequent simulation run and written to the *.inp file but after reading such an *.inp file again the geometry values from the 3D model file are used (and overwrite the manually changed data when saved in the *.inp file). [Upon loading an *.inp file where the geometry of the referenced 3D models is different from the saved geometry data, a warning message is displayed now. This can be "fixed" by opening and saving the *.inp file in 5.20-04 or in 5.20-05 by opening the 3D model dialog for each model listed in the VISSIM log window, closing the dialog with OK and subsequent saving the *.inp file.] - 2D/3D Model Distribution dialog: - Doors data from the Geometry dialog is overwritten if the 3D Model Selection dialog is closed with OK, even if there is no door information in the selected 3D model. - The table on the "Doors" tab page in the Geometry dialog accepts only the decimal seperator selected in the Windows Regional Options (while the "Base" tab accepts "." and ","). If one uses the wrong one in the "Doors" table it is ignored, so for example (with "." selected but "," entered) 0,3 becomes 3.0 and 1,0 becomes 10.0. - 3D Model Selection dialog: - Crashes if group add is interrupted by another add. - Clearing group elements (or deleting the last element) does now remove the selection in the file list, allowing a 3D model to be generally replaced by a block with the 2D/3D geometry data (if the group is empty upon OK). - Edit / Rotate Network: The message that the rotation doesn't apply to background images is not displayed anymore. - If VISSIM is closed after a change of a background position or size a warning message asks if the *.bgr file should be written but if that file is write-protected and if the user selects "Save" the file is not written and no warning message is displayed. - Snapshot file: Simulating a network with a VAP controller after reading a snapshot file does not work correctly (can cause an exception message). - Fixed time control / VISSIG: The intergreen times in the lower part of the matrix are ignored when displaying intergreen conflicts in the signal program. - Fixed time control / VISSIG: Open / File causes an error message if the selected file is located in the same folder as the *.inp file. - Test mode: The smoothed occupancy is not computed correctly for an external signal controller if the simulation resolution differs from the controller frequency. - Test Mode (manual, macro and loop): PT telegrams (from calling points) are not passed to external signal controllers. - An exception message can occur if Arial Regular or Bold system fonts are missing. - Analyzer: The VISUM network file (*.net) is never created. [Attention: The file is still only created if the current *.inp file name including the absolute path is identical with the reference in the *.mdb database (from simulation time).] - ANM Import: Routes (and PT lines and paths) can be broken if they include subsequent nodes with parallel edges in between. - ANM Import: The amber time in the ANM data is used as red-amber time for VISSIG. - ANM Import: creates overlapping VISSIM nodes if ANM nodes are very close and have crosswalks (the import aborts with an error message). [Now, the node exit links are shortened if required which can prevent them from intersecting the crosswalks which will cause reduced pedestrian stage arrows in VISSIG.] - ANM Import: The emergency stop distance of a created VISSIM connector can be bigger than the length of the origin link if the length of an ANM turn pocket has to be reduced because of closely spaced nodes. This causes vehicles to stand forever on the previous link (upstream of the pocket). [The emergency stop distance is limited now to the length of the origin link minus 10 m.] - ANM Import: Detectors on lane turns cause the import to fail with an unknown exception. - ANM Import: Log Window: Cannot zoom to nodes from the message "No edges found from node x, through node y, to node z." - COM Interface: Static 3D objects: Problems with filenames: - Blanks in the path/filename are not handled correctly: The internal filename is cut after the first blank. - If only a filename is passed in the COM script (and not the entire path) the object is not found. - The filename is case-sensitive, i.e. if a different case is used in the COM script than in the *.inp file (referencing the model file) then VISSIM does not find the static object through COM. - Dynamic Assignment: Auto-Routing Selection: Alternative Path Search dialog: It's not possible to enter any values because the edit boxes are outside the visible area of the dialog. (Not with "Windows Classic" theme.) - Pedestrian Module: Warning messages in the *.err file for too high density on input areas have 1) wrong unit and 2) wrong value for short distance set to feet. - Pedestrian Module: VISSIM crashes after +click on a selected area. (This bug was introduced in version 5.20-04.) - Pedestrian Module: If a link overlaps with itself (e.g. for the "reverse parking" trick) at the PT stop location a platform edge generated from the PT stop dialog is not a valid pedestrian area (because the polygon is degenerate) but VISSIM only notices it when trying to read the *.inp file again (and failing). - Pedestrian Module: 2D/3D Model Distribution dialog: Geometry data is ignored if the 3D model file exists, in which case the geometry of the 3D model is used. - Pedestrian Module: Dialog Pedestrian Inputs: "Zoom" from the local menu causes an exception if an input has been deleted from the dialog before. - Pedestrian Module: A simulation run with active queue evaluation or pedestrian record can abort with the message "CriticalError: An error occurred in communication with the external pedestrian model DLL" / "Could not retrieve pedestrian queue flag from pedestrian model for pedestrian" if a pedestrian is pushed back from a queuing area onto the ramp where he came from. - Pedestrian Module: The length of pedestrians is not used correctly in the behavior calculation, nor in the 2D display. [This fix changes pedestrian simulation results.] - Pedestrian Module / Animation replay: Pedestrians are not visible if vehicle visualization is switched off. - Pedestrian Module: Deleting an pedestrian route intermediate point by dragging it outside the network doesn't work. The point remains outside and is not deleted and it has no effect on the pedestrians. - VISSIG: Execution of a stage based signal program crashes after reading a snapshot file. Version 5.20-04 [21070] (2009-11-06) ------------------------------------ + Driving Behavior Parameter Set / Desired position at free flow: can be "Left" now (for right-side traffic) respectively "Right" for left-side traffic. + COM Interface: Detector.AttValue ("PRESENCE") is writable: value 1 to set a continuous detection (a vehicle front end is detected if the detector has not been occupied at the end of the previous time step), value 0 to reset the detector. (The value is not automatically reset to 0 at the end of each time step.) + Pedestrian Module: Pedestrian queue evaluation (*.pqe): Fixed format, with the following parameters: + PedCount (number of pedestrians), average and maximum value (during the respective time interval), + Extent (maximum distance of a pedestrian from the start of the queue), average and maximum value (during the respective time interval). The active areas for this evaluation can be selected in the Queue Evaluation Filter dialog. (Only queuing areas can be selected here (area dialog with checked [x] Queuing. Note: If no dwell time distribution is set for the queuing area the pedestrians do not queue.) + Pedestrian Module: Pedestrian Record: New parameters: + QueueArea : Current queuing area number (0 = pedestrian not in a queue) + QueueDist : beeline distance to begin of current queue + QueueTime : Time spent in last queue (only written in the time step when the pedestrian leaves the queue) + QueueTotalTime: Total time spent in queues [s] (current queue included) + Pedestrian Module: The pedestrian color default distribution 71 ("Shirt Man") has exactly the same grey as the default "Land" color, so the pedestrian is invisible in 2D when using the option "Center line". This color has been changed to light blue. (Note: Input files where the color distributions are already saved can still have this problem. This change only helps when creating a new project.) - The command line parameter -b (for loading an *.ini file) results in a distorted display of the network - View / Options / Display configuration color code dialogs for vehicles (both individual vehicles and aggregated values) and pedestrians (individual pedestrians): VISSIM crashes if you enter a blank for the lower and/or upper bound and close the dialog with OK. - VISSIM crashes at the end of a simulation run if an external driver model DLL has been used. - 2D/3D model distribution: A negative shaft length (e.g. in Stepvan1.v3d) can cause a vehicle to start backwards (rear end downstream) when set into the network if the negative shaft length has an absolute value bigger than the distance traveled in the first time step. (As soon as the distance traveled in a time step then exceeds the distance between the axles the direction switches to forwards.) [The shaft length is ignored now for the first vehicle element.] - Managed Lanes Routing: There is no warning if it is not possible to calculate a partial travel time (because the managed lanes decisions are too close together) during a simulation run. This can seriously influence the managed lanes routing because it does not work properly without enough collected travel times. [Now, a warning message is written into the *.err file.] - 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. - The pan button (hand icon) is disabled after switching from 3D to 2D during a simulation run. Also, the pan button in 2D stays disabled after switching back to zoom during a simulation run. - The vehicle routes dialog doesn't work in Chinese. - Fixed Time Control Editor: Minimum signal durations (e.g. minimum green time) are ignored when compressing a signal program graphically. - Fixed Time Control Editor: Redoing changes does not work correctly if cycle time changes are included. - Fixed Time Control Editor: After selecting File/Open the signal groups are not updated correctly in VISSIM. Additionally, it is possible to open a *.sig file that is not located in the current working directory (of the *.inp file) and thus not used in a simulation run. [Now the user is asked if the *.sig file is to be copied to the working directory. If he declines the file is not opened.] - Adaptive ANM Import: creates only the *.panmRoutes file but not the *.panm file. (This bug was introduced in version 5.20-00.) - Adaptive ANM Import fails in the 64 bit edition. - COM Interface: Changing the TYPE or STATE attribute of a signal group before the start of a simulation run results in an exception. [Now there is an error message stating that this is only possible during a simulation run.] - Dynamic Assignment: VISSIM crashes at the start of simulation run when reading a path file listing a destination parking lot number that does not exist in the network. (This bug was introduced in version 5.20-02.) - Dynamic Assignment: Edge closures are not always deleted if an included link is deleted. The *.inp file written after this refers to the deleted link number but can be read in anyway (the edge closure is ignored). - Pedestrian Module: Alighting pedestrians sometimes get lost between the vehicle and the platform edge. - Pedestrian Module: VISSIM crashes when playing *.ani files with ramps or alighting pedestrians from PT vehicles. - Pedestrian Module: The calculation of the internal geometry of ramps sometimes messes up the levels at the end of the ramp and cuts out small additional slices, preventing the simulation from starting. - Pedestrian Module: The illegal state red/red can be set for pedestrian / vehicle conflict areas by first creating a red/red conflict area for vehicles and then changing one of the links to a pedestrian link. This causes undefined behavior during the simulation and a crash in the conflict area dialog, and the written *.inp file cannot be read in again. - Pedestrian Module: Inserting a new measurement area causes VISSIM to crash if there's no display type no. 1. - Pedestrian Module: Walking Behavior Parameter Sets dialog: The columns in the right (details) grid are alway reset to their default width after selecting another parameter set. - Pedestrian Module: Pedestrian evaluation output isn't working correctly for languages with other code pages (e.g. Cyrillic). - Pedestrian Module: Ramps dialog: - On multiselect, the radio buttons for ceiling opening (headroom / length) and ramp foot (headroom / length) are not selected/deselected correctly if the ramps have different selection states. - On saving, the ceiling opening / ramp foot is always saved by length, even if headroom is selected. When loading the file again, all ramps have length selected. Version 5.20-03 [20621] (2009-10-12) ------------------------------------ + Fixed Time Control Editor: Signal sequences are displayed graphically, the reference to countries has been replaced by the list of the states. + COM Interface: Method RecalculateSplineHeight() which doesn't change the x and y coordinates of spline points of connectors (but only z). + Pedestrian Module: Area Evaluation: New parameter "Source volume" (number of pedestrians who have left the area during the time interval). + Pedestrian Module: LOS display (started through Ctrl-Q) excludes obstacles which are now always shown in their original color. + Pedestrian Module: If feet is selected as unit for small distances the density (e.g. on measurement areas) is given in ped/ft². - Network Editor: Crash upon dragging a network object off a link. This problem happens only if the action is very short (so you have to drag fast and not too wide) [so internally there is only one mouse move event with more than 4 pixels distance from the original click position before the mouse up event]. - The license check for network size considers static 3D models' and background images' positions, so a big static 3D model can prevent a network from being loaded. - License dialog: "Parallel Processes" (for MPI) is still displayed but doesn't do anything (and there is no parallel version anymore). - Errors during the loading of the first *.inp file are written into vissim.err (instead of *.err). - 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. - Node leg orientations (passed to VISSIG for arrow directions) are not calculated correctly for one-way edges (only incoming) or if the distance to the next node is more than 300 m. - Extended Fixed Time Editing (VISSIG): not accessible without SCOOT in the VISSIM license. - External signal controllers: The computation of the current cycle second in VISSIM is wrong, so external controllers that use the cycle second from VISSIM (e.g. VAP) don't work correctly anymore. - External signal controllers: If a PuT telegram is received in the last simulation time step of a signal control time step (i.e. when the signal controller is updated) the same PuT telegram is transmitted in the next signal control time step again. This can result in unexpected behavior of the signal controller. - Signal Control dialog: Changing the type of a controller to RBC causes an Exception message. - 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.] - 3D Model Selection dialog: Looks strange on Vista with Aero (because of different font size), buttons can be outside of the visible area. The dialog can be shrunk too small, too. - Dialogs "Managed Lanes Facilities" and "Toll Pricing Models": - After the last item has been deleted the details on the right are not cleared (but only disabled). - Inserting a new item right after the last one has been deleted causes wrong/undefined behavior. - View - Background - Parameters - Modify: displays wrong origin. - Export - VISUM - Nodes/Edges + routes (*.rim files): Demand segments are not exported. The VISUM version file is not created. Manual import of the *.rim files into VISUM is not possible. (This bug was introduced in version 5.20-02.) - Extended 3D Package: Loading a Sketchup file (*.skp) changes the working directory, so a future File/Save saves the *.inp file to the directory of the *.skp file. (This problem happens only on Windows XP, not on Windows Vista.) - 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. - COM Interface: VISSIM throws an access violation if the attribute LINK is called for on street parking lots. - COM Interface: License warning concerning the pedestrian module is displayed even if VISSIM is started through COM. - Dynamic Assignment: If a start or destination parking lot is located on a parallel edge and there are parking lots on all of these parallel edges VISSIM can decide to use the wrong edge because only the existence of a parking lot is checked but not that it is the right one. [Now, when reading a path file in VISUM format (created from *.anmroutes) the given parking lot is used, and thus the correct edge selected.] - 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: The Tab key doesn't toggle anymore between overlapping pedestrian areas in pedestrian routes editor mode. (This bug was introduced in version 5.20-02.) - Pedestrian Module: The Tab key, the "next" button and single click don't toggle between overlapping pedestrian measurement areas. - Pedestrian Module: Pressing Del causes the deletion of a network object in some dialogs even if the object list doesn't have focus (e.g. while editing a number in an edit field). Other shortcut keys can trigger the local menu, too. - Pedestrian Module: Construction elements dialog (areas/ramps/obstacles): several problems with multi-select. - Pedestrian Module: Dialogs "Area Behavior Types" and "Walking Behavior Parameter Sets": - After the last item has been deleted the details on the right are not cleared (but only disabled). - Inserting a new item right after the last one has been deleted causes wrong/undefined behavior. - Pedestrian Module: A semantic error message is displayed after reading additionally if a pedestrian walking behavior contains a parameter file that is located in the Exe\ or data (*.inp file's path) directory. Version 5.20-02 [20338] (2009-09-24) ------------------------------------ + 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. + Dynamic Assignment: Export - VISUM - Nodes/Edges: Edge closures and connector closures for vehicle classes are passed to VISUM, so they can be used in the VISUM assignment (and VISUM doesn't use paths which are closed in VISSIM). [If there are disjoint parallel edges between nodes in VISSIM which connect from/to different turning relations in these nodes, these edges are exported as one edge to VISUM which is connected to all these turning relations (because the situation cannot be modeled in full detail in the VISUM network model), and a warning message is issued by VISSIM. The resulting VISUM assignment might use paths that are not possible in VISSIM where not all turning relations from the first node are connected to all turning relations in the second node.] + Pedestrian Module: Area Evaluation Configuration for Compiled Data (button "Configuration" in "Area Evaluations" dialog). Only the selected parameters are written to the evaluation file (*.mesp). The configuration is saved in a configuration file (*.mespk) which is referenced in the *.inp file. + Pedestrian Module: The key combination for alternating through the different LOS display definitions is now Ctrl-L (because only L is used in 3D mode for navigation, too). - VISSIM saves the *.inp file using comma (instead of point) as decimal separator one some computers and thus the file cannot be loaded again. - A vehicle aiming for a PT stop or parking space downstream of an occupied PT stop or parking space which is not on the outside lane starts to overtake on the "wrong side" (outside lane, i.e. to the right with right-side traffic) but then changes back to the original lane behind the blocking vehicle. This can happen multiple times. [The restriction that a vehicle leaving a parking space may not pass other parking vehicles on the "wrong" side has been removed now.] - Link segments of a segment node are not always adjusted correctly if spline points of a link or connector are moved. This can cause subsequent problems due to a corrupt node/edge structure. - 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"). - 3D Model Selection dialog: Models with triangle strips (most of the vehicle models) are not loaded. - Signal Control / Calling Points: VISSIM discards PuT telegrams if the signalization frequency is lower than the simulation resolution (time steps per second) and if the telegram is not sent in the last simulation time step before a controller time step. - Vehicle routes dialog: Fatal error (VISSIM has been interrupted...) if the routes dialog is opened for a network containing managed lanes facilities. - Analyzer report dialog: When "Select values or Check All" is displayed, it is not possible to uncheck the checkbox "All" because it is not visible. - 64-bit Edition: Switching to 3D mode with a background file loaded causes an exception message. - COM Interface: VISSIM crashes if a simulation run is started manually after a simulation run that had been started through COM. - Pedestrian Module: Dialog "Construction Elements" (Areas/Ramps/Obstacles): The handling of invalid data in edit fields is not done correctly upon selecting a different element (or creating a new one): An error message is displayed but the selection is not reverted to the original element that caused the error and the invalid data is silently reset to the previous value. - Pedestrian Module: Dialog "Measurement Area": Crash upon second change of the selection in the network window after a change of a value in the dialog. Version 5.20-01 [20195] (2009-09-10) ------------------------------------ + COM Interface: New attributes SUPPLYFILE1, SUPPLYFILE2 and new signalization types (RBC, SCOOT, SCATS, LISA, Econolite3ASC) for attribute TYPE for the COM object SignalController. + COM Interface: New attributes INPUTFILE, WORKINGFOLDER and EXEFOLDER for the COM object VISSIM. Version 5.20-00 (2009-08-24) ---------------------------- + 64 bit edition available: allows usage of more than 3 GB RAM. + VISSIM uses anywhere the Windows system font (user-selectable in the Advanced Appearance Settings) instead of Arial Unicode. This allows better display of Japanese and Chinese characters and the use of bigger fonts (for high DPI values). + Fixed time SCs are automatically converted to the new external controller with graphical signal plan editor (formely EMIL). For each fixed time controller a *.sig file is created which contains the controller data. If the *.inp file is copied into a different directory, these files need to be copied, too (as any external controllers' data files). + Add-on Module "Extended fixed time editing" (stages, interstages): Directions for signal group arrows are derived from the link direction at node entry and can be overridden in the node dialog. (Neighbour nodes must exist!) + Interface to the signal control system SCOOT (add-on module). + External signal controllers (DLLs) can have different controller frequencies now. They must have a lowest common multiple of 10 or less. The controller frequencies for fixed time controllers can be set in the new fixed time GUI - the edit box in the Simulation Parameters dialog has been removed. + External signal controllers: The current cycle second (determined by VISSIM for fixed cycle length) is calculated with the very first cycle starting at midnight (no change if the simulation start time is 00:00:00). + External signal controllers: Error message stating the name of the DLL if an exception happens inside the controller DLL. + New selection dialog for 3D objects (static objects and vehicles): + Display of the selected model in 3D, with zooming/rotating as in the VISSIM network window. + Display of the dimensions of the model. + Option to set the "VISSIM" color (as set by a vehicle type or class) to determine which part of the model has fixed colors. + Display of the number of polygons. + Display of the different states of the model (if existing). + Display of the model in the various Levels of Detail (click the lock button to display the selected LOD regardless of the viewing distance), with the cutoff distances for LOD settable separately per model (overriding the global cutoffs). + Directory tree and buttons for the project directory (of the *.inp file) and the standard model directory of the VISSIM installation (Exe\3DModels\). + For vehicles: + visualization of the location of axles and joints and the shaft length. + For static models: + Specification of the elevation (z coordinate) as a number. + Specification of the rotation (pitch, yaw and roll) as numbers. + Visualization of link parameter "No Lane Change" (vehicle-class dependent prohibition of lane change (per direction) in 2D and 3D: A continuous line closer to the lane where vehicles may not change from adjacent to a dashed line closer to the lane where vehicles may change from. Only one continous line if lane changes are prohibited in both directions. + 2D footprints of static 3D objects are visible in 2D animation and editor. + 3D signal heads can be repositioned along the mast arm in 2D editor mode. + 3D signal heads: Improved handling for left-hand traffic: Attach arm optionally on the right side of the mast (as seen from the upstream vehicles), default side is derived from the simulation parameter "Traffic Regulations". + Direct import of static SketchUp 3D Models (without V3DM): Ctrl-RightClick in the network window in 3D. (In addition to *.skp files *.3ds files and *.dwf file can be read, too, but these might be displayed not completely correct.) + The default 3D model distributions for pedestrian types have been changed to use the new model files with 4 colors. + 3D mode: The size of the rectangular base plane now considers static objects. (This prevents some view problems on large models as well as gaps between large static objects and land.) + 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. + Keyframe dialog: New checkbox "Absolute start times" (default not checked): If checked, the start time of first keyframe is understood as the simulation second to start recording (so that all start times are absolute numbers). The AVI recording is then started if a) the menu option "AVI recording" is activated and b) the simulation time reaches the start time of the first keyframe. If "AVI recording is activated after the (absolute) start time of the first keyframe the AVI recording starts with the first keyframe that has a start time later than the current simulation time. + Keyframe dialog: The checkbox "Delay Later Keyframes"/"Fit Other Starting Times" reads now "Move later keyframes" and has a new behavior if an existing keyframe is edited with this option selected: The starting times of all later keyframes are changed by (new starting time - old starting time + new dwell time - old dwell time). Moving the starting time before the end of the dwell time of the previous keyframe is not possible. [This replaces the previous option to move a keyframe to a different position in the list while keeping all dwell and movement times.] + Network Performance Evaluation: Two new parameters: + Latent Demand = number of vehicles that could not enter the network before the end of the simulation period from vehicle inputs or parking lots. + Latent Delay = total waiting time of vehicles that could not enter the network from vehicle inputs or parking lots. This value includes the vehicle waiting time for vehicles that do enter the network before the end of the simulation period. (There might be several vehicles waiting at the same time at one vehicle input!) + Analyzer Evaluation: Speed up (by writing data into text files during the simulation run and bulk insert into the database once at the end of the run). + Command line parameter -d: sets the number of decimals written to the evaluation files to n. This affects the vehicle record, node evaluation, link evaluation, pedestrian record and Analyzer evaluations. + The message box "During the simulation/test run time warnings were written to the file <...>!" has an additional "Show" button that opens that file in Notepad. + Message box "Complete broken routes" extended: + Zooms automatically to the route. + Cancel is possible at simulation start. + Conflict Area Dialog: The node number can be entered with the keyboard. + Dialog "Display Network Elements": Rows are ordered by network element name. + Context menus in dialogs: Consistent commands and shortcuts. + Partial and Managed Lanes routes: If the route destinations of a partial or managed lanes routing decision are not all on the same link/position, they are repaired at the start of a simulation run and in the routes dialog (Check): All destinations are set to the destination of the route with smallest number. + Export / VISUM / Nodes/Edges: + Exports link speed (VISUM link PrT V0), too, derived from the desired speed distributions used in VISSIM parking lots and desired speed decisions. + New dialog with the choice between "for assignment in VISUM (without VISSIM paths)" or "for visualization in VISUM (with VISSIM paths)". A VISUM version file can be selected, too, so no importing of *.rim files into VISUM is necessary anymore. + ANM Import: Import of only DTA routing into an existing network (without previous network import) is possible (e.g. for manual assignment in VISUM). + Adaptive ANM Import: Additional check for VISSIM nodes (executed at the start of the adaptive import): If the VISSIM node corresponds to an ANM zone, it is checked that the actual edge structure corresponds to the internal ANM attributes (ANM zone connector IDs) of the node. + Adaptive ANM Import: Node geometry is not re-created if only node name and/or link name and/or link type and/or link speed have changed. [Note: on parallel links between two nodes name/type changes deliberately force re-creation of node geometry.] + COM Interface: Link attribute THICKNESS. + COM Interface: Direct access to TYPE and STATE of a signal group, so any controller logic can be implemented in a COM script. (The signal group attributes GREENSTART and GREENEND don't work anymore: They return always zero, and setting them has no effect!) + COM Interface: The simulation and signal controller attribute CONTROLLERFREQUENCY (also available as function in ISimulation) has been removed (because the controller frequency is now set by the external controller DLL, even for fixed time controllers). + COM Interface: Graphics.AttValue("PEDVISUALIZATION") to switch visualization of pedestrians on/off (1/0). + COM Interface: Read/write access to the maximum deceleration value for a vehicle class at a reduced speed area. + Dynamic Assignment: Archived cost/path files are numbered consistently with multi-run evaluation files (using a fixed random seed): starting at _001. + Dynamic Assignment: Automatic check & repair of segment nodes at the start of creation of the network graph: checks for each connector if the position on the origin link is included (if the start of the connector is included) and if the position on the destination link is included (if the end of the connector is included). In case of error, zoom to node, change into node mode, message "Change definition from link segments to a node polygon?" + 2D/3D Vehicle Models: Door positions (for pedestrian module). See manual for details. + Pedestrian Module: Public transport passengers (boarding/alighting) for bus / tram stops: see manual for details. + Pedestrian Module: Intermediate points for pedestrian routes can be placed on ramps. + Pedestrian Module: Separate display configuration in View / Options / Pedestrians (similar as for vehicles). + Pedestrian Module: Configuration dialog for pedestrian record. + Pedestrian Module: Independent default display type for each construction element type (area, obstacle, pedestrian link, ramp). + Pedestrian Module: The maximum density beyond which no pedestrians can be set into an input area has been increased from 4 to 6.25 pedestrians per square meter. Version 5.10-10 (2009-0?-??) ---------------------------- + 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. 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.