Page 1 of 1
| Inherit Train Category properties by default 10/03/2018 at 23:03 #106629 | |
9pN1SEAp
1181 posts 
|
Hi, When creating timetables, it would be nice to inherit the Length, MaxSpeed, Freight Lines etc. characteristics from the Category when it's been used, rather than having to set all the properties for every single TD. Because if you don't specify, a train has a speed of zero and length zero! I am thinking this is a loader function rather than per-sim changes? Thanks Jamie Jamie S (JAMS) Log in to reply |
| Inherit Train Category properties by default 10/03/2018 at 23:13 #106630 | |
pedroathome
916 posts |
9pN1SEAp in post 106629 said:Hi,If you open up the timetable list, goto Train Types, you can set up your train types there. You can then select which ever train type you feel most appropriate for said train. James Log in to reply |
| Inherit Train Category properties by default 11/03/2018 at 17:47 #106655 | |
|
9pN1SEAp
1181 posts
|
This is true, especially if you're doing them manually. I'm using an XML creation tool to import mine from RTT, where the Timetable entry has the Category field, but nothing about the Catgeory is inherited by default.
Jamie S (JAMS) Log in to reply |
| Inherit Train Category properties by default 11/03/2018 at 23:14 #106669 | |
DaveHarries
1285 posts |
I think I see what is being got at here and I think it is this. As I read it Jamie's suggestion would be that, say, you had a train code 1A01 (for example) and it was terminating on sim with its next working being 1E05 then the characteristics (category, max speed, etc.) of 1A01 could automatically pass on to 1E05. Not a bad idea: would speed things up with making timetables perhaps. Dave Log in to reply |
| Inherit Train Category properties by default 12/03/2018 at 08:28 #106675 | |
Meld
1111 posts |
So what your really asking for is the ability to Select the next working and copy stock. That being said it only takes a couple of seconds in the TT editor with the use of a Simplifier filtering by platform to sort. One little tip to save loads of scrolling time, eg. in Wembley Mainline Virgin Services can quickly be done by placing a 1 prefix to 11 Car 390s, 2 to 9 Car 390s, 3 to 5 Car 221s and 4 to 10 Car 221s. This brings them to the top of the traintypes so you can quickly and easily edit/insert without all the scrolling down, just remember to remove the prefix when your done. Same applies to 4/8/12 car 350s and so on Passed the age to be doing 'Spoon Feeding' !!! Log in to reply |
| Inherit Train Category properties by default 12/03/2018 at 19:18 #106694 | |
GeoffM
6376 posts |
DaveHarries in post 106669 said:As I read it Jamie's suggestion would be that, say, you had a train code 1A01 (for example) and it was terminating on sim with its next working being 1E05 then the characteristics (category, max speed, etc.) of 1A01 could automatically pass on to 1E05.Can 9pN1SEAp please confirm whether this is indeed what is meant, as it doesn't tally with the original post, but does make more sense? SimSig Boss Log in to reply |
| Inherit Train Category properties by default 12/03/2018 at 22:22 #106708 | |
|
9pN1SEAp
1181 posts
|
Hi, I was thinking mainly in the XML, you'll have defined a Catgeory such as: <TrainCategories> <TrainCategory ID="Class143_Pacer"> <Description>Class 143 (Pacer) 2-car</Description> <AccelBrakeIndex>3</AccelBrakeIndex> <IsFreight>0</IsFreight> <CanUseGoodsLines>0</CanUseGoodsLines> <MaxSpeed>75</MaxSpeed> <TrainLength>31</TrainLength> <SpeedClass>16</SpeedClass> <PowerToWeightCategory>0</PowerToWeightCategory> <DwellTimes> <RedSignalMoveOff>1</RedSignalMoveOff> <StationReverse>60</StationReverse> </DwellTimes> <Electrification>D</Electrification> </TrainCategory> And then you create a TT entry: <Timetable> <ID>2A57</ID> <UID>C56297</UID> <Description>$template</Description> <Notes/> <Category>Class143_Pacer</Category> But by default the Timetable node doesn't have length/speed/class etc - you have to add it all over again. However it would also be nice for the scheduler to automatically copy the Category into a TD referenced by Next_Train. You'd only have to define it for trains with an Entry or Seed, which would save a lot of time 
Jamie S (JAMS) Log in to reply |
| Inherit Train Category properties by default 12/03/2018 at 22:34 #106711 | |
postal
5265 posts
|
9pN1SEAp in post 106708 said:However it would also be nice for the scheduler to automatically copy the Category into a TD referenced by Next_Train. You'd only have to define it for trains with an Entry or Seed, which would save a lot of time :)How would that work for trains with joins or splits? Presumably you would need to add something into whatever method you used to carry the data forward to negate the automatic process if there was a detach or join in the first trains schedule. And as a result of that would need some sort of flag to remind you to manually enter the new category. As ever, the devil is in the detail. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |
| Inherit Train Category properties by default 12/03/2018 at 23:10 #106712 | |
|
GeoffM
6376 posts |
9pN1SEAp in post 106708 said:But by default the Timetable node doesn't have length/speed/class etc - you have to add it all over again.Ah, so it's the import that is the problem. I have noticed that with some other data I was playing with but assumed it was faulty data rather than the import. I'll look at the code then. 9pN1SEAp in post 106708 said: However it would also be nice for the scheduler to automatically copy the Category into a TD referenced by Next_Train. You'd only have to define it for trains with an Entry or Seed, which would save a lot of time :)As John says, there is more to it than that but for simple Nexts we could perhaps improve things a bit - though in the editor (ie after import). SimSig Boss Log in to reply The following user said thank you: 9pN1SEAp |