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.

 

Just now getting back to things, but got a little bit done on Davisville Yard this morning.

These iconic but ancient fire-watch towers may (?) have been removed since I moved out of Toronto, since they don't show up in any recent satellite photos. The modelling is still incomplete and scale is still maybe a bit big (I have only my eye to go by,) but with the help of Google Earth Pro's Historic Imagery feature, I think I've got them all in their proper locations now! I counted 11. Anybody know if I missed any?


Happy Canada Day!

 

Happy Canada Day

 

Here is the G-1, if you couldn't tell. I've got it to show up in-game as part of a proper formation, as opposed to being just a static or skeletal mesh! That makes it easier to overlook the improper origin, orientation/alignment and lack of texturing (or skeleton.)



All I had to do was take the view component out of the RVM where I had put it for some reason, and put it in the RVV!
Great way to start the work week, if you ask me! Just need to tidy up the folder structure for the model next, before things get out of hand.

 

Nothing groundbreaking to report, but I remembered that this "junction lever template" BP which can be found in "Game/Core/RailNetwork/Junctions/" has a few VHID components, so I can use a child BP made from it as an example of how working VHIDs are meant to be set up:


If I find myself with a spare moment this weekend, I'm going to see if I can get a simple door to slide open and closed, which should also serve as a test of my rigging and animation skills. No promises, but as always I'll keep everyone up to date whenever I make some real progress.

 

On the subject of VHID's I have been messing about trying to setup a Simugraph and RVM (both from scratch) for my GWR steam loco and have just realised the following.

In the RVM each cab control has a "lever" object of the appropriate type (Simple Lever, Irregular levers and so on which use a Blueprint.) These are set up so that the output (which can be between 0 and 1 -or -1 +1 for a Reverser) is mapped to the "real" output (1 =100% throttle etc.) They also have named outputs such as Combined Brake and are presumably used to input the current settings into the Simugraph. These objects include a "box" to set a link to a "Slave" VHID in some way although these are all blank in the Child RVM I'm studying.

The same controls Regulator , Reverser, appear in the RVV but in this blueprint they are VHID objects.

You may already know this but I thought it might be helpful.

Good to see you are still making progress with your project.

 

Good news: I tried unifying the Gloucester model (well, the interior) in it's current state, and seeing if I could import the model as a skeletal mesh, and test the textures and normal maps etc. to see if they looked okay in game. I think they do:



Might want some more variation in the materials, but I'm pretty sure I won't try Substance Painter, as I don't want to further encourage Adobe's software-as-a-service pricing models. It helps that these subways cars are meant to look fresh-off-the-boat.

Bad news: Just as I was getting back into the swing of things, I had to go and injure my finger at work, so I'll have to wait another week or two before I can right click with the mouse comfortably, though I can use my ring finger for that now, if I'm careful. Trying to do as little on the computer as I can until it heals, to be honest. Hunt-and-peck typing, that sort of thing.

I can probably rig the Gloucster up with the appropriate bones and animation given enough time, and I have most of my audio assets lined up. The truly hard part looks like it's going to be getting the VHID components and oh-so-mysterious Simugraph hooked up to everything, much as I suspected. I'll keep you guys posted!

 

Using the mouse is still a bit tricky until my finger heals, but I've managed to do a bit of work on framing the windows, as you can see: (the refence drawing on the right shows the cross-section of the right side of the frame.)

 

I spent the past day or so of working out the basics of the rigging setup, including the blender to PC Editor workflow.

One hot tip: make sure that in your fbx export in blender, you set the export settings to "Forward: -Y" and "Up: Z", and under the Armature tab, set the "Primary Bone Axis" to "X" and "Secondary Bone Axis" to "-Y. This should make things match up when you import them to the PC Editor. you might need to change the scale to .01 depending on how the blender file's units are set up.

I'm using the LIRR_M3a's skeleton as a reference for the hierarchy. The bones presumably need to be parented correctly, the orientation of all the bones should all be identical, pointed forward, as far as I can tell.

Here's a video of me showing off a couple of properly set-up and weighted bones:



and here's a video of me just showing off:



sorry if those are kind of grey looking; it might be my monitor's HDR settings.

 

One last update to end the weekend. I have my Rail Vehicle (G1-A) lying flat now (as you can see.) The culprit was a jumble of Simugraph nodes I had in my Simulation Asset as a placeholder. I still don't know why it was hovering about a meter above the rails, but for now I just moved the model components' location down in the RVV to compensate. Next up, couplers, and then eventually a semi-permanently coupled A-B pair (hopefully.)



