You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It it useful for locos, that carry no cargo, to specify several subtypes.
May be I did a bad description, let me try to make it more detailed.
Usage 1)
I have a loco, let's say "5XXX Series".
F2 would mean, for example
0 - 5000
1 - 5001
... and so on
While life of production it is available, let's say
5000 in 1950-1960
5001 in 1955-1965
5002 in 1957-1958
5003 in 1961-1978
5004 in 1962-1980
in 1961-th, for example, initial value of F2 should be 03, that I supposed to set with CB 36, and disallow it to be 0 and 2
May be it can be done in some other way, but I have no idea which one, except use separate ID for each model (and here we get the limitation for ARvs to 128 IDs to attach.
Usage 2)
When the loco is build while testing the model, it has to have one view, while when bought on market being available for every one - the other. I have no idea how to store it except var F2. The year of build does not fit, because during first part of the year it is exclusive, while during last one - not
Bringing in a feature and then not even using it for what it aims to do (setting cargo subtype for a vehicle without cargo) doesn't sound like a valid solution to the problem
George opened the ticket and wrote:
Reported version: trunk
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/4400
The text was updated successfully, but these errors were encountered: