Önska saker till MSTS 2!

[Mazz]

Det här har jag skickat till Pyttemjuk, fast i lite mer formaterad form:

1 Preface
This document describes a “whish list” for a MSTS2 simulator package, coming from experience of Swedish MSTS train simmers.. It contains whishes from different areas for the game, but overall I think it covers wishes to make the game even more interesting, more real and more solid. I think the game have a lot of support in the area where people actually builds things to the game, and this document reflects lots of issues in that area. I think also that this is an area where the game gets good PR, due to the publicity of the created arts or designs, done by users.
The source for this document is from my own thoughts, mainly from working in the area of Route Editor, and the created routes. It has also thoughts from the Swedish community, at http://msts.e-buzz.net/
2 General
2.1 Bugg fixing
From current MSTS version, fix the known bugs to a solid version of MSTS2. No memory leakage for the Route Editor etc etc..
2.2 Backwards compatibility
Since so much material in routes, trains and objects are done around the MSTS world, I think that it is essential that MSTS2 will be backwards compatible. Fully ok with a translator. This includes that MSTS should be compatible with the worldwide communities standard tsection.dat, since so many high quality routes are based on that.
2.3 Multiplayer
This game is so perfect for a server based multiplayer mode! This bullet should probably be needed to have its own “whish-list”, but since there is no support in current MSTS, I have not made a deeper list in this area.
2.4 Merging routes
To gain large projects, there should be a possibility to merge multiple routes on an easy way. Option should be given if user want to reposition the route in the world too fit a “master route”.
2.5 HW: game controllers
There should be support for external USB game controllers for the game, so it is possible to create physical cab/train controllers.
2.6 Service packs
The game should gain so much in popularity, if service-packs were delivered continuously.
2.7 Tsection.dat
MSTS2 should apply the community standard tsection.dat. Preferable, MSTS2 should be based on track objects created in the package “Xtracks”, or better.
2.8 Central objects/textures/terrtex library
To make it easier to use the objects loaded on the computer, it should be a central library for all “pre-constructed” items, so all is easily used in all routes.
2.9 Single route loading
When entering the sim, it should be preferable that the sim do not examine every route that is loaded in the “ROUTE” map.
2.10 Error handling
Much improved error handling, to gain the user to understand and solve the problem. Would help to keep the train-simmers active in the game..
2.11 Diagnostic tools
Would be helpful to have some diagnostic tools for user created things, such as activities, trains, signals, objects etc..
2.12 More “fool-proof”
Should be possible to change any part in any order in the editors, as tracks, signals, sidings, sound regions etc, and still having the tdb in sync. The user should be able to change anything without having the tdb corrupt.
2.13 API
Some sort of API interface, so third party vendors could create add-ons to the sim.
2.14 Multiple player consists
Possibility to jump between other consists.
3 Route Editor
3.1 Tracks
3.1.1 Dynamic tracks
More types of dynamic track:
- Straight types. Used for all straight tracks from 2m to 1000m.
- Curves. One curve only, with user defined radius and angle.
- Complex. Current type, but possible to declare both left and right and when elevated, the track should remain in its elevation during other adjustments.
3.1.2 Increasing curves
New track type, where the radie starts from a radius value (could be 0, a straight), and in the ending point an end radie is defined.
3.1.3 Favourite configurations
Possibility to define favourite track combinations, as a “library part”. Example, lots of smaller stations looks similar, it should be possible to place that station “in a click