Anyone else still having problems with the AWS on London - Brighton? I've been away from this route for a while and was caught out again after passing a signal at caution but the AWS not alerting me (so I failed to press the button). I know this was mentioned by quite a few people after the route came out, and was hoping it may have been patched by now.
Saw a response on another post that this is a sound trigger issue rather than an AWS config issue, so may not be fixable without some serious jigging around of "sound importance"
