Has anyone been able to complete this activity using open rails? The issues that I have is this. After picking up the empty car at S Parry, I have to tab to get permission to leave the siding after the CP train overtakes me. The CN train never appears to take the crossover on to the CP tracks. No problems with this part in MSTS. Once under it's smooth sailing until I reach Sparrow Lake siding were I have to take the siding and nothing ever appears. I'm unable to tab past the signal after waiting nearly 2 hours. In the MSTS AE it shows that I have the main. If you have been able to complete without any troubles please share what you did. I've tried adjusting times. But that didn't help at all.
-
-
I have had difficulty as well. I think I discovered mention of leaving the second locomotive where the empty lumber cars were.
Some activities seem to be not well described. I have been trying manual mode to operate switches and get by end of authorization blocks.
No magic as yet.
Rick -
Go to Elvas Tower site, the to the Open Rails section. I started a post there about this activity and have received 4 pages of replies with some good info on how to get the activity working.Comment
-
IBM XT i386; 512Kb RAM; 5.25" FDD; 1.4Mb FDD; 5Mb HDD; VGA 256-colour graphics card; AdLib soundcard; DR DOS 6.0; Windows 3.0Comment
-
Here is the link :
http://www.elvastower.com/forums/ind...vity-cn-31451/
And this is the problem with route Bala2 :
The reason for the problems is a construction which is used in sigcfg.dat which I haven't seen before in any route and, admittedly, did not know was possible and allowed.
Various signals are defined as two signal types :
SignalFnType ( NORMAL DISTANCE )
That construction is certainly not supported by OR, and changes to implement that would be very extensive.
This does cause all kinds of problems.
The main problem - and that's the problem which keeps so many signals at danger - is as follows.
In the signal script for normal signals, there is a test if opposite signals are cleared - if so, the actual signal will not clear.
But this test is done for signals of type DISTANCE. As OR cannot allocate two different signal types to a signal, it does not find the intended signal, but instead finds a switch-stand much further down the route (which, strange enough, is also type DISTANCE). A switch-stand never has state STOP, and thus the main signal will never clear.
And here is my suggested solution :
To make the signals work correctly, edit the sigscr.dat file (be sure to make a backup copy first!) and remove all lines which read :
opp_sig_lr (SIGFN_DISTANCE) !=# SIGASP_STOP || // Entry from next interlocking blocked?
The line must be removed to maintain the rest of the "if" statement, which now should look like :
// If required, show the appropriate 'stop' indication.
if ( !enabled || // Not enabled/cleared to show natural state?
block_state() !=# BLOCK_CLEAR || // Block ahead not clear?
!route_set() ) // Switch not set as per link?
state = SIGASP_STOP;
Regards,
Rob RoeterdinkComment
-
Thanks, Rob.
Much obliged for your courtesy in posting that here.IBM XT i386; 512Kb RAM; 5.25" FDD; 1.4Mb FDD; 5Mb HDD; VGA 256-colour graphics card; AdLib soundcard; DR DOS 6.0; Windows 3.0Comment
-
and I'm gathering if someone screws up their Bala Sub V2 with this that MLT will not help you with customer support since it's a hack of the file.Work Safe play hardComment
-
Rule 1 of software and especially MSTS: ALWAYS back up your installation before trying changes...
RobertComment
-
Just a note to say that the workaround/correction from roeter worked! I did the whole route in Act CN31451 in Auto Mode except for picking up the centerbeams. A very simple correction that seems to have solved the issue of the signals and AIs in Bala 2.0 in Open Rails.
I completed this activity and now to test a couple of the other ones and see how it goes.
It was not very involved, just a matter of proceeding through the sigscr in notepad and utilizing the "Find" command to locate and delete those lines. That is where I made the changes and it worked. I did the whole act with no issues and saw all of the AIs, and they were moving!
Comment
-
Ditto, after using exactly the same editing procedure.
Westerngy:
The workaround described is hardly likely to bring down the entire Bala 2 installation.
The only safety net required is the backup of the one file.IBM XT i386; 512Kb RAM; 5.25" FDD; 1.4Mb FDD; 5Mb HDD; VGA 256-colour graphics card; AdLib soundcard; DR DOS 6.0; Windows 3.0Comment
-
Made the changes and they worked, kinda. No meet at Brechin but no red signals either. Seemed to pass the container double stack one siding earlier. Did not find the admin bdlg or set out any item as described in the work order.
At least it worked without putting in manual mode or going into node mode.Comment
-
Will this sigscr.dat modification affect running the route in regular MSTS?Glenn Duba
Cinnaminson, NJComment
-
This change will probably adversely affect the running in MSTS. The modification is only intended if you are running the route in Open Rails. With a backup, it can be reinstalled either way just by adding a (a) after one of the sigscr files, the one you are not using. Just add or subtract the appropriate file whether you are running MSTS or OR at the time. A little extra work, but a cut and paste does not take long, and it should work.
Personally I do not see why anyone would want to run in mSTS after experiencing OR.Comment
-
Thank youGlenn Duba
Cinnaminson, NJComment
Comment