What Type Of Gameplay Do You Prefer? Scenarios/timetable/journey Mode

Spikeyorks, I'm afraid I can't go into the internal workings, but thank you for the detailed post describing what you view as the major issues with the way Scenario Planner currently works. I'll look at raising the points internally and see what can be done about everything you raised.

The reason I took 'umbrage' with your post was because, as a developer, your implication regarding scenario work was that we don't try. I can assure you that isn't the case at all, and we work extremely hard week in and week out to produce content that we believe the community will enjoy. When we miss the mark, we do feel a bit crestfallen because we feel our efforts went to waste.

This is why threads with constructive suggestions on how we could improve are so important.

 

Overall, service mode is my favourite way to play. I do enjoy playing scenarios too as long they’re something unusual that you wouldn’t normally see playing the timetable mode such as the pickup/drop-off goods on Peak Forest, rescuing a failed train, stuff like that.

One thing I’d like DTG to address is journey mode. I personally think that services completed from the service mode timetable should be ticked off in the journey screen, just like how it works for tutorials and scenarios. While it is useful for new players and those who don’t want to spend long deciding what service to play to have a curated playlist by the developer, it also makes those of us who have already completed those services in timetable mode have to play them again from the journey menu if aiming for 100% completion. This means you either have to play some services twice which is a huge time sink on some routes, or you have to play journey mode first to get those services ticked off, I often find journey mode outstays it’s welcome after a handful of runs.

Marking services as complete in journey if done in timetable mode will make journey mode completely optional. I feel this makes for a more player friendly experience, those who play journey can still enjoy it while those who don’t can ignore it and still have their completion progress marked correctly.

 

Thanks for reading my post. It was a long one (and I now realise that I missed about another couple of key points involving Saves and Portals......might add them briefly on the end of this).

The cliche is "A bad workman blames his tools"........in this case it might be the case that the DTG team that works on scenarios SHOULD blame the tools made available to them. Because it is the tools, or the lack of them, or the poor design of them, that is stopping the community from being able to create realistic scenarios. (Assuming the DTG team actually use the same tools we get given?).

Rob my guess is that you create your scenarios by using the full editor and not by using Scenario Planner. Would that be correct? If so then might that explain why DTG, or even your good self, has lost track of how little Scenario Planner can do in its current state? If you don't use the tool yourself then how can you know if it is working correctly or not?

As an example of the inadequacies of the current system here is the breakdown of the paths available to the community to use on the most recent Manchester Airport route. Paths are what makes Scenario Planner work (or not work).

The route shipped with a total of 239 paths available for use in Scenario Planner. (For those that don't know that means there are 239 different 'routings' that you can allocate to either the Player Service or any AI services when designing your scenario). This is, actually, a very impressive number of paths. You would think I would be pleased by that wouldn't you?
Well let's see the breakdown of that number.

1) Of the 239 paths a total of 28 are runs from Piccadilly (all platforms) to Alderley Edge via either the slow or fast lines.
2) Another 28 are runs from Alderley Edge to Piccadilly (all platforms) via either the slow or fast lines.
3) 14 paths are runs from Piccadilly (all platforms) to Ashburys (on the Glossop line).
4) 14 paths are runs from Ashburys returning to Piccadilly (all platforms).
5) A whopping 56 paths run from Piccadilly (all platforms) to Manchester Airport (all platforms).
6) And another 56 paths run from Manchester Airport (all platforms) to Piccadilly (all platforms).
7) 8 paths run to and from Alderley Edge to either the sidings there or the portal at Chelford.
8) 8 paths run to and from Piccadilly 13/14 to Oxford Rd (all platforms).

So out of the 239 paths made available for use in Scenario Planner a massive 212 of them (or 89%) are just through runs from one end of the route (Manchester + Portal) to the other end (Alderley Edge + Portal or Airport) with a slight diversion to Ashburys on the Glossop line.

Of the 27 paths that are left a total of 12 of these are used up bring Cheadle Hulme and Hazel Grove branches into play. (Not necessarily a bad thing as it adds variety to Stockport but that does mean there are now only 15 paths left for "creativity" purposes and since paths are usually paired then that really means only 7 routings are left).

How many of these remaining 7 routings go to/from Longsight depot? - NONE. (even though there are 45 sidings available).
How many of these routings go to Ardwick depot? - NONE. (even though there are 19 sidings / markers available).
Manchester International Depot? - NONE
Stockport Sidings? - NONE
Manchester Piccadilly Sidings or Loops? - NONE
As a result all the above areas of interest are unavailable to Scenario Planner. Why?

This, together with the other issues that I have already highlighted, is why Scenario Planner isn't fit for purpose. The fact that this isn't picked up at the Design Point or at Beta Testing suggests to me that DTG have little interest in Scenarios. What other reason could it be?
*** IMPORTANT NOTE - EVERY route is like this. I just picked Manchester Airport because it is the newest route and, therefore, demonstrates current DTG thinking re route releases.

So Rob here is the big question. If "everyone is trying" how does things like this slip through the net each time? Every route is like this so DTG aren't learning from their previous errors / oversights.

My guess is that it is because you and your team use the full Editor and, possibly, never even look at Scenario Planner. You can't do......because if you did then the above, and all my other points, would whack you between the eyes every single time.

 

You probably won't know this but I have actually produced work for DTG in the distant past and I am aware of the 'restrictions' that are placed on the Creative thought process when you make your scenarios. I'm not intending to criticise anyone by talking about Scenario Planner and am certainly not implying that you have "missed the mark" with any scenario that you have produced. It is the tools (or Scenario Planner itself) that I am criticising. Perhaps you are responsible for these, perhaps you are not. Either way someone isn't reviewing them and keeping them up to date.

Couple more points;

1) PORTALS - Whilst portals let you stack trains inside them they will only let them depart in train length order. A shorter train will never be allowed to leave a portal before a longer train. In fact, give a very short train the earliest departure time from a portal in a scenario and you might never see an AI service at all. Why does that happen?

2) PORTALS (2) - Stack two different services in a portal that have similar couplings and they will appear coupled together departing at the time of the earliest service. (24 car Class 710 rake on the C2C lines at Barking anyone?) This, and point (1) severely restricts what you can do with Portals. So why not do away with the concept of portals and replace them with a small fan of hidden sidings. That way we could have AI services depart in whatever order we wanted.

3) SAVES - Haven't tested this recently but it always used to be the case that if you restarted from a Save in a Scenario then only the Player Service picked up the new restart time. This meant that all 'earlier' AI services were now stuck because the game now viewed them as starting before the start time of the 'new' Scenario.
Also try and restart a modded scenario from a save and it is a straight Crash to Desktop.