Upcoming Events

No events to display

We are not planning any more in-person events until the COVID-19 situation has improved.

Berrima Jn. - 2233 versus BJ84

You are here: Home > Forum > Simulations > Australian Sims > Moss Vale NSW > Berrima Jn. - 2233 versus BJ84

Page 1 of 1

Berrima Jn. - 2233 versus BJ84 13/02/2021 at 12:17 #137198
drew
Avatar
8 posts
I'm really enjoying Moss Vale, it's great to have something so familiar and close to home.

I've encountered an issue with 2233 arriving at Berrima Jn to reverse into the cement works. The train has come to a stand with the rear not clear of BJ84. It had plenty of room to pull past, the next down signal was off. I'm a bit short of workarounds because I'm running the sim on Linux via Crossover, and a number of things aren't working - including right clicking on the train list. I'm going to go back to a previous save and see if it does it again. I'll own any Linux induced weirdness, but maybe it's a sim bug?

Medium term, I'm going to dual boot Windows and get all the options back!

Log in to reply
Berrima Jn. - 2233 versus BJ84 13/02/2021 at 12:34 #137199
postal
Avatar
4687 posts
Online
drew in post 137198 said:
I'm really enjoying Moss Vale, it's great to have something so familiar and close to home.

I've encountered an issue with 2233 arriving at Berrima Jn to reverse into the cement works. The train has come to a stand with the rear not clear of BJ84. It had plenty of room to pull past, the next down signal was off. I'm a bit short of workarounds because I'm running the sim on Linux via Crossover, and a number of things aren't working - including right clicking on the train list. I'm going to go back to a previous save and see if it does it again. I'll own any Linux induced weirdness, but maybe it's a sim bug?

Medium term, I'm going to dual boot Windows and get all the options back!
Is this the same situation that caused a major re-write of bill_gensheet's Motherwell TT? As I understand it, the core code recently changed and now marks trains as arrived before the full train has reached the relevant TC. One fix is to change the stopping position to FX (not sure if a plain Far End suffices).

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 13/02/2021 at 12:34 by postal
Reason: None given

Log in to reply
Berrima Jn. - 2233 versus BJ84 13/02/2021 at 14:33 #137201
flabberdacks
Avatar
336 posts
Can't say I've ever seen this happen

If you can load an older save and get it to happen each time, would you mind uploading your save here?

Log in to reply
Berrima Jn. - 2233 versus BJ84 13/02/2021 at 23:40 #137214
Sparky
Avatar
83 posts
I just tested the scenario and had the same issue. Mantis report made. Ticket #33032


Post has attachments. Log in to view them.
I intend to live forever. So far so good
Log in to reply
Berrima Jn. - 2233 versus BJ84 14/02/2021 at 00:23 #137215
GeoffM
Avatar
5615 posts
postal in post 137199 said:
As I understand it, the core code recently changed and now marks trains as arrived before the full train has reached the relevant TC.
That's not true.

Sparky in post 137214 said:
I just tested the scenario and had the same issue. Mantis report made. Ticket #33032
It was already reported and fixed, though I can't find the ticket number at first glance. The sim still has some issues outstanding which is why it hasn't been re-released with this fix yet.

SimSig Boss
Log in to reply
The following user said thank you: drew
Berrima Jn. - 2233 versus BJ84 14/02/2021 at 10:29 #137219
postal
Avatar
4687 posts
Online
GeoffM in post 137215 said:
postal in post 137199 said:
As I understand it, the core code recently changed and now marks trains as arrived before the full train has reached the relevant TC.
That's not true.
I stand corrected although there was a core code change that required some TT editing.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
Berrima Jn. - 2233 versus BJ84 14/02/2021 at 11:44 #137224
drew
Avatar
8 posts
Thanks everyone for your help. It sounds like the right people are onto it. Hopefully we'll get a fix at some point.
Log in to reply
Berrima Jn. - 2233 versus BJ84 21/02/2021 at 01:08 #137384
dcp4486
Avatar
5 posts
I have noticed that too with it and 2235.
All I did to get around it when it appeared out of Picton, was set its "next location" in the Timetable edit to signal BJ84 and it worked fine.

Cheers
Dave

Last edited: 21/02/2021 at 01:14 by dcp4486
Reason: None given

