Page 5 of 5

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sat Aug 16, 2008 3:53 pm
by jamespetts
Update: I have been unable to carry out any further testing, since, as reported here, I find that the game crashes a few minutes after loading almost no matter what I do, making using it for any purpose, including testing, quite impossible.

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sun Aug 17, 2008 9:51 pm
by RSderek
Hi James,
We have not noticed the instability you have mentioned,
If it was the case we would never have managed to create the IOW addon.
However if you would like to send us your scenario we will take a look at it for you.
If RS is at fault then we can look to address it.
If you have set something up wrong then we can help you and maybe suggest some pointers to put you on the right track so to speak.

regards

Derek

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sun Aug 17, 2008 10:11 pm
by jamespetts
RSderek wrote:Hi James,
We have not noticed the instability you have mentioned,
If it was the case we would never have managed to create the IOW addon.
However if you would like to send us your scenario we will take a look at it for you.
If RS is at fault then we can look to address it.
If you have set something up wrong then we can help you and maybe suggest some pointers to put you on the right track so to speak.

regards

Derek
Thank you for your reply :-) I might have been able to track down the instability problem and solve it: I changed from "Default OS" language to "English", then updated my sound card drivers from the beta to the latest release, and have not had the problem of general instability since. I am continuing to test (although hampered by the missing track at Ealing - will revert to Newcastle-York until that is fixed, since I cannot for the life of me get the tracks to line up when I try to fix it myself). I will also try to see whether I get the random "consist tilt" problem again.

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sun Aug 24, 2008 1:34 pm
by jamespetts
Update: I have produced a substantial update to this thread to reflect developments since the release of Upgrade 1, and a great deal of testing that I have conducted recently. I have revised the entire topic on instability in path handling to add much detail gleaned from recent testing and moved it to the top of the list of critical flaws, because it is so serious. I have removed redundant references to the issue not being in the Upgrade 2 release notes, and instead added a general explanation in the introduction. I have revised the introductory paragraphs to bring the thread up to date, and make it more accessible to new users. I have also revised some of the wording of the earlier items, and introduced some new information based on more recent testing.

Finally, I have removed reference to the train jumping instability, which appears to have been cured by one or both of: (1) changing the language from "Default OS" to "English"; and/or (2) upgrading my sound card drivers.

I should encourage members of the community to continue to post on this thread to add any further issues or comments, including the results of any testing. Given the number of double red markers in the critical list (indicating no improvement since release), matters are not looking promising for improvement in the foreseeable future, but people should at least be made aware of the problems before they invest time and money into this product.

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sun Aug 24, 2008 3:51 pm
by jamespetts
Update: Added information on the results of a recent test, in which two AI trains collided head-on after both emerged from the Salisbury-Exeter portals on the Somerset & Dorset line on the up line (despite the track directionality) to the section on portals.

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Sun Aug 31, 2008 10:22 pm
by jamespetts
Update: Added information to critical issue no. 3 to reflect a recent discovery of another adverse consequence of Rail Simulator having failed to implement route locking, namely the AI trains going off path and ending the scenario issue, as reported by Mauried in this post.

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Wed Sep 03, 2008 7:39 am
by jp4712
Regular visitors to this column may note that quite a lot of posts are no longer here - we have removed all those that were irrelevant, inflammatory, about a completely different product or just plain discourteous. But don't worry, they haven't been deleted completely: they've been put in a nice safe place where the moderators can still see them.

So, just a nice, polite little reminder: any member who feels like making a personal attack, or breaking the forum rules, or 'going off on one', can expect a short holiday from the forums. From now on, please keep it on-topic to justify the usefulness and hence sticky status of this thread.

Have a nice day

Paul

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Fri Jun 12, 2009 4:50 pm
by jamespetts
Now that RailWorks is released, can anyone who has bought it assist as to which, if any, of the operational deficiencies listed in the opening post are resolved?

Re: (Hopefully) definitive list of all operational deficiencies

Posted: Fri Jun 12, 2009 8:55 pm
by tads1970
Nice to see you back James,I'm checking RW forums often to see if anyof the main problems have been fixed.I did see on a RW screenshot the track/junction draw bug still there,although to be fair
they didn't say it would be fixed for RW.Only difference I see is glow from the signals,nothing more.

I'm almost sure the dispatcher will be getting a grand workout relating to RS statement regarding AI.

Daz