Changing signal settings - what do I save?

[749006]

On a number of routes a few Signals have incorrect indications because the link from the signal is wrong.

Good example is London to Brighton when the Signal on the Down Main at Redhill shows a Position 1 for Tonbridge even though the train is routed towards Gatwick.
An easy fix but what should I Save in the route folder - it it just the Tracks.bin or do I need to backup something else?

Thanks

Peter

[brysonman46]

The save will change the Tracks.bin file only. Make sure that it is set to Read/Write or the change will not be saved. If the route files are in a .ap archive, then you will need to extract the Tracks.bin file before making changes

[gptech]

Are you wanting to know which file is changed by the edit or which file to backup before editing Peter?

If the route files are in a .ap archive, then you will need to extract the Tracks.bin file before making changes

Not if the edit is done in game, as it'll create a Tracks.bin external to the .ap archive as part of the save routine.

[brysonman46]

Are you wanting to know which file is changed by the edit or which file to backup before editing Peter?

If the route files are in a .ap archive, then you will need to extract the Tracks.bin file before making changes

Not if the edit is done in game, as it'll create a Tracks.bin external to the .ap archive as part of the save routine.

Surely if done in game/scenario, it will generate a ScenarioNetworks.bin file with the change, specific to only that scenario?

[749006]

As the fault would affect any scenario that went past the affected signal(s) then I would do the changes in the main editor rather than a scenario.
I don't intend to replace any of the signals - just fix - if possible the error(s)

I was wondering if the Tracks.bin would then be the only item I need to backup

Peter

[brysonman46]

I was wondering if the Tracks.bin would then be the only item I need to backup

Peter

Yes

[gptech]

Surely if done in game/scenario, it will generate a ScenarioNetworks.bin file with the change, specific to only that scenario?

But you wouldn't edit it at scenario level in game, it'd be in the World Editor. Signals aren't usually "valid in scenarios", it takes an edited .bin file to enable their use as a scenario specific object.

What's the ID number of the signal Peter?

[749006]

The London to Brighton Line has at least two errors

T487 on the Down Main/Through at the South end of the station has a Pos 1 feather for the Tonbridge Line.
https://www.opentraintimes.com/maps/sig ... #T_REDHILL
The links from the Signal are [1] in the Down Main towards Brighton and [2] towards Tonbridge
The Signal indication has 1 in the box next to route [1] instead of [2] - easy to change and I did it sometime back
An update of something restored the Tracks.bin to default

Between Salfords and Horley on the Down Slow signal T229 is missing
Same map as Redhill on the RH side
It should be inline with T227 on the Down Fast and a magnet for it is provided
Again easy to place the missing signal.

But I can not work out how to get the Correct T229 in the Signal ID box - it just picks up the line speed and shows 90 over 90

And I have noticed a number of errors on some RSSLO routes

Peter

[brysonman46]

But I can not work out how to get the Correct T229 in the Signal ID box - it just picks up the line speed and shows 90 over 90

And I have noticed a number of errors on some RSSLO routes

Peter

Whilst in Editor, you can change the signal ID - but it will still show the line speeds. You need to save, go out of game, and then go back in again to see the save

[749006]

But I can not work out how to get the Correct T229 in the Signal ID box - it just picks up the line speed and shows 90 over 90

Whilst in Editor, you can change the signal ID - but it will still show the line speeds. You need to save, go out of game, and then go back in again to see the save

Thanks Nick, learn something new each day

And that would explain whey the RSSLO signal I changed did not show and different indication - I will go back and look at it again

Peter