New update here!

[Wikkus]

No lights???

Elaborate a little, please.

...and welcome to UKTS

Rik.

[almark]

I assume he means the headlights on the track in front? I believe they are not in this update.

[pdeee]

"Fix to crash when using TAB to pass signals "

Does this mean that a crash occurs whenever you use Tab to pass a signal at danger, this would effect quite a number of existing scenarios, as some signals are inconsistent in operation and it is the only way to pass.

[Darpor]

No. Crashes normally seem to happen when people dont understand approach control. They will approach for instance, a junction signal and press TAB before hitting the AWS ramp, not realising that moving over the AWS ramp then clears the route and gives a green. Because TAB has been pressed, generally proceeding past the signal will cause the crash.

[pdeee]

Thanks Darpor, I appreciate your explanation.

[AndyM77]

No. Crashes normally seem to happen when people dont understand approach control. They will approach for instance, a junction signal and press TAB before hitting the AWS ramp, not realising that moving over the AWS ramp then clears the route and gives a green. Because TAB has been pressed, generally proceeding past the signal will cause the crash.

It's not always the Approach Controlled signals that caused the Red light / Tab / Crash bug, IIRC if you use the bay platform (6 I think) at Reading, pressing tab to pass the 'starter' signal when the AI wasn't on the ball also caused the crash.

Hopefully RS.com have sacked the old signalman and replaced him / her with someone better for the next update!

[AndiS]

My favourite certainly is the offset tool. Over the past months, I have been working on various workarounds which involved Excel sheets which meant that they would never have become too popular.

For the crashing on passing a signal, we will have to wait and see which subclass of issues it fixes, but less crashes must be a good thing.

The "prevent AI trains reversing in unusual circumstances" gives me a nice idea for more political correctness. From now on, it is only "unusual behaviour of AI trains", no more "buggy AI". (I know that the original message was different, I just like the idea, suffering a lot from such "unusualness".)

Like always, these things need to be seen in real life. Overmarze's example shows that everyone needs to see if his own little favourite is in. Regarding the object list, I still hope for an Explorer-style foldable tree list, grouping the assets by provider and product, and maybe subfolder, or maybe not to give the creator the chance to arrange them via some naming convention. But provider/product sure would be great. Plus some means to selectively uninstall parts of a package. This would keep even Overmarze's list below 4000.

[EWS37410]

No. Crashes normally seem to happen when people dont understand approach control. They will approach for instance, a junction signal and press TAB before hitting the AWS ramp, not realising that moving over the AWS ramp then clears the route and gives a green. Because TAB has been pressed, generally proceeding past the signal will cause the crash.

No that's not quite true, specially in all of the times its happened to me. The signalling system needs to be redone simple as. Because most of the times when you need to tab is because there are rouge red lights that wont clear, even if the path in-front is clear of any trains. This is without pressing TAB beforehand.

[RSderek]

Hi,
Don't wish to push anyone buttons, but just because there is a bug does not mean something has to be re written...
Though it is true that coders often like to rewritten someone else's code even if it ends up doing the same thing.

regards

Derek

[Acorncomputer]

Hi Vern

This is the solution -

Emails to support get put into subject folders, the subject with the most emails tends to get looked at and if possible addressed first.

Just send loads of e-mails to RS.com about the same subject and it will come to the top of the list

For me, regular updates containing a limited number of improvements/fixes that have been tried and tested before release is the right way of developing. As more regular stable updates are released, eventually there will be nothing left to fix.

[RSAdam]

Just send loads of e-mails to RS.com about the same subject and it will come to the top of the list

Ah, but we do check for duplicate messages from the same users, mainly to ensure we dont duplicate communication ourselves, but it works both ways.

Regards

[almark]

But what if we all organize to send them in?

[AndiS]

Haha, so I should clearly tag all my input. Otherwise it gets shelved under "AndiS on Operations Dreams".
Would be a fat folder by now ...

Maybe me and Vern and some others should provide annual summaries (or collector's editions) with hierarchical index, so make sure that RSC can honour all the facets in all our ideas.

[Wikkus]

because there are rouge red lights

Vermilion?

Rik?

[Acorncomputer]

Just send loads of e-mails to RS.com about the same subject and it will come to the top of the list

Ah, but we do check for duplicate messages from the same users, mainly to ensure we dont duplicate communication ourselves, but it works both ways.

Regards

Only kidding Adam