Sunday, 9 February 2020

Hello!  A few things for you today.  I'm more or less back to working on the route as much as before, so I've made a bit more progress since the last post.

First of all, I've refreshed the WCMLNorth part of the route as far as Newton, coming from both Glasgow Central (both low and high levels) and Kirkhill.  This hopefully gives a good bulk of core of the route a consistent look the same as the rest of Suburban Glasgow, and refreshes some very old areas.  Here are a couple of pictures of this:

More than just new trees at Newton.  Better looking signs (although still without the Gaelic name!) and a bit of reworking of the immediate surrounding scenery:

And likewise at Kirkhill - I've remodelled some of the station to be a little more accurate:

So this is for the Workshop route.  As time goes on I'll come back and tweak a few different areas, here and there to bring them up to the same standard.

For the detail pack, there is a lot more work to be done...  I already spoke about the "auto-refresh" - which has kind of turned in to a "90% auto, 10% manual" refresh!  I figured it really didn't look ok with some of the results of the asset replacements, and the newer trees definitely don't look ok when they're resized out of scale.  Also, the new "near" trees don't really work when placed a bit further away from the track, as I mentioned in a previous post, so I've had to figure out a way to sort that too.

So I've tweaked the RouteBuilder job further to make sure the aspect ratio remains the same.  I've also figured out a way to for the job to know whether an asset is near the track or not, and I'm much happier with the results now!  If an asset is within around 50m of the track then I make it use the near assets, otherwise they are changed to using the mid ones.

One downside though, is that the sizes are different compared to the originals, so there is still some re-positioning required, which is the bulk of what I'm working on at the moment.  This is quite time consuming, but I'm making progress on it - so far having done from Helensburgh and Balloch to Yoker Depot.  I'll keep picking away at it over the next few weeks.

Here are some pictures of the latest detail pack work - let me know what you think.  Starting with the single track working its way through Helensburgh:

Somewhere along the Balloch branch here.  I've included this pic to demonstrate how the scenery further away from the track has automatically been substituted with mid scenery, whereas nearside is using the newer nearside trees.  This was a bit difficult to achieve, but I managed it by loading a special texture set in to the job and used that to mark areas I considered "nearside".  Actually worked quite well.  Note, I don't have any plans to change the nearside foliage like weeds and brambles:

Passing Bowling, looking towards the Erskine Bridge:

And the final pic is from Dalmuir:

And that's it for the work from the last couple of weeks!

So something else that has just come up over the last couple of days - and something I had no idea was coming - is the new Fife Circle route!  As with any new Scottish route, the first thing I asked myself was "Can this be merged with Suburban Glasgow?".  I posted a poll on the ATS Facebook group asking this very question, and the results were quite convincingly yes - this is something people would like to see.

So I took an hour or two out and passed the route through the job to change the start location to match WCMLNorth and Suburban Glasgow, and it was easily done - so this is something that is now very likely to appear in the next release.

There are some real things to think about here about how to do this.  As I'm also developing an executable installer for the route, I'm actually considering allowing people to choose a specific version of the route to install.  This would require people to download a different version of the Workshop route, depending on the scope - but then the installer would know this and automatically install the route accordingly.

So imagine you kick off the installer, and this appears (final options might be different):

Welcome to Suburban Glasgow.  Please select the route to install:

1)  Only North Clyde Line

2)  Glasgow to Edinburgh and Surrounding Area

3)  Glasgow and the West Highland Line (incorrect Workshop version)

4)  Glasgow, Edinburgh and Fife Circle

5)  All available merged routes

The North Clyde Line trackwork does not contain any copyrighted material from other routes, so doesn't need a Workshop download and will always be available as an option.  I think this is actually not a bad idea, as it still makes the route available to people to who still can't get their head around there being both a Workshop and RWP component!

There would be several other available Workshop downloads that you can install prior to running the installer, and it will detect what is there, what is completed and what is only partially downloaded or installed, and only give you the options to install if they are installed properly.  In the example above, the ones in bold are available and ready to install.  The one in red has a problem and the one in italics simply isn't available.  Obviously, in reality this will be a proper installer, so the unavailable options will be greyed out as opposed to being in italics - I'm just showing this to show what I'm thinking of doing!

What do you think of this?  Is this going to simplify the installation of the route?  I could even, in theory, make it smart enough to know what version you install and only install the scenerios that will work on these sections.

