INSTRUCTIONS TO GET THE ALPHA VERSION OF THE AWS TCS OPERATING
Preparation
Download and install
https://www.uktrains...orm_fileid=4488 (NWT150 DMU) into the mep miniroute
Download and install
https://www.uktrains...orm_fileid=5692 (cabview for NWT150) into the mep miniroute by Graham Parkin
The NWT150 has been wisely suggested by Coolhand, because it has a usable sunflower. However without the AWS TCS it works unproperly.
Download file mep_AWS_demo_pack.zip Rev.10 from here
http://www.interazio...loads/index.php , unpack and install it into your Train Simulator folder for the MEP mini-route install
The pack must be run with OR NewYear MG rev. 53 or later.
For interested people such file includes:
- modified cabview (.cvf file named 2000_aws.cvf), with addition of the animation of the alerter reset button (files are added in the CABVIEW folder of the NWT150)
- AWS bell and beep sounds, and the TCS_AWS_UK.sms file that manages them; the AWS bell sound is the "bing" sound available in
https://www.uktrains...orm_fileid=4053 , by James Horgan (files are added in the SOUND folder of the NWT150)
- modified .eng files, located in the OPENRAILS folder within the NWT150 folder; the modified .eng files refer to the new cabview and include a line
Include ( "AWS_eng.inc")
which includes the references to the script files; such AWS_eng.inc file is also included in the pack and resides within the Openrails subfolder. Its content is as follows
ORTSTrainControlSystem( TCS_AWS_UK )
ORTSTrainControlSystemSound( TCS_AWS_UK.sms )
ORTSTrainControlSystemParameters( TCS_AWS_UK.ini )
The first line refers to file TCS_AWS_UK.cs, which is the script file itself, and which resides within the SCRIPT subfolder of the NWT150 folder
The second line is self-explanatory
The third line refers to the file that contains the configuration parameters of the script file.
To run the AWS script file you must use OR NewYear MG rev. 52.4 or higher, which can be downloaded from here
http://www.interazio...loads/index.php .
To enable AWS operation you must uncheck general option "Disable TCS scripts"
If you want to have also the speed reduction warning check (which applies if there is a speed reduction of more than 25 mph) you must check general option "Speed Control"
If you want to have also the alerter you must check general option "Alerter in cab"
The file includes also the files for two short test activities, that is TESTAWS1 and TESTAWS3. TESTAWS1 operates in a light signals environment, while TESTAWS3 operates in a semaphore environment.
AWS warning acknowledgements occur by pressing the Alerter Reset key or by clicking the AWS reset button with the mouse.
There are uncovered points:
- the AWS braking is stronger than in reality
- shunting NORMAL signals are not excluded (but there are very few)
- the AWS experts could find other flaws.
I am grateful for any comment.
I'm neither sure I manage correctly the case where a speed warning signal is between a speed reduction warning post and the speed reduction post.
You may of course try the pack also in other routes, but you will have to build the test activities by yourself.
You may also play (with some caution) with the configuration parameters of the .ini file.
It is possible to equip other trainsets with the AWS, and therefore to run existing activities using AWS, however if such trainsets don't have Alerter Reset button and operating sunflower there won't be visual cab interaction.
I wish to thank Coolhand and darwins for the many suggestions and explanations. Some support by you is probably still needed.
I credit also gpz and Serana, which developed a well generalized TCS script framework, again Serana for his script for the French TCSs, that I used as guideline to develop my one, and also roeter for his well-organized actual track section structure, that allowed me easily to get the needed data.