I am not often play train simulator games for about 4 years. except OpenBVE, I just played OpenRails last night. It seems promiseful.
What I want for a train simulator or rail simulator? Simply :
Operation: better than EU07
Sound: better than BVE
Control: 3D cabview, full control
Play: support Multi-play
Graphics: independent with other part development
As a former programmer, what I learn is you say more, you can hope less. Although I still feel I have said too much after I have written this.
1. Reality
I think EU07 is the best on control feeling as I know, I mean the real operation procedure, real response (like the brake release time, loco start procedure, etc). I wish a train game even can be used for training. What I want is a 3D cabview and every device can control, even an air conditioner switch (although you can not hope feel cool air). That mean may be need a programmable script for it.
I also want there are different levels so a newbie can skip these steps or better an AI conductor can give tips or even do some operations. I also want an AI conductor who can tell me the distance to next station and speed limit ahead when I ride on a strange route. (and support multi-language subtitle based on language priority)
About cabview, I think 3D cabview will coexist with 2D cabview for a long time. So let the locomotives can share the cabview is important. Even the 2D cabview production is less than 3D loco model. May be let the player can easily borrow the cabview from other loco in GUI is a good idea. And about 3D cabview in future, share 3D component and device (with script) between cabview is also important.
2. Sound
MSTS sound effect is poor than BVE. I think it's because it lack some key event triggers and parameters (like event trigger by travel distance or switch for track sound, and modulate sound by train speed). It can be easily fix and get a good result. (I haven't study BVE)
For more better effect, I think the sound source should have its 3D coordinate, like engine and wheel. And we need better and independently engine physical module, for example diesel engine can have turbo RPM parameter, and brake pipe sound based on air speed within it. So we can hope a perfect steam loco sound. And using low pass filter while view point in vehicle, using different filter or sound while train meet each other, in bridge and in tunnel.
3. Signal
MSTS only have 8 signals. It's not enough for modern railway system. I think there are 2 ways to extended it, and its better using both methods. One is more signals, with two base property (speed and switch classes) and customer name, so one country loco can ride on another country railway track with correct inside signal display. Another is signal defined by frequency of real signal electric wave transferred on track. It can simulate signal device failure, signal loss and one company train ride on other company track (like in USA).
One special thing on graphics: long distance signal lighting display, I wish we can see signal more than 1km without using texture LoD trick or HDR technical.
4. Dispatcher and Multi-play
MSTS so called "AI dispatcher" using a half functional program script to calculate signal state. It's not a full program language for it does not support loop. I don't know the OpenRails Team will support it or make a new implement?
What I want is there can be one or more Dispatcher Console program work with OpenRails. This Dispatcher Console program may also work as a standalone game. We need both manually dispatch and AI dispatch. I think it should based on pre-allocate the controls of the blocks. And in multi-play game, local track block signal should be first priority, and train will automatically request the controls of the blocks ahead to server or peer or dispatcher console.
And about running monitor, it may be too complicate using script to implement, unless it's a powerful script. It may be implement as a standalone program (C/S) or a DLL. In China there are people have written a running monitor program work with MSTS. In theory we may use the real monitor code or even let the real running monitor and record device program run in a virtual machine and communicate with the game. Of course, it's not an easy way.
Sometimes, TDB file may be too big. I think it can split into several parts, so route made by different author can be easily link together. And using a small simple track topology for signal calculating (which will not affected by simple route editing). And a large railway can be controlled by several dispatcher consoles. I can not say I want drive from China to Europe, but there is the possibility.
And more about multi-play, may be two people can drive one train.
5. Content manage
There are too many addons have been made for MSTS. Duplicate, reference and dependence is the problem. I wish OpenRails can have a good content manage system to check these. And if people lack some part, it can give enough information tell lack what addon and may be better can also let user choice using other stuff instead.
6. Game device
Support dual screen (for running monitor and dispatcher console or more view). Support joystick and wheel and even using force feedback.
7. Terrain
I don't want say something about graphics. But I think it's better have a high resolution DEM near the track. Sometimes MSTS seems do not have much details near the track compare to some high quality BVE route. And of course route editor need good tools support edit the terrain easily.
What I want for a train simulator or rail simulator? Simply :
Operation: better than EU07
Sound: better than BVE
Control: 3D cabview, full control
Play: support Multi-play
Graphics: independent with other part development
As a former programmer, what I learn is you say more, you can hope less. Although I still feel I have said too much after I have written this.
1. Reality
I think EU07 is the best on control feeling as I know, I mean the real operation procedure, real response (like the brake release time, loco start procedure, etc). I wish a train game even can be used for training. What I want is a 3D cabview and every device can control, even an air conditioner switch (although you can not hope feel cool air). That mean may be need a programmable script for it.
I also want there are different levels so a newbie can skip these steps or better an AI conductor can give tips or even do some operations. I also want an AI conductor who can tell me the distance to next station and speed limit ahead when I ride on a strange route. (and support multi-language subtitle based on language priority)
About cabview, I think 3D cabview will coexist with 2D cabview for a long time. So let the locomotives can share the cabview is important. Even the 2D cabview production is less than 3D loco model. May be let the player can easily borrow the cabview from other loco in GUI is a good idea. And about 3D cabview in future, share 3D component and device (with script) between cabview is also important.
2. Sound
MSTS sound effect is poor than BVE. I think it's because it lack some key event triggers and parameters (like event trigger by travel distance or switch for track sound, and modulate sound by train speed). It can be easily fix and get a good result. (I haven't study BVE)
For more better effect, I think the sound source should have its 3D coordinate, like engine and wheel. And we need better and independently engine physical module, for example diesel engine can have turbo RPM parameter, and brake pipe sound based on air speed within it. So we can hope a perfect steam loco sound. And using low pass filter while view point in vehicle, using different filter or sound while train meet each other, in bridge and in tunnel.
3. Signal
MSTS only have 8 signals. It's not enough for modern railway system. I think there are 2 ways to extended it, and its better using both methods. One is more signals, with two base property (speed and switch classes) and customer name, so one country loco can ride on another country railway track with correct inside signal display. Another is signal defined by frequency of real signal electric wave transferred on track. It can simulate signal device failure, signal loss and one company train ride on other company track (like in USA).
One special thing on graphics: long distance signal lighting display, I wish we can see signal more than 1km without using texture LoD trick or HDR technical.
4. Dispatcher and Multi-play
MSTS so called "AI dispatcher" using a half functional program script to calculate signal state. It's not a full program language for it does not support loop. I don't know the OpenRails Team will support it or make a new implement?
What I want is there can be one or more Dispatcher Console program work with OpenRails. This Dispatcher Console program may also work as a standalone game. We need both manually dispatch and AI dispatch. I think it should based on pre-allocate the controls of the blocks. And in multi-play game, local track block signal should be first priority, and train will automatically request the controls of the blocks ahead to server or peer or dispatcher console.
And about running monitor, it may be too complicate using script to implement, unless it's a powerful script. It may be implement as a standalone program (C/S) or a DLL. In China there are people have written a running monitor program work with MSTS. In theory we may use the real monitor code or even let the real running monitor and record device program run in a virtual machine and communicate with the game. Of course, it's not an easy way.
Sometimes, TDB file may be too big. I think it can split into several parts, so route made by different author can be easily link together. And using a small simple track topology for signal calculating (which will not affected by simple route editing). And a large railway can be controlled by several dispatcher consoles. I can not say I want drive from China to Europe, but there is the possibility.
And more about multi-play, may be two people can drive one train.
5. Content manage
There are too many addons have been made for MSTS. Duplicate, reference and dependence is the problem. I wish OpenRails can have a good content manage system to check these. And if people lack some part, it can give enough information tell lack what addon and may be better can also let user choice using other stuff instead.
6. Game device
Support dual screen (for running monitor and dispatcher console or more view). Support joystick and wheel and even using force feedback.
7. Terrain
I don't want say something about graphics. But I think it's better have a high resolution DEM near the track. Sometimes MSTS seems do not have much details near the track compare to some high quality BVE route. And of course route editor need good tools support edit the terrain easily.