Scenario behaviour changed since update.

[EWS 58038]

I fail to believe that it is me, but I noticed that the behaviour of my scenarios have changed since the update from TS12 to TS13. Not that trains run anything else, but the signalling part. Where I did put loads of effort in creating scenario's that one might encounter a red aspect, see a train crossing the junction and get a clear signal again, this didn't happen when I updated my Simulator. All I got was a green aspect with the other train standing along the platform waiting for my train to clear the junction.

This is most frustrating as I spend a lot of effort in creating scenario's that are not dull and represent real life situations.

Anyone else noticed anything odd?

 

[hairyhandedfool]

Well, I can't say it is changed as such (having never really tried to complete it before) but on the WCML north scenario 'Polmadie Hop' it seems it is impossible to get into Glasgow Central without either going past a danger aspect (without permission) or being hit by an AI train.

 

[thesignalman]

I fail to believe that it is me, but I noticed that the behaviour of my scenarios have changed since the update from TS12 to TS13. Not that trains run anything else, but the signalling part. Where I did put loads of effort in creating scenario's that one might encounter a red aspect, see a train crossing the junction and get a clear signal again, this didn't happen when I updated my Simulator. All I got was a green aspect with the other train standing along the platform waiting for my train to clear the junction.

This is most frustrating as I spend a lot of effort in creating scenario's that are not dull and represent real life situations.

Anyone else noticed anything odd?

Yes, priorities have changed a little - as you say they are only noticeable in complex scenarios. In contrast to your issues I have found the player train gets held for other traffic in two of my scenarios causing late arrival at destination. Fixing is fairly easy but the testing takes time!

John

 

[Darandio]

Fixing is fairly easy but the testing takes time!

You could use the synckeys to speed up time whilst driving the scenario to test.

I must admit, I create scenarios as much as anyone if not more, and I don't really see much of a change.

 

[CC 72100]

You could use the synckeys to speed up time whilst driving the scenario to test.

That sounds like a useful feature. Which keys and what speeds are on offer?

It takes me about an hour and a half to make a scenario with a reasonable amount of AI traffic, it's the testing which then is a bit frustrating to have to do. (On some I just want to check they work to go back to and enjoy at a later stage)

 

[Darandio]

OK. Just to clarify, this is not the scenario preview where you speed up time within the editor and can cause issues if not used correctly. SyncKeys is just a method of speeding up the scenario as you drive it so no adverse effects occur.

The only issue is managing when you use the speed depending on your type of scenario. Obviously as you are speeding up time, this affects your reactions to speed limits, vigilance, AWS cancelling etc. However....

You need to make a new shortcut from your RW install and put it somewhere accessible, I use the desktop for instance. To make the shortcut, you need to go to C:\Program Files\Steam\steamapps\common\railworks and right click "Railworks.exe" then create shortcut.

Then go to your new shortcut and right click and select properties. Enter EnableASyncKeys in the target location as seen in my attachment. There must be a space between the original command and your new one.

Then, when driving a scenario, use Ctrl+Shift+1* to Ctrl+Shift+5* (*above qwerty). 1 being normal speed and 5 being 5x speed.

 

[CC 72100]

OK. Just to clarify, this is not the scenario preview where you speed up time within the editor and can cause issues if not used correctly. SyncKeys is just a method of speeding up the scenario as you drive it so no adverse effects occur.

The only issue is managing when you use the speed depending on your type of scenario. Obviously as you are speeding up time, this affects your reactions to speed limits, vigilance, AWS cancelling etc. However....

You need to make a new shortcut from your RW install and put it somewhere accessible, I use the desktop for instance. To make the shortcut, you need to go to C:\Program Files\Steam\steamapps\common\railworks and right click "Railworks.exe" then create shortcut.

Then go to your new shortcut and right click and select properties. Enter EnableASyncKeys in the target location as seen in my attachment. There must be a space between the original command and your new one.

Then, when driving a scenario, use Ctrl+Shift+1* to Ctrl+Shift+5* (*above qwerty). 1 being normal speed and 5 being 5x speed.

Yep, that's what I'd be after, to make scenarios run quicker when in the testing phase, just be a bit careful on the old AWS etc.

I'll give that a go nextweek when I'll be back on my Railworks PC.

Until then, Thanks