I can quite easily enhance the RouteBuilder job to chop off large chunks of route, so on my side it'll just be a case of clicking a button to generate these different options.

So going back to the Fife Circle, I need to think about what to actually merge in and where to make the join point.  The obvious (and seems crazy to think I wouldn't) thing to do is to chop off Suburban Glasgow (actually EandG) west of Haymarket and just north of Slateford and replace both Haymarket and Waverley with the newer version in Fife Circle, giving me a free refresh in the process!  But there's a big catch here.  Look at options 2 and 4 in the installer options above.  The point here is that option 2 should not require people to own the Fife Circle, but yet it still includes Edinburgh Waverley!  This is a problem, as I do not want to have different versions of any stations between the different versions of the route.  It would be a logistical nightmare to maintain different versions of the scenarios for example!  So I'll need to sit down and think about how to do this.  What might end up happening, is that I merge the FC to Suburban Glasgow at South Gyle instead, and just manually refresh the scenery around Edinburgh myself.  Might not please the people who own FC, but I think this might end up being the only option I have.  Regardless of what I do here, there will definitely be a link from Dunfermline to Alloa via Longannet, although the scenery might not appear around here for several versions yet, so only trackwork to begin with!

So I'm hoping to get some test version of the route up and running again quite soon - maybe some time in March!  This will certainly have all the new foliage and probably something of the Fife Circle, given the caveats I just described.  I'm not sure how mature the new installer will be as it's pretty much still in the design phase, so there might still be a bit of manual jiggery pokery for a few of the test releases yet!

I think that's everything for now.  Have a good evening!

Sunday, 26 January 2020

Hello and good morning!

Somewhat more positive than the last post now.  There were 90 votes in all - 85 to continue with the new foliage, 5 for the old foliage, and none to just give up!  So that's good to know at least lol.

Anyways - the plan is now something like this:

- For the detail pack, use the auto-foliage replacer and then tweak the places where there are obvious glitches, like trees hanging over the track etc.

- For the Workshop parts of the route, I'm going through and manually updating some of the areas to be the new foliage, and leaving other areas alone.  The reason for this is that auto-replacing the foliage in the legacy routes isn't giving very good results, so I'm thinking that the only way it's going to work in this area is doing it myself.  The goal here is to make the key areas of the Workshop route look exactly the same as the rest of Suburban Glasgow (for nearside scenery at least).  This includes stretches like, Glasgow Central - Newton along the WCML, Rutherglen to Dalmarnock, Newton to Kirkhill.  Like I mentioned before, I'm not promising to update all of EandG, GARL and WCMLNorth, so this will only be done in key places.

Having said that, it will likely change as other parts of Suburban Glasgow develop.  For example, I'm probably going to want to refresh the stretch from Newton to Carfin once I start on the Shotts line, or perhaps as far as Falkirk Grahamston when I do Cumbernauld to Greenhill.  This may extend to further reaches as the route grows more, but there is no plan for this at the moment.

As mentioned before, the OLE changes are dead in the water, unfortunately.

So here are a few screenshots of the WCML upgrade work.  Some of it is a simple "replace of trees and add some weeds" type thing, and others are complete rework of the track to use proper embankments etc.

First up, near Rutherglen:

A little further towards Cambuslang, a couple of photos showing a completely reworked stretch:

And finally, just past Cambuslang:

I'm not quite ready to go hammer and tongs in to the new phase yet.  I've got a little side project that will probably complete around the end of February/start of March, so I'll keep tweaking at this until then.  At this point I'll probably reopen the Suburban Glasgow Test Version route with the changes (probably not the new installer at this point) and then get started on Phase 6.1 proper.

So maybe expect another blog update in 3 or 4 weeks, then I'll get back to the regular weekly Sunday updates in March!

See you soon...


Wednesday, 22 January 2020

Hello and Happy New Year!

Yes, it's been a very long time since I've posted!  And since it's true that I've been spending (much) less time on the route than I was previously, that doesn't mean I've not been touching it at all.

Since the last blog update there have been a few more developments in the plan for the route.  Unfortunately, not everything has turned out as I have planned, so I'm at a bit of a crossroads again.  One of the possible outcomes of this is that development on the route ceases altogether, so please read this post carefully if you are interested in the future development of it!

So what's changed?

Prior to my starting working on Phase 6.1, I decided to engage the community to see what they would like to see in the route - mainly, would you like development to continue full speed ahead, or would you like me to take some time out and refresh a few bits and pieces.  The overwhelming response to this was that the refresh should happen first, so this is what I've been looking at over the last 3 months.  I can split this in to 3 main parts:

1)  Refresh all the Kuju foliage to use the more recent 3D ones
2)  Replace the legacy track based OHLE with the more recent loft based one
3)  Create a proper installer to simplify installation of the route.