Log in to reply
Berrima Jn. - 2233 versus BJ84 03/05/2021 at 16:44 #139274
NorthernWarrior
Avatar
70 posts
It's a while since I ran Moss Vale (about to start a new playthrough if I can drag myself off ETS2 and TSW2), think I might have got round this by using manual shunt forward then stop commands to get the train where it needed to be.
Vern
Log in to reply
Berrima Jn. - 2233 versus BJ84 07/05/2021 at 17:30 #139347
NorthernWarrior
Avatar
70 posts
Okay, little update. 2235 actually worked okay for me but 2233 just stopped at MV11 (cleared) with the back end still over Berrima Jn. I issued an order for the train to shunt forward but dopey driver had already changed direction and promptly started reversing back up the Down Line, towards SN35 rapidly bearing down. Rapid reverse direction order issued, which had to be countermanded as soon as the train was back over Berrima Jn and I set the route onto the branch.

Not very conventional and probably broke about every signalling rule in the book...

So 2233 certainly needs looking at, I've attached a save game which should replicate.

Screenshot of the resulting kerfuffle also attached, for everyone's amusement!

Post has attachments. Log in to view them.
Vern
Last edited: 07/05/2021 at 17:37 by NorthernWarrior
Reason: None given

Log in to reply
Berrima Jn. - 2233 versus BJ84 07/05/2021 at 18:30 #139350
Dionysusnu
Avatar
260 posts
In cases like these, a "set back"/"shunt backwards" command would be nice.
Log in to reply
Berrima Jn. - 2233 versus BJ84 15/05/2021 at 20:37 #139501
NorthernWarrior
Avatar
70 posts
Just to add to my previous findings, I had another (?) 2235 arrive around 2100 time from the Picton direction for the Berrima branch. Now this one did stop short and stand out foul. Currently trying to coax it into the right place with a combination of reversal and shunting instructions, not having much success at present. At times like this it would be useful to have some indication which direction the train is pointing before issuing the instruction or further instructions as I am only assuming the driver has changed ends despite not being able to access the next route. It's also completely and utterly contrary to any established safe working practice to try and jiggle the train in this way.
The schedules probably need amending to bring the train all the way into Moss Vale or round the North Fork and reverse there.

Vern
Log in to reply
Berrima Jn. - 2233 versus BJ84 15/05/2021 at 23:18 #139507
postal
Avatar
4687 posts
Online
NorthernWarrior in post 139501 said:
Just to add to my previous findings, I had another (?) 2235 arrive around 2100 time from the Picton direction for the Berrima branch. Now this one did stop short and stand out foul. Currently trying to coax it into the right place with a combination of reversal and shunting instructions, not having much success at present. At times like this it would be useful to have some indication which direction the train is pointing before issuing the instruction or further instructions as I am only assuming the driver has changed ends despite not being able to access the next route. It's also completely and utterly contrary to any established safe working practice to try and jiggle the train in this way.
The schedules probably need amending to bring the train all the way into Moss Vale or round the North Fork and reverse there.
Would F2 tell you whether the train is facing up or down in this circumstance?

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Log in to reply
Berrima Jn. - 2233 versus BJ84 16/05/2021 at 20:19 #139540
NorthernWarrior
Avatar
70 posts
Not sure, I'll try that next time as, after a bit of a wait the train did eventually move.

One improvement I could suggest so far as the core programme is concerned, is to make it clear when the train is actually moving rather than waiting to reverse. At the moment there seems to be a delay of several minutes before anything happens so maybe there should be two clear stages/messages:
1. Preparing to reverse.
2. Reversing (with the actual speed).

Edit: No F2 doesn't indicate the direction of movement.

Vern
Last edited: 16/05/2021 at 20:21 by NorthernWarrior
Reason: None given

Log in to reply
Berrima Jn. - 2233 versus BJ84 16/05/2021 at 21:36 #139548
clive
Avatar
2357 posts
Online
NorthernWarrior in post 139540 said:

One improvement I could suggest so far as the core programme is concerned, is to make it clear when the train is actually moving rather than waiting to reverse. At the moment there seems to be a delay of several minutes before anything happens
That's the time for the driver to shut down the cab, walk to the other end of the train, and open up the cab.

NorthernWarrior in post 139540 said:

so maybe there should be two clear stages/messages:
1. Preparing to reverse.
2. Reversing (with the actual speed).

Edit: No F2 doesn't indicate the direction of movement.
Um, F2 has a "Dir" column that shows "Up" or "Dn" - that's the direction.

The message "Reversing" means you're in the driver walking stage. If the train is moving, it says "Moving at [speed]".

Log in to reply
The following user said thank you: postal
Berrima Jn. - 2233 versus BJ84 17/05/2021 at 21:27 #139575
NorthernWarrior
Avatar
70 posts
Thanks Clive. Of course in most cases on Moss Vale the reversal will be a messy propelling move, as I believe only the Tahmoor Colliery trains are top and tailed.
Vern
Log in to reply