nilsi wrote:
Most German Locos have been used for both services during their lifetime.
That´s not correct. Although you´re right that most german locomotives have indeed been used both for passengers and freight "during their lifetime", new engines were definitely developed either for express passenger service, passenger service or freight service. Only in later years, when newly developed locomotives entered the scene, engines formerly used in express passenger services were "downgraded" to passenger service and those in passenger service entered freight service (where applicable).
This is an overall feature in German railways, both in DRG and in DB times, and the DBXL has and will reflect this behaviour to a large extent.
dev|ant wrote:
> The problem is that in steamer GRF ID XX would be a passenger loco, while in the other it may be a freight loco, the EMU
> in the third. What to do?
> I mean we can't use ID any more. We need to have some flag to check?
In this case the most useful way to use the 1D callback is with the engine checking the cargo type of the wagon.
There are more ways to ensure usage of the correct coaches and wagons in existing sets. E.g., in DBXL I´m checking for cargo, veh-ID, prop25, ..., and quite a number of other things (can´t look into it ATM).
The only way to achieve something like this (loading multiple vehicle .grfs with the same veh-IDs) properly would be to make it completely transparent for the .grfs. Other than that, more problems would be generated with people having trouble with the sets.
And BTW, TTDPatch has a sophisticated "Graphics Ressource Management" system (GRM), which allows .grfs not only to check the availability of ressources but also allows them to check the
exclusive availability. This is a phantastic feature to disclose known incompatibilities beforehand, but it seems to be wasted in your current approach for OTTD.
regards
Michael