Wishlist for small improvements

[csantucci]

I have a small request: if you keep pressed the throttle or train brake keys, the value of throttle or train brake changes fast. The same does not apply for the dynamic brake key. If you want to increase/decrease the value of the dynamic brake, you have to press many times the related key. So the small request is that also for the dynamic brake keys a continuous pression increases/decreases fast the value of the brake.

[kox]

A setting for anisotropic filtering would be nice too. I know it can be set from the video driver, but this would be better customizable.

[releismetrain]

Hi,
I would like the size of the text in the cabview to be much much smaller.
Example the time and speed display.

Regards Geoff.

[csantucci]

This can be done with release 1330 by changing the relevant cvf parameters. Apparently ORTS and MSTS interpret the size parameters in a different way.

[csantucci]

I like to have the train paths displayed in the dispatcher window. I suggest that the player train path has its specific path colour.

Moreover I have seen that now Combined control (throttle+dynamic brake on same levers/keys) has been implemented on diesel units. My (maybe not so small) request is that this be implemented now also for electrics.

I was quite well impressed by the new Replay function, thank you. It's sometimes nice to watch again what one has done in the last run. I see that there is also the possibility to Replay automatically many times the saved run. This can be useful for demo installations.

[csantucci]

I have a proposal for a function that could be useful and nice in MP and not only: when you click on a train in the dispatcher window, that train is displayed in the main window.

[neyland]

Vacuum brake, implementation.

[UP_4848_Thunder]

Would be nice if the dispatcher window in both multi and single explore modes would implement a safety in signaling:

1. Let signals stay the way the dispatcher sets them when red for stop will not change automatically the closer a train gets to it or changes in switches.
2. Put a safe to fail system where if dispatcher sets one signal clear, advance approach or approach ahead and block is not really clear with a train already in the block, the signal system should not allow the train behind movement unless dispatcher sets the signal to a new tab under signal setup of Restricting flashing red.
3. If possible have a dispatcher setting to set all signals on route to a stop indication where dispatcher has to go to a signal to set its settings up in either signal system controled or indication chosen if safe.

Btw has any OR developer made any documentation tutorials for how to add the new parameters for eng/wag files? Can there as well be a section in the File Library for Open Rail certified files for like high poly shape files only workable in OR would be OR/Only or for both would be MSTS/OR?

[Kristian]

The option to set LoggingPath, ScreenshotPath manually. I don't like to have the logfile appear on my desktop.

[neyland]

The option to set LoggingPath, ScreenshotPath manually. I don't like to have the logfile appear on my desktop.

Ditto.

[eric]

Triple-itto on getting the logging off the desktop... Logs for debugging should show up in the executable directory, or better yet, named with the date/time and saved to a logs sub-directory so it is easier to keep compare logs under different situations...

[csantucci]

I have a proposal for a function that could be useful and nice in MP and not only: when you click on a train in the dispatcher window, that train is displayed in the main window.

I see that this function has been implemented in the x1342 release by clicking the train and then the "see in game" button: thank you, I like it!

[mnjrr]

Hello,

Just to inform the Train Sim community, the OR developers are going to switch gear to focus on resolving bugs related to the software. Please keep your bug reports coming to assist the developers with tracking down bugs. In addition, please feel free to post about what features you would like the developers to include in future releases of Open Rails. Real-time information about OR bug reports and requested features is at https://launchpad.net/or.

Thank you to the community for the important help you are providing making Open Rails a stable working environment with advanced graphics and for realistic train simulator operation.

[Kristian]

I haven't read the complete manual yet to begin with.
I have several routes: SLI's BNSF Seligman2, and BNSF Subdivision2, and freeware routes Surfliner2 and Horseshoe curve I use, at the moment. (PRR as well, but am waiting for the next release whenever that's planned). Converting those tracks to DB tracks I wait for a moment, that's adding another variable.
Those routes were tested under mstsBin which I don't use, so I have no comparison.
Every route I run/load results in some error messages, not recognised shape files e.g. I don't know how that affects the route itself, I also get certain errors resulting in missing loco's in a consist (error in displaying the cab properly?), and quite some activities not working at all (the ones that came with the SLI routes are the only activities I have at the moment).
I hope to get a list of errors before the next release to get as many loco and route related errors fixed, easier said than done. SLI stuff is not freeware so I don't know how you could test that. One of the many changes I want to apply to is to replace the default cabs with ones from trainsim.com, perhaps that solves the problem.
Getting the current routes and loco's available for msts, working properly is more important than adding new features I suppose. Of course we would like to see both.

Edit: I would like to see more flexibility in the camera settings, e.g. when in track side view have a position further away from the train before it passes, being able to move more freely left/right as well in '4', also if possible, not having to press the right mouse button when moving the camera. When I want to turn my head I don't like to press a button first..
I don't know when release of the source code is planned, but tweaking the camera settings is the no 1 reason for me to have access to it.

[csantucci]

As the OR dev team is currently improving cabviews, I kindly ask the team to consider implementation of the Door indicator and of the Speed limit as described within the MSTSbin documentation (priority B).