I want to summarize here which of the suggested features are likely going to make it into the upcoming version 1.2.2 (due to around Sunday, 27th September). Some of these suggestions have been posted here on the forum, others were sent to me privately.

If there is a thread for a subject listed here, use that thread to discuss further, otherwise, use this thread.


New variables in animated objects

It has been suggested to introduce some new variables in animated objects for various purposes.

hasPlugin:
Whether the train uses a plugin (1) or not (0).

acceleration:
The average net acceleration of the train in m/s². Useful for creating accelerometers.

accelerationOutput:
The average acceleration output of the train in m/s², corresponding to the motor force that tries to accelerate the train. Useful for creating ammeters.


Sounds in animated objects

It has been suggested to attach sounds to animated objects and to select the sound to be played, as well as to change pitch and volume.

[Object]
...
Sounds = FILE1, FILE2, FILE3, ...
SoundFunction = FORMULA
SoundPosition = X, Y, Z
VolumeFunction = FORMULA
PitchFunction = FORMULA


Lengths in CSV/RW routes

It is necessary to agree on a previously undefined behavior regarding the colon notation for entering lengths. Background: Via Options.UnitOfLength, it is not only possible to override meter as the default unit, but it is possible to define multiple units. When giving a length, this can then be done in the form a:b:c, where each parameter corresponds to one of the defined units. What happens if fewer parameters are used, e.g. a:b or b:c is currently not defined.

I would like to have one variable that will return the current trackdistance of the object, for both objects and trains.
That would be an important and a convenient variable.

Michelle: I expect that it may also warrant some kind of "Playing = " function along the lines of:

• 0 Sound not played
• 1 Sound played continuously
• 2 Sound played once

[/list]A change (edge event) from <1 to >=1 would trigger a sound to start playing. If the value is 0<x<=2 sets repeat. And '1' would be the default (repeat). This should be enough to allow both the general case of motor sounds, but also firing of a pre-recorded a 30 second motor-start sequence or door closing swoosh. Or possibly a variation of the syntax to request N repeats (eg. trigger two buzzes after door_distance == 0).

It's going to be interesting to hear the squeak of the wind-screen wiper move left-right-left across the 3D soundscape! (Eg. repeating squeek sample loop varied in Pitch based on sin2(r) and with Volume pulled to zero at the end in the dead-zones).