Derailment out of portals.

[Tony_Howard]

I know this was raised some time ago, probably in an older starter pack. (I am using build 117009) At that time various suggestions were made and the problem seemed to disappear. However just recently I am getting a number of derailments from portals again. It seems to be restricted to certain types of locos. I have found the following to be a problem :-
Southern class 455/8 DTSO MSO TSO rakes <Kuid:45317:102523> etc
SWT Class 455/8 DTSO MSO TSO rakes <kuid:45317:100311> etc
Class 377/1 or 4 DMSO MSO PTSO rakes <kuid2:393563:100549:1> etc

No doubt there are a few more as well.

I seem to remember that one of the solutions was to alter the engine spec in the config file, but I would need guidance on that.

Any help would be appreciated.

Tony Howard

 

[Tony_Howard]

Since I raised the thread above back in 2023, I am still encountering problems with portals. As far as I can see it is when emitting a DMU or EMU then it is the reverse driver car that is causing the problem. I have replaced these with a pared down version (removing nearly all of the engine entries in the config file) but to no avail. People have suggested having no track objects in the train length beyond the portal but this does not work either. All of this is really spoiling my enjoyment as the route I am working on covers the south of England where nearly all trains are EMUs, and I am constantly having to go into "Edit Trains" to remove the derailed carriages.

Can anybody make any more suggestions as not being the current version I doubt if N3V will correct ther mistake.

PS I have tried working with TRS22 but that throws up more problems than it solves.

Tony Howard

 

[JCitron]

Try the long portals and not the short Portal Basic. I have found the longer portals work without issue.

 

[paulper]

I currently use Portal <kuid-25:1264> which is a long one and about 5% fail to emerge. They are either incomplete or they derail within the portal which completely screws up the session. I have had this issue for a couple of years now so it's not exclusive to SP4.

I have reported the bug, but out of those bugs that I did report following SP4 I have heard nothing back on this particular issue.

I haven't quite got round to swapping my portals over yet, so do try Portal Basic and let us know how you get on.

For the 'ghost trains' that do emerge incomplete, I have an invisible junction with the switch's default setting set to take consists into a siding. They obviously derail but use of the 'Clean Up Derailed Trains' rule addresses that. If the consist emerges complete and the driver can read the commands then the switch changes and the driver's rules commence as should be expected.

 

[Christopher824]

It may be possible that some wagons in your consists are below build 3.5, and with the newer script restrictions regarding obsolete functions, could be the cause. I've dug into the -25 Portal scripts, and they all have obsolete functions in them, so adding more obsolete stuff into them could create disaster. Just a thought.