Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!
I just subscribed to give the beta site a go, however cannot seem to get it to work. When putting in a station in the search bar and clicking on it, nothing happens even though the URL in the browser does change.
Am I doing something wrong?
I just subscribed to give the beta site a go, however cannot seem to get it to work. When putting in a station in the search bar and clicking on it, nothing happens even though the URL in the browser does change.
Am I doing something wrong?
This is likely to relate to not being logged in. There are also occasionally issues with caching, which can be by clearing site cookies and data. Once I'm a bit closer to getting the site deployed for all users I'll look into getting better cache-buster URLs.
I just subscribed to give the beta site a go, however cannot seem to get it to work. When putting in a station in the search bar and clicking on it, nothing happens even though the URL in the browser does change.
Am I doing something wrong?
There was an issue with the connection to Stripe which affected a couple of users this morning. I've fixed it and emailed them. If you haven't heard from me could you drop me an email so I can figure out what's going on.
There was an issue with the connection to Stripe which affected a couple of users this morning. I've fixed it and emailed them. If you haven't heard from me could you drop me an email so I can figure out what's going on.
Worth bearing in mind that if you pick a train from that list it won't live-update for the moment. I need to get websockets back in before I can get that working.
I'm interested in feedback on how the pick-by-headcode thing looks and how intuitive it is to use.
Worth bearing in mind that if you pick a train from that list it won't live-update for the moment. I need to get websockets back in before I can get that working.
I'm interested in feedback on how the pick-by-headcode thing looks and how intuitive it is to use.
The full timetable bit is actually unrelated, and I may be able to fix that today. I meant that the last report and current delay to the train doesn't update. As it stands, all updates for all trains on the map are sent through a single feed, but of course trains which aren't on the map (or which the system thinks aren't on the map) aren't updated.
Another UI question is around the last report. The previous version of the site contains last and next report as well as last and next stop, which I originally put there because I thought it would be useful, while the new version of the site just displays the last report. Would next report and last/next station information be useful, and if so would it be worth the extra space it would take up on the screen?
Another UI question is around the last report. The previous version of the site contains last and next report as well as last and next stop, which I originally put there because I thought it would be useful, while the new version of the site just displays the last report. Would next report and last/next station information be useful, and if so would it be worth the extra space it would take up on the screen?
In my opinion it is good as it is, although som idea from just the strip of next location and maybe a very basic predicted time could be a useful addition?
Apologies if I'm missing something obvious and this is a known bug, but on the beta maps it really doesn't seem to like updating the position of trains without refreshing the page regularly. If I just sit and watch it the trains remain in the berths that they were in when the map first loaded. I'm having this on desktop and mobile.
Apologies if I'm missing something obvious and this is a known bug, but on the beta maps it really doesn't seem to like updating the position of trains without refreshing the page regularly. If I just sit and watch it the trains remain in the berths that they were in when the map first loaded. I'm having this on desktop and mobile.
I have some really bad experiences on dodgy connections (such as on a train!!).
Unlike the old site, there's seemingly no prompt when it "disconnects" (though, as takno says there's no websockets yet, so that may be why) which means you don't really find out if you're disconnected or not.
I've also had issues where I get no services showing (and no indication that the data is actually loading) as well as sometimes service showing, but all the describers are just ????.
Apologies if I'm missing something obvious and this is a known bug, but on the beta maps it really doesn't seem to like updating the position of trains without refreshing the page regularly. If I just sit and watch it the trains remain in the berths that they were in when the map first loaded. I'm having this on desktop and mobile.
Connections are a bit on the flaky side at the minute, and as MrJeeves say it doesn't attempt to reconnect yet. Getting close to that being next on the list!
Thank you both! I shall continue to play with it and if I have other, hopefully, constructive feedback shall mention it (though it won't be anything like as detailed as what some provide!).
I noticed some strange behaviour at Barnham today. The old site showed the route being set from platform 2 towards Bognor and the signal cleared (this also matched what the signal was saying, and the way the train went), but the new site suggested the route was set for straight on, and the signal was still red. I did refresh the page just before taking the screenshots to try and rule out connection issues.
I noticed some strange behaviour at Barnham today. The old site showed the route being set from platform 2 towards Bognor and the signal cleared (this also matched what the signal was saying, and the way the train went), but the new site suggested the route was set for straight on, and the signal was still red. I did refresh the page just before taking the screenshots to try and rule out connection issues.
I did get a new mapping for Burnham, but I'm not sure it's as good as the old one. I might just switch it back. Ultimately I should be able to write something which spots bad routes like this, but it's not high on the priority list
The beta version of the site is now updated to use websockets. That seems to make the connection a lot more reliable rather than giving up after a few minutes.
You may need to do a hard reset (Ctrl-Shift-R) or delete site settings to get the new code running.
There's still some more to do in terms of detecting when the connection does go down, but it's better than it was, and hopefully I can go back to doing features that are actually visible for a week or two!
Today's update, since it's automerged:
== Doublepost prevention - post automatically merged: ==
I've added basic timetable search to the beta site - if you type "EDB KGX" (or for that matter "Kings cr Edin") into the search bar, it should fetch the whole current day's timetable of direct trains.
As every you may need to do a hard reset or delete site settings to get it running (promise I'll look at that issue soon)
This clearly still needs a bunch more work. That's likely to include being able to pick a date, integrating live running when it's the current day, being able to view more detailed information on each train.
It is pleasantly fast though, and I like the ability to pin a few timetables to the screen and have them to hand as you view the map.
As ever, feedback welcome, including whether this is a feature you'd use/value - I'm aware that the info is already available with more detail on RTT, so it's really a case of whether having it there on the map is useful
I'm also interested to know if offline timetable searches would be useful (possibly as a premium feature) - the underlying store on the server of all current and future trains is about 8mb and daily updates are typically less than 100k, so it's definitely possible to implement. It's just questionable how many places are genuinely offline anymore...
Bit of a funny one: the little lighting icon button (Not sure what it does ahaha) increases in width periodically until it takes up the entire top of the screen is taken up and the search bar has been totally displaced.
I've removed the duplication on this (it was there because it's the fringe between Piccadilly and Preston boxes, and the data has to be filtered to work properly on a map). I've also fixed the mapping so that it should always represent the correct train.
Just following up on this again - the Blackburn bound service remains in the Bromley Cross section after it has cleared it. The screenshot here shows a service (2B81) which is actually approaching Blackburn.
Bit of a funny one: the little lighting icon button (Not sure what it does ahaha) increases in width periodically until it takes up the entire top of the screen is taken up and the search bar has been totally displaced.
The lightning button lets you disconnect and more importantly reconnect. It's not really the right icon but I couldn't decide on anything better. There's definitely something weird with the sizing - doesn't work as I'd expect cross browser
== Doublepost prevention - post automatically merged: ==
Couple of small beta changes today:
- Departure time in the schedules is now correct, rather than just being the arrival time repeated
- Many line codes can now be clicked to see the full line name
- The connection button is now more sensible-looking
- The "Show on Map" button on schedules now works (as long as the train is on the current map)
- Autocomplete options for timetables are now restricted to stations, so typing "Edinburgh YRK" will now only have one autocomplete result
- Autocomplete options are a bit bigger and more clickable on mobile
- The next scheduled train is highlighted on timetables
I'm planning to look at updating next week, but in the meantime you might need to visit https://trasky.uk/live and/or clear cookies to get the new version running
I've also (just) deployed an improvement to the server, so that headcodes like 1S09 and 2F03 won't be turned into 1S90 and 2F30, which could be handy, as well as another change which should mean more headcodes are mapped to their schedules. Quite a productive weekend!
I've also (just) deployed an improvement to the server, so that headcodes like 1S09 and 2F03 won't be turned into 1S90 and 2F30, which could be handy, as well as another change which should mean more headcodes are mapped to their schedules.
A recent release to the main site should reduce the instances of the weird problem with the map button being greyed out. If you are experiencing this it's worth going to https://traksy.uk/live and hitting refresh a couple of times once it's loaded. It's also worth doing this if you are using the beta site, since it should stop the main site from interfering with the beta site.
Another release this evening brings a few new features to the beta site (https://traksy.uk/new):
Timetables for all trains at a station - just click on a station name on the map, or type the station name and selection "Station info for xxxx" in the search box. As with the journey lookups, this provides the entire day in one go, and future dates can be selected from the date selector.
There is a + button next to your login details in the top right. This will open up a list of add-ons you can enable on the platform, including:
Option to include a link to RealTimeTrains on schedule pages. This allows quick access to their Know Your Train feature for people who are interested in unit numbers.
Option to view ORR usage stats. If enabled, you will be able to see these easily on station info pages. They should soon also be available when you look up journeys
A less washed-out colour-scheme if you are in light mode (feedback welcome - I'm not a light mode person, and I struggle with what looks reasonable there)
Various layout stability improvements
The beta is still subscriber-only at the moment, although I'm hoping to open it up to other users in around a month. Newer features such as the RTT links, ORR stats, and timetables are likely to stay subscriber-only (with perhaps a small daily allocation for non-subscribers).
I'm still fighting against the idea of ads on the site, but if subscriber numbers don't pick up a bit I may not have much choice. If that did happen, suscribers would of course have an ad-free experience.
I'm still fighting against the idea of ads on the site, but if subscriber numbers don't pick up a bit I may not have much choice. If that did happen, suscribers would of course have an ad-free experience.
I think there's a big difference between ads that aren't intrusive and those that are, along with how useful you find a site.
RTT's ads are on the edge for me simply because their ad network often serves ads that "escape" their container or really quite distracting animated ones.
As long as Traksy isn't running ads like Reach plc, I don't think it'll be an issue in reality.
I suppose adblockers would be a concern, but I'd be interested in whether more traffic is desktop/mobile. On mobile, of course, you're much less likely to see users using adblockers.
We are aware of an issue with emails from the Forum to Microsoft-based email accounts (hotmail/outlook/live.com email addresses). This is being looked into currently, thanks for your patience meanwhile.