It being so hot today, I then had to take a break and do some typographical gymnastics for the Beltline bridge south of Davisville. Mine's at the top



Now I'll try not to bug everybody for a few days, at least until Dovetail reveals to us all whatever "expect the unexpected" means! (Not anything about my plugin, unfortunately.)

 

I think this warrants an update. I just worked out how to write text onto a texture, and then put that texture into a dynamic material instance during runtime. This lets me put the train number on my subway car, lets the numbering react to shadow and light exactly the same as the rest of the material, and shouldn't impact the performance during gameplay in any meaningful way.


Not sure if that's the way we're supposed to do it. I'm also not sure how to make DTG's numbering system pick an entry and spit it out; right now I'm just setting 5098 as the default, to have something show up.

Meow! (hopefully this doesn't count as vandalism!)


edit: That's supposed to be a cat. (Give me a break, it's like 30 Celcius here!)

I followed a 10-year-old youtube video I found here:

 

Well, I won't have as much free time any more, as my doctor tells me my finger has healed enough for me to return to work. I will be working on it still, though; not to fear.

Looking back at the last few weeks, I'm grateful to have made so much progress, I've found new references both for parts of the Gloucester car and for scenery; I've got the accurate window sizes worked out (if not replicated across the whole model yet; ) I've got the rail vehicle to spawn in with collision (if not quite in the right position,) and I've even got the bare beginnings of my Simugraph started. That ain't nothin' to sneeze at!




What's more, have a look at what's on it's way to me in the mail! :



So tomorrow morning, it's back to work I go, with a song in my heart and a spring in my step!

 

Well, I can tick that one off! (yes, it is a little too far to the left side, I was in a hurry to set up the material!)

 

I decided I'd like to see passengers in my Eglinton Station sooner, rather than later. To that end, I started combining the various meshes that make it up into one main station blueprint. One exception is the blueprint for the escalator steps, which I tried adding to the BP as a child actor, but encountered problems with making changes to the spline component. I'll see soon enough if I can still get the navmesh to include them. I'll be going back to a LIRR M3 service for passenger testing, since passenger loading on those is of course already set up.

I captured some footage of the cosmetic progress I've made on my escalator this weekend, which came as a welcome distraction from my fingertip, which is feeling a bit awkward, but still healing.



Wish I had the time to progress as quickly as I've been watching some others manage to, but I guess that's the way of the world, really... And hey, we'll all be able to check out TSW6 later this week, so there's that to look forward to!

 

So now I'm trying the TSW6 PC Editor after all.
But here's a bit of progress: I've got passengers in my Eglinton station!



I can get them to find the waiting area no problem if I spawn them at platform level; but if I spawn them upstairs and have them use a nav link to take the escalator (or stairs) they disappear shortly after arriving at platform level (though about 1% of the time, one will make it to the safety of the waiting area, I've observed.) I'm sure there's some way of keeping them from doing that. Also they all wait facing away from the train, no matter which way I have the waiting area facing. ¯\_(ツ)_/¯

Also thought you might like to see how I achieved a moving handrail by animating the texture in the material, rather than the mesh.

And happy Canadian Thanksgiving weekend, for those who celebrate!

 

Good to hear you have made progress with passengers.
Before I diverted onto locomotives I spent many happy hours trying to get passengers working on a station but never got as far as you in trying to get them to walk up /down stairs.

You've probably already thought of this but have you tried extending (scaling) the waiting area boxes in the other dimension rather than rotating the boxes themselves ?

 

As a follow-up I've got passengers going 4 different ways to get to the platform, using nav modifier volumes with custom Nav Area types (which I didn't even know was a thing before today,) to balance the navigation costs in the eyes of the AI.



Once at the platform level, they now line up on both the East-side and West-side tracks, facing the correct direction!




(Tip for anyone making a platform without a spline, In your blueprint you will need to have something, as a child of the platform component, that has directionality so the AI knows where to face in the waiting area; I used a simple arrow component.)

 

Spent Sunday afternoon refining my tunnel lighting spline. I wanted the light sockets to cast slight shadows as well, but haven't quite got that looking quite right. It may be a tad dark, it's hard to be sure on my monitor. Overall, though, I'm happy with the results!



Here's how the cutting south of St Clair looks so far. Keep in mind this section was decked over in the mid-seventies, so references are a bit hard to come by:



I've found 3 PM on Sunday is a good time to cut myself off from the editor, in order to not feel I've been cheated out of a whole weekend. How about you folks?

 

that cool. for the tunnel light spline is that it own spline or is it with the tunnel?

 

