CN Bala 2

[poochwilly]

I have tried running a few activities in CN Bala's v2 route and I have noticed when you come to a speed post sign and it either tells you to increase or decrease your track speed it takes a while once you have passed the sign to change, works okay in MSTS but I am running trains now in Open Rails version x2007. Most of the other routes don't have this issue. Guess it's a work in progress situation with Open Rails or CN Bala2 needs some modifications. Have to wait for a patch. Not into fuddling with stuff if it still works somewhat.....

Thanks Happy Family Day to all Canadians.

Thanks Poochwilly

p.s. I will go over and hopefully post which acts I have found these in.

[r_claxton]

Bala 2 was not designed to be used or tested for Open Rails. There is no solid finished OR program yet, its still a work-in-progress, I have not had time to fiddle with it yet. So therefor the problems in OR I am unaware of.

Now with that said, once I get the scenery upgrade complete, I WILL be going over the whole route and redesigning it for Open Rails (making all curves dynamic track in order to have super elevation - as stock curve shapes wont super-elevate, increasing details that MSTS could not handle and making sure the signalling logic works correctly, etc etc). By this time, perhaps a solid Version 1 of Open Rails with all functions working properly will be available, which will make OR less daunting to users.

Cheers,
Robin

[Don6218]

Poochwilly if you search through my posts here in the OR section, there is a workaround for Bala 2.0. It is a simple change and allows OR to see the signals and AI trains differently. It is a simple change that does help with the enjoyment of a great route.

[slipperman]

Hi poochwilly,

when you come to a speed post sign and it either tells you to increase or decrease your track speed it takes a while once you have passed the sign to change

I may be wrong, but I think Open Rails doesn't effect an increased speed limit until the last vehicle in the consist has passed the sign, whereas MSTS increases the limit as soon as the first vehicle (usually the loco) passes it.

Cheers,
Ged

[seagoon]

..I may be wrong, but I think Open Rails doesn't effect an increased speed limit until the last vehicle in the consist has passed the sign, whereas MSTS increases the limit as soon as the first vehicle (usually the loco) passes it....

That is 100% correct.

Some considerable time ago this change was made so as to reflect real life, where the increase in speed is not to take place until the last car is past the sign.

Just another small item whereby the realism in OR improves on its host.

[seagoon]

..... when you come to a speed post sign and it either tells you to increase or decrease your track speed it takes a while once you have passed the sign to change, works okay in MSTS .....

No, it doesn't work okay in MSTS.
That has been completely wrong right from the start.

Acceleration to posted speed (or maximum permissible speed for any particular train) must only occur after the last car of a train has passed the sign which advises of the increase.

Open Rails has it operating the way it should.

[poochwilly]

Is it possible for you send me your work around fix for this not into messing anything up. Just a thought if allowed? Thanks Poochwilly

[geepster775]

That is 100% correct.

Some considerable time ago this change was made so as to reflect real life, where the increase in speed is not to take place until the last car is past the sign.

Just another small item whereby the realism in OR improves on its host.

But is that really realism? In today's world, that's what your distance counter is for. And in the olden days, experience was your distance counter. When you exit a speed zone, on paper it should go back to full speed, but the engineer usually uses the distance counter to know when his rear end clears the zone.

Perhaps that knowledge of when to resume speed should remain with the user and not be quite so "programmed in"? Or at a minimum, do that with AI traffic only?

[seagoon]

But is that really realism? .....but the engineer usually uses the distance counter to know when his rear end clears the zone.

Perhaps that knowledge of when to resume speed should remain with the user and not be quite so "programmed in"? Or at a minimum, do that with AI traffic only?

It isn't programmed!

If you want to flout the law and increase your speed early, then fine....go ahead and do so. Open Rails won't stop you doing that but it will warn you that you are exceeding the posted speed by changing the track colour in the F4 pop-up.

The "black bar" pop-up which advises you that you may now increase speed is the current OR equivalent of the engineer's distance counter.

Open Rails can't place a working DC in the cab.....that is part of the locomotive arrangement and to my limited knowledge has never been done in MSTS.

[blillpers]

It should take some time before you get a higher speed, the whole train needs to pass the speed post before you start accelerating. However, a decrese in speed should not be affected by this.

[seagoon]

It should take some time before you get a higher speed, the whole train needs to pass the speed post before you start accelerating. However, a decrese in speed should not be affected by this.

Huh?

[eric]

I think what he's saying is

When the new limit is higher, it isn't effective until after the end of the train is past the speedpost.

When the new limit is lower, it takes effect when the front of the train passes the speedpost.

Whether or not the latter is being reflected correctly in the track monitor I have no idea...

[eric]

Open Rails can't place a working DC in the cab.....that is part of the locomotive arrangement and to my limited knowledge has never been done in MSTS.

In the actual cabview, you're correct, but couldn't we have a keystroke driven distance counter as a pop-up or in the heads-up display, showing both the distance traveled since activating, as well as the distance remaining for the calculated length of the train?...

[seagoon]

In the actual cabview, you're correct, but couldn't we have a keystroke driven distance counter as a pop-up or in the heads-up display, showing both the distance traveled since activating, as well as the distance remaining for the calculated length of the train?...

I was the one (maybe not the only one) who suggested a distance counter in the first place, and it was as a result of using Run 8, where the utility is inbuilt as featured in the real locos.

At the time we were informed that it could be done using the pop-up bar but your suggestion would enhance that method, for sure.

I wonder if it can be done?

[eric]

I'll add it to the wish list at the other site... I pulled up the Dash 9 operating manual for BNSF, and they detail out the counter's functionality -- it can either count up from zero, or count down toward zero from a preset, which could be the train's length.