Release Notes for v2.0.7
These are the changes that were made in TSCAD v2.0.7. Changes include both Bug Fixes and a few new enhancements. Details of the bug fixes as well as a summary of the new enhancements are detailed on this page.
If you do not already have the TSCAD User Manual for v2.0.7, you can download it here.
Bug Fixes
1. Cajon Route Displaying Black
A problem that has been very elusive and only seems to have existed for some users, some of the time. Sporadically, the Cajon Sub Route would display a black screen and even cause TSCAD to lock up and crash. Thanks to some help from users - as I was never able to cause this to happen myself - I believe that the problem has been identified and fixed. Please feel free to Report A Bug if you still experience this problem after upgrading to v2.0.7.
2. Alignment to Unowned Routes
If you have attempted to align a route from one territory to an adjacent territory that you do not own, you have probably seen this error:
That has been fixed in v2.0.7. You can now align signals from your territory to territories you do not own. There are two important things to note about this. First, the painting of blocks may not appear entirely correct for blocks toward the territory you do not own. For example, when aligning a signal at Kern Jct from UP Main 2 (on UP DS-254 North) to BNSF DS-26 at Bakersfield:
Note that the second block remains white and appears unaligned. This is because TSCAD considers this to be part of the next territory (Bakersfield, which is not installed in this example) and therefore does not paint the indication. Second, if there is a signal aligned against the signal you are attempting to set up, this can cause conflict and two trains can be aligned toward each other. Because you do not own the second route, TSCAD is unable to see any signals in that route and is therefore unable to know if trains may be aligned against the signal you are setting up. So be aware, particularly in a multi-player session.
3. DTMF Notifications
Previously, when a train would “tone up” the dispatcher, all dispatchers would receive a notification of the tone, whether it for trains in their route or not. This has been fixed. Now, a dispatcher will only receive a notification of a tone for trains within their territories.
Note: The latest updates to each route is required to get this fix, in addition to TSCAD v2.0.7.
4. DTMF Notification Display
Some radio towers would previously show a more-cryptic description, such as BNSF_AshHill_Tower. This has now been fixed and the name of the tower should properly show.
Note: The latest updates to each route is required to get this fix, in addition to TSCAD v2.0.7.
5. Accidentally Closing TSCAD
Previously, when clicking on the “X” in the upper-right corner of the main TSCAD window, the entire application would immediately shut down with no warning. That has been fixed. TSCAD will now confirm whether you wish to shut down the application.
This will also apply to any dispatch window you have open and are logged in to as the active dispatcher. Confirmation will be asked before close any such dispatcher windows. If you have a dispatcher window open you are not logged in as the active dispatcher on any tab, no confirmation will be asked when closing the window.
6. Premature Route Stack Execution
Occasionally, Run 8 will send a signal dropping to red before it will send the occupancy of the block beyond that signal. When this happens, TSCAD sees the signal drop to red with nothing in the OS beyond the signal. If there is a route stacked through that OS, TSCAD will believe it is okay to execute the route stack as there is no conflicting routing and nothing in the OS (occupancies).
When TSCAD believes it is safe to execute a stacked route, it will now wait one second and then check again. This should provide enough time for any occupancies to be transmitted from Run 8, blocking the route (if appropriate) before the route stack can execute.
New Features
1. Requesting a Train’s Speed
Adding the ability to request the speed of AI trains. See Chapter 3 under Basic Dispatching / Requesting a Train’s Speed for details in the TSCAD User Manual for v2.0.7.
2. Fleet For
Adding the ability to set a signal in fleet mode for a specific number of trains. See Chapter 3 under Advanced Dispatching / Fleet For for details in the TSCAD Manual for v2.0.7.
3. Revamped Messaging Screen
Adding the ability for the dispatcher to add as many tabs for communications as the would like. In addition, each tab can support up to five channels of incoming messaging traffic. Added the ability to toggle always on top to the messaging screen. See Chapter 6 under TSCAD Messaging for details in the TSCAD Manual for v2.0.7.
Additional Notes
— FAQs —
Some answers to common questions and points of confusion have been added as a new chapter in the TSCAD User Manual starting with v2.0.7. See Chapter 9 in the manual.
— Dispatcher State —
Information on the dispatcher state feature was aded to the TSCAD User Manual in Chapter 2 / Dispatcher State. This feature is not new to v2.0.7, but information about it was unintentionally left out of the initial User Manual.