|
Post by Jimi on Jul 23, 2020 19:15:23 GMT
UPDATE TO THE ABOVE:
OK, I see the issue and I'm certain we have seen this before in another scenario. Signal A584c (SBK WB home) is red for no good reason. There's no train in the section ahead. Likewise WK50b (TGN WB home) is red for no good reason. The issue is there are 2 trains which each start in a platform (TGN and SBK). We don't know WHY this causes an issue with these specific platform WB home signals, only that is DOES. If we move the trains to a position in rear of the platforms and let them start it causes all the signals to operate correctly. The respective home signals with go red as the train passes into the platform, and will clear once it clears the starters and platform track section. I've just made edits to move the trains and will now re-test. Specific moves were: AI train D78-SBK-RMD7-WKN2 moved back to in rear of signal A584a (was in TGN1 in advance of A584c) AI train D78-TGN-EBY9-ACT4 moved back in rear of signal WK50a (was in SBK1 in advance of WK50b) More news once I've re-tested...
MORE UPDATE:
OK, it's fixed and I just need Ed to upload it to his DropBox so you can get it. If you feel comfortable editing a scenario, and moving a train, you can replicate my fix as described above. Make sure you click on the radio button marked "Consist Select" on the bottom-left of the editor screen. You can then click/drag the whole train in one go. Travel from ECMDT to TGN and move that train to in rear of A584a. Then continue to SBK and move that train to in rear of WK50a. Save and then quit when the scenario starts. Then re-run (or ESC, restart). Running directly from the editor after a save is not recommended as it may not fully init the scenario.
I'm currently saved at TGN with left RI showing for the RMD road. I'll continue this evening and make sure the rest runs OK - but I'm 99% certain its now fixed.
|
|
|
Post by Eddie on Jul 24, 2020 16:51:37 GMT
The fix for that scenario is here on my dropbox. Download it and copy it across to your TS/ Content/ Routes/ d59cee1....../ Scenarios folder, overwriting the files. Please let us know if this fixes the issue. Or not. Many thanks for the bug report. www.dropbox.com/sh/waucrlpew1h0oi2/AABotoflxMpA1lx5341kfBo9a?dl=0All these hot fixes will get compiled into a new installer when we extend the route eastwards. Please accept apologies for not issuing multiple hot patches as a separate update on the BDTS site as it just gets confusing for everyone.
|
|
|
Post by Jimi on Jul 26, 2020 14:34:05 GMT
Quick request: Would anyone who had issues with the "2nd Half Timetabled" scenario please grab the fix per Ed's post above and let us know that it works for you? Whenever you get a chance - thanks!
|
|
pops
Station Staff
Posts: 15
|
Post by pops on Jul 28, 2020 13:56:27 GMT
I've just rerun the revised scenario without any problems. I did have to TAB (well Ctrl/TAB when I remembered!) past the signal just outside Richmond, and also TAB past the signal at Gunnersbury.
Tim
|
|
|
Post by Jimi on Jul 28, 2020 16:28:40 GMT
Thanks Tim! That scenario was written years ago and in the time since we've figured how to avoid those signal lockups. Ed & I were chatting recently about some new scenarios we intend to create once Phase III (Lower Circle) is complete; and I opined I'd like to do at least one fully timetabled one. So we will do some remove/replace on some of the scenarios, as the new tracks will allow yet more paths. DR from GRD to WHI, via MAN TOH ALD-E. And mixed-in Circle traffic to/from ALD. So we will then be able to simulate a DR from WHI WB getting held at signal OB31 waiting for an Outer Circle ex-ALD to clear Minories Jct. I'm told that happens periodically :-)
Expect us to post news about Phase III progress shortly. We've been busy.
|
|
pops
Station Staff
Posts: 15
|
Post by pops on Jul 29, 2020 9:35:37 GMT
Very much looking forward to Phase III
|
|
|
Post by AlexTheMole on Jul 29, 2020 19:22:45 GMT
Phase III news you say? Ooooooh me likey!
|
|
|
Post by Eddie on Jul 31, 2020 11:13:03 GMT
A very brief update. I finished tracklaying to Whitechapel this week and Jimi is now editing the track properties, electrification, direction, speed boards and so on. This will be a lengthy process as there is miles of new track from South Kensington all the way through the West End and City to the East End. He will no doubt update you in more detail as he progresses.
|
|
jmm
Station Staff
Posts: 21
|
Post by jmm on Jul 31, 2020 11:16:35 GMT
Which layout does Whitechapel have? The current 2-platform one or the former 4-platform one? Thanks!
|
|
|
Post by Eddie on Jul 31, 2020 11:26:51 GMT
The older 4 platform layout.
|
|
|
Post by AlexTheMole on Jul 31, 2020 14:50:32 GMT
Fantastic, I cannot wait for Phase III!
|
|
|
Post by Jimi on Aug 1, 2020 22:34:25 GMT
We made a deliberate decision to go with the older layout on a number of stations,including Whitechapel (4 pfm) and Mansion House (retained the bay pfm). We have stocks covering a wide time period and this decision allows us to replicate older scenarios and layouts with suitably older stocks. We have made sure, however, that all platforms are of suitable length to handle all the differing trains.
Another item I'll be addressing as part of my usual job is the signaling. This will include using all the new JT Met tunnel sigs where appropriate, PLUS replacing all the current signals with tunnel types where required across the whole route (a few handfuls twixt ECT and EBY plus the Upper Circle). Our sincere thanks to JT for creating a very comprehensive LUL signals set. This will NOT change any pre-reqs as the Met was already one when we released v2.1, in part to allow this improvement. Phase III is the logical time to deploy it.
|
|
pops
Station Staff
Posts: 15
|
Post by pops on Aug 4, 2020 14:43:29 GMT
I seem to have a signalling problem Westbound outside Hammersmith station. There's a train in front of me at platform 1, and consequently signal WD39 is showing red. However, when I approach, the preceding signal (WD40C) is showing green. Consequently I run into the train at platform 1 - oops! Shouldn't signal WD40C be showing a Yellow, so I have time to stop? Here's a screenshot (I hope) postimg.cc/0rQRD5BkTim
|
|
|
Post by Jimi on Aug 4, 2020 22:56:26 GMT
WD40C is correctly showing green as there's a clear section ahead of it to WD39. What it ISN'T doing is acting like the multi-home it should be as we can't simulate those. Signals having an alphabetic suffix (A/B/C/etc) shouldn't clear until the train ahead starts to leave the platform, with the "C" signal clearing once the train ahead has passed the starter and the platform is clear. In other similar cases (between RPK and CPK for example) I've added a repeater to the "C" signal so you can at least see warning of an upcoming red home signal from sufficient distance to react. And route knowledge will tell you that it's possible the home signal is red :-)
As part of my current signals upgrade for Phase III (in progress) I have now added a repeater head to that signal (and similar for the fast road signal alongside) so you will see a yellow and have a better chance of being alerted to a possible red home signal. I wish we could realistically simulate multi-homes, but it's not easy.
|
|
pops
Station Staff
Posts: 15
|
Post by pops on Aug 5, 2020 8:45:27 GMT
Many thanks Jimi
|
|
|
Post by Jimi on Aug 5, 2020 11:29:38 GMT
I did manage to implement a prototype of multi-home signals in the Microsoft simulator a long time ago. As part of designing that, I ended up in a discussion with TubePrune (Piers Connor) on the DD forum back in November 2007 - have we *really* been doing this stuff that long? For those curious as to how multi-homes are supposed to work I refer you to Piers' excellent description, authored as part of a broader set of notes on LUL signals.
|
|
|
Post by Eddie on Aug 8, 2020 16:51:35 GMT
It will be interesting to see if multi-home signalling is employed on the new TSW2 Bakerloo Line. Through the West End it would be widely expected to be in use to maximise throughput of services particularly during rush hour. This is the sort of flesh DTG need to put on the bones of this route. Will it all be just eye candy ?
|
|
|
Post by madnessracer14 on Aug 17, 2020 10:44:48 GMT
Hi there, i finally got the chance to replay scenario 'second half phase 2 timetabled D78 AI' this morning. The good news is that I saved the game at Ravenscourt park instead of SBK. quit and then resumed. and yes it did clear both the start signals for SBK and Turnham Green on the ECT to RMD leg.
then on the RMD back to ECT leg, the start signal (GB8) at Gunnersbury did the same and stuck on Red, so I saved the game again there, quit and resumed, that also cleared this signal.
and finally on the return to the depot form Ealing Broadway. the shunt signal at WM5 signal on Ealing common platform 2 in to the Yard west entrance. that was also stuck at red, so i tried the same trick again, save, quit and resume from that point. once again, it worked and cleared the shunt disc allowing me into the Yard. that scenario is now complete and on time, Just!
The briefing wasn't kidding when it said tight timetable, 1 min between most stations yet 10 mins in timetable for RMD to Kew Gardens. great fun trying to keep time though.
|
|
|
Post by Jimi on Aug 17, 2020 11:52:40 GMT
Thanks for taking the time to let us know and congratulations on your success! That is not an easy scenario. There are a few unusually lengthy stops on the RMD road that I don't understand. When I built it, I allowed the dispatcher to determine the times and then checked the "timetabled" flag on each task. This ensures that the player should be able to make the times. However, the dispatcher seems to feel it takes much longer then actual to drive certain legs - TGB-GUN is one IIRC, and the RMD-KEW as you note. Which leaves you yawning at a starter with the doors open for several minutes. One possible clue is the inclusion of slow speed limits in parts of the task path, and I suspect the dispatcher has issues calculating path times within those sections. Or maybe the calculation is simplified to allow for the slowest section (15mph) and applies it for more distance than is actual. Else how do we explain the "several minutes too long" ETDs when most of the scenario is indeed quite tight and well calculated?
Again - our congratulations! That scenario was created a long time ago, and I will be creating at least one more fully timetabled one for Phase III. Hopefully I will also find a way to work around the dispatcher's idiosyncrasies.
|
|
gcr
Station Staff
Posts: 2
|
Post by gcr on Aug 17, 2020 20:23:03 GMT
Hello,
Thankyou for an excellent add-on for TS2020. I think it's great. I had a question with one of the scenarios, though, and I hope someone can help.
All scenarios - including the additional ones from ATS - work fine except for the "Easy Does It TO53 - GRD-EBY. When I load it, I can see it's loaded but there's an error that says "Driver 'Service 1' at Lat 51.49473 Long -0.18448 - Can't find destination - Platform 51"
The only option is to exit or load the scenario editor - which I am reluctant to do because I dont' really know what I am doing :-)
I cleared the local cache, verified the integrity of the game files, reinstalled the Virtual District Line - but the problem is still there. I am pretty certain that I have all of the required add-ons because I bought what I didn't already have - but this kind of error in the workshop normally means I am missing something.
Any ideas on what could be the problem here ? Many thanks.
|
|
|
Post by Jimi on Aug 17, 2020 22:14:22 GMT
This has been fixed and is available from Ed's DropBox. Please read back a few pages and you'll see the related discussion and download location. I think we have issued updates to 3 scenarios in total, all noted in prior pages.
If you can't find what you need or are not sure how to replace a scenario folder, etc. please yell and we'll talk you through it. EDIT: To save you reading back here's a repeat of the relevant info. Still worth a read back as there's more info and yet another scenario fix discussed and available. But the info below will get "easy Does It" running for you.
-------------------------------------------------------------------------------------------- Thanks for the bug report, as Jimi has said somehow the 2.2 kit build stopped this scenario working. During the small fix needed he also found the Heritage Railtour with the Standard Stock scenario folder was somehow buried inside the Easy Does It folder. So there are two fixes bundled here into a 7zip file. In the zip you will find 2 scenario folders: f609882b-... = Easy Does It ff8a1b63-... = Std Stock heritage Tour
Download the 7zip file from the DropBox (link below) and unzip the folders/files into your <TS>/Content/Routes/df59cee1-........./Scenarios folder overwriting existing files. We're hosting this on Ed's DropBox until we can build a new hot patch and new installers. Note this fix has now been deleted and replaced with a newer update that fixes another bug in the scenario. See the note 2 posts down.
|
|
gcr
Station Staff
Posts: 2
|
Post by gcr on Aug 18, 2020 1:37:27 GMT
Thank you very much. I downloaded the fix and applied it - and it worked perfectly and I just completed the scenario. Many thanks.
|
|
|
Post by Jimi on Dec 4, 2020 17:00:59 GMT
As an update to the above, Kev made us aware there was still a bug in the "Easy Does It" scenario which was using a single S8 AI train (Service 14), where this should have been an S7+1. We have now fixed that error and created a revised scenario and uploaded it. Please grab the fixed scenario (and/or the Std Stock Heritage Tour if you do not yet have it) from this new DropBox location:
In that DropBox you will find a ReadMe txt file, plus 2 scenario folders. These folders should be copied into your VDL Route scenarios folder as noted in the ReadMe.
|
|
|
Post by kymriskadraken on Dec 5, 2020 17:57:11 GMT
Fix worked perfectly. Thanks for the rapid solution.
Kev
|
|
|
Post by Eddie on Dec 5, 2020 18:13:39 GMT
Thanks for posting the result Kev. Glad the fix worked , but sorry you had to apply it.............
|
|