Loose consist lights

[fchrist16]

So through some testing with slipperman, I have found out that ORTS treats separated engines headlights as "on bright" when uncoupled from the main consist.

Is this a bug in ORTS that is yet to be worked out or...?

Regards,

-Frank C.

[slipperman]

Hi,
Further investigation has shown that this does NOT occur when using default MSTS locos in Open Rails and does NOT occur in MSTS when using Frank's selected locos (SD40-2_SNOOT from SLI UP Trainset Vol 1). The problem also occurs in the Player consist in an activity.

This would seem to imply that something within the Lights section of the SLI locos is being mis-interpreted by OR - I'll be carrying out more tests and will report back (unless somebody else has already found the solution!).

Cheers,
Ged

EDIT : Frank - please remove some of your messages - you cannot accept any more PMs!

[fchrist16]

Hi,
Further investigation has shown that this does NOT occur when using default MSTS locos in Open Rails and does NOT occur in MSTS when using Frank's selected locos (SD40-2_SNOOT from SLI UP Trainset Vol 1). The problem also occurs in the Player consist in an activity.

This would seem to imply that something within the Lights section of the SLI locos is being mis-interpreted by OR - I'll be carrying out more tests and will report back (unless somebody else has already found the solution!).

Cheers,
Ged

EDIT : Frank - please remove some of your messages - you cannot accept any more PMs!

Ged,

PMs all cleaned up!

Regards,

-Frank C.

[slipperman]

Hi,
Correction!! Using two of the default SD40-2 locos in a consist, the uncoupled loco's lights are turned on, even when they weren't initially.

My previous tests were with default GP38s, which seem to behave differently, but I've still not found the reason! I wondered if it was caused by different Headlight controller settings, but in all locos, default and SLI, it's the same (Headlights ( 0 0.25 1 0 )).

I'm using Open Rails version X1.3.1-42 under Win 7.

Cheers,
Ged

[slipperman]

Hi (again!),
I have a suspicion that this problem may be caused by Open Rails not using the Headlights controller. Removing this line from the .eng file makes no difference to OR, but in MSTS, prevents the lights from showing at any setting of the "H" key.

Cheers,
Ged

[slipperman]

Hi,
I have now tested with completely different locos - 2 x Class 20s in Mid East Plus route - with the same results. When uncoupled, the second loco assumes the lights equivalent to the Full/Bright setting of its "H" switch, irrespective of its original setting. No "out of service" conditions have been set, so this seems to be a totally incorrect action, and I'll be reporting it as a bug.

Cheers,
Ged

[wwhall]

I believe that OR automatically assumes that an engine in "lead" or "trail" position becomes a potential AI locomotive when it is a loose consist. OR is set up to automatically display headlights on the lead of an AI train--that is the likely reason that the code was written the way that it was. I don't consider that as a "bug," because the programming is doing what the programmer intended. That said, I don't think that loose consist engines should be displaying lights unless it is functioning as a "static AI" train--that is, a non-moving train that is placed to simulate a train waiting on a siding, etc.

Overall, lighting is an area where OR really needs some work. A lot of what is in the program are artifacts from trying to keep rolling stock compatible with MSTS. That gets back to the debate about when or if model builders--freeware or payware--should "cut the cord" with MSTS. My personal opinion is that it's time for that.

[crstagg]

The title of this thread should be "Separated Consists" not "Loose Consists". Loose Consists are defined in ACT files and are treated differently.

What is the Control value for this light in the separated ENG file, if it does have a Control line for that light?
What is the affect if you set (add) the Control condition to 2 for the separated engine?

Control

(n)

0 = Ignore control status 1 = player has no control for the vehicle (f.i. 2nd engine) 2 = player operates vehicle

[slipperman]

Hi Frank,
Carlo has now created a modification to OR to correct this problem. It is to be applied to v1.3.1-42 and may be downloaded from this thread on Elvastower : http://www.elvastower.com/forums/ind...0-loco-lights/

My own limited tests have been successful, but I think it needs more extensive testing by as many users as possible to ensure the unintended errors haven't been introduced.

Cheers,
Ged

[fchrist16]

Thank you Ged, and Charles, most of my Control ( ) lines are set to either 0 or 2, I have been slowly replacing things with 2 with no change.

Regards,

-Frank C.