![]() However it would require extra info in dat files - load/unload ability for certain cargo, and storage capacity for certain cargo. It happened to me that passengers enter the last car and stay on board forever, because they cannot leave the train.Īs to the type of platform, I would like it as option similar to separate cargo capacities - so that mail & passengers do not unload on cargo platforms and vice versa, perhaps with some more specialty platforms (bulk, oil, cars) available. Maybe some intelligence added - so that passengers/cargo enter only cars that they can leave later. Hello, it seems that three different issues poped up here.Īs to the length of platforms I would stick to current behavior - cars outside platform do not (un)load. We could also discuss if we should compare the platform to a wagon or have another approach where we specify goods on a platform and compare it to the goods loaded on a wagon, in a similar manner. If we can handle this per wagon the display could actually show that some wagons are empty before others are (nice eye candy). On a match the factor is added to the load/unload calculation. The idea is to compare each wagon's platform array against the the platform name. For more examples the Regesp for dummies will serve as a copy paste library for the most common cases. For those (I guess the majority) the ^ and $ are very simple to grasp and will get you very far. If we use regular expressions we can define quite advanced rules. The new platform array defines how the wagon would be accepted for a particular platform. Platform=No-Platform,- # The "No-Platform" is not supported. Platform=Platform$,100 # All platforms ending with "Platform" gets a 1.00 factor. #For those who are not so familiar with Regular expressions the same result can be achieved with multiple rules. This will match any platform ending with "Platform" but not beginning with "No-". # If we use the platform name as a regular expression we could create both simple # All unspecifyed platforms will not perform any loading/unloading. ![]() # Cars can ONLY be handled by a CarLoadingPlatform. Platform=No-Platform,200 # <- Built in platform type to specify "outside" platform # A passenger car loading platform gives a 1.60 penalty factor # A passenger platform gives a 1.00 factor ![]() # Here we specify the bonus/penalty for different platforms #".*(?could bring it one step further to also delay cargo unloaded/loaded on the wrong type of platform. In OpenTTD the load/unload time are significant increased for wagons outside the platform. It will contribute to gaming experience in a way that you need to build your platforms and convoys to match for best result. The question is - would this add anything of substance compared to our existing notional system or would it merely be cosmetic? I tend to incline towards the latter but can anyone suggest any real differences that this might make to the simulation that might justify the significant coding that it would require? What we do not have in Experimental is a system whereby the actual loading/unloading of packets of passengers, mail and goods is delayed based on a loading time factor. In Experimental, there is also a waiting time and (in the latest release candidates) a transfer time, but these figures are both used for journey time calculations for the purposes of choosing which route to take and the journey time tolerance. What is proposed is different to what we have in Experimental: in Experimental, there is a variable dwell time for convoys in stops (which is also now in Standard, with some small differences that are not relevant here) set by the pakset maintainers for each vehicle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |