[mrmosky]

Hi All,

I have reinstalled the Class150 loco and cab and the demo pack and followed the instructions, and I am not getting the sunflower to change in the activities. I am getting a beep, but not a ping.

But don't worry about this if it's working for you guys. It's more important that you get the details sorted out first. Once you have a package that you are happy with, I'll try again.

Just curious to know what keyword to use for the animated sunflower in a 3d cab?

Geoff

[Csantucci]

As written by Darwin,
this

            CabSignalDisplay (
                        Type ( ASPECT_DISPLAY CAB_SIGNAL_DISPLAY )
                        Position ( 600 79 40 40 )
                        Graphic ( aws.ACE )
                )

has to be used.
This type of display has 8 states (frames), which correspond to the 8 signal aspects. The first seven frames usually show the sunflower, while the eighth hides it.

[darwins]

Hi Carlo
What is the second to last aspect?
Before you started work, I included the Sunflower in my BR steam cab view.
I copied what had been previously used for MSTS.
https://imgur.com/NkmT8pt.jpg

This was:
Top row four frames show the sunflower.
Bottom row first two frames from left show the sunflower.
Bottom row last two frames (black circles) hide the sunflower.
I am now wondering what frame 7 is and why you are saying 7+1 and I had previously had 6+2.

Thanks
Darwin

[Csantucci]

Hi Darwin,
With the AWS script the final result would be the same in the two cases.
Your 6+2 pattern lets the sunflower disappear in aspects Clear_1 and Clear_2, while a 7+1 pattern lets the sunflower disappear only in aspect Clear_2.
However, as decided within this thread, the AWS script manages Clear_1, Clear_2 and Restricting in the same way, that is in all three cases the sunflower disappears and no AWS warning is generated.
Therefore the AWS script translates all three aspects into Clear_2 and sends this back to the cabview code. Therefore for all three original aspects the cabview code will select the last frame.
I hope I was clear.

[darwins]

Csantucci, on 12 February 2020 - 02:34 AM, said:

Hi Darwin,
With the AWS script the final result would be the same in the two cases.
Your 6+2 pattern lets the sunflower disappear in aspects Clear_1 and Clear_2, while a 7+1 pattern lets the sunflower disappear only in aspect Clear_2.
However, as decided within this thread, the AWS script manages Clear_1, Clear_2 and Restricting in the same way, that is in all three cases the sunflower disappears and no AWS warning is generated.
Therefore the AWS script translates all three aspects into Clear_2 and sends this back to the cabview code. Therefore for all three original aspects the cabview code will select the last frame.
I hope I was clear.

Yes, thanks, I understand now. This means that no change is needed to existing textures. http://www.elvastower.com/forums/public/style_emoticons/default/biggrin.gif

[mrmosky]

I have had success with the new AWS feature. I have added a working AWS sunflower to my latest 3d cab (unfinished) and attached it to the Class 150.


The sunflower works fine, as does the reset button. Some screenshots below. Well done Carlo, Darwin and Coolhand, for making this happen.

Geoff

[Coolhand101]

That's a good looking cab Geoff. Looks like a Class 317?

Thanks

[mrmosky]

Coolhand101, on 13 February 2020 - 06:01 AM, said:

That's a good looking cab Geoff. Looks like a Class 317?

It is a Class 317. Well spotted! There are still some details to finish off with it, but I'm happy that the AWS will be operable at some future date, once the scripting goes into the official release.

Geoff

[Coolhand101]

Hi Carlo

I have been testing the TCS INI Vigilance and I have a couple of questions.

In the ENG vigilance section, it is possible to activate the Vigilance alarm when the train is stationary providing that the reverser is at forward or reverse. I cannot seem to duplicate this in the INI file vigilance section?

If a penalty delay is inserted into the INI vigilance section( Ie 60 secs), it appears that you have to wait until this time has passed, only then can the reset button be used to release the brakes.

I'm unsure if this could be modified to allow the time delay to commence once the reset button is used. Normally, a penalty delay for the vigilance would require a full stop, so something in this order:

1.Train stop by vigilance TCS.
2.Press reset button to start 60 second penalty countdown.
3.Brakes release after 60 seconds has expired.

I could not see a method in the INI to achieve this?

Also in the TCS AWS SMS files. I'm roughly guessing here what the triggers are for:

109 AWS bing/bell!

110 Unknown!

113 AWS Alert post vigilance ?

115 AWS Alert = Signal ?

117 Vigilance beep ?


Thanks

[Coolhand101]

Csantucci, on 09 February 2020 - 10:27 AM, said:

1. They don't have AWS if they don't have a hidden dummy distance signal

I have change my colour light repeaters( Repeater to Distance in the SigCFG ) and now the AWS recognizes the repeater signals. The actual repeater script did not need any editing.

Does the 'dummy distance signal' work with colour light signals? My next plan is to use a 2-aspect Home signal with AWS!

Thanks