ValleyLines142
Established Member
All showing now.There are no allocations for GWR in TOPS either at the moment, maybe they are still having issues with the problems over the weekend
All showing now.There are no allocations for GWR in TOPS either at the moment, maybe they are still having issues with the problems over the weekend
Can you email support please with more details about your browser, OS and versions please. There's something we're looking into that causes the bottom ad unit to come up with the keyboard on some devices and not on others (gets hidden underneath the keyboard).The search button is mostly visible, but still slightly covered. But this is much better than before.
Email sent to feedback@ email addressCan you email support please with more details about your browser, OS and versions please.
Just done a Maidenhead stopping at Slough for 'now' - all trains in the right direction come up. Add 'passenger calls' and you get all those in the right direction. Did the same for tomorrow - all fine. A search restriction exists for trying the same for more than 24 hours in the past.There is a bug I noticed that I have been meaning to post on here and email support about for awhile, and I wondered if anybody else experiences it.
Basically, if you ask for trains at A, with a subsequent stop at B, it also shows trains that have previously stopped at B, provided that they pass through (and don’t stop at) A. In other words, it shows trains going the wrong direction if they are non stop at A. This is in addition to the correct trains you’d expect.
For example, if you request Maidenhead with a subsequent stop at Slough, it also shows all the Oxford/Cotswold bound trains. If you request Didcot with a subsequent stop at Reading, it shows all the nonstop South Wales bound trains. If requesting Stevenage, with a subsequent stop at Peterborough, it shows all non stop trains from the north that have called at Peterborough.
I know about the restriction for more than 24 hours ago, and it definitely wasn’t that. It must just be for me then.Just done a Maidenhead stopping at Slough for 'now' - all trains in the right direction come up. Add 'passenger calls' and you get all those in the right direction. Did the same for tomorrow - all fine. A search restriction exists for trying the same for more than 24 hours in the past.
As per Wychwood93's reply, you need to select 'passenger calls' from the [Service Type] dropdown menu...I know about the restriction for more than 24 hours ago, and it definitely wasn’t that. It must just be for me then.
I’ve uploaded a screenshot so you can see what I mean.
Yes that does stop those services from appearing, but it nonetheless seems inaccurate to show services that have previously stopped at a station when requesting those subsequently stopping there, whether or not they pass/stop at the “current” station. Thus I assumed it was a bug, but maybe it‘s just a deliberate quirk.As per Wychwood93's reply, you need to select 'passenger calls' from the [Service Type] dropdown menu...
MARK
I think it's a bug, and the cause appears to be that if the train doesn't stop at the current station then the current station is incorrectly believed to first in the running order of the train - maybe the code is meant to look up the position of the current station in the running order but incorrectly concludes it to be the first position, which is then used in comparing with the position of the filtering point.Yes that does stop those services from appearing, but it nonetheless seems inaccurate to show services that have previously stopped at a station when requesting those subsequently stopping there, whether or not they pass/stop at the “current” station. Thus I assumed it was a bug, but maybe it‘s just a deliberate quirk.
Sorry if this has already been mentioned further up but whatever happened to the RTT app?
I think also 'duplication' of work came into it which meant Tom could more time on the main site. I am sure Tom may confirm in due course.
Even Network Rail is advertising dev roles with less than £40k salary! Looking at the market £35k is the norm of a mid-level developer outside London.2) Costs of people
The other complication is that software people aren't cheap right now. Advertise a job with a salary less than £70k, and you aren't going to get many applications. Good app programmers expect even more pay. Day rates of £600 are not unusual. It is also really hard to take junior people into a small team. A good developer can be 100 times more effective than a mediocre developer.
The apps were removed in late 2017 when there were a number of issues in my personal life and I was seriously considering selling off RTT to one of my customers (and a level of negotiations did occur at that time). They were quite dated even then and needed a considerable amount of maintenance on both sides. Fortunately for me now I snapped somewhat out of that and took 2018 largely out for my own benefit and 2019 obviously saw the new version of RTT and what we have now.It was done away with as found un-necessary as today's mobile phones all have internet access via the browser along with the App had limited facilities too compared with main site. I think also 'duplication' of work came into it which meant Tom could more time on the main site. I am sure Tom may confirm in due course.
I agree. The quality and level of innovation is amazing for a website run by such a small team.I am amazed at what you have been able to do with so little to be honest.
Very likely. The class of EMU is stored in the same field as the trailing load, so it will have been put in as a traction type of E rather than EMUhttps://www.realtimetrains.co.uk/service/gb-nr:W37443/2022-11-22/detailed apparently, the 22/11/22's Northern 1N56 1046 Manchester Airport to Blackpool North is pathed as an "electric locomotive, trailing load 331 tonnes" and planned for 100mph max. Is this an error of Class 331 EMU?
https://www.realtimetrains.co.uk/service/gb-nr:W37443/2022-11-22/detailed apparently, the 22/11/22's Northern 1N56 1046 Manchester Airport to Blackpool North is pathed as an "electric locomotive, trailing load 331 tonnes" and planned for 100mph max. Is this an error of Class 331 EMU?
All services planned to be a 331 use that timing load.
the 325s which work Royal Mail services are the same:
Realtime Trains | 1M44 1620 Shieldmuir Mail Terminal to Warrington Royal Mail(Dbs) | 11/11/2022
Real-time train running information for 1M44 1620 departure from Shieldmuir Mail Terminal to Warrington Royal Mail(Dbs) on 11/11/2022. From Realtime Trains, an independent source of train running info for Great Britain.www.realtimetrains.co.uk
As is always the case, this is because it is just a timing load rather than an allocation.
MARK
Hi there, do any of you guys know how to fix this bug where the train appears like this:
Also this only happens with Northern 319's, 769's and 323's.
Likewise I’ve seen the occasional post asking why some London - Edinburgh services are still timed under the class 91 timing load of ‘Electric Locomotive, trailing load 410 tonnes’Indeed. You get the occasional post asking Tom (the creator) why some services are still timed as Pacers in the Valleys and on Northern.
It's a data feed bug, nothing you can do about it.Hi there, do any of you guys know how to fix this bug where the train appears like this:
Also this only happens with Northern 319's, 769's and 323's.
Thanks for that, I was just wondering if it was perhaps an issue with my browser or my device, glad too hear it's not!It's a data feed bug, nothing you can do about it.
Yep... all that's happening is the data feed is providing the vehicle numbers in number order.Thanks for that, I was just wondering if it was perhaps an issue with my browser or my device, glad too hear it's not!
To be fair, I don't think that's strictly true. You are never going to have a non-driving carriage as the first or last coach of a unit, and even then, it is really quite rare for the coaches in units to be swapped around nowadays.It's a data feed bug, nothing you can do about it.