Creation Sharing Diary Of Creating A Route - Toronto Subway Opening Day

If you have specific questions or run into a roadblock, just let me know

 

Gosh, I didn't think I'd be spending so much of my weekend setting up the lenses on my signals!

Now for the gory details:

Well, instead of using timelines to animate the "On-ness" parameter of the dynamic instanced meshes on my lenses, I'm going to try doing the animation all in the signalview blueprint using my own custom timers.

My rationale for this is that using timelines would have required spawning a new actor for each lens of each signal on the system, whereas with my method, they can still just be components of the signalview. It remains to be seen if that's still too many dynamically instanced materials, but I would very much like to see them ramp-up and fade while turning on and off, particularly with the dual flashing reds of a timed signal. We'll see. Any thoughts on this, cActUsjUiCe ?

Oh, and the editor crashed twice this weekend, removing a bunch of track proxies, and the signals I'd put down (not very many, thankfully.) Using a backup version of my TS_x0_y1 tile, I got my rail network and proxies all back in, at least!

Does anybody know what tile the signal meshes reside in? The ribbon info for the signals were still there. I may have been able to re-attach the signalviews to them somehow, but I found it easier to re-lay those sections.

And of course, I'll backup everything again, right now!

 

Signals should either reside in the TT or TS tiles (definitely not in LT and I highly doubt they could ever be assigned to ST), but I guess they should always be in track scenery tiles rather than track or even scenery tiles (if the latter of these would possible at all).

Also could just be a visual bug that signals persist even after being deleted (had something similar as well) and then the yet persisting information vanishes when restarting the Editor.

Anyway, try to avoid glueing things together by yourself and if something appears to be off or broken and it isn't too much work to redo, then its best to invest time in redoing sections from scratch and set all signals (and in case even lay tracks) completely new I think.

 

Well, my understanding of signals and junctions has developed by leaps and bounds this week. A few days ago I was bugging cActUsjUiCe for a way to read the setting on the junction ahead to use in my signal aspects, when I didn't even know that I hadn't even started to set my junctions up properly! (sorry, cActUsjUiCe)

For anyone making the move from simply having rail ribbons connected in junctions to having proper, game-recognized and interactable junctions with associated levers and such, try making a child blueprint of TSW5 PC Editor/TrainSimWorld5Mod/TS2Prototype/Content/Core/RailNetwork/Junctions/BP_JunctionLever_Template. I think you'll find that it's a sound foundation to build on!

And for another tip, I've puzzled out that you need to have your junction in a row in a data table (with row structure of JunctionLever_Struct, I think, I've found the one in core content works) for manual switches to stay that way, and for the junction's event graph to fire anything off, as far as I can tell. Once you add a new data table, and add a row for each junction, you should specify that data table (and row) in the details of your junction actor. Automatic junctions will presumably be set up slightly differently.

With any luck I should have the signals showing switch indications by the end of the weekend, either with custom events, or casting, or some other method.

Now I'm going to sit back and have a beer. This is not typical behaviour for me, but it's been an unusually hellish week for me at work. Cheers!

 

Signals reside in the TS tiles, but i'd back up your TT tiles as well just in case things get corrupted again

 

So you're working on flashing lights? I'll explain it as best as I can. It's not intuitive at all because there's so many components. This is by no means a comprehensive guide but it should get you on the right track.

• Create an enumeration somewhere in your folder structure and give it a name like "LampColor". Create individual entries for each color the signals in your project will be capable of displaying.
• Set up your Signal Lens Base blueprint. This will have a parent class of Blueprintable Static Mesh Component. This base is the parent for all your actual lenses used on the signal heads. At a minimum it should have:
  • a function named "SetColor" with just a single input of your "LampColor" enumeration.
  • a boolean variable named "Flashing"
  • a Material Instance Dynamic variable
  • a function named "SetColorAndFlash" with two inputs. One of your "LampColor" enumeration and one of the "Flashing" boolean. Wire it up like this photo:
• Set up a signal lens blueprint. This will have a parent class of your previously created Signal Lens Base. It's set up with a variable named "Material Index" and just has an event that fires off every time fhe "SetColor" function in the Signal Lens Base is called. It looks like this:
• Inside your actual signal head blueprint, add components for your signal lenses. This will be the signal lens blueprint configured above. You'll need one for each light on your signal head. Then click into each lens component you added and set the material to be that of the appropriate color. The DLCs come with material instances that you should be able to reference.
• Also inside your signal head blueprint, you need to make a function called something like "SetLamps". This gets fired off whenever the Signal Head Base's "SetAspect" function gets called.

• You'll also need a Signal Head Base blueprint that acts as the parent for all of your actual signal head blueprints. The signal head base has functions like "SetAspect" and can do other things as needed. It's parent class is just "actor". The SetAspect function just has a single input for the Aspect Class you're trying to set on the signal.

There are other things too like programming the Material Instances/Material Functions but I'm not very good at that, so I can't speak intelligently to it. Hopefully this helps.

 

Thanks for the signal setup and colour tips, cActUsjUiCe! Knowing me, I'll probably try to do it a vastly different way, and then sheepishly* emulate your setup when mine fails spectacularly.

Well, besides figuring out some stuff about signals and junctions, and getting the down-escalators moving again at Eglinton Station, I've managed a guest appearance of a 6-car '38 London Tube Stock formation, which will be ready to do test timetable runs to Davisville, once I sit down with it to have a long talk about electrification requirements.

I'm digging that family resemblance!


*EDIT: I mean "sheepishly" in the humbled, hat-in-hand sense.

 

Well, the 38 Stock had all kinds of fourth rail requirements, so I put it aside and tried out an M3 from the LIRR, which had no such complaints. And now I've had a couple successful runs of my test service! Passenger loading isn't working yet, so this one's just a go-to from Eglinton to Davisville. Maybe it's just a small bit of progress in the grand scheme of things, but it's something I've been anxious to see

The video below starts with a brief look at the top side of Eglinton, before we venture down to see what awaits us at the platform. A brief reminder that the roads and buildings at street level are missing, but I basically just need to re-import those assets. I was so excited to capture this video, I didn't even have time to fix up those signals or bake the lighting in the tunnel again!


Want to see how my route looks in its current state, with a train running on it for Mario Day? Let's-a go!

 

Looks beautiful.

 

Thank you very much! To my critical eyes, it's hard not to see everything that still needs doing, but I'm glad you like it so far! I've made a little progress since then, but perhaps not enough to share just yet.

 

Well, I may not be able to do much more on the route for the next couple weeks or so (due to other areas of my life unexpectedly needing urgent attention,) so I thought I'd make a post with a few small updates.

First, here is a nice shot of the eastside platform at Eglinton, showing an analogue clock blueprint with the parent class of "/Game/Core/BlueprintResources/Clock/Analogue/BP_ClockAnalogue_01", which I will rework a bit to match reference photos I have. A useful blueprint class to be sure! Also note the track switch blades are correctly lit, now that I've got the skylight turned off in the station.


Next, A little more work has been put in, leading up to the tunnel entrance south of Davisville, still a ways to go here...:


Lastly, Here you can see some of the iconic fire-watch towers in Davisville yard, as seen across Yonge Street from Mt. Pleasant Cemetery. They're maybe a little oversized and missing some details, but I think they already give a good impression:

Well, that might have to be it for a little while. Hopefully not too long though. I wouldn't worry, I don't think it's anything that will jeopardize my route. In any case, I want to say thanks to everyone that's helped me out so far, and continued good luck to everyone on their amazing projects!

 

Hello all!

I know it's been a while since my last post, and I certainly wish I had better news with which to present you.

It's not easy for me to say this, but the project has been put on indefinite pause because my housing situation has become uncertain, and I'm facing the much more pressing issue of keeping a roof over my, and my mother's heads. I'm not sure what the future of the route will be.

I'm up to putting the plugin in it's current state somewhere online to preserve it in some form, if anyone has some easy suggestions. I've never used "the cloud," for instance, and I'm not sure how much it would cost to preserve 5 GB of data. I'm open to all and any suggestions that would be cheap, and easy to implement. I don't think I'd have a problem with other people taking a poke at it either, as it was always supposed to release as free. I do hope to put out a somewhat definitive version.... eventually. If all goes well.

There's just no way I've got time to try to pack or cook the plugin, or even trim out any fat.

I have my reference material backed up in a couple locations on my computer, which I certainly hope will survive all of this.

I'll have a look at any suggestions you all have, but this may be my last post for a while. If I do get the WIP plugin put online somewhere, I'll try to get the word out. Wish us luck! I feel we'll need it.

 

Wish you luck with whatever you need to deal with and as for the storage, Google Drive gives 15GB free for every account so you can just upload a 5 gig ZIP file.

As for the references, if they are too large to upload, get a pair of flash drives (from reputable brand) and copy the files on both of them. That's a cheap option and the data should survive unless you leave them for like 10 years without plugging into anything.

 

Just popping by to let you all know the project's not dead yet, and my housing situation is no longer in question!

One major change is that I've decided to allow one dependency for my route: DTG's (delightful, IMHO) Liverpool Lime Street - Crewe. This will allow me to use the passengers, which should look fairly accuate, though based 3 years later, and in the mother country as opposed to the colonies

Also, this could in theory allow for periodic (and period accurate) AI steam freight services on the beltline bridge, as the player drives their Gloucester to and fro in Davisville yard beneath. Even if they're not the 4-4-2s Canadian National operated at the time, I rather like the idea.

With that said, don't expect much in the way of progress for at least a month or so, as things are still getting settled.