Then, I will consult with others to refine the TT further and ensure it chains with Marylebone successfully. I am closing in on finishing the timetable. Newhampshires in post 145246 said: In December, I started working on a Leamington Spa & Fenny Compton timetable to chain with the below-mentioned Marylebone simulation. The Friday 13th addition to the bundle won't be complete by that time and will probably release in the autumn, possibly with a possible 2022 CTA schedule. Due to my want to release them at the same time, I anticipate that the 2021 timetable will be released at the same time as the intense timetable at the end of my work's spring term. If anyone has access to and can give me a copy of historical CTA L schedules that cover all the lines in the loop I would be greatly appreciative, but have come up short on the Googles and not finding a complete set & I don't want to hassle the busy CTA helpdesk with a request for this and don't know if I can file a FOIA from this side of the pond. This stupidity in the number of decisions and the want of trains to terminate-reverse when terminating at CLALAK, ADAWAB & HWLIB after traversing the junctions, which is exacerbated by the fact that there is no route programmed from the signals they now face (X16, X18 & X108) and no mention of the reverse happening to the user in game or in the wiki, instead of the expected and behaviour seen elsewhere of terminate-forward. Rfw in post 142785 said: Should I feel particularly self-loathing, I'm considering creating a 'Friday 13th' timetable variant using a butt ton of decisions to add a scaled down 'Gremins at Work' level of delays (increased dwell times) and simulated reduced power (by capping train max speed, acceleration type and weight) without the failures that'd render this sim unusable very quickly.The Friday 13th development has hit a bit of a snag in that my intended approach was to have each trip as an individual train, and use decisions to roll the dice on what bad thing should happen to the train (extended dwell to simulate the wrong kind of food trolley and potentially crippling loss of power), which if I remember my calculations rightly is 3 or 4 decisions per trip resulting in about ~70 odd permutations of a journey for each journey across the sim. The core element of this, the normal SSUx, So & Suo timetables are now complete to a standard that I'd be happy to release, but still am having issues with load time and autosaves at around 1m30s to load in from the menu - I guess SimSig isn't optimised for these operations when the timetable contains a silly 15183 possible trains where every train references a single decision deciding the day to run, does anyone else run into long load and save times with chunky timetables or can I blame it on my potato of a computer rfw in post 142785 said: This increases the theoretical maximum unique UIDs that can exist in a single timetable opening up the opportunity for a Project X esc 'chaos' timetable where I throw a ridiculous number of trains into the loop and hope for junction conflicts.I'm now play testing the first iteration of this intense timetable, I have noted a couple of changes in the early morning to improve flow and am considering reducing the number of trains in the morning peak as the queue at Clinton often stops new trains from entering the sim and in in danger of turning into a log jam puzzle, I wanted this to be an intense timetable for multiplayer use but may have overdone it a bit - I had 21 trains in the area earlier (see screencap) Any further info you can provide will allow us to run through the TT and test what's going on, even if you can run through the TT again yourself and take a save before the culprit train approaches that area and drop it into this thread.Update on Chicago Loop 2021 TT pack rfw in post 142785 said: I'm writing a 2021 timetable pack for the much under loved Chicago Loop. A user has 2 options in the telephone book for Longbridge Rover, 1. Are you sure that the slot you were given was the ARR/DEP and not the REC/DEP? Just to be clear, If you are only able to route to REC/DEP, then that has to be the slot you are given, otherwise you will be presented with a "A slot is required for this route" in your message box. When the slot is given, it will only allow you to set to the route for that slot. Snbower in post 147173 said: Hi, I was on the down slow, and could only set a route to 'DEP/REC' not, 'ARR/DEP'Could you tell me what Timetable you are running, just to see if we can reproduce the issue that you are having. How to route 6M37 into 'Austin Rover Plant ARR/DEP' at 01:17 #147175
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |