openBVE - Downloads

Downloads - openBVE 0.8.0.0 - Release notes

Changes between versions 0.7 and 0.8

The BlendingMode/SetBlendingMode commands for B3D/CSV objects have been replaced by BlendMode/SetBlendMode with different syntax to allow for more control on the glow behavior. The old commands will still be available until version 1.0 (exclusive), which means that they should have been replaced until then by the developers. More information about the syntax is available here.

There are some new keyboard commands available for the camera. See the readme for more information.

Additions to the CSV/RW routes:

● The Options.BlockLength and Options.UnitOfLength commands have been introduced to support different block lengths than 25 m as well as other units of length than the meter.
● The Track.PointOfInterest command has been introduced to allow for scripted camera points which can be cycled through.
● The Track.FreeObj command has been extended to allow for more rotation, namely Pitch and Roll.
See the specifications (work in progress) and the compatibility section for more information.

Additions to the B3D/CSV objects:

● The BlendMode or SetBlendMode commands have been introduced to select blend modes, the glow attenuation distances and glow modes.
See the specifications (work in progress) for more information.

This is not a fully functional version. Please see the Compatibility sections to find out which things are supported and which things are not. Additionally, the Roadmap tells you when to expect which features to be implemented. The following is a list of known issues with the current version and of tips to avoid some pitfalls.

Panels: The panels are (hopefully) correctly aligned, but a proper camera restriction is not applied for the cab view. This can force some parts that would usually be outside the cab to be visible on-screen, especially for some BVE 4 trains.
Panels: BVE 4 panels feature needles which can employ under-damped oscillation. openBVE does not currently support this. Instead, every needle resembles an over-damped oscillator.
Route: The transponder objects are currently misaligned in curves, which will be corrected in future versions.
Physics: Not all train internals are simulated yet. Some delays, the passenger happiness, adhesion, load compensation and passenger-related shaking at stations are currently not available.
Graphics: The different elements in the panel are stacked as 3D objects as illustrated here. The closer the elements are stacked, the better the result will look like. However, if they are too close, z-fighting may occur. To avoid this, you can adjust the panel stack distance (given in meters) in the configuration file.
Graphics: The text output is currently not all too fast, so expect a 5-10% drop of frame rate when the full debug output is enabled.
Audio: The compressor sound is composed of a start and a loop sound. According to mackoy's specification, the loop sound should start playing 5 seconds after the start sound is played. Currently, in openBVE, the loop sound is played only once the start sound has finished, leading to a slightly different behavior.
Audio: Currently, train sounds are only played for the first car. This is due to the fact that there is no information about which cars would emit which sounds in existing BVE trains.
Audio: Some stereo sounds will not be audible because of destructive interference. See the note box in the Features: Audio section for further information.
Audio: Only 22050/44100 KHz, 8/16 bit, PCM WAV files are currently guaranteed to work (hopefully at least).

Attention: All route, train and panel files are text files encoded using a certain encoding. For correct parsing of those files, it is important to know which encoding the files were encoded in. As BVE files do not employ a tag about the encoding, you currently need to specify the correct encoding in the settings.cfg file. Further information is available in the readme.txt file.

If there are problems with the route file, you will see messages of the following form:

Screenshot

Errors are quite likely mistakes made by the route developer that should be fixed or missing files due to an incomplete distribution or download. Warnings are currently generated in ambiguous situations that should be avoided by developers. You can ignore either type of problem and still get the route to work quite well in most cases by clicking the Ignore button.

Note: The error report is currently deliberately only shown in window mode and will thus not appear in fullscreen mode.