Using parameters with DB Set doubles train prices?

[Dropzone]

I am having a rather strange problem with the DB Set. It seems that if I supply any parameters to the set (I was trying to enable random livery for tankers and steel wagons), the prices of all rail vehicles, and also rail depots, are exactly doubled. For example, if I have the line "newgrf/dbsetxlw.grf" in my newgrfw.cfg, then in the year 1950 a BR45 costs £25,000, and a rail depot £2,420. If I change the line to "newgrf/dbsetxlw.grf 6" (or any other parameter), the same BR45 will cost £50,000, and the depot will cost £4,840. Other vehicles (e.g. trucks) are NOT affected - neither are rail tracks or stations. Income from trains is also not affected. The change in prices doesn't seem to get saved in savegames - adding a parameter causes prices to be doubled even when you load a game saved without a parameter there, and vice versa.

I am using the Windows version of TTD. I have version 2.0.1 alpha 48 of the patch, and I am using DB set version 0.81. This problem happens even when the DB set is the only line in newgrfw.cfg. I have attached my ttdpatch.cfg file.

[Hyronymus]

Did you read the manual?

[Dropzone]

Yes... and unless I'm missing something, it doesn't say anything about this happening. The only thing it mentions about changing the price of trains is:

"If used with the "hard" setting for building cost the DB set uses real historical prices, at least for the early and medium engines but not for the modern ones - an ICE-1 would cost 50 million DM."

It doesn't mention anything to do with a connection between parameters and train prices - not even in the known bugs section.

[Patchman]

I believe the higher prices are what it should be by default. It might be a bug that you get the lower prices at all by leaving off the parameter.

[Dropzone]

Ah, okay - I hadn't thought about it that way round. Guess I'll leave the parameter there, then