London commuter class 377 has a problem with the AWS alarm sound. I have noticed the alarm sound does not work in some busy areas on the route at random. Gary
Just drove 1M09 and noted this also in the 387 as I approached London with several clear signals. Otherwise the AWS worked as expected.
I think the 387 may also have the same issue intermittently along the route. The AWS sunflower appears but no sounding alarm which does not seem right to me. The vigilance alarm is also very quiet and have missed it a couple of times resulting in an e-brake
I'm having the same issue with the 377. AWS will not sound when approaching adverse signals, but the system is working as it should. It wants an acknowledgement, and if it doesn't get one it stops the train. It just seems to be an issue with the sound. I did a morning London to Reigate service twice and it happened in the same places both times.
Same here, also signal VC589 coming into Clapham Junction no AWS sound but comes on so could miss it potentially.
Does anyone know if it's the same signals causing the problem all the time? Or does it depend on the service you're running. I haven't had much time to experiment this week
Can anyone also confirm the speed limiter doesn't work very well? I shut power to 0, set speed limiter, and the train just slowed to a stop bizarrely
You need to have power on the unit and then press the speed set button and then adjust the speed. You can't set the speed with no throttle on.
This problem might be new and quite bigger as I've today experienced it on the NEC route with ATC/ACSES on ACS-64 lighting up to be acknowledged, but letting out no sound.
There's a few signals this happens with. Reproduce it and reply on the main thread and add your voice.
I can confirm, the cruise control does not work. When you set the speed, the orange pointer remains at zero. For example, if you set the speed to 30mph and activate cruise control, the 377 will slow down to zero instead of accelerating to 30mph.
I believe a little like the 465 you also have to be in full throttle (step 4) for it to work - so step 4, speed select on - select the speed
I know, but if the orange pointer stays at zero, the 377 also wants to go back to zero as soon as you activate cruise control while in Notch 4.
Regarding AWS/TPWS it should be pointed out that in the 387 it should speak to you when the cab is activated and in the event of it going off on route.
It does that for me, when setting up the cab. I’ve never had an activation en route with the 387 so I can’t comment on that.
yes I just noticed the startup one (I suspect the volume is too low) not sure about activations. I’ll just have to drive a 387 through Clapham where all the silent magnets are!!
It does work, but there seems to be a bug (or maybe that is prototypical?) that when you change the set speed while it is not active, the needle will remain at 0 when you activate it. So when you use it, activate it and then set the speed. Or set the speed one notch below your desire, activate it, and then up it one notch to the desired speed, then the needle will jump up to the correct speed and it should work fine
Just after starting service 2B23 (north of Selkirk) there seems to be a hot magnet warning you about a speed reduction (to 40 mph) that never makes the class 377/4 play the warning sound for me. Especially deceiving since it is at about the time the sunflower would turn black after the starting program anyway.
I can see this is an old thread, just wondering if there was any solution to the silent AWS/Vigilance alarm. I've just got off a 377 service and noticed this problem myself.
It's not a single problem, but a problem with individual signals which are likely incorrectly mapped. Unfortunately this may not be under Adam's remit so may need a more "escalated fix"
That was a mod I made. Regarding the silent AWS issue, it’s caused by sounds cutting out, due to the severely limited amount of sound channels TSW can offer. It seems like the priority of the AWS sound hasn’t been set high enough, which means other sounds are taking its ‘slot’ Unfortunately, but unsurprisingly, there is no fix in sight, nor any mention of the issue even existing by DTG.
Speed control on the 377 doesn't work like AFB. You can only set speed when it's activated, and you can only activate it with positive throttle on. This means that when you first start out, there will be a momentary "hitch" as you activate it with the speed at the default setting of 0, since the system wants to slow the train down to nothing. So be prepared to activate and increase quickly; it's easier at low speeds. The good news is that once you've set it, it remembers the setting the next time you activate it. That is, so long as you don't make the mistake of fiddling with it when the train is stopped; that resets it to 0. (I don't know if that's prototypical or a bug)
Omsi had a slider for the amount of sounds, it went up to 1000 I think. With 600 even the most complex busses had everything working. But omsi didn't have to deal with consoles and their limits...
Has anyone submitted a bug report about the AWS sound being intermittent in busy areas (just in case they don't read any of the several threads about this problem on these forums ) It is annoying. It happened to me again the other day after being away from the route for some months. I was hoping it had maybe been patched, but alas.............................
It really doesn't matter what someone says. In this case the game engine only has that many channels. If you want more than 32 sounds playing at the same time then it won't be enough. If they're mixed badly so you end up with dead channels then it won't be enough.