So here is a quick update on all three.  Probably not 100% a good update to be honest!

So first of all, the foliage.  This is partly good and partly bad!  It was always my intention from the beginning to try to automate as much of the greenery refresh as possible.  If I sat and tweaked each individual bush and tree over the entire route then I might as well have started the route from scratch.  So I enhanced the route moving tool to do a lot of asset manipulation as well and ran it on the detail pack.  This basically did a batch auto-replace of the old assets with new ones, but since the assets are mostly placed to a certain size, it necessitated me resizing them too.  So I have done this, all automated.

Thing is, I'm only 80% happy with the results.  The main issue being the way I used some of the assets originally.  For example, I always used the "Tree Line Mixed Near" asset as a kind of a generic greenery line, even quite far from the track, as that gave the impression I was looking for.  But there are no similar "all purpose" assets in the new set.  So even though the new sets might contain better individual assets, the placing of each asset is no longer completely appropriate.  Perhaps some of the pictures below help demonstrate.

Here is the approach to Cardross from the Helensburgh direction.  As you can see, the tree line gives a kind of a wall of trees:

New with the auto-replace done, this is now full of the new trees:

So hands up who thinks the new look is better?  I'm actually completely undecided.  But the effect, I think, is different to what I was originally trying to achieve.  Maybe I'm viewing it through ultra-critical glasses, maybe not!

The truth here is that if I was creating this area from scratch with the new assets then I'd probably not use these tree line assets at all, rather creating it with other woodland assets.  So this is an example of something I'm not so sure about.  Like I said, I'm not planning to go through the route ripping up bits and pieces of it, so what I'm wanting to achieve needs to happen with automation or it doesn't happen at all.

On the other hand, here we have the line to Helensburgh Upper, which I think has benefited greatly from the replacement.  None of this has been touched by hand.  (bear in mind most people will be viewing this with the AP track, so take this in to account!):

So seeing these pictures, and given some of them look better and some of them look worse, I'm curious what people think here.  Is it worth the bother?  My gut feel is it looks generally a little better overall.

Next, the OHLE Replacement.  Unfortunately, this is all but dead in the water now.  My plan, again, was to automate as much of this as possible, and it oh so nearly worked!  The thinking was in the way the new assets are used to join the wires together.  Once the wires are there, the masts and gantries can actually be moved about and edited or replaced as needed.  This gave me the idea of using a global asset replace to replace the old ones, join the dots and string all the wires together, then do the same replace in reverse to put the old assets back.  Bingo!  The OHLE would now suddenly be all wired together, but yet it would keep the original posts and gantries etc, thus giving me the best of both worlds and cutting back all the work needing done!

I spent a lot of time coding this and then doing the initial POC - from Helensburgh to about half way to Cardross, which took a couple of hours - an acceptable time I thought, meaning the whole route could be done in a few weeks.  I replaced the old assets with something that gave the hoop to wire up the new OLE, I wired it, then I replaced it all back again.  But then the problem appeared.  Look at this picture at Craigendoran with the old OLE:

