Package: wnpp
Severity: wishlist

* Package name    : openbve
  Version         :
  Upstream Author : Christopher Lees <>
* URL             :
* License         : Public Domain
  Programming Lang: C#
  Description     : Realistic 3D Train / Railway Simulator

openBVE is a railway train-driving simulator with an emphasis on
 in-cab driving, realistic physics, braking system and train safety
 system modelling.

 Technically, the simulator handles detailed per-car simulation of the
 brake systems, friction, air resistance, toppling and more. In trains
 supplied with 3D cabs, the driving experience is augmented with
 forces that shake the driver's simulated body upon acceleration and
 braking, as well as through curves.

 Compared to other rail-based simulators, openBVE has its main focus on
 realism---not necessarily on user-friendliness. There may be a need
 to study operational manuals for the routes and trains chosen, rather
 than merely memorising a few keystrokes.

 The simulator is designed to be backwards-compatible with existing
 'BVE Trainsim' routes and cab interiors, allowing a wide range of
 existing scenarios to be loaded by a single-program (BVE1, BVE2,
 BVE4 and extended openBVE route formats).

 OpenBVE uses OpenGL for 3D graphics rendering, OpenAL for positional
 surround sound, and is written in the C# language.  Note that binary
 train extension plugins are not currently supported on Linux/Unix,
 because these would require Win32 emulation.


openBVE was previously part of the Debian / Ubuntu repositories, but was
removed due to unresolved bugs, and lack of upstream development.

I became the primary developer / upstream maintainer approximately 4 years ago,
and have been involved in the wider BVE community for 20+ years.

We've been in contact with both the previous Debian / Ubuntu maintainers
(sladen - Paul Sladen & directhex - Jo Shields), and we're agreed that in
priciple, we would like to bring openBVE back into the repositories.
With this in mind, we have an offer from Henrich to sponsor the potential
new package.

Our release cycle tends to be whenever we have a major feature, so something
variable from 1-3 months.
The full source-code is available from
and *should* build a compliant Debian package from stock.
(N.B. There is also a makefile, which as one of it's options will build a
debian package, but this isn't fully standards compliant)


Reply via email to