## Feature #3828

### Make unit conversions work with non-constant values

Status: | Confirmed | Start date: | 2012-03-15 | ||
---|---|---|---|---|---|

Priority: | Normal | Due date: | |||

Assignee: | - | % Done: | 50% | ||

Category: | - | ||||

Target version: | - |

**Description**

calling nmlc test.nml on the attached NewGRF gives a

nmlc: "test.nml", line 53: Unit conversion specified for property, but no constant value found

while it should just use the parameter value (without conversion probably) as the property value.

Mind, if that is solved, the grf won't build due to missing graphics.

### Associated revisions

Change #3828: Allow the 'nfo' unit to be used with non-constant values.

Change #3828: Allow the 'nfo' unit to be used with non-constant values.

Change #3828: Allow the 'nfo' unit to be used with non-constant values.

Change #3828: Allow the 'nfo' unit to be used with non-constant values.

Feature #3828: Unit conversions for non-constant values.

Feature #3828: Unit conversions for non-constant values.

Change #3828: Rework the RV speed prperty, so it works with non-constant values.

Change #3828: Rework the RV speed prperty, so it works with non-constant values.

### History

#### #1 Updated by Hirundo about 5 years ago

**Tracker**changed from*Bug*to*Feature***Subject**changed from*named parameter not accepted as property value*to*Make unit conversions work with non-constant values*

Changed to a feature request.

To make this work the floating-point arithmetic should be replaced by fixed-point arithmetic (i.e. multiply, then divide).

This fixed-point arithmetic can then be done at runtime.

#### #2 Updated by Hirundo about 5 years ago

**% Done**changed from*0*to*50*