If you can see the wire (you might have to enlarge the image), you'll see what's probably the most hated thing about the old OLE - the fact the wires "turn" at points where they are not connected to gantries.  Right at the very beginning of the route building I was aware of this and made the conscious decision to place OLE assets where they were in real life rather than where they would match the wires in the sim.  But perhaps more importantly, the gantry on the right is positioned in such a way that it causes problems.  Here is a diagram I've just made that demonstrates:
The top one shows the contact arms being placed close to the top rail as it would be in the new OLE, so the wire is always in a place that contacts the pantograph.  This is the case for both push and pull type masts (which I've not really implemented in most parts of the route).  However, as masts with the original OLE are more generally aligned with the middle of the track, and sometimes even in completely the wrong side, wiring them together has caused the wires to be in the wrong place, as shown in the second part!  I hope I've explained this ok.  So this is what happened when I ran a train between Helensburgh Central and Craigendoran.  As the wires are aligned to masts that are aligned to the centre of the track and not the edge of it, they overhang the track:

That's gonna be a lot of downed wires!

So unfortunately, it looks like there's no quick(ish) fix to put the new wires up, meaning the only way to do the new OLE is to do it all by hand, including in all the merged routes.  So I'm dropping it!

The New Installer.  It has been a gripe from many many people, way since the first version of the route nearly 7 years ago now, that it's way too complicated to install.  As I've outlined many times, this comes from the various permissions I've had from the payware DLC providers, that I only have permission to merge in their routes if they are kept available on the Workshop.  So this is why I have the two parts - install the Workshop route with all the merged routes, then install the detail pack that adds in my stuff.  Sounds simple, so I don't know why it's so difficult for some people!

But anyways, I've decided to look in to creating an executable installer, that although it doesn't take away the need for the Workshop route, it can at least tell you if it's installed properly, and direct you if it's not.  99% of the issues people have are because they go ahead and start the installation of the detail pack before the Workshop route has been confirmed as installed properly.  Me gently reminding them to actually follow my instructions is usually enough (if I've told you to re-read steps 3-6 then you're guilty!) but this is something I want to stop altogether.  So I've started looking at Inno Setup, one of the tools that can be used to create self installers.  The good news is that I've got it to figure out if the workshop route is installed as a test, so I'm going to go through and set up a proper installer for the next release, if it goes ahead.  If you try and install the Detail Pack when the Workshop route is not installed, then it will direct you to Subscribe, wait for it to download, set up etc, then automatically detect when it completes and advise you to unsubscribe and continue with the installation of the Detail Pack.  Hopefully that solves all the installation problems!

So there you have it, this is where I'm at with the route at the moment.  The big decision now is what to do going forward.  Besides my own parts of the route, it is out of the question for me to go through it all, including all the legacy merged in routes like GARL, WCMLNorth and EandG and update both the scenery and OHLE to be up-to-date.  I could maybe just about manage tweaking my own work, but it was never my intention to make the three other aged routes as if they were created in 2020!  This is a lifetime project for someone and it's certainly not me!  So the question is, with this in mind:

1)  Do I go ahead with the automated foliage changes I've outlined above, drop the OLE changes, and then release phase 6.1 (Cumbernauld, East Kilbride etc) in a few months with the nice installer in place?

2)  Do I count my losses with the last three months and revert to the old foliage, then continue where I left off?

3)  And finally, and not the answer I hope to hear!  Do I accept that the extensive use of old assets in the route means it's not as attractive as it used to be, and stop work on it altogether?

I'll post a poll on the Facebook ATS group with these three options.  If you're not part of that group then feel free to comment here instead!  I'm hoping to get started on Phase 6.1 proper very soon, working the lines out to Cumbernauld and East Kilbride, but my motivation isn't in a good place just now, so really needing to work myself up to getting a bit more focused!

Hoping for some feedback!

Tuesday, 8 October 2019

Ehh, seven weeks it's been!  I'm still here though and the route plans are still very much alive. :-)

I've been taking a little bit of a break and also creating a "Route Building Guide" for people working on the outlying parts of the route.  If anyone's interested in seeing this it is available at Suburban Glasgow Route Building Guide.docx.  It's intended for Suburban Glasgow but works for any route in theory.  Just take note of  some of the things mentioned if you do use it for other routes.

I do actually have some screenshots to show you though.  The route building guide in question is based on the stretch between Clarkston and Busby, which I completed as I was writing the guide, so I could reference work in progress etc.

Here we are looking back towards Clarkston from Overlee Playing Fields:

The viaduct across the White Cart, looking north:

and finally, from Busby itself:

The up and down platforms are not aligned, as you can see here!

So I'm not quite ready to get stuck in to the next phase of route building hammer and tongs, but it's not that far away...  Maybe expect to hear from me in a month or so, with the continuation from the M80 towards Gartcosh and Cumbernauld.  Cheers!

Tuesday, 20 August 2019

Hello and welcome to Suburban Glasgow version 6.0h!

If you'd asked me 6 months ago what that meant I'd probably have told you that the Cumbernauld and East Kilbride lines were completed, but obviously that's not the case now since the scope has completely changed! (these will be Phase 6.1).

So to recap, this version is:

- everything that was Suburban Glasgow Phase 5.2 with a handful of fixes
- Edinburgh to Glasgow (the DPS extended version with Stirling and Carstairs)
- West Highland Line South
- West Highland Line Extension
- Glasgow Airport Rail Link (with the actual airport bit removed, funnily enough)
- The original UKTS Oban Line

