When you are acknowledging the AWS warning horn at a yellow/red signal with the circle button you don't hear the AWS acknowledge button click sound? Just double checking as this is the test I just did and there is the button click sound and the button moves on my console at least.
I will have to check it again. And record it. I think what I hear is the pedal and the button at the same time. Which shouldn't be.
The pedal and button are both activated when pressing the circle in the above situation. So you will be hearing those 2 sounds at the same time.
I am just wondering why though they are both activated as unless the dsd and vigilance is going off you don't need to press the pedal. Just it's not prototypical I don't think of real world practices. Granted you would always keep your foot on the pedal but still. Doesn't make me less like it..just it's not like the real world.
Most likely he meant that pressing Q produces AWS and DSD acknowledgement at the same time, whereas they are different signaling systems. It turns out that there are 2 ways out: to press them not in the interface, but directly in the driver's cabin, or to set separate hotkeys, but I have not checked if there is such a possibility.
Yes that's what I meant. I should have clarified. Because they are assigned to the same button on my ps5 is why they both go off together. It's a bit annoying
That has indeed always been an issue on ECW: it looks like the AWS and Vigilance systems are both responding to the vigilance keybinding. I've never managed to get AWS to only respond to the AWS key being pressed (Steam - PC version). So this is not only a console issue.
Been playing ECML on and off the last couple of evenings, yes even enjoying the Azuma which does seem to have received a slight sound buff. And I have to say, despite all the critical feedback at the time, DTG or whoever built this route did a far better job with this TSW4 UK launch route than this year’s WCMLS. Not least the long, long run particularly when you get a non or limited stop service it really feels like a proper route where the Azuma can stretch its legs. Unlike Eus to MKC for the Pendolino. With hindsight I really do feel DTG should have ensured WCMLS at least went to Rugby.
Still getting flickering accelerometer thingy even with no power applied. Used to give great indication of if accelerating or decelerating but no more
Any update on the 801 door sounds.............? Such a minor thing that would take so little time to fix, yet so annoying.
Yesterday I noticed that when running BR Class 801 using hotkeys, it is impossible to properly enable AWS+TPWS. During initialisation, AWS is in the ON position and TPWS is in OFF. When I press Ctrl+Enter they change their positions, AWS is off and TPWS is on. With DSD there is no such problem and it is switched on correctly by pressing Shift+Enter. I know that 801 has many safety systems, maybe I don't understand something? On the other trains AWS & TPWS work together, and the Class 801 startup manual says to turn both on. Of course I can run everything manually, but that's what hotkeys are for, to make it easier, right?
Why is it stopping me? I didn't go through any stop signs. In the next attempt, when I pressed SPAD, everything was successful and the automatic stop did not work. I uploaded the video to MEGA, check it out from ~0:50: https://mega.nz/file/t6oCAKpY#v1CMTCF84vmQW2ENSl664uj3A2knw1Ip4bScBGjpX0E
Why does the PIS tell me the next train calls at Peterborough and London Kings Cross when I'm at Peterborough already? It shouldn't, instead it should list calling points after Peterborough. This is an issue at every station on this route a service ends.
Saw this online. Some small changes could be made to the TMS to make it a lot more realistic. Also been having a few issues with the head code showing. When driving 1D25 the other day, the TMS showed various head codes throughout the journey including 1D31, 1D29, 1D03, 1D02.
The TMS is buggy as heck. DTG don't care though. They have left it so long, they hope everyone has just forgotten about the bugs.
Of azuma. Also that damn speedo and tms screen. Keeps going off. I have a feeling it's due to the pointer thing
Azuma TMS Bug Played on E2G 1E11 Next station stop, Berwick-upon-Tweed sticks out of screen such that the d is not visible and the 9 cars is covered.
Had this happen to me but I dare not touch the screen as it will then turn off. Must have reported this issue a lot of times lol. It's immersion breaking.
Playing on ps5. On class 66. This has happened everytime but basically when I switch the weather preset in photo mode it gets rid of the weather I had selected! So it goes from fog to being clear in an instance! Happens on other routes too
Also it said with patch notes the cab would be lighter at night? Seeing no difference whatsoever. Still have to use the torch to find or stumble my way round in the cab.
Think this is a known bug. Read something in a recent patch note about something related to this, but maybe still an ongoing fix. I interpreted it as saying interior would now have correct lighting. A walk through a class 801 at night now allows you to see passengers rather than them being shadows.
Ah okay. I thought it had said the cab lights up at night lol. I think I reported elsewhere about the hair of the pax going luminous almost. This was post update. Very strange. That needs looking into also. Very odd also why when I touch tms screen and speedo screen it goes black. Think it's to do with the cursor feature or something.
Are you on PC? Just wondering as you mentioned cursor. Any mods perhaps? No clue myself with this kind of thing, as I'm PS5.
I am on ps5 yes. What I meant was the thing they implemented for tsw5 where you can interact with screens now. It doesn't like it when you go into that view on some trains like the azuma for example. You can hardly interact with anything at all now. You used to but not now. Also they need to sort out that accelerometer. It's the suspension causing problems. Even with no power applied the bar (orange or blue) bounces around. I attribute this to the suspension. Isn't present on older routes with no suspension..hence on can't accurately judge if going to speed up or down. I have recorded it before but hope we get a fix..I fear also this will be appearing on other routes with suspension also. It really bugs me. Hope that clarifies things? I am not the best at explaining in a coherent manner at times.
The screen feature hasn't worked well for me. I don't know how it could be properly implemented tbh, and can see why it was done, but I've deactivated it. Yes, noticed this. I had it on E2G today on the 801, but as you say not observed it on other locos. Worth attaching the video here so the devs can see - or sending in a ticket, That does explain things - it's clear so don't worry
I have done the ticket thing many a times. They say all the time the same things unfortunately. I guess it's not a priority. I will attach the screen thing now. I uploaded it to my YouTube.
Looks like you are changing power, although I agree the fluctuations up and down are odd. What I had on E2G was even weirder, it just changed by itself when going over track joints etc. despite PBC being off
It was hard to crop but you can see the flickering quite a bit can't you? I may record some more. It has got the quality capped at 480p which awfully doesn't help.
I believe I didn't capture also it being in neutral. I can't remember what I was doing with the power setting when capturing this video but it could be that what you are seeing is simply that flickering make you think I am applying power. I will try and record more. I hope they get this logged. It's bugging me a bit.
I can see the flickering - it certainly shouldn't be doing that AFAIK. What I was saying is I've also had it at times with the PBC off, I.e. just flicking above and below the (effectively) x=0.
To clarify, I meant I had it with the PBC off - i.e. no braking force, no tractive force - not with the reverser in neutral. I've never put the reverser to neutral while running a train before, so don't know what effect that'd have.
On the 801, not 385. I had it on the 801 on E2G in the new sprinter timetable. Not timetable linked, likely loco liked
Yes. So it will be probably the same issues I am having. Like I said I do awfully worry it will seep it's way on other trains with suspension. Seems to only affect suspension trains. Before, when it wasn't tsw5 and 4, it was fine. Albeit back then we still had the dark speedometer screen. At least I did.
I think I might send a ticket about this all as it's annoying me. I wonder if it's on the other routes that have been released which have suspension.
Passenger not boarding Bakerloo line London Underground train on the west coast mainline ( all service , created a ticket and got a generic reply saying thanks for logging, ticket has now been closed
