Railworks America

Is there a scenario pack available for this route?

None that I am aware of. Quick Drive is your best bet for now. I am working on some scenarios but it'll be a while.

wacampbell wrote:None that I am aware of. Quick Drive is your best bet for now. I am working on some scenarios but it'll be a while.

Thanks for the reply Wayne. I'll just hop into OR and play with the London & Port Stanley.

I created a simple timetable of CVP Trains (see attached). If you would like a copy of the Excel file, PM me. I also have a Switchlist Generator file setup for the CVP.

Harry

Very cool Harry. I'll try to develop some scenarios around it.

This is a heads up to anyone planning to publish scenarios for the CVP. I have made a few minor track changes which will be released soon. The changes haven't impacted any of my scenarios ( eg - added sidings - nothing was removed ). But before I release these changes and hopefully lock down the track network, I thought I'd see if any others have come across track problems. For those writing scenarios, are there any problems or annoyances with the track layout you'd like to see fixed?

Wayne

PS - Harry, did you happen to do a train graph for that timetable?

PPS - here are the changes I"ve made so far:

- added drill track at Panaska so CVP can switch without fouling the main
- added a two track coach yard at Columbia to facilitate servicing and making up trains
- added a separate RIP track and MOW storage at Columbia
- shifted the Adam's bay dock spur to simplify turning passenger trains on the wye

Wayne,

I'm preparing a detailed answer to your track network update - please check PM

À Bientôt, QcRail

QcRail wrote:Wayne,

I'm preparing a detailed answer to your track network update - please check PM

À Bientôt, QcRail

Well, not quite as you have deactivated your private mail

These proposals reflect a very personal approach to scenario creation (and I'm very far from being a guru - not like painting), but I'm sharing a few changes that I have made and use.

1. Adams Bay : a fuel pumping station for diesel service with easy road access,
a crossover to bypass freight cars on yard holding track (give access to rear industries while having cars on wait)


2. Columbia : a new industrial spur. My choice is the Land'O Lakes Creamery. It could be a brewery


3. Grand Bend : 2 crossovers to quickly access the Foundery yard complex (for longer trains and modernizing scheme). As is the network is quite coherent as it provide a clear seperation and longer shunting manouvers.


4. Panaska : crossovers to holding yard OUPS cannot go beyond 5 attachments

Thus... enjoy while I finish the last proposal
QcRail

These are good ideas. Keep it coming.

Hi Wayne,

4. Panaska : crossovers to holding yard + 2 short spurs for temporary shunting...


As you can see, I've added a few new markers to maximise scenerio creations



A final tought: increase the numbers of portals. My meager experience has showned that if I want to increase traffic in both directions, new portals would help to concentrate consist and get rid of them after the event has passed. It is important on a short route. (I may be in left field on this one - as I may not program AI properly ). Nonetheless, my list:
1. Around mile oost 73 (between Juliet and Hope),
2. East of M.P. 73 near Columbia, especially for westbound trains,
3. Migrate existing Portal 5 closer to Columbia and add a new one near the East of the Yale Y-junction, thus freeing action at Panaska and not to have to wait until Portal2.

... and if you want to please the crowds you could create a new industrial complex for a brewery, as we have a large fleet of reefers (long summer in post confinement )

Thus is my early X-mas list, and THANKs Wayne for a beautiful route.

Have a nice summer in BC, QcRail

Thanks for the ideas.

I didn't do a timeline.

Harry

wacampbell wrote:This is a heads up to anyone planning to publish scenarios for the CVP. I have made a few minor track changes which will be released soon.

As I put this together I realized the changes were mostly minor and not really worth breaking existing scenarios under development. I will keep the track network as it was first released. Of course everyone is welcome to add their own personal tweaks and changes, but to encourage scenario builders they can consider the track network 'locked down'.

wacampbell wrote: ...but to encourage scenario builders they can consider the track network 'locked down'.

Good to know. Thank you.