Thanks to Thomson and Milepost for permission to include their products in this merged route, and also to Darren Porter and Michael Hamilton for permission to include their work too.  As previously mentioned, I've altered the textures to work with Suburban Glasgow so they may now look a bit different for some routes than originally intended.

Obviously, the increased scope of the route has required me to add more DLC to the list of requirements.  These are now (for the core route at least):

WCML North
WCML Over Shap
Edinburgh to Glasgow
London Faversham High Speed
West Highland Line South
West Highland Line Extension
Glasgow Airport Rail Link

The UKTS Oban Line is included in the route so nothing more needs to be downloaded for it.

Installation of the route is exactly as it was before, with the Workshop route getting set up and verified, then the detail pack installed on top of it.  As the route is now enormous, it's even more important that steps 4 and 5 in the detail pack instructions are followed to the letter, or else you'll end up with something that keeps crashing.

It's maybe also worth mentioning that I've not been able to have all the scenarios tested by second eyes (but I've tested them all myself) simply due to the fact that some of them are extremely time consuming with the longest taking almost eight hours.  If anyone finds they get 95% of the way through one of the longer scenarios and then something breaks, please be gentle!!  If you complete any of the 3+ hour scenarios then I'd appreciate it if you could let me know, so I can sign it off as complete. :-)

People who have made their own scenarios for previous versions of Suburban Glasgow might need to tweak a few things here and there to get them to continue to work, as I have had to raise/lower track here and there to make it connect to the various routes.  It shouldn't be much though (hopefully).

So as always, I'm going to go away and take a break to do something completely un-train-sim related, in this case playing Red Dead Redemption 2, before I come back and get started on some proper route building - coming back to the M80 and continuing the line to Stepps and Gartcosh Junction along with the Busby area.

I've also made some enhancements to the "route origin move" tool I developed to do some other things - like mass batched asset swaps, with the ability to swap single assets for multiple assets (picking them at random - good for trees etc), while resizing and rotating (only 90/raising them etc too if desired.  I'll be using this to experiment with replacing the ageing Kuju trees etc I have in the route with the more recent 3D ones.  It can be done on a per-tile basis too so it's possible you'll see updates creep in to future versions bit by bit, perhaps along with updated modernised OLE (again, per tile, so you might not see it all updated at once).  None of this is in this recent version though and it may be several months yet before any of it creeps in to released versions, so don't hold your breath!

Finally, for those who do not want the large merged route, a version of Suburban Glasgow Phase 5.2 will continue to be available in the Older Versions section of the website.

So I think that's it for the moment (until I remember and come back and post some more!).  Enjoy the latest phase and please let me know how you get on!


Wednesday, 31 July 2019

Good evening!  Well, it has been a long time, hasn't it?

So I've learned a good bit more about working on huge routes since the last post!  Basically, the route editor is every bit as capable for huge routes as it is for small routes, however capable you think that might be.  Other than the age it takes to save Tracks.bin, it performs pretty much exactly the same and is perfectly adequate.

Now the Scenario Editor on the other hand, was not designed for this!  Goodness me, no chance.

Basically, the reason it's taken so long to get to this stage is that it has taken a long time to get the scenarios ready due to limitations in the editor.  It's always been the case that you try creating and testing a scenario, something doesn't work like an AI doesn't move as expected, you fix it, start again and so on and so forth until the scenario is ready.  But for scenarios that can last up to eight hours this just isn't feasable!  Thankfully I didn't come across an error seven hours in to the Alcan scenario or else I'm sure my PC would have been thrown out the window.  However, I did have to restart the 6Y15 and 1Y44 scenarios several times, several hours in to them, so it's a very slow and frustrating process.

Anyways, we're here now, so here are some screenshots from the West Highland Line scenarios.

Starting with 1Y44 - from Mallaig to Queen St.  Passing the Jacobite at Glenfinnan:

Next up was a 1980s Class 37 hauled service from Fort William to Queen St, using the new Armstrong Powerhouse Class 37:

6Y15, the TTA wagons run to Fort William Yard in winter.  Passing Red Road (ok, it's demolished, I've taken a bit of route-builders-license here!):

....Helensburgh Upper, at the start of the West Highland Line:

....and passing Corrour:

Finally, 6S45, the Alcans scenario.  Thankfully this was a straightforward test!  At Craigendoran Junction: Horseshoe Bend:

....crossing Rannoch Moor:

....west of Tulloch:

....and finally, working the Alcan Smelter itself:

So for the actual release, I'm hoping to get the next full version released as early as next week.  However, if anyone wants to help testing scenarios in the meantime, I can give access to the pre-release version just now!  This offer is also available to anyone that wants to start creating their own scenarios.

Watch this space and I'll update you when the next release is ready!

So in other news... :-)

I'm delighted to say that I'm getting a bit of help with the route these days.  Not just for scenarios and testing, but even route building is getting to the stage now where it's not just me.  So introducing Callum Gordon, who will be adding in the scenery to the line from Stirling to Alloa.  This is scheduled to be part of Phase 6.1, approximately towards the end of the year, which makes the scope now:

- Springburn to Gartcosh and Coatbridge
- Busby to East Kilbride
- Stirling to Alloa

I'll give Callum access to this blog as well so he can give an update from time to time too.

Finally, I've created a new section on the website for Forms outlining key information for the more involved scenarios.  This is at:

and is already available so you can get an idea what the new/extended scenarios are going to be like. :-)

So I think that's it this time.  Take it easy!

Sunday, 23 June 2019

Hello again...  I've decided to make an additional blog post to address several questions I've been getting since making the merged route...

These questions all revolve around enhancements and extensions, and whether or not I plan to do this and that.

So let me break everything down...  For potential changes, there are four types:

1) things I plan to do
2) things I might do eventually
3) things I'd love to do but probably never will
4) things I have no intention of doing

It all sounds pretty obvious, but let me give you a different list now. :-)

Here is the list of things I plan to do after the big merge is complete:

- create scenery from Springburn to Greenhill Lower (about 9 months)
- create scenery from Busby to East Kilbride (about 3 months)
- create scenery from Airdrie to Newbridge Junction via Bathgate (about a year)
- create scenery from Carfin to Midcalder Junction via Shotts (about a year)

So when someone asks me if I'm going to do things like electrify the Edinburgh to Glasgow line, recreate the route with easements where there are none (EtoG, WCMLNorth, GARL), recreate the electrified sections with newer OHLE, replace the older foliage with newer versions etc etc, the first question I would ask is, exactly when do you mean?  Are you asking if I'll drop my current plans and do this instead then I'm afraid the answer is definitely no.  If you're asking if I'm going to do it in 3 years after all the other stuff is done, then, well, that's 3 years from now - I have no idea what I'll be doing!!

So the answer to all these things is somewhere between 2) and 3).  I would like to do all these things, but I'll not be doing them any time soon.  But three years from now when all the other stuff is done? Who knows!

The only thing that might change here is if someone else offers to do some of the updating instead of me, leaving me with time to do the stuff I plan to do.  This might work for some (but not all) updates, but it would be severely limited by a number of things:

- The Tracks.bin file, which is one single file, can only be updated by one person at a time.  This means that if I released the file to someone to be updated with this and that, then it's not available to me to work on during this.  As I'm hammering changes to the file left, right and centre just now, this isn't really practical!  This rules out other people making OHLE changes, for example.  Also, significant track changes (easements etc) are likely to break existing scenarios so I'd be hesitant to allow it at all.

- I have reuse permissions for the parts of the route that I have not created myself (all of it except Suburban Glasgow, basically).  This has been given with the caveat that I use the Workshop to distribute it, which means I cannot use my own custom assets, or for that matter, any assets that are not on Steam.  This rules out quite a lot, unfortunately, like the use of custom OHLE or any redesigned nameboards or other items that people might have created.

- I've had a few people offering me some changes and updates they've made to WCMLNorth or Edinburgh to Glasgow to make them a bit more up to date.  However, once a route has been merged in to another route, it effectively becomes part of it and cannot be merged again.  Therefore, I'm afraid I cannot accept changes made to the core routes that are contained in the merge.  I'd need to know about and include the changes before doing the original merge for this to work!

But despite everything I've just said here, there is scope for some updates to be done by other people, if anyone was so inclined.  If someone offered to do pure scenery updates to some of the merged in routes (to specific tiles, with no track changes, keeping in line with the look and feel of the route in general) then I'd certainly consider it.  And of course, the scenery part of the route building itself is now open to others, with the Alloa line already in development by Callum Gordon!