TS Mullan Pass Expantion Pack

[gammaray84]

Yes Alt + Left click works

Thank you all for you info. Somehow i was not aware of this in Open Rails until today. Thas why i was confused.
About the derail bug, yes i understand why it is on low priority list. I do remember that OR not supporting derailment, but somehow it does?
In the manual it says "MSTS triggers for derailment are currently not managed by OR", but in this case this is ignored? I am guessing couse of this route built for OR?

Anyway, thank you all very much.

[derekmorton]

Ho Rok,

We have not got you there yet.
Its NOT a bug, derail devices exist in the real world.
Shunters/switchmen have to disable them in the real world, I still my key for the Victorian railways Scotch block as they were called.
Get used to them they have been in a route for 16 years.

[PerryPlatypus]

In my opinion there is a bug here, not specific to derails, but rather to the way OR handles running through an improperly-lined switch in general, and the OP's video shows it. I would think that what OR SHOULD consistently do is either stop your train immediately when it hits the improperly lined switch points (similar to when you hit a bumper or end of track), or it should force the switch points over and report that the switch has been damaged. Teleporting the train forward, backwards, sideways onto to another track, or flipping the consist direction entirely (I've experienced all of those) do not seem like viable solutions to me, and are far from prototypical

[derekmorton]

Hi Sean,

Yes, badly worded on my part.

There is a bug in the handling of the derail device.

[R. Steele]

In my opinion there is a bug here, not specific to derails, but rather to the way OR handles running through an improperly-lined switch in general, and the OP's video shows it. I would think that what OR SHOULD consistently do is either stop your train immediately when it hits the improperly lined switch points (similar to when you hit a bumper or end of track), or it should force the switch points over and report that the switch has been damaged. Teleporting the train forward, backwards, sideways onto to another track, or flipping the consist direction entirely (I've experienced all of those) do not seem like viable solutions to me, and are far from prototypical

Exactly. That is what I meant by using the "bug" term in my post. In some older MSTS routes where there is a derail device, the car will roll right through it ( GM&O Springfield Switch as an example )...because it's just a shape file in the route that does not behave like an actual derail...while in the Mullan -- made for OR -- it is an interactive ( is that the correct term? I'm not a route builder )

[ebnertra000]

Exactly. That is what I meant by using the "bug" term in my post. In some older MSTS routes where there is a derail device, the car will roll right through it ( GM&O Springfield Switch as an example )...because it's just a shape file in the route that does not behave like an actual derail...while in the Mullan -- made for OR -- it is an interactive ( is that the correct term? I'm not a route builder )

Derails are usually just switches that are designed to play the part. There's actually no interactive part unless the derail shape is set up as a signal object or something. I think the stands on Mullan are actually part of the track shape, so there are no interactives at all, just a switch that is designed to "derail" a train that runs over it while lined wrong. I myself typically use 0-deg switches, that were initially designed to combat Cutbank syndrome , with a switchstand object placed separately, but there are purpose-built derails in most track types (ScaleRail included).

That said, running through a switch of any type definitely should not result in any warp-factor movements. So I, too, would classify this occurrence as a bug

[geepster775]

In the older versions of Scalerail (Feather River route time frame) the derails were switches with an invisible side spur, so if you ran through them, the response was more like a true split-rail derail where the railcar appeared to veer off into the weeds and stopped when it hit the end of track 'pole' on the invisible diverging route. These derails on Mullan do not seem to operate that way. Is the difference in derail design impacting the OR interpretation of what to do?

[eric]

Yep, invisirail is a wonderful thing...

It's clear on the track monitor that you have a red signal - is it at the derail?

Sent from my SM-G981U using Tapatalk

[PerryPlatypus]

In the older versions of Scalerail (Feather River route time frame) the derails were switches with an invisible side spur, so if you ran through them, the response was more like a true split-rail derail where the railcar appeared to veer off into the weeds and stopped when it hit the end of track 'pole' on the invisible diverging route. These derails on Mullan do not seem to operate that way. Is the difference in derail design impacting the OR interpretation of what to do?

The derails on Mullan are exactly like the ones on Feather River. The reason for the strange anomaly in the OP's video is because the direction his train was traveling was backwards through the derail. At 1:50 you can see the result after OR "teleports" the train so that it lands on the TDB line that the derail leads to (the "path into the weeds" as you call it). The engines are now on this path that veers off to the side.

[eric]

Ah... I thought the snap to the other track on the junction issue had been fixed.

Sent from my SM-G981U using Tapatalk

[gammaray84]

Very interesting i must say.

I am not trying to deny them. In my time playing i did encounter them on the different tracks, but as i remember (might not be correct, did not go check the routes, talking form my head) they were just part of the track, as a not interractive thing. So you just ran over and it was ok.
It was just a visual thing.

I do understand they are real and all over the world. It is safety device been around for long time all over the world.

I did a post on Elvas Tower about this, lets see if it can be fixed. This happenes in all versions of OR.