It's a separate spline blueprint that spawns a light and the mesh (with emissive "bulb" material) for the light every 1000 units (as I recall) along the spline. I cobbled it together myself, using the blueprint my escalator steps use as a starting point. Luckily all the parameters (radius, length, color, intensity, falloff etc.) that I needed to specify for the point light can be set in blueprints, as it turns out.

At one point I had the lights disappearing one by one as the train got about 10 meters away, but this was because I hadn't disabled shadow casting on the meshes that had the lights located inside of them!

I did end up making the lights a bit brighter, having checked them on another display:

 

wow that so cool. for me i made my tunnel spine and i do have light fixture assets and added light bulb to it but i didn't know how to add it to tunnel walls. so the light fixture has to be a spline object to work.

 

Well, strictly speaking, the fixture mesh doesn't have to be a spline, but it certainly makes things easier when you're planning to place a lot of them!

I'll be home in a few hours, I'll see if I can take a screen capture of the blueprint in case you or anybody else wants to use it as an example for their own work.

 

Here is the BP, it "does the thing," as the saying goes.

 

oh thank you.

 

No problem! The bits where 90 degrees are added to the mesh's rotation are totally not just because I couldn't be bothered to re-orient the light fixture I made and export it again in blender.

 

i set the height of the fixture in blender and now changed it to ground level in blender.
for your light fixture is the white glow bar separate object.
for my tunnel light i had to separate the lens object from the fixture in order to add the glow material in the bp file.
here the spline light fixture but no lens yet. still playing around with the BP script

 

btw how did you get that X Y Z return value node list on get rotation at distances along spline tab there?

 

For that, you want to right click on the return value pin of the node, and select Split Struct Pin. There's actually a lot of different Blueprint nodes that you can do this with, as it turns out. Sometimes you can do it with input pins, as well!

 

My next challenge is to figure out why the double slip crossover just south of Eglinton is acting up. The problem started when i re-laid a section in the tunnel. When I take out the crossover, the junctions can be operated manually, (as they are set up to be) and respect their default directions, which is straight through. When I put the crossover back in, the junctions can't be operated manually (at least from map view), the one immediately in front of the change now points into the slip, and when the train starts to take the turn it spontaneously derails. I've tried refilling the track sections and resimulating the timetable, with no change. The "signals" I have aren't even set up to change aspect yet, but I'll try removing them to see if that makes a difference. Other than that, I'm out of ideas for the moment.

update: disabling "player assist auto set junction" in the scenario manager works for now, and will let me test out various sections of track to make sure they're at least drivable, but ultimately I'll want to set this back on for scenarios. The underdeveloped signals may-or-may-not be contributing to the spontaneous derailing, but I'm putting that on the back burner for now. I wouldn't be surprised if it is a "signal thing."

2nd update: Never mind, didn't fix it.

 

how did you get the tunnel so dark?

 

Two things: I used an ambient occlusion volume, and another custom blueprint which does quite a bit: it identifies the skylight component of the TOD4 system, then lowers its intentisty as the player travels along the length of a bounding box from 1 to 0, since the skylight seeps in everywhere to some extent, as far as I can tell. I'll post that one later as well, but it's quite complex. I have a hunch DTG use something similar, but if so, I couldn't find it.

 

Actually, I won't have time tonight to show my "Skylight Modulator" blueprint, but an older thread of mine shows how to set up the nodes to find and turn off the skylight using blueprint : https://forums.dovetailgames.com/threads/yet-another-quick-lighting-tip.90057/

 

Put a few blank services out on the sidings in Davisville Yard, and looking around them made me feel all warm and fuzzy. Even if this interim RVV model has some misaligned normals, and something has broken with the material instancing in my train numbering system.

Even if so many things are half-finished, and the challenges, both inside and out of the PC Editor may be many; reminding myself how far I've come has renewed my determination that this whole thing is worth seeing through, either in this iteration of TSW or the next.



Happy Holidays and Merry Christmas everyone! This is PWilson79, wishing you all and your loved ones all the best in the new year!

 

Feeling a little down because there seems to be something deeply wrong with either the collision or the simulation asset on my subway car. Testing out an experimental driver's seat, once I sit down, the whole subway car makes like a submarine in an emergency dive. Then the game detects a "derailment" and declares the scenario failed. I think it may be related to the passenger seat "pop-up toaster" effect, I can't seem to pin down why it's happening despite copying values and settings from child blueprints of a working subway car, and worst of all, I've run out of time to work on it tonight!

Anyways, I'll keep you all posted on any developments.

 

Assume you have a Driver's environment in your RVM and that you have a socket "Seat_Driver" in the skeletal mesh of your Cab to attach the driver's Seat Component (in the RVV) to (Parent Socket box)
This sounds similar to the bottomless pit problems I had which turned out to be the socket.

