Please contact McTrans with any new issues raised that may be added to this list.

1.  When coding link connections (on the Map View or the Edit > Feeders screen), automatic flow balancing does not work properly if the summation of upstream left-turn and right-turn volumes exceeds the downstream thru volume.  In this situation, it might be necessary for the user to manually code feeding flows in the Feeders screen.*

2.  When importing a CORSIM input file into T7F10, two-way stop-controlled (TWSC) intersections are not imported.  The next version of TRANSYT-7F will allow the user to import TWSC nodes if desired, or import signalized intersections only.*

3.  In the time-space diagram screen, efficiency and attainability are not computed correctly when progression bands "wrap" at a two-way stop-controlled (TWSC) node, such that the "bottom" band is above the "top" band at the TWSC node.*

4.  In the Lane Configuration screen, if volumes are coded prior to lane channelizations, subsequent changes to the lane channelizations might automatically change the volumes.  This might make it necessary to re-code some of the volume data (i.e., volume, peak hour factor, and turn bay storage).*

5.  In the Route Summary Report, the route-wide Disutility Index (DI) is not computed correctly for the first route in the data file.  To get around this problem, the DI for route #1 could be computed manually, by taking the summation of link-specific DI's within the route.*

6.  When importing a CORSIM input file into T7F10, T-intersections operating under actuated control are sometimes not assigned the correct approach direction (NB, SB, EB, WB).  This does not affect the ability to perform direct CORSIM processing or optimization, but if the user tries to perform a macroscopic TRANSYT analysis, volumes and timings might be assigned to the wrong approach.*

*Indicates that this issue will be resolved in the next software release.