Hello,
TRS22Plus has presented several problems for me, e.g. the flashing trees and some signals being dark. Another one of these problems is this.
I have a medium-sized route (120 MB in CM) that runs well in TRS19. It has over 20 trains, and lasts two hours. Most trains however reach their destination much earlier.
I use the very same route and session assets, at build 5.0, in TRS22. Unfortunately, in TRS22 (122411 and 123794) it always ends in CTD. In a very unpredictable manner, however. I see no pattern.
For testing, I have disabled many assets, though sometimes that disturbed the session of course. Buildings, signals, industries and various other scripted assets. I have also tried eliminating the EIT, by disabling the signal box asset, and/or disabling the rule assets, and even taking out the trains that use EIT commands.
But, it also happened that the program crashed when I started scrolling the onscreen Drivers listing immediately after the start of the session. The trains had not even begun running. I could at least reproduce that once more. But when I followed one train on the screen, it could take longer, even up to 30 minutes before a CTD occurred.
No missing assets, no faulties in CM. The whole session runs to its end in TRS19. Not so in TRS22.
What has changed that could make the difference, and how could I critically test it?
Thanks for any suggestions.
Paul
TRS22Plus has presented several problems for me, e.g. the flashing trees and some signals being dark. Another one of these problems is this.
I have a medium-sized route (120 MB in CM) that runs well in TRS19. It has over 20 trains, and lasts two hours. Most trains however reach their destination much earlier.
I use the very same route and session assets, at build 5.0, in TRS22. Unfortunately, in TRS22 (122411 and 123794) it always ends in CTD. In a very unpredictable manner, however. I see no pattern.
For testing, I have disabled many assets, though sometimes that disturbed the session of course. Buildings, signals, industries and various other scripted assets. I have also tried eliminating the EIT, by disabling the signal box asset, and/or disabling the rule assets, and even taking out the trains that use EIT commands.
But, it also happened that the program crashed when I started scrolling the onscreen Drivers listing immediately after the start of the session. The trains had not even begun running. I could at least reproduce that once more. But when I followed one train on the screen, it could take longer, even up to 30 minutes before a CTD occurred.
No missing assets, no faulties in CM. The whole session runs to its end in TRS19. Not so in TRS22.
What has changed that could make the difference, and how could I critically test it?
Thanks for any suggestions.
Paul