Difference between revisions of "Callback: Change vehicle properties"
(→Change vehicle properties (36): Aircraft range) |
(rename passenger/mail capacity to primary/secondary cargo capacity) |
||
| Line 76: | Line 76: | ||
|||{{ottdp|0.6|2.6|ttdprev=r1507|ottdrev=r9678}}||0E (Running cost factor)|| |
|||{{ottdp|0.6|2.6|ttdprev=r1507|ottdrev=r9678}}||0E (Running cost factor)|| |
||
|- |
|- |
||
| − | |||{{ottdp|1.0|no|ottdrev=r19218}}||0F ( |
+ | |||{{ottdp|1.0|no|ottdrev=r19218}}||0F (Primary cargo capacity)||See also [[Callbacks#Refitted capacity callback 15|callback 15]] |
|- |
|- |
||
| − | |||{{ottdp|1.0|no|ottdrev=r19218}}||11 ( |
+ | |||{{ottdp|1.0|no|ottdrev=r19218}}||11 (Secondary cargo capacity)|| |
|- |
|- |
||
|||{{ottdp|1.2|no|ottdrev=r22713}}||1C (Custom cargo ageing period)|| |
|||{{ottdp|1.2|no|ottdrev=r22713}}||1C (Custom cargo ageing period)|| |
||
| Line 93: | Line 93: | ||
Before r1758 (both 2.5 and TTDPatch 2.6), [[Callbacks#Change vehicle properties (36) |callback 36]] was sometimes called with the 40+x and 80+x variables unavailable when they should have been available, or with not all 80+x variables properly initialized, causing some 40+x variables to be unsafe. |
Before r1758 (both 2.5 and TTDPatch 2.6), [[Callbacks#Change vehicle properties (36) |callback 36]] was sometimes called with the 40+x and 80+x variables unavailable when they should have been available, or with not all 80+x variables properly initialized, causing some 40+x variables to be unsafe. |
||
| − | About the capacity properties see also the summary page about |
+ | About the capacity properties see also the summary page about [[VehicleRefitting|vehicle refitting]]. |
[[Category:Callbacks]] |
[[Category:Callbacks]] |
||
Revision as of 13:24, 28 January 2012
Change vehicle properties (36)
This common callback allows modification of certain properties of a vehicle for which there exists no specific callback (like CBs 10, 11, 12). The low byte of variable 10 holds the property number from Action 0.
The following properties are supported:
| Feature | Version | Property | Remarks |
|---|---|---|---|
| Trains (00) |  1.2  GRFv8 |
07 (Load amount) | See also callback 12 |
0.6  2.5 |
09 (Speed) | ||
| 0.6 2.5 |
0B (Power) | ||
| 0.6 2.6 |
0D (Running cost factor) | ||
| 0.6 2.6 |
14 (Cargo capacity) | See also callback 15 | |
| 0.6 2.5 |
16 (Weight) | ||
| 0.6 |
17 (Cost factor) | ||
| 0.6 2.5 |
1F (Tractive effort) | ||
| 1.2 GRFv8 |
21 (Short wagons) [1] | See also callback 11 | |
 |
22 (Visual effect & powered wagons) | Changeable via callback 10 | |
| 0.6 2.5 |
25 (User data) | ||
| 1.2 |
2B (Custom cargo ageing period) | ||
| Road Vehicles (01) | 1.2 GRFv8 |
07 (Load amount) | See also callback 12 |
| 1.0 |
09 (Running cost factor) | ||
| 0.6 |
0F (Cargo capacity) | See also callback 15 | |
| 0.6 |
11 (Cost factor) | ||
| 1.1 |
13 (Power) | ||
| 1.1 |
14 (Weight) | ||
| 1.1 |
15 (Speed) | ||
| 1.1 |
18 (Tractive effort) | ||
| |
21 (Visual effect) | Changeable via callback 10 | |
| 1.2 |
22 (Custom cargo ageing period) | ||
| 1.2 GRFv8 |
23 (Short wagons)[1] | See also callback 11 | |
| Ships (02) | 1.2 GRFv8 |
07 (Load amount) | See also callback 12 |
| 0.6 2.6 |
0A (Cost factor) | ||
| 0.6 2.5 |
0B (Speed) | ||
| 0.6 2.6 |
0D (Cargo capacity) | See also callback 15 | |
| 0.6 2.6 |
0F (Running cost factor) | ||
| |
1C (Visual effect) | Changeable via callback 10 | |
| 1.2 |
1D (Custom cargo ageing period) | ||
| Planes (03) | 1.2 GRFv8 |
07 (Load amount) | See also callback 12 |
| 0.6 |
0B (Cost factor) | ||
| 0.6 2.5 |
0C (Speed) | ||
| 0.6 2.6 |
0E (Running cost factor) | ||
| 1.0 |
0F (Primary cargo capacity) | See also callback 15 | |
| 1.0 |
11 (Secondary cargo capacity) | ||
| 1.2 |
1C (Custom cargo ageing period) | ||
| 1.2 |
1F (Aircraft range) |
- ↑ 1.0 1.1 These properties may only change their value when the vehicle is inside a depot. That means, if your vehicle supports autorefit and refitting can change these properties, you must use callback 15E to prevent the refitting.
Most properties will only change when the vehicle is bought, serviced (enters a depot), visits a station or on loading of a saved game. Other ones such as TE are called every time a TE calculation is run.
If the callback fails, the corresponding value from the action 0 property will be used. The callback is always used when defined, no bit in the action 0 property needs to be set to activate it.
Before r1758 (both 2.5 and TTDPatch 2.6), callback 36 was sometimes called with the 40+x and 80+x variables unavailable when they should have been available, or with not all 80+x variables properly initialized, causing some 40+x variables to be unsafe.
About the capacity properties see also the summary page about vehicle refitting.
