Hi! I have been away from MSTS for a few years but am now getting back to it due to ORv8. The new sim runs great with excellent frame rates and over-all good appearance. However, when runnning an activity in MSTS and then in ORv8, I've noticed differences that OR does not appear to have addressed. I've found that Distant Mountains, Active Water and sounds need improvement (train whistles do not have short blasts). As I have been away, I don't know if my MSTS files need to be improved with freeware add-ons which OR would pick up or if the problem is that OR just has not covered these items. This then begs the question "Is there a published list of deficiencies that the OR Dev Team is working on which are likely to show up in future releases?"
List of Deficiencies
Collapse
This topic is closed.
X
X
-
Got it in one....or if the problem is that OR just has not covered these items.
You may want to review the various warning messages generated when you start an activity. Some of them will describe a simple data problem you can fix, stuff like finding "m/s" when it should be "N/m/s". In MSTS things like that were simply ignored and nobody really knows what the operating consequences were but the OR team decided to call those out so they could be fixed by the user.
Some are obvious about what's going on, others not... you just have to read thru it and see what jumps out as worth digging into.
There will also be a few where the message says, basically, it found something and simply doesn't know what to do with it. Cab stuff mostly. Just more stuff not yet implemented.
If you get a message that has "Error" in it, that is something the OR team wants to know about.
p.s. somebody is looking into making some of the messages a bit more clear as to whether its a data problem or an unimplemented feature.Dave Nelson
sigpic
Seldom visiting, posting less often that that. -
As this fits this thread:
I would be happy to see in the trace not only the callstack, but also the parameters that caused the error! Probaby it is also possible to outline errors regarding currently not implemented (but planned) features to show clearly where changes are necessary an where to wait for the next version.Comment
-
I am curious too about such lists and plans, but I think it cannot be expected of the developers. OR is not a business venture. Developers most probably doing these kind of things as part of their jobs, but they come to OR for having fun, and writing these lists is definitely not that.Last edited by gpz; 11-05-2012, 07:10.Peter Gulyas
sigpicComment
-
Hi! Any actual error messages I have had I've been able to deal with by using RouteRiter or by copy/paste files within MSTS. If OR has an error/event log, I've not fournd it. Also, as OR is supposed to be "open" I would have thought there would be an authorized blog about what is actively being worked upon.
I merely asked the original question to see if there was info as to what direction OR was taking, other than MP.Cheers; Chuck F.
"the people keep coming but the train has gone"Comment
-
Appologies to cougar - the linked page was not current and I've temporarily disabled it to avoid confusion.Comment



Comment