A workaround for static train lights being on?

[Nicolás]

I'm trying to create a three part scenario for the SN route. I have almost everything ready for the first part, but there's a minor issue that's bugging me a bit. Obviously I have some static trains (mostly steeplecabs) placed all over the route, but when I go to test the scenario, most of the time such static trains will have their lights partly on, sometimes entirely off. I say partly because if you look straight at their lights you won't see a corona, but you'll clearly see they are indeed illuminating in front of them. Lone steeplecabs will have both lights on, illuminating in front and back.

I have asked people on Steam if there's a workaround for this, and they advised me to turn the static trains into AI trains with a schedule meant to start way after the scenario is over, but this generates even more trouble with their paths crossing my own. I tried to contact the author of the career scenarios of this route (jbfried) without success. Does anyone know a proper way of handling this?

[ozinoz]

Hi,

If these are just static trains basically as scenery, you should be able to click on the loco, and in the flyout on the right hand side of the screen mark it as dead (ie, just patiently sitting there) This should fix the lights on issue. This is how I would tackle it. Certainly wouldnt create paths etc, as you said, that just causes pathing issues.



Good luck...

[Alpenfreight]

A lot of times this has to do with the engine scripts not being written correctly for engines that aren't currently tasked with something. This is really noticeable on Soldier's Summit where it absolutely kills the FPS any time you enter a yard. Dovetail actually fixed this with the SS GP9 when they released the extension with TS2019, but the SD40T still suffers from this.

https://live.dovetailgames.com/live/tra ... ilable-now

Fixed the “always on” headlights on the GP9 when used as a dead loco or a static consist

As far as I know the only way it can truly be fixed is with the engine scripts being updated. Unfortunately these are encoded and can't really be edited by us.

[Nicolás]

If these are just static trains basically as scenery, you should be able to click on the loco, and in the flyout on the right hand side of the screen mark it as dead (ie, just patiently sitting there) This should fix the lights on issue. This is how I would tackle it. Certainly wouldnt create paths etc, as you said, that just causes pathing issues.

When I click on a locomotive I only have two options, a checkbox for "Broken Engine" and the number selector. I tried to check all static engines as broken, but they still display their lights on when I test the scenario. I'm pretty sure there should be a solution to this, as in jbfried scenarios the static locomotives always have their lights off, as it should be. Maybe this could be related to the test feature of the scenario editor? I haven't tried playing the scenario directly from the Drive tab.