I am thoroughly looking forward to making a District Line 2018 Rush Hour scenario pack, having done one for the Met, the District one so far is more interesting!
I've only just started on it with teo scenarios, I haven't used the announcements as I can't figure out how it works, I copied the work order of the T/OP S7 scenarios but when I do it in my own ones, no sounds play, not sure how it knows what your destination is either. Is there a guide somewhere so that we can use these in our own District scenarios or are they scripted only for the T/OP scenarios?
Doesn't matter if they cant be used for custom scenarios.
My main point of this post is I just started an Ealing - Upminster one, to end at Gloucester Road, but I see the next stage is already in testing and I'm not looking for an exact ETA, but I assume this may be a release this year?
I only ask as if the extension is due soon, I'll hold off creation until 2.1A is released.
I have done Wimbledon - Edgware Road and back so far, and it really is astonishing freeware!!
James,thanks for your kind words, it is much appreciated by all the team. As regards creating scenarios, you would be well advised to wait until 2.1a is released before creating scenarios that go to or from Gloucester Road. The Wimbleware should be fine however. The reason no sounds play in your scenarios is probably because you have no wavs in your en folder. That is where the audio is kept. We have a library of audio sounds for the District S7 and the Met too, plus there is something in the pipeline. The route has the necessary markers for announcements built in, but the key is our audio library. You could, however, create a library of your own..............
I believe James is TubeMad on UKTS, and if so he's been around about as long as we have :-) James the reason to wait for 2.1a (which won't be long) is it provides modifications and extensions at GRD that allow us to continue building towards Tower Hill, etc. but also allows folks to build scenarios using GRD that will then still work in the future. If you were to build one now, we can't guarantee it will work with future route builds as locations, markers, portals, etc. are being changed or added in v2.1a.
As regards the audio in the TopMan scenarios... As Ed notes, we have added audio trigger markers into route v2.1 at key locations approaching and within station areas. Using these as Via points in the train timetable (task list) means the event completes when a train passes over them and that causes an event trigger. The event number (unique for each announcement) is passed to a chunk of LUA code within the ScenarioScript.LUA file. The LUA decodes the event number and then calls a TS system function to play the related WAV file, that is located in the scenario's En folder. All of that capability has been around for quite a while, so I'm not really giving away secrets by describing it. There are a LOT of clever things one can do with scenario scripting - our latest version (in dev/test) also causes triggered weather changes during the scenario. What did take us a lot of time is the careful positioning of all the audio trigger points, and developing the audio so it matched prototypical LUL announcements, and we used the initial set of TopMan scenarios as a proof of concept. And as Ed also notes, there is more to come...
Armed with the description above, you could make your own WAVs and populate the En folder and cause them to be triggered via our ScenarioScript.LUA code. And we will keep everyone informed about v2.1a. As we have been dev/testing the next set of scenarios, we have had need to make small detail changes to the route, signals, etc. That work is onging.
Thank you very much! That explains why the sounds aren't working, I didn't think it could be just adding the waypoint and trigger instructions that would make it work!
Jimi - Yes it is indeed tubemad from UKTS, playing simulators since Cab View Driver, Mechanik and BVE1!
Thank you very much for your advice, I shall put the project on hold, as I say not worried about dates, but I wouldn't want to make 20 scenario's, then find I've got to re-write all 20 scenario's, thought it would be best to check first!
I know it will be worth the wait, always amazes me how some aren't interested in freeware because it won't be any good, quite the opposite when you compare this and JT's Met!
I found writing on JT's Met line was rather difficult, in that it just wasn't flexible, and a vast amjority of the sidings, which are used by S8 Met stock, is just there for show and not to be used. Then couldn't even be bothered with an AI 1996 stock for the Jubilee section
Compared to this, which has all the operational flexibility of yards and depot's that can be used, and appropriate AI stock! Countless times I've done Paddington on C Stock's to either Earls Court or Edgware Road, and all recognisable on this route
The next phase will be well worth the wait! Just out of interest, will there be more portals on the Wimbledon line? Just noticed when I was doing Wimbledon from Edgware, the nearest exit point to get rid of AI was Gloucester Road. Doesn't need a lot of portals though
James - here's the latest portal list from the in-development v2.1a. Significantly more than before. I'll update the route docs with the final list for 2.1a. I've only listed the "inbound" (entry) LU portals. In every case there are companion outbound (lose the train) portals nearby.
Barons Ct (Picc) WB - train spawns in the pipe in rear of signal A654
Rayners Lane (Picc) EB - train spawns in N Ealing EB platform in advance of home signal A102
Northfields (Picc) EB Fast - train spawns in rear of signal A498
Northfields (Picc) EB Slow - train spawns in rear of signal A497
Ealing Bdy (Central) WB - train spawns in rear of signal WL46
Ealing Bdy (DR) EB - train spawns in advance of signal WMX549
Edgware Road Circle Inner Rail WB - train spawns at end of track in the east tunnel in rear of signal OP1A
Edgware Road Circle Outer Rail EB - renamed for consistency with other ERD portals and destination markers
Royal Oak H&C EB - train spawns at end of track in rear of signal TRX127
Olympia SB - train spawns in advance of signal A604 on the SB road of the double-tracked section
Gloucester Rd WB - train spawns in rear of signal EF265
Richmond (DR) EB - train spawns in rear of gantry signal GB16
Wimbledon (DR) EB - train spawns in rear of signal W374
West Kensington (DR) EB/WB - in or out. Sited between WKN and BCT roughly abeam (James May word) the pipe
Gunnersbury (NLL) - NLL portal WB (In) / EB (Out)
Richmond - From Putney WB, Putney EB, From Kingston EB, Kingston WB
Olympia/Fulham Broadway - From Shepherds Bush Inbound, To Shepherds Bush NB portal, From Clapham Jct Inbound, To Clapham Jct SB
East Putney (SWT) - East Putney SWT WB (in) / EB (out)
Wimbledon - Croydon tramlink NB / Elmers End, From Sutton EB / To Sutton, Guildford slow / Portsmouth fast, Raynes Pk fast/slow, Raynes Pk EB fast/slow, From Streatham to Wim Inbound / Streatham, From Waterloo slow / fast up, To Earlsfiled slow, To Waterloo fast down
Some of these portals ( inbound ) exhibit strange behaviour. The one at Ealing Broadway and North Ealing being two. The train spawns but then loops back after passing some signals. Eventually if you have more than 1 service in those 2 portals you will end up with an AI collision. We tried moving these slightly, moving them a lot etc etc. But with no success. So not all of them work properly, there is no science , it is witchcraft, but we did our best.
Eddie - Maybe an issue with Portals in general? Are you doing it with different services? Not that I've used Portals much, but I found they seem to work with a simple A-B short route, anything else is out the question! I did some services starting from a Portal, one took a Fast Line, the next took the Slow Line over the nearby crossover, it didn't like that! The slow service derailed. Then I altered it to crossover elsewhere, then it got stuck at a red and the next AI train crashed into it, then I decided not to bother with the portals for entries!!
This was at Bedford on the MML Route, the thing is you needed the portal as the 'run off' track was so short, you couldn't have a static fast and slow train out of sight ready to overtake you.
Also, not reporting this as an error as I have no idea if the signal's are like that as it may well be the case, but for the last signal coming into High Street Kensington, from Notting Hill Gate, does it have a repeater? On my scenario from Edgware you follow a Circle to HSK. I know it's in front, but I left Notting Hill, next signal was green, passed that, round a left blind curve, and round it to see a red ! Slammed on the brakes but just, and only just, whacked the tripcock. There was no previous yellow aspect, is this how it is set up in real life?
If so I would assume in real life you'd take the curve slower than line speed in case, driving on sight rather than relying on repeaters?
I do the signals, so I'll answer, having re-checked my charts. There *is* an error approaching HSK WB, but not quite as you thought. We're not missing a repeater, but rather have a wrong signal on approach to HSK.
What we have now going WB from NHG is A162 (NHG starter), about 500m later at the end of the straight is A158, then E300/RED3 on the curve (the one you found red), then RED4 on the approach, then ED4 (HSK starter).
The error is that repeater RED4 on approach should be a semi home ED3, which is logical as we have ED300 (speed control) with co-located RED3 (home signal repeater) in rear - so we should expect ED3 (home) next. No idea how I goofed that, but I have fixed it so it's now dev current and will be in the v2.1a build.
What happened to you is there was a train ahead in HSK platform, but no home signal protecting it in rear at platform end as there should be. ED300 was acting like an outer home but was wrongly including the platform area in its track circuit, and to compound the error was on a curve and had no repeater to warn you it was red. (As my father used to say, if the worst comes to the worst...we're screwed).
Normally ED300 would NOT be red, once you reduce speed to 25 on approach, and it's designed to reduce train speed (on the 1:70 downgrade) approaching HSK home. So once you reduce speed you'd expect green over yellow (ED300/RED3) if there was a train in the platform because ED3 (home) would be red. And you'd be slower (25mph) passing ED300 and now have plenty of warning of the red home and room to stop at that speed.
Short version: I have fixed it by replacing the (wrong) RED4 with ED3 (home) and it will all work as LUL intended :-) Route knowledge would tell you that you needed to slow after A158 approaching the curve (25 limit plus ED300 speed control), after which you'd be fine as RED3 would alert you if home was red and you have room to stop in time.