also du brauchst ne neue aplha, das DB Set UND das DB Set XL
Und du musst das in der newgrf.cfg auf ne hohe priorität setzen(also wentweder ganz unten oder ganz oben hinne, weis ich gerad nich)

Zitat:How to install the DB set XL?
Preliminaries

The DB set XL is available in a DOS and in a Windows version ("dbsetxl.grf" resp. "dbsetxlw.grf"). Just copy the appropriate DB set XL grf file into the "newgrf" directory under your TTD main directory and add the entry "newgrf/dbsetxl.grf" resp. "newgrf/dbsetxlw.grf" to your "newgrf.cfg" resp. "newgrfw.cfg" file.

The actual version of the DB Set XL is v0.64, grf-ID is 6D 62 04 01 and it´s of april 4th, 2004.

You´ll need TTDPatch version 2.0.1 alpha 19 (or higher) to run this version.

This is because since version 0.6 the DB Set includes a set of freight wagons specific to the german railway companies DR and DB which will override the original freight wagons and those which are added by the CargoSet. The novel freight wagon scheme makes heavy use of the new patch feature of "wagon refitting" which is only available since TTDPatch version 2.0.1 alpha 12. In addition, there are many other new features which are available only since TTDPatch 2.0.1 alpha 14. In addition, realistic tractive effort calculation is available only since alpha 19.

Because of the need to preserve the 0.5x versions of the DB Set for the benefit of people which are not using the latest alpha versions of TTDPatch (and in need to differentiate between both DB Set versions) a different grf-ID had to be introduced for the XL version.

Therefore, you´ll have to issue a "cht: graphics 6D 62 04 01" command to load the new DB Set XL if you want to use savegames which have been saved under the previous DB Set and you have "saveoptionaldata" set to "on" in "ttdpatch.cfg". If you don´t use "saveoptionaldata" a "cht: graphics" would be sufficient.

It would be also a very good idea to remove all those old wagons because they don´t fit well with the new ones, at least because they have different offsets than the new wagons.



Configuring "newgrf[w].cfg"

Grf files of different vehicle sets can only coexist if they´re for a different climate. This is due to the internal mechanism how a grf file is loaded and activated by TTDPatch. E.g. TempSet and ArcticSet could be both included into "newgrf[w].cfg" but only one of them would be activated, depending on the chosen climate.

Because the DB Set XL, the DB Set v0.5 and the TempSet are all intended for the temperate climate, you could encounter difficulties with this mechanism. Because the DB Set XL is a full set it uses all available vehicle IDs, but e.g. the TempSet does not. Insofar, you would get only the expected behaviour when having the line "newgrf/dbset[w].grf" after the line "newgrf/tempset[w].grf", but not vice versa!

In the latter case, the TempSet vehicles would overload those DB set XL vehicles with the same identifiers resulting into an (unwanted) mix of both sets.

To prevent this, especially with additional train sets for the temperate climate to come, a special mechanism has been built into TTDPatch. This mechanism prevents a vehicle set from being loaded if another vehicle set for the same climate has been loaded before.

Because of the way this feature is implemented it´s only possible to skip loading of further sets for the same climate, i.e. always the first set of the same climate will get activated. If there is more than one set for the same climate in your "newgrf[w].cfg" you have to take care of order of entries in "newgrf[w].cfg" yourself.

However, because this mechanism relies on a joint behaviour (mutual exclusive sets have to check against each other´s grf-ID) it´s only possible to set up such a scheme to include a new set by modifying all those other sets too (only to include the grf-ID of the new set).

Because this procedure isn´t always suitable with regard to the novice user, alpha 14 introduces an additional mechanism for grf-handling which enables deactivation of incompatible grfs.

The DB Set XL uses this feature to cooperate with following sets:
DB Set v0.5 (both 5.0a and 5.0b, grf-ID 6D 62 04 00)
TempSet v0.4 (grf-ID 6D 62 02 04)
CargoSet (both v0.4 and v0.5, grf-ID 6D 62 03 05)

Because the DB Set XL is able to overwrite previously loaded grfs and to reset the list of vehicle IDs which could have been already re-ordered by a previously loaded grf file it´s best to have this order of grf entries in "newgrf.cfg":

.
newgrf/dbset.grf
newgrf/tempset.grf
newgrf/cargoset.grf
newgrf/dbsetxl.grf
.

When deactivating grf files the DB Set XL issues a warning message to give the user a hint for re-arranging his/her newgrf.cfg file.

E.g. if you´re using

.
newgrf/dbset.grf
newgrf/tempset.grf
newgrf/dbsetxl.grf
newgrf/cargoset.grf
.

the warning message "Deactivating CargoSet. Must be loaded before DB Set XL." is given. This is because both the CargoSet and the DB Set XL contain freight wagons, hence those loaded first would be overwritten by the set loaded afterwards. OTOH, because there are no cargo trucks in the different DB Sets you´ll still need the CargoSet for availability of trucks.

Therefore, to get the DB Set XL running and to include the trucks of the CargoSet you should have the DB Set XL entry after the CargoSet entry in "newgrf[w].cfg". If you have the CargoSet´s entry after the DB Set XL entry, it would be deactivated to avoid confusion. Of course, this would result in having none of the CargoSet´s trucks available.

OTOH, if you want to use one of the older DB Set versions you´ll have to comment out the DB Set XL entry in the "newgrf.cfg" file because it cannot be overwritten by any of the other grfs, neither by the old DB set versions nor by the TempSet.