Are you spawning in the seat or getting into the train at the start ?. You said it happens when you sit down so do you get the same problem if you tick the "start scenario driving train" box (spawn in cab).
If the problem is only happening when you sit down it could be something in the Scenario set up (Timetable or Definition) that is wrong. There are lots of settings in there which could cause the game to object to your trying to drive the train.

I don't think it's the Simulation Asset (Simugraph) as there's nothing in there linked to the Driver.

As always, I hope these suggestions will help (you may already have thought of them) and I have found that the solution to these seemingly insurmountable problems is often simple once you know what it is ! Good luck !!

 

Thanks for the encouragement, Daunfr59 ! That's definitely something I'll double-check tonight.

 

No luck pinning this down yet. Here's the relevant section of the output log, for what it's worth. It says there's no VHID component, but I've put a throttle in, so I'm not sure if it's some other type of VHID Component it might be looking for. I still feel like this submarining might be linked to the seated-to-standing-superman-syndrome. Oh well, that's for tomorrow to worry about.

Code:

TS2: Warning: DriverPawn: No VirtualHIDComponent found in the Drivable RVM_TSUB_G1_A_C_16
TS2: Derailment - Wheel Left Track - Axle Offset X=31.596 Y=-1.999 Z=-1.551
TS2: Derailment - Wheel Left Track - Axle Offset X=31.586 Y=-2.000 Z=-1.562
TS2: Derailment - Wheel Left Track - Axle Offset X=31.586 Y=-2.000 Z=-1.562
TS2: Derailment - Wheel Left Track - Axle Offset X=31.596 Y=-1.999 Z=-1.551
TS2: Warning: URailVehicleComponent::BeginDerail [Vehicle] {14220461-4970-9F82-0D4A-DAB8A528A8C7}, [Reason] WheelLeftTrack, [Location] Lat: 43.70607, Lon: -79.39848
TS2: Error: Rail Vehicle Derailed: RVM_TSUB_G1_A_C_19 (None) at Lat: 43.70607, Lon: -79.39848
TS2: Error: AScenarioManagerActor::OnDerailed - Rail Vehicle has derailed but it's not driven by player!
TS2: Error: AScenarioManagerActor::OnAnyVehicleDerailed() - Player location - Lat:43.704781 Long:-79.398412
TS2: AScenarioManagerActor::GetObjectiveFlowManagerFromIndex - FlowIndex is invalid!
TS2: Warning: URailVehicleComponent::BeginDerail [Vehicle] {2368E47C-4DAE-9931-1CD2-76A9CF7EB8AB}, [Reason] WheelLeftTrack, [Location] Lat: 43.70588, Lon: -79.39847
TS2: Error: Rail Vehicle Derailed: RVM_TSUB_G1_A_C_18 (None) at Lat: 43.70588, Lon: -79.39847
TS2: Error: AScenarioManagerActor::OnDerailed - Rail Vehicle has derailed but it's not driven by player!
TS2: Error: AScenarioManagerActor::OnAnyVehicleDerailed() - Player location - Lat:43.704781 Long:-79.398412
TS2: Warning: URailVehicleComponent::BeginDerail [Vehicle] {AC0D57DC-41A2-5636-7052-15AFA9D971A3}, [Reason] WheelLeftTrack, [Location] Lat: 43.70564, Lon: -79.39846
TS2: Error: Rail Vehicle Derailed: RVM_TSUB_G1_A_C_17 (None) at Lat: 43.70564, Lon: -79.39846
TS2: Error: AScenarioManagerActor::OnDerailed - Rail Vehicle has derailed but it's not driven by player!
TS2: Error: AScenarioManagerActor::OnAnyVehicleDerailed() - Player location - Lat:43.704781 Long:-79.398412
TS2: Warning: URailVehicleComponent::BeginDerail [Vehicle] {479CCA2F-429E-A4AC-C25A-829AE9CF4D40}, [Reason] WheelLeftTrack, [Location] Lat: 43.70547, Lon: -79.39844
TS2: Error: Rail Vehicle Derailed: RVM_TSUB_G1_A_C_16 (None) at Lat: 43.70547, Lon: -79.39844
TS2: Error: AScenarioManagerActor::OnAnyVehicleDerailed() - Player location - Lat:43.704781 Long:-79.398412
TS2: AScenarioManagerActor - Outro is done. Complete!

Anyway I shouldn't get too upset with myself, I don't get time to do much more than poke at it a bit during the work week; here's hoping for more progress this weekend.)